On Fri, 3 Jun 2005, Parag Warudkar wrote: > On Friday 03 June 2005 16:57, Alan Stern wrote: > > That may be a harmless artifact, arising because the OHCI driver is loaded > > before the EHCI driver. > > Trouble is when this error is in dmesg no USB device works (Mouse, Storage). > It happens infrequently as I said.
If you get rid of the EHCI driver entirely (for example, rename /lib/modules/.../drivers/usb/host/ehci-hcd.ko to something else so that modprobe can't find it), does the "Unlink after no-IRQ?" error still occur? > > Your SysRq-T output is incomplete. �Sometimes syslogd doesn't capture all > > the data. �You're better off running in single-user mode with > > non-essential daemons shut down, and you should use dmesg to capture the > > SysRq-T trace. > > > I took the output from /var/log/messages - No matter what I do I don't seem > to > be able to get more than that - and mysteriously the hung modprobe process is > always missing in the output. You should do what I said: boot to single-user mode, kill all unnecessary daemons, and use dmesg to get the SysRq-T output instead of taking it from /var/log/messages. > I have a USB mouse and external HDD attached - modprobe hangs irrespective of > their presence/absence. That's potentially useful information, although at the moment its meaning isn't clear. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
