Hi Sarah, Did you get a chance to take a look at this issue? Thanks, Geoffroy PS: I can also open an official bug report if that helps you track it. Just let me know > -----Original Message----- > From: Sharp, Sarah A > Sent: Wednesday, November 10, 2010 8:04 PM > To: VanCutsem, Geoffroy > Cc: linux-usb@xxxxxxxxxxxxxxx > Subject: Re: Problem with USB on Lenovo W510 > > On Wed, Nov 10, 2010 at 04:27:54AM -0800, VanCutsem, Geoffroy wrote: > > Hi Sarah, > > > > Have you been able to identify anything useful in the log files I > have provided? > > Please let me know if there are additional tests I could run to help > debug this issue. > > Yes, sorry, I've been dealing with post-conference email and about 7 > other xHCI bug reports. I'll let you know as soon as I take a look. > > > I also would like to enable suspend/resume on my system at some point > but some traffic on the mailing list indicate it will only be available > with 2.6.37. Is this correct? > > Yes, suspend/resume only works on 2.6.37-rc1. Alternately, you can > unload the xHCI driver before you want to suspend (which will kill all > your USB devices, but it's possibly better than not suspending at all). > > Sarah Sharp > > > > > -----Original Message----- > > > From: VanCutsem, Geoffroy > > > Sent: Friday, November 05, 2010 12:38 PM > > > To: Sharp, Sarah A > > > Cc: linux-usb@xxxxxxxxxxxxxxx > > > Subject: RE: Problem with USB on Lenovo W510 > > > > > > Hi Sarah, > > > > > > I have ran more tests today (with debugging turned on) -- log files > > > attached. The results are not always 100% consistent but at least I > > > have seen the crash occuring on multiple occasions and with both > the > > > USB 2.0 and USB 3.0 ports. I am always testing with the exact same > iso > > > (to take that one variable out of the equation) but working with 2 > > > different USB sticks. Here are the two models I am using (just in > case > > > it could be relevant): > > > - Kingston DataTraveler 1GB (DTI/1GB) -- log files which pertain to > > > this key have the '-wk' extension because it's a white key. > > > - PQI Cool Drive U339 1GB -- log files which pertain to this key > have > > > the '-bk' extension because it's a blue key. > > > > > > The blue key (PQI) was the one that seemed to trigger the crashes > most > > > frequently. > > > > > > Just to clarify how I am running these tests: > > > - Using a 2.6.35.8 kernel from kernel.org with the standard 2.5.35 > > > Ubuntu config file + USB debugging turned on (as per your request) > > > - I always reboot the machine before the next experiment if I see a > > > crash. > > > - I always unmount the USB stick before attempting 'dd' (using > 'sudo > > > umount /media/my_usb_stick_name') > > > - I have not yet tried to physically unplug the drive in the middle > of > > > a 'dd' session but that's an easy experiment to do if it makes > sense. > > > > > > I hope these logs will help you understand what is going on on my > > > system. > > > > > > Thanks! > > > Geoffroy > > > > > > > -----Original Message----- > > > > From: Sharp, Sarah A > > > > Sent: Thursday, November 04, 2010 7:40 PM > > > > To: VanCutsem, Geoffroy > > > > Cc: linux-usb@xxxxxxxxxxxxxxx > > > > Subject: Re: Problem with USB on Lenovo W510 > > > > > > > > On Thu, Nov 04, 2010 at 09:32:07AM -0700, VanCutsem, Geoffroy > wrote: > > > > > Hi Sarah, > > > > > > > > > > > -----Original Message----- > > > > > > From: Sharp, Sarah A > > > > > > > > > > > > There may be both EHCI and xHCI host controllers in the same > > > > system. > > > > > > xHCI handles all speeds of USB devices plugged into it. The > odd > > > > thing > > > > > > is your dmesg on the bug report you linked to shows that the > xHCI > > > > > > driver is handling your storage device, but your lspci output > > > > > > doesn't show > > > > it! > > > > > > > > > > Wasn't it reflected by this entry: > > > > > 0f:00.0 USB Controller: NEC Corporation Device 0194 (rev 03) > > > > > (prog-if > > > > 30) > > > > > > > > Oh, sorry, I guess I missed that. > > > > > > > > > I have done this today and the interesting thing is that with > this > > > > vanilla 2.6.35.8 kernel (from kernel.org) and debugging turned > on, > > > the > > > > problem seems to have gone away. I have been able to 'dd' the > exact > > > > same image onto a USB stick (tried twice, once from a USB3 port > and > > > > once from the 'normal' port)... so perhaps this is a bug in > > > > Ubuntu/Canonical variant of 2.6.35?? I have attahched the > relevant > > > > dmesg / lspci output to this email. > > > > > > > > Well, I'm not so sure you actually triggered the bug. The > previous > > > > log showed the crash after the USB device disconnected in the > middle > > > > of the dd transfer. This log doesn't show a disconnect during a > > > > transfer under the USB 3.0 port; it only shows a disconnect when > you > > > > switched the device over to the USB 2.0 port. > > > > > > > > You can probably trigger the bug if you physically pull out the > > > device > > > > while you're in the middle of the dd. Can you try that with the > > > > 2.6.35.8 kernel? > > > > > > > > Another possibility is the USB core and xHCI debugging is causing > a > > > > delay that's hiding the bug. You can also try turning off > debugging > > > > on the 2.6.35.8 kernel and dding a iso over, if yanking out the > > > device > > > > doesn't cause the bug. > > > > > > > > Sarah Sharp Intel Corporation NV/SA Kings Square, Veldkant 31 2550 Kontich RPM (Bruxelles) 0415.497.718. Citibank, Brussels, account 570/1031255/09 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -- 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
