Thread View: comp.sys.next.sysadmin
3 messages
3 total messages
Started by Hubert B. Hickman
Fri, 06 Nov 1992 07:02
System panic while reading CDROM
Author: Hubert B. Hickman
Date: Fri, 06 Nov 1992 07:02
Date: Fri, 06 Nov 1992 07:02
59 lines
3026 bytes
3026 bytes
Well I seem to have myself an interesting problem. Some time
back I received the NeXT 3rd party demo CDROM. I accessed some
of the demos shortly after I received it and everything seemed
pretty much OK. Note that at this time I was running 2.1 and
had to update the CDROM filesystem as per instructions included
in the CDROM.
Since that time I have upgraded to 3.0. Since our local user
group is holding a meeting on Saturday, I thought it would be
a good idea to show this CDROM at the meeting. So, I take
it out, pop it in the drive and try to navigate around in it.
Well, at about the 4th or fifth directory - BLOOEY - system
panic. This happens consistently every time I try to read the
demo CD. I can read the 3.0 upgrade CD just fine, runs apps of
it, copy things from it, etc. No problems with it.
The only difference that is noticeable from the console is that
the 3rd party demo CD initialized the CDROM filesystem and the
3.0CD does not :
-----
Disk is Write Protected
CDROM File System: LOADED
CDROM File System: Initialized
Nov 6 00:45:08 Workspace: Mounted scsi disk at /Q2_92
Nov 6 00:45:17 Workspace: Unmounted foreign disk at /Q2_92
Disk Label: NeXTSTEP_3.0
Disk Capacity 659MB, Device Block 2048 bytes
Disk is Write Protected
Nov 6 00:45:59 Workspace: Mounted hard disk at /NeXTSTEP_3.0
Nov 6 00:46:40 Workspace: Unmounted hard disk at /NeXTSTEP_3.0
---------------
The system panics all look like the following:
------------ #1
Nov 5 23:22:00 localhost syslog: Workspace logged in
Nov 5 23:22:25 localhost mach: Disk is Write Protected
Nov 5 23:22:28 localhost mach: CDROM File System: LOADED
Nov 5 23:22:28 localhost mach: CDROM File System: Initialized
Nov 5 23:22:42 localhost mach: unexpected kernel page fault failure
Nov 5 23:22:42 localhost mach: trap: type 0x410 fcode 5 rw 3 faultaddr 0x0
Nov 5 23:22:42 localhost mach: trap: pc 0x4002396 sp 0xfff60 sr 0x2000
Nov 5 23:22:42 localhost mach: trap: cpu 0 th 0x10146dcc proc 0x10146910 pid 13
1 pcb 0x10fa600c
Nov 5 23:22:42 localhost mach: traceback: fp 0x10fa6cfc
Nov 5 23:22:42 localhost mach: called from pc 040908e2 fp 10fa6d10 4-args 10fc2
350 00000000 00002000 10fa6d48
{lots of these} .....
Nov 5 23:22:42 localhost mach: last fp 0x10fa6f81
Nov 5 23:22:42 localhost mach: panic: (Cpu 0) MMU invalid descriptor during tab
le walk
-----------
What is going on here? I have had no other system panics on my machine
(in fact this is the first one that I remember) - and machine is an
early slab!
Thanks for any help,
Hubert Hickman
hickman@cse.unl.edu
Re: System panic while reading CDROM
Author: bwild
Date: Fri, 06 Nov 1992 08:23
Date: Fri, 06 Nov 1992 08:23
32 lines
1887 bytes
1887 bytes
In article <1dd5ajINNd7q@crcnis1.unl.edu> hickman@cse.unl.edu (Hubert B. Hickman) writes: .. > Since that time I have upgraded to 3.0. Since our local user > group is holding a meeting on Saturday, I thought it would be > a good idea to show this CDROM at the meeting. So, I take > it out, pop it in the drive and try to navigate around in it. > Well, at about the 4th or fifth directory - BLOOEY - system > panic. This happens consistently every time I try to read the > demo CD. I can read the 3.0 upgrade CD just fine, runs apps of > it, copy things from it, etc. No problems with it. > > The only difference that is noticeable from the console is that > the 3rd party demo CD initialized the CDROM filesystem and the > 3.0CD does not : We had the same effect. Additionally, it was impossible to mount Sun or PC CDs under Workspace Manager. The trick to recover was to copy the directory /usr/filesystems from a machine where we encountered no problems to the machine which crashed on CD access. After that everything works fine! Bernd Wild =============================================== Bernd Wild Forschungszentrum Informatik FZI Dept. Technical Expert Systems and Robotics Haid-und-Neu-Strasse 10-14 D-7500 Karlsruhe GERMANY Tel: +49-721-9654-310 Fax: +49-721-9654-309 email: bwild@fzi.de ===============================================
Re: System panic while reading CDROM
Author: Rob Francis
Date: Fri, 06 Nov 1992 17:09
Date: Fri, 06 Nov 1992 17:09
27 lines
1899 bytes
1899 bytes
In article <1dd5ajINNd7q@crcnis1.unl.edu> hickman@cse.unl.edu (Hubert B. Hickman) writes: >Well I seem to have myself an interesting problem. Some time >back I received the NeXT 3rd party demo CDROM. I accessed some >of the demos shortly after I received it and everything seemed >pretty much OK. Note that at this time I was running 2.1 and >had to update the CDROM filesystem as per instructions included >in the CDROM. > >Since that time I have upgraded to 3.0. Since our local user >group is holding a meeting on Saturday, I thought it would be >a good idea to show this CDROM at the meeting. So, I take >it out, pop it in the drive and try to navigate around in it. >Well, at about the 4th or fifth directory - BLOOEY - system >panic. This happens consistently every time I try to read the >demo CD. I can read the 3.0 upgrade CD just fine, runs apps of >it, copy things from it, etc. No problems with it. I encountered this the day after I upgraded to 3.0. If you recall, there was a script that you had to run when you got the 3rd Party ROM --it altered /usr/filesystems/CDROM.fs and is bogus to 3.0 i.e., it makes 3.0 panic. Just copy /usr/lib/filesystems/CDROM.fs off of the 3.0 CD, and all will be well. -rob ---- Rob Francis Unix Systems Specialist, Indiana University francisr@indiana.edu (812)855-0327
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