Subject: port-alpha/18983: Alpha crash.
To: None <gnats-bugs@gnats.netbsd.org>
From: None <kpneal@pobox.com>
List: netbsd-bugs
Date: 11/08/2002 19:52:18
>Number: 18983
>Category: port-alpha
>Synopsis: Kernel trap on Alpha at 1.6
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: port-alpha-maintainer
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Nov 08 16:58:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Kevin P. Neal
>Release: NetBSD 1.6
>Organization:
--
Kevin P. Neal http://www.pobox.com/~kpn/
"You know, I think I can hear the machine screaming from here... \
'help me! hellpp meeee!'" - Heather Flanagan, 14:52:23 Wed Jun 10 1998
>Environment:
System: NetBSD tesseract.neutralgood.org 1.6 NetBSD 1.6 (TESSERACT) #35: Mon Oct 28 22:44:20 EST 2002 kpn@neutralgood.org:/local/kernel/compile/TESSERACT alpha
Architecture: alpha
Machine: alpha
>Description:
I got up this morning to find that my AXPpci33 had crashed. From looking
at the dmesg I'd guess that there was some sort of network problem that
blew up NFS (NFS that was mounted through the automounter, even).
I do have a crash dump if it is needed.
From my dmesg:
setclock: 50/11/8/1/57/24
nfs server tome:/local: not responding
nfs server tome:/usr: not responding
nfs server tome:/var: not responding
CPU 0: fatal kernel trap:
CPU 0 trap entry = 0x4 (unaligned access fault)
CPU 0 a0 = 0xdeadbeefdeadbeef
CPU 0 a1 = 0x28
CPU 0 a2 = 0x3
CPU 0 pc = 0xfffffc0000351e20
CPU 0 ra = 0xfffffc0000448f38
CPU 0 pv = 0xfffffc0000351da0
CPU 0 curproc = 0xfffffc00021ecba0
CPU 0 pid = 542, comm = find
panic: trap
syncing disks... tlp0: receive ring overrun
tlp1: receive ring overrun
panic: lockmgr: locking against myself
dumping to dev 8,9 offset 298595
>How-To-Repeat:
I really don't know.
>Fix:
Dunno.
>Release-Note:
>Audit-Trail:
>Unformatted: