On Sun, 27 Feb 2005, Gerd v. Egidy wrote: > > It might be that the cables are okay, but there's just too much EMI > > created by the motherboard. > > I'm going to play around with the hardware (case, power supply, cables, > other pci-cards, different processor,...) tomorrow. > > But for now I tried it with your patches (on top of 2.6.11-rc5). > I had to fiddle around a bit with them to make them apply & compile > together. I attached them just in case someone else is interested. > Maybe you can take a look that I didn't mess them up.
The kernel is a moving target... And those patches were written for the USB development kernel, which isn't exactly the same as 2.6.11-rc5. If the patches need updating I'll compare my version with yours. > It is still not working, I still get a complete usb disconnect after some > time. The good news is that it isn't oopsing anymore. Well, the patches were never intended to solve the underlying transmission problem, just the oops. Too bad about the disconnect though -- apparently the device gets sufficiently confused that even a port reset fails, leaving disconnection as the only option. > Until the disconnect the speed is a little bit better. The messages are a bit > different than before: I continously get this type of message: <...> That's the normal case. It's supposed to be like that always. > and seldom this type: <...> This shows a failed transfer followed by a port reset. In this case the reset succeeded and things went ahead as they should. > and after a while: <...> This shows a port reset failing. It's not clear why it failed (looks like you didn't have CONFIG_USB_DEBUG set), but maybe that doesn't matter. You can also see the problem with the SCSI drivers that used to cause the oops: When the drive reconnects it becomes sdb because sda is still in use by the SCSI error handler, even though it's not supposed to be in use by anything any more. > I'll report what happens when I play around with the hardware but maybe > you have another good patch for me to try out... Sorry, nothing more has come up. I think the only way to attack this problem will be by modifying the ehci-hcd driver. But exactly what's going wrong and what changes are needed... no idea. You wouldn't happen to have a USB bus analyzer lying around, would you? :-) > Thank you for your great support so far. You're welcome. 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 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
