On Fri, 17 Jun 2011, Andrey Rahmatullin wrote: > On Fri, Jun 17, 2011 at 10:14:16AM -0400, Alan Stern wrote: > > > > Okay, the next step is to try and find out exactly where the ehci > > > > suspend procedure is hanging. The patch below adds a bunch of > > > > printouts at various spots throughout the procedure. Let's see what > > > > shows up. > > > I don't see any of these new messages. > > Are you sure the new ehci-hcd.ko module was loaded when you ran the > > test? > Yes. I'll triple-check though. > > > Another thing you should do when testing: > > > > echo 9 >/proc/sys/kernel/printk > > > > (Or equivalently, Alt-SysRq-9 on the keyboard.) I should have > > mentioned that before sending the test patch. Oh well.... > I used dmesg -n8. Okay, then you must have seen all the verbose PM debugging messages. Which means the last suspend callback to run was for the 1-1 device rather than the usb1 device, right? If so, it means I was looking in the wrong place. 1-1 is the internal rate-matching hub, whereas usb1 is the EHCI controller's root hub. Can you add your own dev_info() statements to the hub_quiesce() and hub_suspend() routines in drivers/usb/core/hub.c, or should I send a patch? 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
