NetBSD Problem Report #9295

Received: (qmail 26321 invoked from network); 25 Jan 2000 22:39:42 -0000
Message-Id: <200001252239.XAA04929@serpens.de>
Date: Tue, 25 Jan 2000 23:39:32 +0100 (MET)
From: "S.P.Zeidler" <spz@serpens.de>
Reply-To: spz@serpens.de
To: gnats-bugs@gnats.netbsd.org
Subject: panic: MMU fault -> unlk    a6
X-Send-Pr-Version: 3.95

>Number:         9295
>Category:       port-amiga
>Synopsis:       panic: MMU fault
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-amiga-maintainer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jan 25 14:42:00 +0000 2000
>Closed-Date:    Mon Oct 16 21:24:23 +0000 2000
>Last-Modified:  Mon Oct 16 21:24:23 +0000 2000
>Originator:     S.P.Zeidler
>Release:        1.4.1
>Organization:
spz@serpens.swb.de (S.P.Zeidler)
>Environment:

System: NetBSD serpens.de 1.4.1 NetBSD 1.4.1 (SERPENS) #6: Sat Oct 23 20:09:54 MEST 1999 spz@serpens.de:/data/src1.4.1/sys/arch/amiga/compile/SERPENS amiga


>Description:

Jan 25 00:05:40 serpens /netbsd: uid 8 on /var/spool/news: file system full
uvm_fault(0x100d64, 0x0, 0, 0x1) -> 0x1
  type 8, code [mmu,,ssw]: 505
trap type 8, code = 505, v = 98
pid = 19590, pc = 000B26BE, ps = 2000, sfc = 1, dfc = 1
Registers:
             0        1        2        3        4        5        6        7
dreg: 00000013 00000001 03EF29CC 00000000 04081EC4 00000000 04081F0C 03EF29CC
areg: 000B26AA 04081E28 00040B40 00000000 03EF29CC 03EF29CC 04081DE0 0DFFDFEC

Kernel stack (04081C90):
081C90: 000ECC96 04081D50 00000080 000ECC30 00000008 00000505 00000098 00000008
081CB0: 04081CFC 000ED00C 00000008 00000505 00000098 04081D50 00000008 00000000
081CD0: 00000000 00000000 00000505 00000098 04182B08 00000000 03EF29CC 03EF29CC
081CF0: 000AF89E 00EA9DB8 00000001 04081D3C 000ED38C 00000008 00000505 00000098
081D10: 04081D50 04182B08 00000000 00000000 03EF29CC 00000000 04081EC4 00000000
081D30: 04081F0C 03EF29CC 00040B40 04081DE0 00002056 00000008 00000505 00000098
081D50: 00000013 00000001 03EF29CC 00000000 04081EC4 00000000 04081F0C 03EF29CC
081D70: 000B26AA 04081E28 00040B40 00000000 03EF29CC 03EF29CC 04081DE0 0DFFDFEC
081D90: 00000000 2000000B 26BE7008 04081DDC 05050005 00050005 00000098 04081DD0
081DB0: 03EF29CC 04081EC4 00040B40 03EF3E84 03EF3E84 03EF29CC 000F8340 03EF29CC
081DD0: 03EF29CC 00040B40 03EF3E84 03EF3E84 04081E5C 000B2D26 04081E28 03EF3E84
081DF0: 00000002 00000000 0001E6A7 080845DA 00000409 03EF29CC 03EF3E84 04182B08
081E10: 03EF29CC 2B1C13A2 00000000 04081E80 03EF3E84 00000000 000F8604 03EF29CC
081E30: 00000000 04081F0C 000F8778 03EF29CC 04081EC4 04081E54 00761B00 00000000
081E50: 03EF3ED0 388CC262 2B1C13A2 04081F30 0004533C 04081E80 00000000 00000080
081E70: 00000008 0DFFDFF0 000F77B4 04182B08 000F866C 03EF29CC 03EF3E84 04081F0C
panic: MMU fault
Stopped in batcher at   _Debugger+0x6:  unlk    a6
db> cu: Got hangup signal

Disconnected.

>How-To-Repeat:
	I have no idea, but this "unlk    a6" has smiled at me before, and
	it may be related to heavy disk activity (but then that's the only thing
	really stressing serpens). No diagnostics from the debugger, sorry;
	I'll get these if it doesn't happen after midnight on a workday.

	I'm not sure if the Cyberstorm PPC (which is a rather ancient model)
	isn't subtly messing things up.
>Fix:
	a diagnosis would be a start .. :-)
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: is 
State-Changed-When: Sun Jan 30 04:07:53 PST 2000 
State-Changed-Why:  
Submitter has been asked to provide symbolic traceback, or take a kernel  
coredump, if this happens again. 
State-Changed-From-To: feedback->closed 
State-Changed-By: is 
State-Changed-When: Mon Oct 16 14:22:46 PDT 2000 
State-Changed-Why:  
Submitter could not reproduce, and upgraded to 1.5ish; asked us to close 
PR. 
>Unformatted:

Home	PR Database Search