On Mon, Nov 14, 2005 at 07:36:13PM +0100, Jan Kiszka wrote: > Greg KH wrote: > > On Mon, Nov 14, 2005 at 06:54:17PM +0100, Jan Kiszka wrote: > >> Greg KH wrote: > >>> On Mon, Nov 14, 2005 at 06:35:22PM +0100, Jan Kiszka wrote: > >>>> Hi, > >>>> > >>>> on a VIA Eden box, I'm getting sporadic USB disconnects after longer > >>>> operation times. Typically, there is no USB load when it disconnects. > >>>> The kernel output is like this: > >>>> > >>>> kernel: hub 4-0:1.0: state 5 ports 6 chg 0000 evt 0008 > >>>> kernel: ehci_hcd 0000:00:10.3: GetStatus port 3 status 00180b POWER > >>>> sig=j PEC CSC CONNECT > >>>> kernel: hub 4-0:1.0: port 3, status 0501, change 0003, 480 Mb/s > >>>> kernel: usb 4-3: USB disconnect, address 2 > >>>> kernel: usb 4-3: usb_disable_device nuking all URBs > >>>> kernel: ehci_hcd 0000:00:10.3: shutdown urb c633cc20 pipe 80000280 ep0in > >>>> kernel: usb 4-3: hcd_unlink_urb c633cc20 fail -16 > >>>> > >>>> Attached are either a rt2570-based USB WLAN stick (via native driver) or > >>>> a LinkSys WUSB54G WLAN adapter (via ndiswrapper). Both fail, and in both > >>>> cases the USB subsystem locks up in some nasty way (deadlock, rest of > >>>> system still alive) so that no resetting/unloading of the involved > >>>> drivers is possible. Only a hard reboot helps. I'm watching this effect > >>>> for quite a while now, so far with 2.6.8 kernels, now also with a recent > >>>> 2.6.14.2. > >>> If you are using ndiswrapper, there's nothing we can do to help you, > >>> sorry. > >> We do not need to raise a discussion about this topic here. > > > > That's fine, just letting you know. > > > >> I only mentioned ndiswrapper and the WUSB54G to express that this issues > >> does not seem to be high-level driver related. I always thought it would > >> be a ndiswrapper or LinkSys Windows driver issue until I bought this > >> second device. > >> > >>> What driver controls the rt2570-based USB WLAN device, usbnet? > >> http://sourceforge.net/projects/rt2400, the stable rt2570 driver > > > > I suggest you ask the authors of this driver, not much we can do here > > either :( > > > > Now if you have a problem with an in-kernel driver, then we can help. > > > > Well, I must say that this degree of cooperation from an Open Source > project is rather new to me. Did I violate your policy by posting to > devel directly? Than sorry, just tell me.
No, no "policy violation", it's just that we really have no idea what is going on in drivers that we don't have access too, that's all. > All I am asking for are some hints what may go wrong in my case, what > the messages e.g. mean. If you are not /able/ to debug this problem in > theory (likely I will have to do this on my hardware in real anyway), > then please explain why you can exclude a bug in the USB stack. I can't exclude such a bug. But I really think it's a bug in the lower level driver, as this problem doesn't seem to be reported for any other usb driver so far that I have seen. > Otherwise, with my currently limited detail knowledge of the involved > components, I may easily end up being bumped between both projects. If the rt2400 people push you back here, with information showing that it is a USB core problem, we will be glad to help you out. Otherwise, how are we supposed to be able to help (given previously mentioned lack of source to rely on.) I'm not trying to pass you on to someone else because I don't want to help, I'm only trying to point you to who is in the best position to help you out with your problem. thanks, greg k-h ------------------------------------------------------- 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
