Panic BAD TRAP errors

UNIX Solaris
1

One of our Sun E450 machines crashed and has this message in the /var/adm/messages after it rebooted automatically. An extract of the log is below. I suspect it is memory, but I am not sure. Can anyone give me any ideas how to diagnose this correctly?

Thanks
Margaret Floyd

Apr 10 08:18:54 upgserver unix: [ID 836849 kern.notice]
Apr 10 08:18:54 upgserver ^Mpanic[cpu3]/thread=30001baba60:
Apr 10 08:18:54 upgserver unix: [ID 799565 kern.notice] BAD TRAP: type=31 rp=2a1
002d7470 addr=2b468050 mmu_fsr=0
Apr 10 08:18:54 upgserver unix: [ID 100000 kern.notice]
Apr 10 08:18:54 upgserver unix: [ID 839527 kern.notice] pageout:
Apr 10 08:18:54 upgserver unix: [ID 520581 kern.notice] trap type = 0x31
Apr 10 08:18:54 upgserver unix: [ID 381800 kern.notice] addr=0x2b468050
Apr 10 08:18:54 upgserver unix: [ID 101969 kern.notice] pid=2, pc=0x7835671c, sp
=0x2a1002d6d11, tstate=0x1180001603, context=0x0
Apr 10 08:18:54 upgserver unix: [ID 743441 kern.notice] g1-g7: 2a1002d77c8, 7000
1e1ef50, 70001e1d510, 2a1002d7688, 8500, 10, 30001baba60
Apr 10 08:18:54 upgserver unix: [ID 100000 kern.notice]
Apr 10 08:18:54 upgserver genunix: [ID 723222 kern.notice] 000002a1002d7190 unix
:die+a4 (31, 2a1002d7470, 2b468050, 0, 16, 60)
Apr 10 08:18:54 upgserver genunix: [ID 179002 kern.notice] %l0-3: 000000000000
0000 000000002b468000 000002a1002d7470 000002a1002d7360
Apr 10 08:18:54 upgserver %l4-7: 0000000000000031 0000000000000001 00000300002
d3b90 0000000000000000
Apr 10 08:18:54 upgserver genunix: [ID 723222 kern.notice] 000002a1002d7270 unix
:trap+8e4 (2a1002d7470, 0, 10000, 10200, 0, 60)
Apr 10 08:18:54 upgserver genunix: [ID 179002 kern.notice] %l0-3: 000000000000
0001 0000000000000000 0000030001baea20 0000000000000031

2

I disagree. Usually (always?) when I've seen panics due to memory the messages point to which memory module is at fault. This output doesn't have any reference to a memory module or location.

I belive Bad Trap errors are due to a software bug, not hardware. In any case, if this server is under support you'll want to call Sun to enter a trouble ticket. If not, check google searching for the specific error info like "trap type 0x31" to see if you get any hits.