On 11/16/2011 02:28 AM, Julian Sikorski wrote: > W dniu 15.11.2011 12:55, Julian Sikorski pisze: >> W dniu 15.11.2011 09:59, Andiry Xu pisze: >>> On 11/15/2011 04:36 PM, Julian Sikorski wrote: >>>> W dniu 15.11.2011 07:42, Andiry Xu pisze: >>>>> Please keep usb mail list CCed. >>>> >>>> I thought I am, but I guess something went wrong with gmane. Did you get >>>> my other messages btw? >>>> >>>>> >>>>> On 11/14/2011 08:40 PM, Julian Sikorski wrote: >>>>>> >>>>>> >>>>>> W dniu 14.11.2011 10:27, Julian Sikorski pisze: >>>>>>> W dniu 2011-11-14 10:24, Andiry Xu pisze: >>>>>>>> On 11/12/2011 02:20 PM, Julian Sikorski wrote: >>>>>>>>> W dniu 11.11.2011 21:11, Julian Sikorski pisze: >>>>>>>>>> W dniu 31.08.2011 22:25, Julian Sikorski pisze: >>>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> I originally reported this problem here: >>>>>>>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=35212 >>>>>>>>>>> Summing up, the external hard drive will produce an io-error after >>>>>>>>>>> about >>>>>>>>>>> 30 minutes of being connected. After such event, system does not >>>>>>>>>>> notice >>>>>>>>>>> if the device is re-connected upon disconnection. I am attaching the >>>>>>>>>>> relevant portion of /var/log/messages. >>>>>>>>>>> The problem happens on an up-to-date Fedora 15 x86_64 (running >>>>>>>>>>> kernel >>>>>>>>>>> 2.6.40.3-0.fc15.x86_64) on a Clevo P150HM laptop and Lacie Rugged >>>>>>>>>>> USB >>>>>>>>>>> 3.0 hard disk. >>>>>>>>>>> Please let me know if I can provide more information >>>>>>>>>>> >>>>>>>>>>> Regards, >>>>>>>>>>> Julian >>>>>>>>>> I have recently upgraded to Fedora 16, and I am now running kernel >>>>>>>>>> 3.1.0-7.fc16.x86_64. This problem is far from being gone, >>>>>>>>>> unfortunately. >>>>>>>>>> It will go as follows: >>>>>>>>>> - you plug the drive into one of USB3 ports >>>>>>>>>> - everything works fine >>>>>>>>>> - suspend and resume (not sure if this is necessary) >>>>>>>> >>>>>>>> Have you figured out if this suspend/resume step is necessary? >>>>>>> >>>>>>> Not yet. I will try later today (but bear with me given the hour needed >>>>>>> to trigger the problem). >>>>>>> >>>>>> >>>>>> Due to long time needed to reproduce the problem please accept this >>>>>> partial report. >>>>>> I have updated the kernel to 3.1.1-1.fc16.x86_64 (which showed up in >>>>>> Fedora repositories earlier today). I then rebooted and am now running >>>>>> with the drive connected for more than an hour downloading something off >>>>>> bittorrent. Here is the fragment of /var/log/messages from the drive >>>>>> connection until now. Keep in mind that these "stalled endpoint" >>>>>> messages show up every 30 minutes (12:26, 12:56 and 13:26) - maybe if >>>>>> the PC was suspended before they trigger the error? >>>>>> >>>>> >>>>> Stalled endpoint message is normal. A reset endpoint command should >>>>> bring it back into normal state. >>>>> >>>>> Do you connect other full speed devices to USB3 ports? >>>> >>>> Normally not since this machine has 2 USB3 ports and 3 USB2 ports. I can >>>> try and see if the problem can also be reproduced if you would like me to. >>>> >>> >>> You don't need to try that. The device first connected as a full speed >>> device and fail to initialize, and then recognise as super speed device. >>> Sounds like a device issue. >>> >>> Anyway, try the patch attached, do a suspend/resume and see if it still >>> occur. >>> >>> Thanks, >>> Andiry >>> >>> >>> >> With your patch, I was able to do the following: >> 10:40 plugged in. >> 10:42 suspend/resume >> 11:38 disconnect/reconnect >> 12:40 tried to unmount, says device busy, worked slightly later >> 12:44 disconnect/reconnect >> The drive is still alive and kicking, so it seems like the patch might >> be working. Let's not get ahead of ourselves though, I'll keep an eye on >> it for the rest of the day. I am attaching /var/log/messages of the >> session in case there might be something interesting in it. Thanks again >> for looking into this. >> >> Regards, >> Julian >> > I think we are looking good. I was trying various combinations of > suspending, resuming, disconnecting and reconnecting and I haven't > managed to break it so far. The only hiccup was when after one > suspend/resume with drive disconnected the port which was in use before > was not working. The other port was, and another suspend/resume brought > the order back. /var/log/messages of the whole session is attached. > OK, so your host may need a reset-on-resume quirk, though I wonder why it works for a period of time after resume and then break. Please provide the PCI vendor and device ID by post the output of 'lspci -n'. Thanks. Andiry -- 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
