From owner-freebsd-bugs@FreeBSD.ORG Wed Mar 10 19:50:17 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E5CC16A4CE for ; Wed, 10 Mar 2004 19:50:17 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77A1843D39 for ; Wed, 10 Mar 2004 19:50:17 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i2B3oHbv019900 for ; Wed, 10 Mar 2004 19:50:17 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i2B3oGJf019898; Wed, 10 Mar 2004 19:50:16 -0800 (PST) (envelope-from gnats) Date: Wed, 10 Mar 2004 19:50:16 -0800 (PST) Message-Id: <200403110350.i2B3oGJf019898@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Andrew Boothman Subject: Re: kern/62889: Panic in vr(4): interrupt related X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Andrew Boothman List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Mar 2004 03:50:17 -0000 The following reply was made to PR kern/62889; it has been noted by GNATS. From: Andrew Boothman To: freebsd-gnats-submit@FreeBSD.org, andrew@mux.org.uk Cc: silby@FreeBSD.org Subject: Re: kern/62889: Panic in vr(4): interrupt related Date: Thu, 11 Mar 2004 03:40:25 +0000 [CC'ed to silby as the developer with his hands most frequently in vr recently - hope you don't mind] > A trace then gave me : > > vr_rxeof(...) ... > vr_intr(...) ... > ithread_loop(...) ... > fork_exit(...) ... > fork_tampoline(...) ... > Just to add that I had another one of these panics today, in exactly the same place as before, happening just after the "Shutting off power using ACPI" message is printed. No further information other than that - I'm still happy to supply more information, test patches or whatever. Is there anything that can be done in the debugger to obtain more information once the panic has happened? It's been a month between panics so we might have a wait before I can do anything about it however... Thanks. Andrew