Date: Tue, 31 Jul 2001 08:45:19 -0700 (PDT) From: John Baldwin <jhb@FreeBSD.org> To: Vincent Poy <vince@oahu.WURLDLINK.NET> Cc: current@FreeBSD.org, Kris Kennaway <kris@obsecurity.org>, Sheldon Hearn <sheldonh@starjuice.net> Subject: Re: -current lockups Message-ID: <XFMail.010731084519.jhb@FreeBSD.org> In-Reply-To: <20010730222040.Y87252-100000@oahu.WURLDLINK.NET>
next in thread | previous in thread | raw e-mail | index | archive | help
On 31-Jul-01 Vincent Poy wrote: > On Mon, 30 Jul 2001, John Baldwin wrote: > >> On 30-Jul-01 Sheldon Hearn wrote: >> > >> > >> > On Mon, 30 Jul 2001 07:38:47 MST, "David O'Brien" wrote: >> > >> >> However, those boxes were panicing often before I made that statement. >> >> So I still believe current is now in better shape than it was in June. >> > >> > I'll be a lot happier when I can enabled DDB_UNATTENDED and do whatever >> > it is that causes my panic of the day and actually get a crashdump >> > instead of >> > >> > panic: witness_restore: lock (sleep mutex) Giant not locked >> >> This is a different one. Is this during the dump itself? That I can try to >> work on. (Basically, I need to make witness just stop doing all of its >> various >> checks if panicstr != NULL). > > I'm getting the following lock order reversal for any -current > since July 19, 2001 including today and it just hangs solid after this, no > db> prompt or anything... It only happens after passwd or chpass > successfully rebuilds the database, vipw works fine. > > root@pele [9:29pm][/usr/temp] >> > Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal > Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal > Jul 28 21:29:40 pele /boot/kernel/kernel: 1st 0xd92fea9c process lock @ > /usr/src/sys/vm/vm_glue.c:469 > Jul 28 21:29:40 pele /boot/kernel/kernel: 1st 0xd92fea9c process lock @ > /usr/src/sys/vm/vm_glue.c:469 > Jul 28 21:29:40 pele /boot/kernel/kernel: 2nd 0xc118dfb0 lockmgr interlock > @ /usr/src/sys/kern/kern_lock.c:239 > Jul 28 21:29:40 pele /boot/kernel/kernel: 2nd 0xc118dfb0 lockmgr interlock > @ /usr/src/sys/kern/kern_lock.c:239 This is due to the way that lockmgr locks are implemented unfortunately, and will be fixed when vm maps switch to sx locks instead of lockmgr locks. -- John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.010731084519.jhb>