From owner-freebsd-current Sat May 23 09:54:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17095 for freebsd-current-outgoing; Sat, 23 May 1998 09:54:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (tc-50.acadiau.ca [131.162.2.150]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17004 for ; Sat, 23 May 1998 09:54:33 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id NAA26739; Sat, 23 May 1998 13:54:18 -0300 (ADT) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sat, 23 May 1998 13:54:18 -0300 (ADT) From: The Hermit Hacker To: Michael Hancock cc: Julian Elischer , freebsd-current@FreeBSD.ORG Subject: Re: May 17th UP machine 'panic' In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 24 May 1998, Michael Hancock wrote: > The panic is saying that proc 26748 is trying to unlock an exclusive lock > owned by proc 1. It doesn't seem to be as you describe. This might not > have anything to do with quotas at all. Is vfs_unmountall() in the trace? Haven't been able to get a coredump yet, due to another problem (see newer email)... I've just upgraded to May22nd -current, and have the kernel installed...someone suggested that: /usr/src/sys/kern/vfs_subr.c:v1.153 might fix it... And, yes, I am using quotas, for those that asked that also... > > Regards, > > > Mike Hancock > > On Sat, 23 May 1998, Julian Elischer wrote: > > > you have quotas right? > > the addition of the locking intot he kernel was done without taking into > > account quotas and when winding up the quota file it locks it and then > > tries to lock and release all open files. > > then when it gets to teh quota file.. > > oops it's already locked.... > > panic .. > > > > I have no fix yet but I see this here and am planning on tracking it down > > this weekend. > > > > > > On Fri, 22 May 1998, The Hermit Hacker wrote: > > > > > > > > On a reboot, I get: > > > > > > syncing disks... 68 51 25 done > > > panic: lockmgr: pid 26748, not exclusive lock holder 1 unlocking > > > > > > When I reported this the first time through, the comment had to do with > > > multiple CPUs...except this is a UP motherboard... > > > > > > Does anyone know why I would be getting this, or if there has been a fix > > > for it in the past 5 days that I haven't clued into on the commit list? > Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message