NetBSD Problem Report #26407
Received: (qmail 29390 invoked by uid 605); 23 Jul 2004 00:08:46 -0000
Message-Id: <20040722214443.3314A11160@narn.netbsd.org>
Date: Thu, 22 Jul 2004 21:44:43 +0000 (UTC)
From: raeburn@raeburn.org
Sender: gnats-bugs-owner@NetBSD.org
Reply-To: raeburn@raeburn.org
To: gnats-bugs@gnats.NetBSD.org
Subject: panic while updating async mount option
X-Send-Pr-Version: www-1.0
>Number: 26407
>Category: kern
>Synopsis: panic while updating async mount option
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: kern-bug-people
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Jul 23 00:09:00 +0000 2004
>Closed-Date: Wed Nov 28 06:05:44 +0000 2018
>Last-Modified: Wed Nov 28 06:05:44 +0000 2018
>Originator: Ken Raeburn
>Release: 2.0 branch as of several days ago, maybe the 17th
>Organization:
MIT
>Environment:
alpha xp1000, everything rebuilt out of cvs after a 1.6 install; GENERIC kernel config
>Description:
I was running "top", a checkout of pkgsrc, and a build of the perl58-thread package from pkgsrc. Out of curiousity for the difference it would make, I switched the "async" mount option on and off a few times while looking at the "top" output.
The last few lines of the slogin session:
venix# mount -u -o noasync /usr
venix# mount -u -o async /usr
venix# mount -u -o noasync /usr
sync
Since this is over a LAN, I assume from the lack of another prompt that it probably didn't finish the mount and didn't get to the "sync" command.
At this point, the kernel popped into the debugger:
panic: lockmgr: release of unlocked lock!
A traceback, quickly copied from the screen, includes:
panic
lockmgr
genfs_unlock
VOP_UNLOCK+0x3c
sched_sync+0x288
exception_return
I didn't get a crash dump.
>How-To-Repeat:
Repeatedly turn async on and off while doing lots of file system updates?
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback
State-Changed-By: pooka@narn.netbsd.org
State-Changed-When: Sun, 20 Jan 2008 00:23:28 +0200
State-Changed-Why:
seen this in a while?
From: Ken Raeburn <raeburn@raeburn.org>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: kern/26407 (panic while updating async mount option)
Date: Sat, 19 Jan 2008 17:30:53 -0500
On Jan 19, 2008, at 17:23, pooka@NetBSD.org wrote:
> seen this in a while?
No, but I've avoided doing such things since then.
From: Antti Kantee <pooka@cs.hut.fi>
To: gnats-bugs@NetBSD.org, raeburn@raeburn.org
Cc:
Subject: Re: kern/26407 (panic while updating async mount option)
Date: Sun, 20 Jan 2008 04:30:43 +0200
On Sat Jan 19 2008 at 23:20:07 +0000, Ken Raeburn wrote:
> The following reply was made to PR kern/26407; it has been noted by GNATS.
>
> From: Ken Raeburn <raeburn@raeburn.org>
> To: gnats-bugs@NetBSD.org
> Cc:
> Subject: Re: kern/26407 (panic while updating async mount option)
> Date: Sat, 19 Jan 2008 17:30:53 -0500
>
> On Jan 19, 2008, at 17:23, pooka@NetBSD.org wrote:
> > seen this in a while?
>
> No, but I've avoided doing such things since then.
If you have a machine you can affort to crash, could you see if it's
still repeatable?
--
Antti Kantee <pooka@iki.fi> Of course he runs NetBSD
http://www.iki.fi/pooka/ http://www.NetBSD.org/
"la qualité la plus indispensable du cuisinier est l'exactitude"
State-Changed-From-To: feedback->open
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Mon, 23 Dec 2013 22:32:39 +0000
State-Changed-Why:
Feedback timeout (close on six years...)
All this needs is for someone to try reproducing it, which anyone can do
if they have a crash machine available, or a crashable vm.
State-Changed-From-To: open->closed
State-Changed-By: maya@NetBSD.org
State-Changed-When: Wed, 28 Nov 2018 06:05:44 +0000
State-Changed-Why:
It called for someone with a crash machine, that's all my machines. Anyway, can't reproduce this issue. It did get fixed in the end.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.43 2018/01/16 07:36:43 maya Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2017
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.