On Thu, 12 Apr 2012, Steven Rostedt wrote: > On Thu, 2012-04-12 at 14:17 -0400, Steven Rostedt wrote: > > > And I forgot that the echo isn't enough, and I need to do a pm-suspend > > too ;-) > > > > # dmesg | grep target > > [ 8829.427534] atl1c 0000:04:00.0: target 3 wakeup 0 error 0 > > [ 8829.443524] xhci_hcd 0000:03:00.0: target 3 wakeup 1 error 0 > > [ 8829.459506] iwlwifi 0000:02:00.0: target 3 wakeup 0 error 0 > > [ 8829.459560] pci 0000:00:1f.3: target 0 wakeup 0 error 0 > > [ 8829.459607] pci 0000:00:1f.0: target 0 wakeup 0 error 0 > > [ 8829.475458] ehci_hcd 0000:00:1d.0: target 3 wakeup 1 error 0 > > [ 8829.491433] ehci_hcd 0000:00:1a.0: target 3 wakeup 1 error 0 > > [ 8829.507416] pci 0000:00:16.0: target 3 wakeup 0 error 0 > > > > The above was without the script, with the script: > > # dmesg | grep target > [ 8829.427534] atl1c 0000:04:00.0: target 3 wakeup 0 error 0 > [ 8829.443524] xhci_hcd 0000:03:00.0: target 3 wakeup 1 error 0 > [ 8829.459506] iwlwifi 0000:02:00.0: target 3 wakeup 0 error 0 > [ 8829.459560] pci 0000:00:1f.3: target 0 wakeup 0 error 0 > [ 8829.459607] pci 0000:00:1f.0: target 0 wakeup 0 error 0 > [ 8829.475458] ehci_hcd 0000:00:1d.0: target 3 wakeup 1 error 0 > [ 8829.491433] ehci_hcd 0000:00:1a.0: target 3 wakeup 1 error 0 > [ 8829.507416] pci 0000:00:16.0: target 3 wakeup 0 error 0 The entries above are left over from the earlier test. > [ 9419.750158] atl1c 0000:04:00.0: target 3 wakeup 0 error 0 > [ 9419.766134] pci 0000:03:00.0: target 3 wakeup 1 error 0 > [ 9419.782126] iwlwifi 0000:02:00.0: target 3 wakeup 0 error 0 > [ 9419.782181] pci 0000:00:1f.3: target 0 wakeup 0 error 0 > [ 9419.782230] pci 0000:00:1f.0: target 0 wakeup 0 error 0 > [ 9419.798087] pci 0000:00:1d.0: target 3 wakeup 1 error 0 > [ 9419.814064] pci 0000:00:1a.0: target 3 wakeup 1 error 0 > [ 9419.830031] pci 0000:00:16.0: target 3 wakeup 0 error 0 Evidently the script unbinds xhci-hcd too. Did you check to make sure it is unrelated to the suspend problem? Anyway, this shows that the EHCI controllers are being set to the same power state with the same wakeup settings in both cases. And yet one hangs the computer while the other doesn't. Here's another rather drastic test you can do. In drivers/usb/host/ehci-pci.c:ehci_pci_suspend(), call ehci_reset(ehci) just before the final return statement. That should leave the hardware in exactly the same state as if ehci-hcd had been unbound. Alan Stern -- 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
