From owner-freebsd-current Mon Jun 28 23:13:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 39B8414C87 for ; Mon, 28 Jun 1999 23:13:13 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 6191383; Tue, 29 Jun 1999 14:13:10 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Holm Cc: freebsd-current@freebsd.org Subject: Re: lockmgr crashes... In-reply-to: Your message of "Tue, 29 Jun 1999 08:01:36 +0200." <37786140.ACB199AF@holm.cc> Date: Tue, 29 Jun 1999 14:13:10 +0800 From: Peter Wemm Message-Id: <19990629061310.6191383@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Holm wrote: > > > > Date: Mon, 28 Jun 1999 17:22:22 -0400 (EDT) > > From: Kenneth Wayne Culver > > To: freebsd-current@FreeBSD.ORG > > > > > > Just to let someone know... I recently (a couple of hours ago) have been > > having a problem with kernel panics.... I tried to remake the world and > > the kernel panics saying: > > > > panic: lockmgr: > > > > then what follows is different every time... all I know is that it doesn't > > happen until the process number is in the 25000 range, and after this, the > > disks refuse to sync, and I have to push the reset button on my > > computer... > > > > Kenneth Culver > > > > I can reproduce the same error within an hour. > > Here's a stack trace : > #9 0xc0165bc4 in panic () > #10 0xc0161610 in lockmgr () > #11 0xc0238c52 in relpbuf () > #12 0xc022daa4 in swp_pager_async_iodone () > #13 0xc0186393 in biodone () > #14 0xc028d227 in wdintr () > #15 0xc025e7ec in slow_copyout () This should be fixed a few minutes ago. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message