From owner-freebsd-current Thu May 31 13:57:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 768B937B424; Thu, 31 May 2001 13:57:46 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f4VKvaX34738; Thu, 31 May 2001 13:57:36 -0700 (PDT) Date: Thu, 31 May 2001 13:57:36 -0700 (PDT) From: David Wolfskill Message-Id: <200105312057.f4VKvaX34738@bunrab.catwhisker.org> To: david@catwhisker.org, jhb@FreeBSD.org Subject: RE: panic (witness_destroy+0x237) after booting today's -CURRENT Cc: current@FreeBSD.org In-Reply-To: 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 >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. Thanks, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message