Sparc 10 Random Trap
Matthew Sloan Evans
I have been running a SS10 with 2.5.1, 96 megs of ram, a GX+, and a
SunVideo for a couple months. In that time its never given me any trouble
whatsoever. Just recently it started behaving irreguarly. In particular,
it had a 35 day uptime (it went down since i went out of town for a while
and its my personal workstation) but has crashed 3 times in the last 2 days.
I am beyond bewildered with this one. Looking through my dmesg/syslog/messages
i am finding this stuff. The first time it happened, i was shutting a
netscape window that was trying to run a java applet. shouldn't cause
the machine to die. 2nd time i was doing something else silly in usermode
land but i ca't remember what. 3rd time i did /exec -o prtconf | grep Mem
from ircII. that sure as hell shouldn't cause a machine to die. Anyway,
i know next to nogthing about reading trap logs and things like that and
thats the only info i get. I am running CDE on it and the trap of course
starts and prints some nice stuff on the console, scrolling CDE and friends
off the top of the screen.
showrev -p reports:
> showrev -p
Patch: 103663-01 Obsoletes: Packages: SUNWcsu, SUNWhea
Patch: 103594-03 Obsoletes: , Requires:, 103663-01 Packages: SUNWcsu
Patch: 103630-01 Obsoletes: Packages: SUNWcsu, SUNWcsr
Patch: 103680-01 Obsoletes: , Requires:, 103663-01 Packages: SUNWcsu
Patch: 103683-01 Obsoletes: , Requires:, 103663-01 Packages: SUNWcsu
Patch: 103817-01 Obsoletes: Packages: SUNWcsu
Patch: 103582-01 Obsoletes: Packages: SUNWcsr
Patch: 103743-01 Obsoletes: , Requires:, 103663-01 Packages: SUNWfns
Patch: 103686-01 Obsoletes: , Requires:, 103663-01 Packages: SUNWnisu
i just stuck on the 2.5.1 recommned pack a while ago. no biggie...
and now for some of these dump logs....
---
this is from dmesg after the most recent "death"
---
BAD TRAP: type=9 rp=fc0f47cc addr=56699fa0 mmu_fsr=126 rw=1
modinfo: Data fault
kernel read fault at addr=0x56699fa0, pme=0x0
MMU sfsr=126: Invalid Address on supv data fetch at level 1
pte addr = 0xf5f98d58, level = 1
pid=13245, pc=0xf0084220, sp=0xfc0f4818, psr=0x400000c4, context=39
g1-g7: 0, 20000000, f0091e08, 1, f5ddb9e8, 1, f6069800
Begin traceback... sp = fc0f4818
Called from f0083f4c, fp=fc0f4878, args=56699fa0 f027fa80 f5bdc974 fff2 f5a7cb48 fbec6804
Called from f0101e84, fp=fc0f48d8, args=f5bdc8f8 f027fa80 ffb034c0 1 0 f6069800
Called from f0101974, fp=fc0f4938, args=f5b56760 fc0f49f8 f5a7cbd8 31a8 348 34f0
Called from f010109c, fp=fc0f4998, args=f5b56760 fc0f49f8 1 0 fc0f49f8 4d
Called from f0091e74, fp=fc0f4ba0, args=fc0f4c90 fc0f4c00 ef756a84 0 effff1a4 980
Called from f006d1a0, fp=fc0f4c08, args=2 fc0f4c64 effff1a4 24 f027b140 f5ddb9e8
Called from 10804, fp=effff350, args=1 effff3b4 20f34 10cc0 1 20ec8
End traceback...
panic: Data fault
syncing file systems... [10] 42 [10] 42 [10] 42 [10] 42 [10] 42 [10] 42 [10] 42 [10] 42 [10] 42 [10] 42 [10] 42 [10] 42 [10] 42 [10] 42
[10] 42 [10] 42 [10] 42 [10] 42 [10] 42 [10] 42 done
3245 static and sysmap kernel pages
here is some more dmesg stuff
BAD TRAP: type=9 rp=fc0317bc addr=bfc5470 mmu_fsr=126 rw=1
netstat: Data fault
kernel read fault at addr=0xbfc5470, pme=0x0
MMU sfsr=126: Invalid Address on supv data fetch at level 1
pte addr = 0xf5fc8c2c, level = 1
pid=28231, pc=0xf0084220, sp=0xfc031808, psr=0x400000c1, context=47
g1-g7: 0, 20000000, f00b6d64, 1, f6068a18, 1, f5fb8020
Begin traceback... sp = fc031808
Called from f0083f4c, fp=fc031868, args=bfc5470 fbec6172 f5bdca14 fff2 74 fbec6a8c
Called from f5b041f8, fp=fc0318c8, args=f5bdc998 fbec6172 fbec5f20 0 f0272ed0 252
Called from f5b047c4, fp=fc031970, args=fbec6172 f62ad77f f627e8c0 f6259500 2 fbec5910
Called from f59cc3dc, fp=fc0319d0, args=fc031a38 f5b04e88 f5fc6d58 1 f5b04e80 f5b04744
Called from f00fcbd8, fp=fc031a40, args=0 f6136224 f5ac6738 f61361b0 fc031b44 0
Called from f00b6b70, fp=fc031b98, args=ef6f4d7c 0 1 0 fc031bfc 0
Called from f006d1a0, fp=fc031c08, args=ef6f4d7c 1 0 0 0 0
Called from 113a8, fp=effff2c0, args=ef6f4d7c 0 0 0 26ba4 28398
End traceback...
panic: Data fault
syncing file systems... [8] 39 [8] 39 [8] 39 [8] 39 [8] 39 [8] 39 [8] 39 [8] 39 [8] 39 [8] 39 [8] 39 [8] 39 [8] 39 [8] 39 [8] 39 [8] 39
[8] 39 [8] 39 [8] 39 [8] 39 done
2997 static and sysmap kernel pages
and a litle more...
NFS server megadeth ok
BAD TRAP: type=9 rp=fc0887bc addr=bfc5470 mmu_fsr=126 rw=1
pr ult at addr=0xbfc5470, pme=0x0
MMU sfsr=126: Invalid Address on supv data fetch at level 1
p^A^C\ddr = 0xf5ff8c2c, level = 1
pid=25995, pc=0xf0084220, sp=0xfc088808, psr=0x400000c2, context=47
g1-g^B, 20000000, f00b6d64, 1, f6066488, 1, f60c27e0
Begin traceback... sp = fc088808
Called from f008/platform/sun4m/ufsbootion-10/ufsboot2 f5bdca14 fff2 74 fbec6a8c
Called from f5b041f8, fp=fc0888c8, args=f5bdc998 fbec6172 fbec5f20 0 f0272ed0 252
Called from f5b047c4, fp=fc088970, args=fbec6172 f624277f f62138c0 f61ee500 2 fbec5910
Called from f59cc3dc, fp=fc0889d0, args=fc088a38 f5b04e88 f5b27048 1 f5b04e80 f5b04744
Called from f00fcbd8, fp=fc088a40, args=0 f609b99c f607fec0 f609b928 fc088b44 0
Called from f00b6b70, fp=fc088b98, args=ef7a4d7c 0 1 0 fc088bfc 0
Called from f006d1a0, fp=fc088c08, args=ef7a4d7c 1 ^Afff0f8, args=ef7a4d7c 0 0 0 effff3b8 259a8
End traceback...
pani ^Ams... 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 done
and heres the last thing in my dmesg...
NFS server megadeth not responding still trying
NFS server megadeth ok
that has happened every time the machine has died...it doesn't find the NFS
server on the first try, then finds it on the 2nd. i know the nfs server is
fine and running dandily, its sitting right next to me and its the only other
machine on this ethernet hub. its gotsomething on the order of a 45 day
uptime and the NFS traffic between the two is typically quite heavy and
i have never seen any problems with its NFS.
wierd...
well... at anyrate, its a SS10/51 and up until this i haven't had any problems
with it ever...i have no service contract or anything like that, this is
my personal machine....for anyone that has any ideas on this or would like to
help me out, i' dbe happy to mail you the my /var/adm/messages files if
you want a little better look at whats going on. personally i dont have a
clue what the hell could be wrong. perhaps the kernel images on the hard disk
are mauled up or something, but other then that i have no idea...
prtconf says this, just incase you see anything blaring about my config...
System Configuration: Sun Microsystems sun4m
Memory size: 96 Megabytes
System Peripherals (Software Nodes):
SUNW,SPARCstation-10
packages (driver not attached)
disk-label (driver not attached)
deblocker (driver not attached)
obp-tftp (driver not attached)
options, instance #0
aliases (driver not attached)
openprom (driver not attached)
iommu, instance #0
sbus, instance #0
espdma, instance #0
esp, instance #0
sd (driver not attached)
st (driver not attached)
sd, instance #0 (driver not attached)
sd, instance #1 (driver not attached)
sd, instance #2 (driver not attached)
sd, instance #3
sd, instance #4 (driver not attached)
sd, instance #5 (driver not attached)
sd, instance #6 (driver not attached)
ledma, instance #0
le, instance #0
SUNW,bpp (driver not attached)
SUNW,DBRIe (driver not attached)
mmcodec (driver not attached)
cgsix, instance #0
SUNW,rtvc, instance #0
obio, instance #0
zs, instance #0
zs, instance #1
eeprom (driver not attached)
counter (driver not attached)
interrupt (driver not attached)
SUNW,fdtwo, instance #0
auxio (driver not attached)
power (driver not attached)
memory (driver not attached)
virtual-memory (driver not attached)
eccmemctl (driver not attached)
TI,TMS390Z55 (driver not attached)
pseudo, instance #0
.....
once again, any help with this would be appreciated...
thanks for your time..
--
***********************************************************
* Matt Evans *
* University of Nebraska, Lincoln work: bma...@ntr.net *
* Computer Engineering Major school: mev...@cse.unl.edu *