🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.next.sysadmin
Article #2014

CDROM panics system

#2014
From: james dehnert
Date: Fri, 25 Dec 1992 21:38
109 lines
5732 bytes
  My system is as follows;

  040 Cube
  16 Megs mem
  NeXT CDROM drive
  OD
  FUJITSU M2266S 1.2 gig HD
  
  My problem is this,  every time I attempt to copy something off of a CDROM  
the system panics.  This also happens if I try to read a file from the CDROM,  
as oposed to moving it to the HD then reading it.
  The CD's I have been using are both ISO-9660 format, one from Sun and the  
other is the source code CDROM from Walnut Creek CDROM.  
  And now, a few examples from the message file ;

Dec 24 18:23:44 znext mach: 	Disk is Write Protected
Dec 24 18:23:48 znext mach: CDROM File System: LOADED
Dec 24 18:23:48 znext mach: CDROM File System: Initialized
Dec 24 18:24:19 znext syslogd: going down on signal 15
Dec 24 18:30:57 znext mach: unexpected kernel page fault failure
Dec 24 18:30:57 znext mach: trap: type 0x410 fcode 5 rw 3 faultaddr 0x0
Dec 24 18:30:57 znext mach: trap: pc 0x4002392 sp 0x3ffcf14 sr 0x2000
Dec 24 18:30:57 znext mach: trap: cpu 0 th 0x1010d270 proc 0x10187510 pid 340  
pcb 0x1069000c
Dec 24 18:30:57 znext mach: traceback: fp 0x10690cfc
Dec 24 18:30:57 znext mach: called from pc 040908e2 fp 10690d10 4-args 110f8350  
00000000 00000105 10690d48
Dec 24 18:30:57 znext mach: called from pc 1069d6d0 fp 10690d48 4-args 110f8350  
00000000 00000105 ffffe105
Dec 24 18:30:57 znext mach: called from pc 1069c790 fp 10690e3c 4-args 10690d78  
00000105 040dfb12 10690d74
Dec 24 18:30:57 znext mach: called from pc 04068fcc fp 10690e6c 4-args 10181840  
040dfb12 00000000 10153c5c
Dec 24 18:30:57 znext mach: called from pc 04067218 fp 10690e7c 4-args 040dfb12  
00000000 10690ee0 040635aa
Dec 24 18:30:57 znext mach: called from pc 040635aa fp 10690ee0 4-args 1013e14c  
040dfb12 00000000 00000410
Dec 24 18:30:57 znext mach: called from pc 0409307a fp 10690f68 4-args 101635a0  
000bc000 00000001 00000000
Dec 24 18:30:57 znext mach: called from pc 040020e8 fp 10690f81 4-args 00008410  
00000001 00000001 000bc000
Dec 24 18:30:57 znext mach: last fp 0x10690f81
Dec 24 18:30:57 znext mach: panic: (Cpu 0) MMU invalid descriptor during table  
walk
Dec 24 18:30:57 znext mach: NeXT ROM Monitor 2.2 v63
Dec 24 18:30:57 znext mach: panic: NeXT Mach 3.0: Wed Jul 29 19:43:28 PDT 1992;  
root(rcbuilder):mk-127.15/BUILD/RELEASE_M68K
Dec 24 18:30:57 znext mach: 
Dec 24 18:30:57 znext mach: Killing all processes 
Dec 24 18:30:57 znext mach: continuing
Dec 24 18:30:57 znext mach: unmounting /CDROM ... cfs: cannot unmount; refcnt=1
Dec 24 18:30:57 znext mach: FAILED
Dec 24 18:30:57 znext mach: Root unmount FAILED
Dec 24 18:30:57 znext mach: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 

Dec 24 18:31:57 znext mach: 	Disk is Write Protected
Dec 24 18:32:14 znext mach: CDROM File System: LOADED
Dec 24 18:32:14 znext mach: CDROM File System: Initialized
Dec 24 18:32:42 znext mach: unexpected kernel page fault failure
Dec 24 18:32:42 znext mach: trap: type 0x410 fcode 5 rw 3 faultaddr 0x0
Dec 24 18:32:42 znext mach: trap: pc 0x4002396 sp 0x3fff400 sr 0x2000
Dec 24 18:32:42 znext mach: trap: cpu 0 th 0x10175760 proc 0x10174a20 pid 217  
pcb 0x110f100c
Dec 24 18:32:42 znext mach: traceback: fp 0x110f1b64
Dec 24 18:32:42 znext mach: called from pc 040908e2 fp 110f1b78 4-args 110f81a8  
00000000 00001001 110f1bb0
Dec 24 18:32:42 znext mach: called from pc 110f36d0 fp 110f1bb0 4-args 110f81a8  
00000000 00001001 fffff001
Dec 24 18:32:42 znext mach: called from pc 110f2790 fp 110f1ca4 4-args 110f1be0  
00001001 040e48b2 110f1bdc
Dec 24 18:32:42 znext mach: called from pc 04068fcc fp 110f1cd4 4-args 1018d140  
040e48b2 00000000 10176d00
Dec 24 18:32:42 znext mach: called from pc 04067218 fp 110f1ce4 4-args 040e48b2  
110f1dcc 110f1d48 040635aa
Dec 24 18:32:42 znext mach: called from pc 040635aa fp 110f1d48 4-args 1018ce20  
040e48b2 110f1dcc 110f1dcc
Dec 24 18:32:42 znext mach: called from pc 04092b9e fp 110f1dd0 4-args 10161550  
0004e000 00000001 00000000
Dec 24 18:32:42 znext mach: called from pc 040020e8 fp 110f1de9 4-args 00000410  
00000001 00000001 0004e000
Dec 24 18:32:42 znext mach: last fp 0x110f1de9
Dec 24 18:32:42 znext mach: panic: (Cpu 0) MMU invalid descriptor during table  
walk
Dec 24 18:32:42 znext mach: NeXT ROM Monitor 2.2 v63
Dec 24 18:32:42 znext mach: panic: NeXT Mach 3.0: Wed Jul 29 19:43:28 PDT 1992;  
root(rcbuilder):mk-127.15/BUILD/RELEASE_M68K

Dec 24 18:42:34 znext mach: CDROM File System: LOADED
Dec 24 18:42:34 znext mach: CDROM File System: Initialized
Dec 24 18:45:14 znext mach: unexpected kernel page fault failure
Dec 24 18:45:15 znext syslogd: going down on signal 15
Dec 24 18:51:54 znext mach: Killing all processes 
Dec 24 18:51:54 znext mach: rebooting Mach...

  Any insight would be quite helpfull.

  Thanks,
	Zeke

  P.S. I was running Mamakos' slip, but the problem occurs even if the sysem is  
not booted up with slip.  That is the only real tweaking I have done on the  
system.  I dont have my 3.0 CDROM handy, so I don't know if the same problem  
will occur with that CDROM.

-- 
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
=+   +=   Eschew Obfuscation           Next Mail Welcome  =+   +=
+=   =+   James "Zeke" Dehnert        zeke@znext.cts.com  +=   =+
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
Technical Details
Message-ID: <1992Dec25.213858.745@znext.cts.com>
Path: arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!sdd.hp.com!ncr-sd!crash!znext!zeke

Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.sysadmin
Path: arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!sdd.hp.com!ncr-sd!crash!znext!zeke
From: zeke@znext (james dehnert)
Subject: CDROM panics system
Message-ID: <1992Dec25.213858.745@znext.cts.com>
Sender: zeke@znext.cts.com (james dehnert)
Reply-To: zeke@znext.cts.com
Organization: pnet
Date: Fri, 25 Dec 1992 21:38:58 GMT
Lines: 109