On Tue, 15 Mar 2005, Guilhem Lavaux wrote: > > Can you send the file contents from before you rmmod uhci-hcd the first > > time? > > Here it is, just after the first modprobe (and before rmmod). There is > nearly nothing in it.
That's as expected. What's not expected is the line saying: stat1 = 0091 Connected It should say: "0093 ConnectChange Connected". It's also surprising that this is the stat1 entry; your logs show you were using port 2 on that controller, not port 1. > > There's still something weird about the timing in your log. Several of > > the delays there should last for 5 seconds, but the timestamps are all the > > same. Here's another patch to try and track it down: > > > > It seems that if I load manually the 5 seconds delay is respected > according to syslogd. Maybe it does not have the precise timing when the > system is loading it as the USB module loading happens really early in > the boot sequence. Yes, of course, that's the explanation. The timestamps in the log reflect the time that your syslog daemon wrote out the log entry, well after startup, not the time that the log entry actually occurred. > >>So I conclude there must be something special with the freebox device > >>which pollute the bus state. > > > > > > If that were true then you would never be able to use the freebox and the > > key on the same bus. But the sixth and seventh lines of results above > > show that you can. > > > > Part of the problem may be this timing issue. Another part may be related > > to the fact that the ehci-hcd driver gets loaded while uhci-hcd is in the > > middle of initializing the freebox. If you can arrange to load ehci-hcd > > first (or not at all) maybe that will help. > > > > > > It doesn't change anything. The error at the first modprobe after reboot > remains unchanged whatever I do: modprobe ehci_hcd, wait a bit, modprobe > uhci_hcd or the reverse or only uhci_hcd. 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. You can try buying or borrowing a PCI USB controller card, and see if it works any better than your hardware. The ones by NEC are said to be pretty good. Alan Stern ------------------------------------------------------- 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 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
