NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/22218 (using a USB isochronous endpoint freezes kernel)



On Wed, 8 Oct 2008, Jared D. McNeill wrote:

Date: Wed,  8 Oct 2008 18:20:04 +0000 (UTC)
From: Jared D. McNeill <jmcneill%invisible.ca@localhost>
Reply-To: gnats-bugs%NetBSD.org@localhost
To: kern-bug-people%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost,
    netbsd-bugs%NetBSD.org@localhost, coto%marsrakete.de@localhost
Subject: Re: kern/22218 (using a USB isochronous endpoint freezes kernel)

The following reply was made to PR kern/22218; it has been noted by GNATS.

From: "Jared D. McNeill" <jmcneill%invisible.ca@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
netbsd-bugs%netbsd.org@localhost,
   coto%core.de@localhost
Subject: Re: kern/22218 (using a USB isochronous endpoint freezes kernel)
Date: Wed, 8 Oct 2008 14:18:58 -0400 (EDT)

On Wed, 8 Oct 2008, Thomas Runge wrote:
> I kept the app running for a few days. This works quite nicely, as long,
> as there is no activity on this system. When I start a cvs update, the
> kernel will panic soon. This is my latest stacktrace:
>
> ugen_isoc_rintr(c1079100,c6e41374,0,1,0,e500,15c0,4,3c1,4) at 
netbsd:ugen_isoc_rintr+0x56
> usb_transfer_complete(c1079100,15c0,20,a,3,c6e41380,c6509520,0,0,0) at 
netbsd:usb_transfer_complete+0xba
> ohci_softintr(c6509524,0,30,c63b0010,c63c0010,0,1fc7be0,c0e9f080,0,c63bbda0)  
at netbsd:ohci_softintr+0x543
> softint_dispatch(c74adae0,4,0,0,0,0,c63bbd90,c63bbbd8,c63bbc30,28) at 
netbsd:softint_dispatch+0x7c
> DDB lost frame for netbsd:Xsoftintr+0x3d, trying 0xc63bbd88
> Xsoftintr() at netbsd:Xsoftintr+0x3d
> ---  interrupt  ---
> fatal page fault in supervisor mode
> trap type 6 code 0 eip c052f6f7 cs 8 eflags 10202 cr2 3c ilevel 8
> kernel: supervisor trap page fault, code=0
> Faulted in DDB;  continuing...
> db{0}>

This looks identical to an issue I'm seeing with a USB ATSC tuner and
ehci(4). I suspect the ehci isoc code was based on the ohci and uhci
implementations.. are you able to try this camera on a uhci to see if you
can reproduce the same crash there?

I'm afraid, I can't. I do not own any uhci hardware. This old laptop has
ohci built-in, but I tried (on the same hardware) a USB2-PC-CARD. This
one procides ehci and ohci. Same results.

Do you know any hardware that is known to have uhci? Maybe I could
try on a friends laptop.

--
Tom



Home | Main Index | Thread Index | Old Index