SUMMARY: unix: BAD TRAP

From: Daniel Lorenzini (lorenzd@gsdns003.gcm.com)
Date: Thu Aug 12 1999 - 12:20:13 CDT


Greetings,

I got three responses to my question (repeated below) about a BAD TRAP
crash on an Ultra 2. Credits go to:

        Bunny Pfau <bunny@hao.ucar.edu>
        Satinder S Mangat <mangat_satinder@jpmorgan.com>
        Johannes <rjohanne@piper.hamline.edu>

There was no clear concensus. The following possibilities were
mentioned:

Hardware:
        CPU1 bad or overheating
        Bad memory

Software:
        Problem with patch 103640-27
        Program accessing illegal address

Thanks to you all.

Regards,

Dan Lorenzini Greenwich Capital Markets
dal@gcm.com 600 Steamboat Road
203-625-6088 Greenwich, CT 06830
------------------------------------------------------------------------
Original question:
>
> Greetings,
>
> One of our production servers crashed and rebooted yesterday. Here is
> a snip from the messages file:
>
> Aug 8 15:52:54 gsnfs001 unix: BAD TRAP: cpu=1 type=0x30 rp=0x301b18f0 addr=0x1006e000 mmu_fsr=0x11009b
> Aug 8 15:52:54 gsnfs001 unix: sched: data access exception:
> Aug 8 15:52:54 gsnfs001 unix: MMU sfsr=11009b: Privilege Violation on ASI 0x11 E 0 CID 1 PRIV 1 W 0 OW 1 FV 1
> Aug 8 15:52:54 gsnfs001 unix: pid=0, pc=0x1002b5c8, sp=0x0, tstate=0x301b198000000044, context=0x1e04
> Aug 8 15:52:54 gsnfs001 unix: g1-g7: 0, 10446000, 0, 0, 0, 0, 301b1ec0
> Aug 8 15:52:54 gsnfs001 unix: Begin traceback... sp = 301b1980
> Aug 8 15:52:54 gsnfs001 unix: Called from 10025c84, fp=301b19e8, args=301b1b70 301b1a5c 1 1 1006e6e0 0
> Aug 8 15:52:54 gsnfs001 unix: Called from 1001b250, fp=301b1a88, args=301b1b70 0 0 5 1 0
> Aug 8 15:52:55 gsnfs001 unix: Called from 10006a88, fp=301b1b10, args=0 4 0 0 10466660 0
> Aug 8 15:52:55 gsnfs001 unix: Called from c, fp=301b1c00, args=6001ac40 60605000 298 60f24d98 300 300
> Aug 8 15:52:55 gsnfs001 unix: Called from 1006f39c, fp=301b1c60, args=6001ac40 60605000 0 6001acc0 6050c544 0
> Aug 8 15:52:55 gsnfs001 unix: Called from 1007052c, fp=301b1cc0, args=6001ac40 1 0 60605000 6001ad00 6001ad40
> Aug 8 15:52:55 gsnfs001 unix: Called from 100254fc, fp=301b1d20, args=10446000 0 10438434 10438434 60019380 60017fc0
> Aug 8 15:52:55 gsnfs001 unix: Called from 10070378, fp=0, args=0 0 0 0 0 0
> Aug 8 15:52:55 gsnfs001 unix: End traceback...
> Aug 8 15:52:55 gsnfs001 unix: panic[cpu1]/thread=0x301b1ec0: trap
> Aug 8 15:52:55 gsnfs001 unix: syncing file systems... 12 done
> Aug 8 15:52:55 gsnfs001 unix: 3243 static and sysmap kernel pages
> Aug 8 15:52:55 gsnfs001 unix: 137 dynamic kernel data pages
> Aug 8 15:52:55 gsnfs001 unix: 223 kernel-pageable pages
>
> The machine is an Ultra 2 with 2 168Mhz CPUs. It is running Solaris
> 2.5.1 with all recommended and security patches as of June. In
> particular, the kernel patch is 103640-27. It has a largen number of
> SCSI drives configured with disksuite. It is only used as a
> fileserver.
>
> I am assuming that this is a hardware problem. If so, is it possible
> to tell from the above whether the problem lies with the motherboard,
> CPU module(s), or memory? Any insight would be appreciated, obviously,
> as quickly as possible. Thanks.
**********************************************************************
This e-mail is intended only for the addressee named above.
As this e-mail may contain confidential or privileged information,
if you are not the named addressee, you are not authorised to
retain, read, copy or disseminate this message or any part of it.
************************************************************************



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:24 CDT