Re: [Em28xx] dvb-core random crashes - Got it

Alan Stern <[email protected]>
Newsgroups gmane.linux.usb.devel,gmane.linux.drivers.em28xx
Message-ID <[email protected]>
On Thu, 12 Jul 2007, Christoph wrote:

> So,
> 
> since yesterday I'm running this:
> 
> drivers/usb/host/ehci-hcd.c:611
>     /* complete the unlinking of some qh [4.15.2.3] */
>     if (status & STS_IAA) {
>         if (ehci->reclaim) {
>             COUNT (ehci->stats.reclaim);
>             ehci->reclaim_ready = 1;
>             bh = 1;
>         } else {
>             printk(KERN_ERR "AUA: ehci reclaim NULL status: %u\n", status);
>         }
>     }
> 
> 
> and got (once so far):
> 
> Jul 11 16:19:03 denon kernel: [13475.940000] drivers/usb/input/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0306 wIndex=0x0000 wLength=2
> Jul 11 16:19:03 denon kernel: [13475.960000] drivers/usb/input/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0336 wIndex=0x0000 wLength=2
> Jul 11 16:19:22 denon kernel: [13495.008000] AUA: ehci reclaim NULL status: 32
> Jul 11 16:19:22 denon kernel: [13495.364000]  usbdev4.4_ep81: ep_device_release called for usbdev4.4_ep81
> Jul 11 16:19:22 denon kernel: [13495.364000]  usbdev4.4_ep82: ep_device_release called for usbdev4.4_ep82
> Jul 11 16:19:22 denon kernel: [13495.368000]  usbdev4.4_ep84: ep_device_release called for usbdev4.4_ep84
> Jul 11 16:20:03 denon kernel: [13535.964000] drivers/usb/input/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0331 wIndex=0x0000 wLength=3
> Jul 11 16:20:03 denon kernel: [13536.004000] drivers/usb/input/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0326 wIndex=0x0000 wLength=3
> 
> no crash, all usb devices happy.
> 
> Conclusion:
> 
> - It's the bug. Anywhere else in the code reclaim_ready will only set if ehci->reclaim is valid.
> - I spammed the wrong ML :)
> 
> I still have some questions to the usb ppl:

You should ask David Brownell since he's the maintainer for that
driver.

> * what is on status STS_IAA supposed to do?

Interrupt on Async Advance: It indicates that the controller has 
advanced the async schedule.

> * should bh set anyway and call ehci_work?

I believe that it was intended as a workaround for some design bugs in 
certain EHCI controllers.

> * what is [4.15.2.3] referring to?

It is a section number in the EHCI specification document.

Alan Stern


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.