> -----Original Message----- > From: CAI Qian [mailto:caiqian@xxxxxxxxxx] > Sent: Wednesday, April 13, 2011 10:18 AM > To: Sarah Sharp > Cc: John Youn; Paul Zimmerman; Alan Stern; linux-usb@xxxxxxxxxxxxxxx; Don > Zickus; Xu, Andiry > Subject: Re: [RFT] usbcore: Bug fix: system can't suspend with USB3.0 > device connected to USB3.0 hub > > > > ----- Original Message ----- > > ----- Original Message ----- > > > ----- Original Message ----- > > > > On Tue, Apr 12, 2011 at 06:25:26PM -0400, CAI Qian wrote: > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > On Tue, Apr 12, 2011 at 04:34:10PM -0400, CAI Qian wrote: > > > > > > > > If auto-suspend is working properly, you > > > > > > > > should > > > > > > > > see messages like: > > > > > > > > > > > > > > > > "usb 9-1: usb auto-suspend" > > > > > > > Yes, there was a message there. > > > > > > > > > > > > > > kernel: usb 9-1.2: usb auto-suspend > > > > > > > > > > > > Ok, will you please try the patch Alan sent (the one that > > > > > > removes > > > > > > the > > > > > > can_submit check). I am able to reproduce this with Linus' > > > > > > latest > > > > > After applied this patch on the top of the 5 patches, it is now > > > > > working. > > > > > Awesome! Thanks! > > > > > > > > Great! Can you test with just Andiry's work-around patch and > > > > Alan's > > > > patch? Andiry's 5 patches are too large to go into 2.6.39, so we > > > > need a quick fix for 2.6.39. > > > That is also working for me. > > > > > > CAI Qian > > > > I noticed that there was one issue with the resume from hibernate > > > > on > > > > my > > > > system, and I'll send you a patch shortly. > > I have also noticed one major problem though that the USB 3.0 storage > > device is gone after the hibernate/resume. > > > > usb 8-1: usb auto-suspend > > hub 8-0:1.0: hub_suspend > > usb usb8: bus auto-suspend > > xhci_hcd 0000:1a:00.0: suspend USB 2.0 root hub > > xhci_hcd 0000:1a:00.0: `MEM_WRITE_DWORD(3'b000, 32'hffffc90012858450, > > 32'ha0002a0, 4'hf); > > xhci_hcd 0000:1a:00.0: `MEM_WRITE_DWORD(3'b000, 32'hffffc90012858440, > > 32'hc000e61, 4'hf); > > xhci_hcd 0000:1a:00.0: `MEM_WRITE_DWORD(3'b000, 32'hffffc90012858444, > > 32'h8, 4'hf); > > sd 5:0:0:0: [sdb] Unhandled error code > > sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > > sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 01 00 00 01 00 > > end_request: I/O error, dev sdb, sector 8 > > Buffer I/O error on device sdb, logical block 1 > > sd 5:0:0:0: [sdb] Unhandled error code > > sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > > sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 01 00 00 01 00 > > end_request: I/O error, dev sdb, sector 8 > > Buffer I/O error on device sdb, logical block 1 > > sd 5:0:0:0: [sdb] Unhandled error code > > sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > > sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 2b aa 14 74 00 00 01 00 > > end_request: I/O error, dev sdb, sector 5860533152 > > Buffer I/O error on device sdb, logical block 732566644 > > > > ... > This problem is also existed for the kernel applied the patch on > the top of the 5 patches. > > PM: Syncing filesystems ... done. > (elapsed 0.01 seconds) done. > Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. > PM: Preallocating image memory... done (allocated 312035 pages) > PM: Allocated 1248140 kbytes in 0.61 seconds (2046.13 MB/s) > serial 00:08: disabled > 00:06:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > ata_piix 0000:00:1f.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > ata_piix 0000:00:1f.5: PCI INT C -> GSI 21 (level, low) -> IRQ 21 > serial 00:07: activated > serial 00:08: activated > hub 9-1:1.0: hub_port_status failed (err = -22) > hub 9-1:1.0: hub_port_status failed (err = -22) > hub 9-1:1.0: hub_port_status failed (err = -22) > hub 9-1:1.0: hub_port_status failed (err = -22) > hub 9-1:1.0: activate --> -22 > mptsas 0000:01:00.0: BAR 0: set to [io 0x1000-0x10ff] (PCI address > [0x1000-0x10ff]) > mptsas 0000:01:00.0: BAR 1: set to [mem 0x97910000-0x97913fff 64bit] (PCI > address [0x97910000-0x97913fff]) > mptsas 0000:01:00.0: BAR 3: set to [mem 0x97900000-0x9790ffff 64bit] (PCI > address [0x97900000-0x9790ffff]) > bnx2 0000:0b:00.0: eth0: NIC Copper Link is Down > mptsas 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > mptbase: ioc0: pci-resume: ioc-state=0x1,doorbell=0x10000000 > ata3: SATA link down (SStatus 0 SControl 300) > ata4: SATA link down (SStatus 0 SControl 300) > ata1.00: SATA link down (SStatus 0 SControl 300) > ata1.01: SATA link down (SStatus 0 SControl 300) > ata2.00: SATA link down (SStatus 0 SControl 300) > ata2.01: SATA link down (SStatus 0 SControl 300) > bnx2 0000:0b:00.0: eth0: NIC Copper Link is Up, 1000 Mbps full duplex > mptbase: ioc0: Sending mpt_do_ioc_recovery > mptbase: ioc0: Initiating bringup > ioc0: LSISAS1064E B3: Capabilities={Initiator} > mptbase: ioc0: pci-resume: success > PM: thaw of devices complete after 15048.141 msecs > PM: Compressing and saving image data (307962 pages) ... done > PM: Wrote 1231848 kbytes in 11.62 seconds (106.01 MB/s) > PM: S| > md: stopping all md devices. > kvm: exiting hardware virtualization > ACPI: Preparing to enter system sleep state S5 > Disabling non-boot CPUs ... > Power down. > Does the issue occur with system suspend/resume? Thanks, Andiry ÿô.nlj·Ÿ®‰†+%ŠË±é¥Šwÿº{.nlj·¥Š{±þë)íè jg¬±¨ ¶‰šŽŠÝjÿ¾«þG«é¸ ¢·¦j:+v‰¨Šwèm¶Ÿÿþø®w¥þŠà£¢·hšâÿ†Ù
