NetBSD Problem Report #40549

From www@NetBSD.org  Tue Feb  3 16:57:53 2009
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by narn.NetBSD.org (Postfix) with ESMTP id C567C63C07D
	for <gnats-bugs@gnats.netbsd.org>; Tue,  3 Feb 2009 16:57:52 +0000 (UTC)
Message-Id: <20090203165752.8FAE463B879@narn.NetBSD.org>
Date: Tue,  3 Feb 2009 16:57:52 +0000 (UTC)
From: raymond.meyer@rambler.ru
Reply-To: raymond.meyer@rambler.ru
To: gnats-bugs@NetBSD.org
Subject: Reader / writer lock error: rw_vector_enter: locking against myself
X-Send-Pr-Version: www-1.0

>Number:         40549
>Category:       kern
>Synopsis:       Reader / writer lock error: rw_vector_enter: locking against myself
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Feb 03 17:00:00 +0000 2009
>Closed-Date:    Sun Apr 30 00:54:55 +0000 2023
>Last-Modified:  Sun May 07 06:35:01 +0000 2023
>Originator:     RM
>Release:        
>Organization:
>Environment:
NetBSD ultra10 5.0_BETA NetBSD 5.0_BETA (GENERIC) #0: Sat Jan 24 11:11:56 PST 2009  builds@wb31:/home/builds/ab/netbsd-5/sparc64/200901240002Z-obj/home/builds/ab/netbsd-5/src/sys/arch/sparc64/compile/GENERIC sparc64
>Description:
I can reproduce this panic if I:

mount /proc filesystem
try to build sysutils/xfce4-diskperf-plugin package from pkgsrc

With the /proc filesystem unmounted, the panic does not occur.

$ uname -a
NetBSD ultra10 5.0_BETA NetBSD 5.0_BETA (GENERIC) #0: Sat Jan 24 11:11:56 PST 2009  builds@wb31:/home/builds/ab/netbsd-5/sparc64/200901240002Z-obj/home/builds/ab/netbsd-5/src/sys/arch/sparc64/compile/GENERIC sparc64

Below are the details captured via ssh and serial console:

===> Configuring for xfce4-diskperf-plugin-2.1.0
=> Modifying GNU configure scripts to avoid --recheck
=> Replacing config-guess with pkgsrc versions
=> Replacing config-sub with pkgsrc versions
=> Replacing install-sh with pkgsrc version
=> Fixing locale directory references.
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking build system type... sparc64-unknown-netbsd5.0.
checking host system type... sparc64--netbsd
checking target system type... sparc64--netbsd
checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... /usr/bin/awk
checking whether make sets $(MAKE)... yes
checking for sparc64--netbsd-strip... no
checking for strip... strip
checking how to create a ustar tar archive... 

Reader / writer lock error: rw_vector_enter: locking against myself

lock address : 0x000000000f234878
current cpu  :                  0
current lwp  : 0x000000000d8140c0
owner/count  : 0x000000000d8140c0 flags    : 0x0000000000000004

panic: lock error
Stopped in pid 1660.1 (gtar) at netbsd:cpu_Debugger+0x4:        nop
db> bt

lockdebug_abort(f234878, 181be40, 14f1148, 16506b8, 0, 1) at netbsd:lockdebug_ab
ort+0x24
rw_vector_enter(f234878, 1, 0, 1, 0, e9331b8) at netbsd:rw_vector_enter+0x130
vlockmgr(f234878, 2, 0, a, 0, 0) at netbsd:vlockmgr+0x110
VOP_LOCK(f234640, 2, 0, 1, 0, e930000) at netbsd:VOP_LOCK+0x58
vn_lock(f234640, 20002, 2, 2, 4, d80e8c0) at netbsd:vn_lock+0x84
getcwd_common(f234640, d920140, e933718, 3384000, 200, 0) at netbsd:getcwd_commo
n+0x3c
procfs_readlink(16, 2, 2, 10, 0, 0) at netbsd:procfs_readlink+0x35c
layer_bypass(e933920, e933b50, e933b78, ffffffffffff88f8, 1, 2f) at netbsd:layer
_bypass+0xc8
VOP_READLINK(f2343e0, e933a10, d6b7980, 0, 0, 1) at netbsd:VOP_READLINK+0x5c
namei(0, ffffffffffff9aa5, e933b78, e933b28, 4, ffffffffffff9aa3) at netbsd:name
i+0x1bc
do_sys_stat(ffffffffffff9a93, 54, e933c78, 0, 0, 0) at netbsd:do_sys_stat+0x20
sys___stat30(d8140c0, e933dc0, e933e00, fefefefefefefeff, ffffffffffffffff, 1818
be8) at netbsd:sys___stat30+0x10
syscall_plain(e933ed0, 2, 4073ef34, 4073ef38, 0, e933dc0) at netbsd:syscall_plai
n+0x138
?(ffffffffffff9a93, ffffffffffff9a08, 4, 13ef80, 0, 40a00098) at 0x1008c68
>How-To-Repeat:

>Fix:

>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->feedback
State-Changed-By: snj@NetBSD.org
State-Changed-When: Wed, 01 Apr 2009 23:45:07 +0000
State-Changed-Why:
I believe this has been fixed.  Can you still reproduce it with
the latest netbsd-5? (RC3 proper should do).


From: raymond.meyer@rambler.ru
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/40549 (Reader / writer lock error: rw_vector_enter:
 locking against myself)
Date: Sun, 5 Apr 2009 20:08:30 +0100

 It dosn't look like it has been fixed, I can still reproduce it with
 netbsd-5 RC3 kernel.

State-Changed-From-To: feedback->open
State-Changed-By: snj@NetBSD.org
State-Changed-When: Sun, 05 Apr 2009 19:39:23 +0000
State-Changed-Why:
Not fixed.


From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/40549 locking against myself with gtar on procfs
Date: Mon, 25 Jan 2010 15:33:17 +0100

 Could you please check the configure script and find out how it invokes
 gtar?

 A simple gtar command line to reproduce the problem would be very helpfull.

 Thanks,

 Martin

State-Changed-From-To: open->closed
State-Changed-By: gutteridge@NetBSD.org
State-Changed-When: Sun, 30 Apr 2023 00:54:55 +0000
State-Changed-Why:
Stale bug report, not reproducible for me, closing.

From: "David H. Gutteridge" <david@gutteridge.ca>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/40549 (Reader / writer lock error: rw_vector_enter: locking
 against myself)
Date: Sat, 29 Apr 2023 20:57:44 -0400

 On 2023-04-29 20:54, gutteridge@NetBSD.org wrote:
 > Stale bug report, not reproducible for me, closing.

 This is against sparc64, and seems could be hardware-specific, however
 a request for further information was sent 13 years ago, with no reply.

From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/40549 (Reader / writer lock error: rw_vector_enter: locking
 against myself)
Date: Sun, 7 May 2023 06:32:44 +0000

 On Sun, Apr 30, 2023 at 01:00:04AM +0000, David H. Gutteridge wrote:
  >  > Stale bug report, not reproducible for me, closing.
  >  
  >  This is against sparc64, and seems could be hardware-specific, however
  >  a request for further information was sent 13 years ago, with no reply.

 Not likely given that it was in vnode locking. Also, any problem in
 vnode locking back then is going to be different now if not already
 fixed.

 although the presence of layer_bypass in the trace is making me wonder
 what the original setup actually was...

 -- 
 David A. Holland
 dholland@netbsd.org

>Unformatted:

Home	PR Database Search