Thu, 03 Nov 2005 @ 07:57 -0800, David Brownell said: > A similar issue -- often also with VIA hardware -- is devices that work > for a while and then spontaneously disconnect themselves. It might be > this is another case where VIA hardware needs to be stroked in ways that > other hardware doesn't care about.
I have had devices online for weeks without disconnect. I have never seen spontaneous disconnect with this motherboard. That's in a bit over a year of usage with various storage devices, USB1 and USB2. It seems like in that time I've had seen some kind of problem, and it also seems like if there were hardware issues, I'd have seen them under other operating systems. > (In which case testing with some add-in PCI card with a non-VIA > controller would be more successful.) I'd be willing, but I don't have anything myself. > > In all cases, even when the kernel makes no syslog entry at all, > > /proc/interupts show that interrupts were received upon each device plug > > and unplug. > > I'd expect that CONFIG_USB_DEBUG=y would show some more messages. I've enabled it specifically to debug this, but it isn't showing me anything extra. > This is early enumeration code. In fact, the read/64 stuff doesn't need > to be done; there's only one ep0 maxpacket size possible for high (or low) > speed devices. One person reported some success with a patch that bypasses > the "guess the ep0 maxpacket" dance except for full speed (which is the only > case where it's necessary) ... one theory is that since that dance forces > devices into certain fault modes, either (a) devices don't always handle > those fault modes correctly, or (b) Linux doesn't. So bypassing those > fault modes could make them both happier. If it means anything, my "MyFlash" 1GB flash drive has more problems than my Apple iPod. Right now, the MyFlash drive doesn't get a reaction from the kernel at all. It see interrupts, but that's it. The iPod generates the enumeration errors. > Start with CONFIG_USB_DEBUG=y to see what other messages are reported. For some reason, it doesn't seem to have any effect. > If this started with 2.6.10, then maybe you could help pinpoint which patch > to 2.6.9 started to make this failure happen more often. I'll get around to it and see what happens. I can't completely remember where the trouble started, so that would be a good test. -- shannon "AT" widomaker.com -- ["Tara is grass, and behold how Troy lieth low--And even the English, perchance their hour will come!"] ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
