On Tue, Oct 12, 2010 at 02:42:04PM -0400, Alan Stern wrote: > On Tue, 12 Oct 2010, Sarah Sharp wrote: > > > Hi Andiry, > > > > I just tested this patch (along with the other PM patches), and I got an > > oops. All USB devices were unplugged, the roothub suspended, I plugged > > in a USB 3.0 hard drive, and then the oops happened. Full dmesg > > (xhci-device-pm-siig-usb3-2010-10-12-09-08-roothub-suspended.txt) and > > markup of the oops is attached > > (xhci-device-pm-siig-usb3-2010-10-12-09-08-roothub-suspended-markup.txt), > > along with the .config that I used. > > > > It's a very odd looking oops. It looks like a control transfer for the > > *roothub* timed out, and then the USB core tried to print a warning > > message, but the struct device pointer was bogus. I have no idea why > > the roothub control transfer would time out. > > You need to find out what's happening at this address: > > > [ 203.030733] [<ffffffffa01f119a>] hub_activate+0x14a/0x490 [usbcore] > > The stuff between that and the dev_printk line isn't reliable (which > is why those '?' symbols are there, IIUC). Doh! It seems the oops came from some debugging I added that wasn't part of Andiry's patchset. Device suspend seems to work fine for my pl2303 USB serial adapter and the USB 3.0 hard drive when the usb-storage driver isn't loaded. So, Andiry, if you include the two patches I suggested into your new patchset, I would be happy to ack this. Sarah Sharp -- 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
