From owner-freebsd-bugs@FreeBSD.ORG Sun Feb 15 13:20:14 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 2CE0416A4CE for ; Sun, 15 Feb 2004 13:20:14 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 105AA43D31 for ; Sun, 15 Feb 2004 13:20:14 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i1FLKDbv050211 for ; Sun, 15 Feb 2004 13:20:13 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i1FLKDai050210; Sun, 15 Feb 2004 13:20:13 -0800 (PST) (envelope-from gnats) Resent-Date: Sun, 15 Feb 2004 13:20:13 -0800 (PST) Resent-Message-Id: <200402152120.i1FLKDai050210@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Andrew Boothman Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F7BC16A4CE for ; Sun, 15 Feb 2004 13:17:48 -0800 (PST) Received: from 82-41-27-158.cable.ubr04.edin.blueyonder.co.uk (82-41-27-158.cable.ubr04.edin.blueyonder.co.uk [82.41.27.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id C590843D2F for ; Sun, 15 Feb 2004 13:17:47 -0800 (PST) (envelope-from andrew@mux.org.uk) Received: from spatula.flat (spatula.flat [192.168.0.2]) by myriad.flat (Postfix) with ESMTP id 4D1B6BC for ; Sun, 15 Feb 2004 20:07:27 +0000 (GMT) Received: by spatula.flat (Postfix, from userid 1001) id 6356B3F28; Sun, 15 Feb 2004 21:18:43 +0000 (GMT) Message-Id: <20040215211843.6356B3F28@spatula.flat> Date: Sun, 15 Feb 2004 21:18:43 +0000 (GMT) From: Andrew Boothman To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: 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: Sun, 15 Feb 2004 21:20:14 -0000 >Number: 62889 >Category: kern >Synopsis: Panic in vr(4): interrupt related >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Feb 15 13:20:13 PST 2004 >Closed-Date: >Last-Modified: >Originator: Andrew Boothman >Release: FreeBSD 5.2-CURRENT i386 >Organization: >Environment: System: FreeBSD spatula.flat 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Sun Feb 8 03:34:19 GMT 2004 andrew@spatula.flat:/usr/obj/usr/src/sys/SPATULA i386 >Description: The vr(4) driver appears to sometimes have problems dealing with interrupts. This has shown itself once for me via a panic that occured during a shutdown via ACPI. A loose transcription of the panic is: Fatal trap 12 Fault virtual address = 0x8 Fault code = Supervisor ready, page not present . . Current process = 21 (irq10: fwohci vr0+) kernel: type 12 trap, code = 0 Stopped at vr_rxeof+0x140: pushl 0x8(%edx) A trace then gave me : vr_rxeof(...) ... vr_intr(...) ... ithread_loop(...) ... fork_exit(...) ... fork_tampoline(...) ... Following a post to -current, Nate Lawson noted that: "Your backtrace shows this is not an ACPI problem, it's a problem with vr(4) (the Via Rhine ethernet driver). It should check flags to see if the driver is going away in the device_detach case. I'm not sure how the intr handler got called since interrupts are disabled before powering off the system." While Doug White mentioned: "Pretty sure this is a bug in the vr driver; I've had the same thing happen on my KT400. It gets an interrupt at exactly the wrong moment and boom. I haven't had it happen in months, however." >How-To-Repeat: So far I've not been able to repeat this problem. Although Doug White indicates that is has happened before. >Fix: Unknown at this time >Release-Note: >Audit-Trail: >Unformatted: