UNIX for Dummies Questions & Answers

I have a system that upon boot, will declare a bad trap and reboot, whereupon it encounters the same bad trap and reboots in an endless cycle until I stop it. I can get to the ok prompt. An attempt to boot in single user mode left the box completely hung and required a power cycle to re-establish any type of communication.

This box is a piece of equipment used for remote testing of communication lines. I've replaced the CPU with a known good and the problem persists. I'm afraid I need to replace the hard drive.

My question is, would wiping the hard drive clean, reloading the software and reconfiguring the unit possibly fix the problem? Below are logs of the trap and reboot sequence.

Rebooting with command:
Boot device: /iommu/sbus/espdma@5,8400000/esp@5,8800000/sd@0,0 File and args: -r
SunOS Release 5.6 Version Generic_105181-12 [UNIX(R) System V Release 4.0]
Copyright (c) 1983-1997, Sun Microsystems, Inc.
BAD TRAP: type=2 rp=f024342c addr=0 mmu_fsr=0 rw=0
: Illegal instruction
pid=0, pc=0xf59e52ec, sp=0xf0243478, psr=0x4900cc0, context=0
g1-g7: f00f2db0, 0, f596d7bd, f006acd8, 200, 1, f0244020
Begin traceback... sp = f0243478
Called from f59e336c, fp=f02434d8, args=f59a3648 f59a3648 8 0 0 ff00
Called from f009c148, fp=f0243538, args=f59a3648 0 20 0 f592ed58 f70
Called from f00775c0, fp=f0243598, args=f59a3648 0 f59e334c 1 f597be40 f006ae1c
Called from f0077478, fp=f02435f8, args=f59a3648 f59a3648 f59e3c64 f027d5e4 f5974d74 bfc
Called from f0115fd8, fp=f0243658, args=0 f59a3648 1 f59e3c64 3b f5978408
Called from f00f2b48, fp=f02436b8, args=f59783fc f59a3648 f027d5e4 0 f59783fc 0
Called from f00f4458, fp=f0243718, args=f59e3c64 3b f5978410 f5978408 f59783fc 0
Called from f5a6c3e8, fp=f0243898, args=ffffffff 0 ffffffff 4c 3b f59a3788
Called from f0077d94, fp=f02438f8, args=f5aa5000 f025df08 20 f592ebf0 1000 f5ab1000
Called from f5a8f234, fp=f0243968, args=f5aa5000 1 20 f592ebf0 1000 f5ab1000
Called from f5a6c268, fp=f02439d8, args=f028a658 0 f028a658 0 8 c00
Called from f0077d94, fp=f0243a38, args=f027cc9c f025def8 f5a6d584 f028b3a4 f5a6d400 0
Called from f0100888, fp=f0243a98, args=f5ab0000 f028c400 1000 f5911e40 1 0
Called from f00b4740, fp=f0243af8, args=f027cc00 4400ce7 0 44000e7 f0244020 f02798f0
Called from f00411c4, fp=f0243b88, args=f026012c 4400fe0 2000 44000e0 81c52000 f005fa54
Called from 105c5c, fp=0, args=13fc00 145ef0 12b000 f7 14203c 13fe4c
End traceback...
panic: Illegal instruction
rebooting...
Resetting ...

Here is another piece of information from the diag test-all. I'm not sure what this is telling me, but thought it may help someone else help me.

Testing /obio/zs@0,100000
!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~Testing /iommu@0,10000000/sbus@0,10001000/SUNW,CS4231@4,c000000
IAR Error: Actual=1c Expected=1d

Try booting the system into single user off of cdrom. If that blows up too, then it's probably memory (if that cpu is actually good). If it will boot up single user from cdrom, then you can fsck your / partition instead of wiping it out - this may save you some time and fix your problem.

From the errors you are getting, nothing in Sunsolve seems to relate to it. You might want to post the hardware being used.

Also, were any patches recently put on the system? If so, were they done in single user mode?

Thanks for the suggestions. I'll give them a try. The memory passed diags. Patches were not loaded within the past year.