BAD TRAP crashes..

[Chris Elvin]

In article <6557 at brazos.Rice.edu> karim at oak.uncwil.edu (Omar A. Karim) writes:
>X-Sun-Spots-Digest: Volume 9, Issue 119, message 1
>
>My SUN 4/110 running 4.0.1 crashes about once a day with the included
>messaages.  SUN claims it is probably a corrupted swap partition and that
>I should re-format the disk. I will do this if it will fix the problem,
[deleted]

>Apr  7 16:02:00 oak vmunix: screenblank: Data fault
>Apr  7 16:02:00 oak vmunix: kernel write fault at addr=0x9001e3, pme=0x70000060
>Apr  7 16:02:00 oak vmunix: Bus Error Reg 80<INVALID>
>Apr  7 16:02:00 oak vmunix: pid=100, pc=0xf807fddc, sp=0xffffe9b0, psr=0xc2, context=3
>Apr  7 16:02:00 oak vmunix: g1-g7: 0, 9000e3, ffffffff, 0, 0, 0, 0
>Apr  7 16:02:00 oak vmunix: Begin traceback... sp = ffffe9b0
>Apr  7 16:02:00 oak vmunix: Called from f8021788, fp=ffffea10, args=58 ff04fc90 ff11aa44 1c 38 9001e3
[deleted]

I had a similar problem with a SUN 4/330, sunos 4.0.3, 2*327MB scsi disks
(All SUN supplied)

I was changing the root and boot device from sd6 (default) to sd2.  I
formatted and partitioned sd2 OK and used dump and restore to transfer the
partitions across by mounting each new partition temporarily.  I installed
the boot block and changed the eeprom without trouble.  When I booted
(from sd2) the boot failed after fsck'ing / and /usr  and I had a similar
sort of trace output.

Looking at the messages produced when booting, it became clear that in
/etc/fstab, I had forgotten to change the references of sd6 to sd2 so that
although I was booting from sd2, my root and /usr were on sd6.  Does SUNOS
insist on the swap partition being on the same device as boot or root.
Booting on sd2 and changing /etc/fstab on sd6 cured the problem

Chris Elvin
C.Elvin at EE.Surrey.Ac.UK
Dept of Elec. Eng, University of Surrey, Guildford, Surrey, GU2 5XH. England