kern/62889: Panic in vr(4): interrupt related

[Andrew Boothman]

>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 at 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 <nate at root.org> 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 <dwhite at gumbysoft.com> 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: