SUMMARY: BAD TRAP, Sync Error Reg 80

From: Scott E. Keller (sekell@nicsn1.monsanto.com)
Date: Mon Jan 13 1997 - 15:59:21 CST


Responses were received from:

popp@corpmail.nwest.attws.com (Jeff Popp)
foster@bial1.ucsd.edu (Dave Foster)
Paul Kanz <paul@icx.com>
"Keith G. Weinberg" <kwein@fir.ml.com>

Some questioned proper SIMM location, recent upgrades, etc. But since the
system has been stable and unchanged for a year or so, that's not an issue.
Most indicated hardware, particularly memory.

I removed, cleaned, and replaced the SIMMs after swapping out the box. The
machine then ran fine over the weekend with many high-load processes keeping
it busy. However, when returned to its original enviroment and location,
the behavior returned and the machine would panic at various stages of
booting with errors similar to those below. A replacement motherboard had
already been received, so I replaced it. The machine seems fine, now.

                                                        Scott

Original question:

> System: SPARCstation 2 (4/75), 32 MB memory, Solaris 2.4
> Problem: System crashes and often comes up unstable. Has been behaving
> strangely. Many simple things (like sh) core dump.
>
> Looking through the archives, bad traps usually indicate hardware problems.
> The system passes memory and le0/net tests OK. Kernel checksum matches that
> of identically configured systems.
>
> Any ideas?
>
>
>
> Output from dmesg:
>
> dump on /dev/dsk/c0t1d0s1 size 33136K
> BAD TRAP
> sh: Data fault
> bad kernel read fault at addr=0xade19068
> Sync Error Reg 80<INVALID>
> pid=270, pc=0xf0034a6c, sp=0xf0322c00, psr=0x119000c0, context=12
> g1-g7: 0, 0, f0026494, 3b0, ff3caad8, 1, ff32a120
> Begin traceback... sp = f0322c00
> Called from ff105ba0, fp=f0322c60, args=ff172e40 f0322d38 0 d752d321 2 ade19030
> Called from f0048788, fp=f0322cc8, args=ff172e40 f0322d38 f0322d34 ff156d20 0 ff172e38
> Called from f0036b48, fp=f0322e38, args=f0322edc 0 0 f0322ee4 f0322ee0 ff172e40
> Called from f0026500, fp=f0322ef0, args=f0322fe0 f0322f50 0 0 ff3caad8 ff35eb48
> Called from f00269c4, fp=f0322f58, args=4f7a8 4f6b4 4f6cc 0 f0036a88 ff3caad8
> Called from 16398, fp=effff378, args=4f7a8 4f6b4 400040 4bc00 0 4bc00
> End traceback...
> panic: Data fault
>
>
> Output of /var/adm/messages:
>
> Jan 8 08:14:00 bb300c.monsanto.com unix: BAD TRAP
> Jan 8 08:14:00 bb300c.monsanto.com unix: sh: Data fault
> Jan 8 08:14:00 bb300c.monsanto.com unix: bad kernel read fault at addr=0xade19068
> Jan 8 08:14:00 bb300c.monsanto.com unix: Sync Error Reg 80<INVALID>
> Jan 8 08:14:00 bb300c.monsanto.com unix: pid=270, pc=0xf0034a6c, sp=0xf0322c00, psr=0x119000c0, context=12
> Jan 8 08:14:00 bb300c.monsanto.com unix: g1-g7: 0, 0, f0026494, 3b0, ff3caad8,
> 1, ff32a120
> Jan 8 08:14:00 bb300c.monsanto.com unix: Begin traceback... sp = f0322c00
> Jan 8 08:14:00 bb300c.monsanto.com unix: Called from ff105ba0, fp=f0322c60, args=ff172e40 f0322d38 0 d752d321 2 ade19030
> Jan 8 08:14:00 bb300c.monsanto.com unix: Called from f0048788, fp=f0322cc8, args=ff172e40 f0322d38 f0322d34 ff156d20 0 ff172e38
> Jan 8 08:14:00 bb300c.monsanto.com unix: Called from f0036b48, fp=f0322e38, args=f0322edc 0 0 f0322ee4 f0322ee0 ff172e40
> Jan 8 08:14:00 bb300c.monsanto.com unix: Called from f0026500, fp=f0322ef0, args=f0322fe0 f0322f50 0 0 ff3caad8 ff35eb48
> Jan 8 08:14:00 bb300c.monsanto.com unix: Called from f00269c4, fp=f0322f58, args=4f7a8 4f6b4 4f6cc 0 f0036a88 ff3caad8
> Jan 8 08:14:00 bb300c.monsanto.com unix: Called from 16398, fp=effff378, args=4f7a8 4f6b4 400040 4bc00 0 4bc00
> Jan 8 08:14:00 bb300c.monsanto.com unix: End traceback...
> Jan 8 08:14:00 bb300c.monsanto.com unix: panic: Data fault
 
 -------------------------------------------------------------------------------
     Scott Keller +1 314 537 7545 Monsanto Company - IT Shared Services
                         sekell@turbo.monsanto.com
 -------------------------------------------------------------------------------
 



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:42 CDT