NetBSD Problem Report #9263
Received: (qmail 9389 invoked from network); 20 Jan 2000 20:12:16 -0000
Message-Id: <200001202011.VAA05052@lyssa.zhadum.de>
Date: Thu, 20 Jan 2000 21:11:57 +0100 (CET)
From: Matthias Scheler <tron@lyssa.zhadum.de>
Reply-To: tron@lyssa.zhadum.de
To: gnats-bugs@gnats.netbsd.org
Subject: random kernel panics due to locking problems
X-Send-Pr-Version: 3.95
>Number: 9263
>Category: kern
>Synopsis: random kernel panics due to locking problems
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: thorpej
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Jan 20 14:30:00 +0000 2000
>Closed-Date: Mon Jan 24 22:02:21 +0000 2000
>Last-Modified: Mon Jan 24 22:02:34 +0000 2000
>Originator: Matthias Scheler
>Release: 2000/01/20
>Organization:
Matthias Scheler http://www.sighardstrasse.de/~tron/
>Environment:
System: NetBSD lyssa.zhadum.de 1.4P NetBSD 1.4P (LYSSA) #0: Thu Jan 20 14:22:24 CET 2000 tron@lyssa.zhadum.de:/src/sys/compile/LYSSA i386
>Description:
For about a week my current i386 system is panicing on random occasions.
Because it always happened when X11 was running I couldn't see DDB output
and thus wasn't able to get a crash dump until I switched DDB off.
Afterwars I got a crash dump with this trace back:
(gdb) target kcore netbsd.0.core
panic: lockmgr: processor %lu, not exclusive lock holder %lu unlocking
#0 0xf02ec620 in deflate_window_in ()
(gdb) where
#0 0xf02ec620 in deflate_window_in ()
#1 0x5768000 in ?? ()
#2 0xf026ad53 in cpu_reboot ()
#3 0xf01b4f31 in panic ()
#4 0xf01a8cda in lockmgr ()
#5 0xf01aa30c in proclist_unlock_write ()
#6 0xf01a64ff in sys_wait4 ()
#7 0xf0270f79 in syscall ()
#8 0xf0100d65 in syscall1 ()
can not access 0xefbfd120, invalid translation (invalid PDE)
can not access 0xefbfd120, invalid translation (invalid PDE)
Cannot access memory at address 0xefbfd120.
Obviously a lock which wasn't locked is unlocked somewhere.
>How-To-Repeat:
I can't exactly repeat it but it always happend when X11 (XFree86 3.3.6
compiled from our X11 sources) was running.
>Fix:
Sorry, I don't know.
>Release-Note:
>Audit-Trail:
From: Assar Westerlund <assar@sics.se>
To: tron@lyssa.zhadum.de
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/9263: random kernel panics due to locking problems
Date: 21 Jan 2000 10:06:13 +0100
Matthias Scheler <tron@lyssa.zhadum.de> writes:
> (gdb) target kcore netbsd.0.core
> panic: lockmgr: processor %lu, not exclusive lock holder %lu unlocking
> #0 0xf02ec620 in deflate_window_in ()
> (gdb) where
> #0 0xf02ec620 in deflate_window_in ()
> #1 0x5768000 in ?? ()
> #2 0xf026ad53 in cpu_reboot ()
> #3 0xf01b4f31 in panic ()
> #4 0xf01a8cda in lockmgr ()
> #5 0xf01aa30c in proclist_unlock_write ()
> #6 0xf01a64ff in sys_wait4 ()
> #7 0xf0270f79 in syscall ()
> #8 0xf0100d65 in syscall1 ()
> can not access 0xefbfd120, invalid translation (invalid PDE)
> can not access 0xefbfd120, invalid translation (invalid PDE)
> Cannot access memory at address 0xefbfd120.
>
> Obviously a lock which wasn't locked is unlocked somewhere.
Can you try reverting to kern_proc.c:1.35 and see if you still
experience this problem?
/assar
From: Matthias Scheler <tron@zhadum.de>
To: gnats-bugs@gnats.netbsd.org, kern-bug-people@netbsd.org
Cc: "Jason R. Thorpe" <thorpej@nas.nasa.gov>, Assar Westerlund <assar@sics.se>
Subject: Re: kern/9263: random kernel panics due to locking problems
Date: Sat, 22 Jan 2000 12:17:02 +0100
On Thu, Jan 20, 2000 at 10:30:01PM -0000, gnats-bugs@gnats.netbsd.org wrote:
> Thank you very much for your problem report.
> It has the internal identification `kern/9263'.
> The individual assigned to look at your
> bug is: kern-bug-people (Kernel Bug People).
>
> >Category: kern
> >Responsible: kern-bug-people
> >Synopsis: random kernel panics due to locking problems
> >Arrival-Date: Thu Jan 20 14:30:00 2000
On a hint by Assar Westerlund by compiled a kernel with version 1.35
of "syssrc/sys/kern/kern_proc.c" and the problem seems to be solved.
--
Matthias Scheler http://www.sighardstrasse.de/~tron/
From: Assar Westerlund <assar@sics.se>
To: Matthias Scheler <tron@zhadum.de>
Cc: gnats-bugs@gnats.netbsd.org, kern-bug-people@netbsd.org,
"Jason R. Thorpe" <thorpej@nas.nasa.gov>
Subject: Re: kern/9263: random kernel panics due to locking problems
Date: 22 Jan 2000 16:28:03 +0100
Matthias Scheler <tron@zhadum.de> writes:
> On a hint by Assar Westerlund by compiled a kernel with version 1.35
> of "syssrc/sys/kern/kern_proc.c" and the problem seems to be solved.
Yeah, that was the first suspect when I had crashes in that area. And
it seemed to cure the problem for me too. I haven't searched for
places where the proclist might be modified at a relevant spl. Jason,
any ideas?
/assar
State-Changed-From-To: open->feedback
State-Changed-By: thorpej
State-Changed-When: Sat Jan 22 08:34:40 PST 2000
State-Changed-Why:
Please update to rev 1.37 of kern_proc.c; this should fix the problem.
Responsible-Changed-From-To: kern-bug-people->thorpej
Responsible-Changed-By: thorpej
Responsible-Changed-When: Sat Jan 22 08:34:40 PST 2000
Responsible-Changed-Why:
Bug was my fault.
From: Jason Thorpe <thorpej@nas.nasa.gov>
To: Assar Westerlund <assar@sics.se>
Cc: Matthias Scheler <tron@zhadum.de>, gnats-bugs@gnats.netbsd.org,
kern-bug-people@netbsd.org
Subject: Re: kern/9263: random kernel panics due to locking problems
Date: Sat, 22 Jan 2000 09:09:46 -0800
On 22 Jan 2000 16:28:03 +0100
Assar Westerlund <assar@sics.se> wrote:
> Yeah, that was the first suspect when I had crashes in that area. And
> it seemed to cure the problem for me too. I haven't searched for
> places where the proclist might be modified at a relevant spl. Jason,
> any ideas?
Yes, I was being bone-headed :-) Bug is fixed now.
-- Jason R. Thorpe <thorpej@nas.nasa.gov>
State-Changed-From-To: feedback->closed
State-Changed-By: thorpej
State-Changed-When: Mon Jan 24 14:02:21 PST 2000
State-Changed-Why:
Bug is fixed.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.