Printing from clean install of 3.0 causes System Panic (3 times)

Thread View: comp.sys.next.sysadmin

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Brian Willoughby Fri, 02 Oct 1992 18:25

#1712

Author: Brian Willoughby
Date: Fri, 02 Oct 1992 18:25

35 lines
1986 bytes

I did a clean install of 3.0 (Hyper3B) after reformatting my NeXTdimension's  
400M NeXT drive for 1024 byte blocks.

I have tried printing on three occasions, and the system panicked each time.   
Here are the relevant excerpts from /usr/adm/messages (note the large gap  
between the previous message and each panic, showing that nothing else was  
interacting):

- 1 -
Sep 28 08:49:26 sounds syslog: Workspace logged in
Sep 28 15:58:11 sounds mach: panic: (Cpu 0) No more room in kernel map
- 2 -
Sep 28 23:21:28 sounds mach: 	Disk Label: disk.1
Sep 28 23:21:28 sounds mach: 	Disk Capacity 1440 KB, Device Block 512 bytes
Sep 28 23:58:09 sounds mach: panic: (Cpu 0) No more room in kernel map
- 3 -
Sep 29 09:33:41 sounds WindowServer[192]: IPCFlushOutput: failed to flush  
output for stream 0x211524.
Sep 29 09:39:05 sounds mach: panic: (Cpu 0) No more room in kernel map

The first time I printing from NewsGrazer, the second from 3.0's Edit, and the  
third from 2.1's WriteNow.

I have 28MB System and 20M dimension memory and I am running UUCP with  
Mamakos's SLIP.

I just got the Printer Test page to print today after using PrintManager.app  
for the first time since I loaded 3.0 - I'll give printing another trial run,  
but I wanted to get this post out before I take a chance on panicking my  
machine again.
-- 
Brian Willoughby	Software Design Engineer, BSEE NCSU
BrianW@SoundS.WA.com	Sound Signal Processing Software and Consulting
NeXTmail welcome	- NO EMAIL SOLICITATION without prior permission

Re: Printing from clean install of 3.0 causes System Panic (3 times)

#1723

Author: Brian Willoughby
Date: Sat, 03 Oct 1992 07:13

21 lines
1530 bytes

Brian Willoughby writes
| I have tried printing on three occasions, and the system panicked each time.   
| 
| Sep 28 15:58:11 sounds mach: panic: (Cpu 0) No more room in kernel map
| Sep 28 23:58:09 sounds mach: panic: (Cpu 0) No more room in kernel map
| Sep 29 09:39:05 sounds mach: panic: (Cpu 0) No more room in kernel map

I can print now.

My best guess is that my problem may have been due to the fact that I installed  
3.0 without my printer connected (I had moved the machine), and I had never run  
PrintManager.app before I tried printing these three times.  There must be some  
magick in PrintManager, because once I called it up and printed a test page,  
everything seems to be OK.

If my job were testing 3.0, I would attempt to install 3.0 without a printer  
and then try printing without using PrintManager - but that's not my job :-)
-- 
Brian Willoughby	Software Design Engineer, BSEE NCSU
BrianW@SoundS.WA.com	Sound Signal Processing Software and Consulting
NeXTmail welcome	- NO EMAIL SOLICITATION without prior permission

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads