On Tuesday 10 July 2007, Alan Stern wrote:
> On Tue, 10 Jul 2007, Christoph wrote:
> > > For whatever it's worth, the crash occurred in end_async_unlink because
> > > ehci->reclaim was NULL. This may imply that ehci->reclaim_ready was
> > > set when it shouldn't be. Don't ask me how either of these could
> > > have happened.
> > >
> > > Alan Stern
> > >
> >
> > mh, how about this:
> > drivers/usb/host/ehci-hcd.c:640
> >
> > /* complete the unlinking of some qh [4.15.2.3] */
> > if (status & STS_IAA) {
> > COUNT (ehci->stats.reclaim);
> > ehci->reclaim_ready = 1;
> > bh = 1;
> > }
> > ...
> > if (bh)
> > ehci_work (ehci);
> >
> > bh was set to 1 ... possible there?!
>
> It is possible; I don't know enough about how the driver works to say
> for sure. You could test it easily enough. Just add a printk there if
> ehci->reclaim is NULL.
Makes sense to me. That whole timer thing is a bit dodgey
anyway ... combining the IAA watchdog (without which VIA parts
lose horribly) with the other mechanisms has always seemed to
me like it would hold some bugs.
- Dave
-------------------------------------------------------------------------
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
