SunFire V440, 5.9, 4xcpu: panic[cpu2] BAD TRAP type=3 due to a NULL pointer reference ?

From: Tony Magtalas (ttk67@yahoo.com)
Date: Tue Mar 21 2006 - 17:11:00 EST


Dear Managers:

My V440 server crashed a few days ago and crashed
again yesterday, with the following error message:

Mar 17 20:26:06 myserver
^Mpanic[cpu2]/thread=2a10053dd40:
Mar 17 20:26:06 myserver unix: [ID 340138 kern.notice]
BAD TRAP: type=3
1 rp=1438090 addr=10 mmu_fsr=0 occurred in module
"genunix" due to a NULL pointer dereference
Mar 17 20:26:36 myserver
^Mpanic[cpu2]/thread=2a10053dd40:
Mar 17 20:26:36 myserver unix: [ID 715357 kern.notice]
panic sync timeout
Mar 20 16:20:23 myserver savecore: [ID 570001
auth.error] reboot after panic: [AFT1] errID
0x00322ef8.d37d3084 UE CE EDU FRU WDU FRC Error(s)
Mar 20 16:19:24 myserver lpfc: [ID 685918 kern.notice]
NOTICE: lpfc1: Acquired FCP/SCSI Target 81 LUN 7

#./prtdiag -v|more
System Configuration: Sun Microsystems sun4u Sun Fire
V440
System clock frequency: 177 MHZ
Memory size: 8GB

==================================== CPUs
====================================
               E$ CPU CPU
 Temperature
CPU Freq Size Implementation Mask
 Die Amb. Status
Location
--- -------- ---------- ------------------- -----
 ---- ---- ------
--------
  0 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4
   - - online
  -
  1 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4
   - - online
  -
  2 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4
   - - online
  -
  3 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4
   - - online
  -

It is a SunFire V440 with 4x1593 Mhz CPU and 8 GB of
memory running Oracle & Solaris 5.9:

# uname -a
SunOS myserver 5.9 Generic_118558-04 sun4u sparc
SUNW,Sun-Fire-V440

I reported this problem to Sun. After reviewing the
core dumps, they said they can't find any problem with
the server (we have a Sun platinum support contract).
They said the server just had a "hiccup" for no
determined reason; and suggested that we bring down
the server and run extended POST a couple of times to
test for any hardware problem, which is a no-no,
because this is one of our critical production Oracle
servers.

Has anybody seen this error message before? What is my
next course of actions? (with Sun).

Thanks,
TM
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:39:21 EDT