Alan Stern wrote: > The advantage of attaching the trace to the bug report is that it will > still be available for people to look at long after you have removed it > from your server. > If 250k is not a waste of storage, I'll upload. > >> (no other usb device had been in use while doing the test) >> > > That's not correct. The trace shows that a device attached to port 2 > (the card reader was on port 3) was quite active while your test was > running. > There is a builtin WLAN adapter that is connected through USB (and unfortunately the kernel driver completely ignores the physical WLAN switch, so it is always turned on) but I assumed that it will not be active if I tell the Network Manager (lousy piece of software) to stop the WLAN. sorry for that. > > The trace does not show the transfer stopping completely. It was still > going strong at the end of the trace. > > Maybe the bug is in the USB hardware on your computer instead of the > card reader. I can't tell which. > > Thanks for the hint. Well, the reader worked perfectly on other machines, and the notebook has trouble with several devices like USB pendrivers, so if there's a damage, it must be the computer. But I have two notebooks with intel chipsets and both have similar problems, so I would be astonished if both of them were broken. And if I remember correctly, I could fix the problem by stepping back to an older kernel when the problem occured for the first time, but that's long time ago. :-( regards Hadmut -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
