https://bugzilla.novell.com/show_bug.cgi?id=419250 User sbrandt@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=419250#c24 Sebastian Brandt <sbrandt@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|sbrandt@gmx.de | --- Comment #24 from Sebastian Brandt <sbrandt@gmx.de> 2008-10-16 10:30:59 MDT --- Comment #7, in my opinion, shows that - at that moment - the OHCI hang already "spread" so far that even the UHCI did no longer work, but at least noticed that it had a problem. During the months, I *never* had any problem with the UHCI/EHCI, unless OHCI was alread hanging. The similiarity with bug #370872 is rather a consequence, not the problem itself, I believe. The stack trace I gave with comment #18 is in so far misleading, as I already tried to unload the ohci-hcd there. My guess is, the ohci interrupts get lost (somehow?); the unability to unload the driver module follows from there. Thus, the usb-related stack traces from comment #21 might be more exact, as they show threads hanging in the usb subsystem itself, but not in the OHCI subsystem ... hints at losing interrupts, to me. I will also apply the patch from bug #370872 and see what happens. Any other/newer kernel version I should try? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.