I'm beginning to think that there's something wrong with your UHCI
hardware. The log shows several problems, even your syslog.3 where
neither the USB key nor the mass storage device initialized correctly. There are port resets failing -- which is almost impossible if the devices
function correctly -- and read requests failing that succeeded later.
N.B.: I don't know what happened but it seems that I've managed one time to get reboot several times without getting anymore the error. I had to power off the computer and boot again to see it.
More evidence that the USB controller hardware is at fault.
I am not convinced. Both windows and linux 2.6.8.1 are starting it rightly (though I cannot check 2.6.8.1 completely because of the freebox bug that was not worked around at that time). I am going to check patches regressively between 2.6.8.1 and 2.6.11 to know what has broken the startup sequence.
Actually the situation was a bit more complex. After a few tests it appeared that the 'USB Legacy support' option in the bios was for something in the problem which is happening at the first module insertion of uhci_hcd. For the moment the situation has stabilized and the uhci controller is initializing peacefully with 2.6.11. However the second problem is still there but that one is linked to some broken protocol handling in the freebox I guess. I can circumvent it by using another bus.
Regards,
Guilhem Lavaux.
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
