On Thu, Jan 23, 2014 at 03:12:10PM -0500, Alan Stern wrote: > 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? nope, i'm booting off of that hd (IDE) that's hooked up to usb and yes i caught a lot of it's traffice since it was on bus2. could it have something to do with this? i'm moving to usb3 soon though. did you have a change to look at the systemd-udev msg in my previous posts? > > 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 > i will have to try this after moving to usb3. problem might even go away? -- 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
