On Thu, 23 Jan 2014, glphvgacs wrote: > > The trace shows that the mouse appears, and then apparently is unused. > > It kind of looks as though the mouse goes into runtime suspend, but not > > entirely. After 60 seconds, the mouse disconnects itself and then > > reconnects a little later. > > > > Does the mouse work at all? From what I can tell in the usbmon trace, > > nothing would happen if you moved it or pressed a button. > > works just fine. That's strange. Can you provide a usbmon trace that shows what happens when you use the mouse? And to keep down the size of the trace file, can you unplug the USB drive (the sdb drive) while running the test? > i don't have control under power, here is what i have: > wakeup_abort_count > wakeup_active > wakeup_total_time_ms > wakeup_active_count > wakeup_max_time_ms > wakeup_count > wakeup_last_time_ms > wakeup > persist > wakeup_expire_count Okay, so runtime suspend is not being used. > but really the question is whether this is related to the 30sec delay in > the boot. i couldn't care less with my logs getting filled up with that msg > if it's harmless. Delays during boot are hard to track down, because they occur before you have a chance to do anything about them. To work on this issue, you should boot with the USB drive unplugged. Start a usbmon trace and then plug in the drive. Continue the trace until after the delay ends. The trace will probably indicate the reason for the delay. 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
