From owner-freebsd-current Thu May 31 14:56:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 3865C37B424 for ; Thu, 31 May 2001 14:56:24 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f4VLuFG44700; Thu, 31 May 2001 14:56:15 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200105312057.f4VKvaX34738@bunrab.catwhisker.org> Date: Thu, 31 May 2001 14:56:23 -0700 (PDT) From: John Baldwin To: David Wolfskill Subject: RE: panic (witness_destroy+0x237) after booting today's -CURRENT Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 31-May-01 David Wolfskill wrote: >>Date: Thu, 31 May 2001 13:46:01 -0700 (PDT) >>From: John Baldwin > >>Did you get any other messages, such as a faulting virtual address, etc.? > > I had been using vty1; when the panic ocurred, I was (forcibly) switched > to vty0. There are no faulting virtual address-flavored messages on > vty0. If there were on vty1, I didn't see them quickly enough. > >>Is %edx 0? > > [Checks "man ddb"...] > > Yes, it is. Anything else that might be of interest? I'm about to head > into a meeting, but I'll leave the crashed system crashed as long as I > can if it might be useful to poke around in there. Hmm, not that I can think of atm. It looks like the SLIST of all lock in the system got corrupted somehow. :( -- John Baldwin -- 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