Panic after 3.0 upgrade

Thread View: comp.sys.next.sysadmin

2 messages

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

2 total messages Started by Dave Griffiths Fri, 30 Oct 1992 01:09

#39

Author: Dave Griffiths
Date: Fri, 30 Oct 1992 01:09

22 lines
1470 bytes

I've just installed release 3.0 and it panics with the following messages:

Oct 29 16:08:48 localhost mach: unexpected kernel page fault failure
Oct 29 16:08:48 localhost mach: trap: type 0x410 fcode 5 rw 3 faultaddr 0x3fffda0
Oct 29 16:08:48 localhost mach: trap: pc 0x405ea1a sp 0x3fffdcc sr 0x2004
Oct 29 16:08:48 localhost mach: trap: cpu 0 th 0x1013ec34 proc 0x0 pid 0 pcb 0x10fb600c
Oct 29 16:08:48 localhost mach: traceback: fp 0x3fffdd8
Oct 29 16:08:48 localhost mach: last fp 0x3fffdd8
Oct 29 16:08:48 localhost mach: panic: (Cpu 0) MMU invalid descriptor during table walk

The 3.0 installation seemed to work fine. The panic occurs a few seconds
after the "reboot complete" message. The disk I'm using is a brand new
Fujitsu 2624. Prior to the installation, I did a /usr/etc/builddisk on
this new disk. I'm running 2.0 on a 24MB 25MHz Cube. My default boot disk
is still my old 2.0 disk, so to boot from the 3.0 disk I interrupt the
boot and type "bsd -a" and then "sd1" when prompted for the boot disk. The
/etc/fstab has been set up OK. There's 150 MB free on the new disk.

Anyone know what can be causing the panic?

Dave Griffiths

Re: Panic after 3.0 upgrade (solved)

#55

Author: Dave Griffiths
Date: Fri, 30 Oct 1992 18:12

24 lines
1588 bytes

In article <1992Oct30.010919.470@prim> dave@prim.demon.co.uk (Dave Griffiths) writes:
>
>I've just installed release 3.0 and it panics with the following messages:
>
>Oct 29 16:08:48 localhost mach: unexpected kernel page fault failure
>Oct 29 16:08:48 localhost mach: panic: (Cpu 0) MMU invalid descriptor during table walk
>
>The 3.0 installation seemed to work fine. The panic occurs a few seconds
>after the "reboot complete" message. The disk I'm using is a brand new
>Fujitsu 2624. Prior to the installation, I did a /usr/etc/builddisk on
>this new disk. I'm running 2.0 on a 24MB 25MHz Cube. My default boot disk
>is still my old 2.0 disk, so to boot from the 3.0 disk I interrupt the
>boot and type "bsd -a" and then "sd1" when prompted for the boot disk. The
>/etc/fstab has been set up OK. There's 150 MB free on the new disk.
>

OK, I found the problem. It worked fine when I did a "bsd(1,0,0)sdmach
rootdev=sd1", so the problem was related to booting via "bsd -a". Presumably
it's related to using the wrong boot program. Strange that it got so far though.

First impressions of 3.0: cooool. Seems quite fast too. Don't know if this is
the new disk or lack of fragmentation though.

Dave Griffiths

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