Hmm. With 2.5.47bk2 and debug=3 (set at compile time, thewas the /proc/driver/uhci/<pci addr> output not helpful, even with debug set to 3 (or more)? (i.e. modprobe uhci-hcd debug=3)The uhci-hcd "dmesg" output was un-informative, as it's been before when I've hit this failure. Just two messages:- "host controller process error, something bad happened" - "host controller halted. very bad"
new modprobe doesn't seem to understand module params yet)
I didn't see the problem. That was also running in X11
(so I could use machine in case dmesg was streaming text
after "very bad"), and I saw the same thing with the device
connected at boot time or later.
Doesn't look like UHCI changed in some time, so either this
problem was caused by some other bug (now fixed, what?) or
it's just not consistently reproducible ... which was my
original suspicion.
- Dave
p.s. 2.5.47bk2 doesn't hotplug correctly since "depmod"
isn't producing the /lib/.../modules.*map files ...
-------------------------------------------------------
This sf.net email is sponsored by: Are you worried about your web server security? Click here for a FREE Thawte Apache SSL Guide and answer your Apache SSL security needs: http://www.gothawte.com/rd523.html
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
