>>I've got one fix in that area still queued, which I'll send >>separately on the chance it makes a difference in this case. > > > That fix made only things worse
... broken patch, sorry. I thought I'd sanity checked it, but that was a couple weeks ago and I suspect I really didn't. Turns out it can be simpler, a code shrink (yay!). I'll send a better patch in a while, maybe it'll fix your hang too. > I'm under the impression that the OHCI controller is kinda > picky whether or not any devices are plugged in when activating the chip. Shouldn't be, at least common-ish ones like SiS. At least, if that's the case, the current code should have restored some of the funky non-spec initialization that some silicon seems to require; some earlier ohci-hcd versions didn't have that stuff. >>Can you resend similar output but with the OHCI debugging turned on? > > > See attached pwc-24-ohci-debug file. There's something odd going on there ... there are two status values I see in your unlinks. Most are "-2" (-ENOENT) indicating a synchronous unlink. The last one is "-104" (-ECONNRESET), to indicate an asynchronous one, and that's the last one you sent. (Presumably that's where the problem/hang showed up.) Since that "-ECONNRESET" async unlink case is also the last one before the hang, that's likely the issue. I have a good clue now, thanks for the info! - Dave ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Stuff, things, and much much more. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
