Re: PROBLEM: Mouse connected to USB-3 stopped working 2.6.38->39 regression

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Can you please adjust your mail client to wrap lines after 72 columns 
or so?

On Sat, 23 Apr 2011, Thomas Lindroth wrote:

> My Logitech G700 mouse that is connected to a USB-3 socket stopped working when I updated from 2.6.38 to latest Linus tree. I bisected the problem and found the first bad commit to be:
> 926008c9386dde09b015753b6681c502177baa30 USB: xhci: simplify logic of skipping missed isoc TDs
> Running origin/master with that patch reverted works fine.
> 
> This system is just a few days old and I'm still trying to work out the kinks. It's definitively possible that it's a hardware/bios error because the usb support is flakey. The commit message also made me believe this code takes care of exceptional events. The reason I have a mouse connected to a usb3 socket is because all usb2 sockets stops working if I plug it into any of them. The mouse is charged over usb so it has higher power requirement than normal usb devices. The mouse always works in the EFI bios no matter which socket it's connected to but the usb connected keyboard often fails to work in bootloaders like grub.

The power requirement shouldn't matter, so long as you don't plug the 
mouse into a bus-powered hub.

> When I run 2.6.28 and have the mouse connected to a usb2 socket I get lots of lines like this in dmesg:
>  usb 2-1.5: unlink qh1-3008/ffff88022f751280 start 0 [1/2 us]
>  hub 2-1:1.0: port 5 not reset yet, waiting 10ms
>  usb 2-1.5: reset full speed USB device using ehci_hcd and address 5
>  hub 2-1:1.0: port 5 not reset yet, waiting 10ms
>  hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0020
>  usb 2-1.5: ep0 maxpacket = 32
> 
> The post got too big when I tried to include the full dmesg. I'll have to send them in a separate post.

Your separate post didn't include the dmesg showing what happened when
you plugged the mouse into an EHCI controller.  In fact, a usbmon trace
of those events would be more useful than a dmesg log.  Can you post
one of those?  It doesn't need to start until just before you plug in
the mouse.

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


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux