On Thu, Jan 23, 2014 at 01:24:55PM -0500, Alan Stern wrote: > On Thu, 23 Jan 2014, glphvgacs wrote: > > > i don't know what i'm looking for but i was listening to bus2 while kprinf > > was giving disconnect msg: > > > > http://bpaste.net/show/171349/ > > > > and see the attached for repeated blocks of msg (device number gets > > incremented by 1) > > Yes, that's right. The mouse was on bus 2. > > 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. > Is the mouse enabled for runtime suspend? Yuo can find out by reading > the file /sys/bus/usb/devices/2-1.6/power/control. If the file > contains "auto", try writing "on" to it. > > Alan Stern 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 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. -- 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
