OK, see how this patch behaves for you. The "bad entry" stuff seems to have been caused by trying to have a fast-path ...
Well, was this supposed to work with 2.6.3-bk9 or 2.6.4-rc1? At least it applied almost cleanly (probably harmless offset) and compiled.
Shouldn't matter, OHCI didn't change.
However, things are getting really worse now, sorry. For me the HC dies when connecting hub+device which produces a number of bad entries again. And it seems the hub driver deadlocks on disconnect then. Maybe it was too aggressive wrt. interrupt urb's or rh handling?
Didn't change any of that. So I think there's another bug lurking. Maybe one of the other things I tried will make a difference in that case ... that patch alone made a pretty dramatic change though.
For "too aggressive" -- in start_ed_unlink(), try making tick be two frames after current, not just one.
FYI I ran a loop of test #11/#12 for about four hours, no problems; it previously failed almost immediately. Then I added another device; I forgot it had some test firmware, so it automatically joined the loop for #12. Then it gave some "bad entry" errors -- very odd, it was on a different controller! Another timing thing ...
- Dave
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
