On Thu, 30 May 2013, Grant wrote: > > There are two things you can do to help diagnose this. One is to build > > a kernel with CONFIG_USB_DEBUG enabled and then post the portion of the > > dmesg log showing what happens when you eject, unplug, and replug the > > device. > > I've enabled CONFIG_USB_DEBUG. Here is the output after mounting in > Thunar and then the sequence you specified: > > [ 2536.683944] EXT4-fs (sdb1): mounted filesystem with ordered data > mode. Opts: (null) > [ 2539.556586] sd 16:0:0:0: [sdb] Synchronizing SCSI cache > [ 2543.885054] xhci_hcd 0000:02:00.0: Port Status Change Event for port 3 > [ 2543.885070] xhci_hcd 0000:02:00.0: handle_port_status: starting port polling. > [ 2543.885156] hub 4-0:1.0: state 7 ports 2 chg 0000 evt 0002 > [ 2543.885255] xhci_hcd 0000:02:00.0: get port status, actual port 0 > status = 0x202c0 > [ 2543.885261] xhci_hcd 0000:02:00.0: Get port status returned 0x102c0 > [ 2543.885300] xhci_hcd 0000:02:00.0: clear port connect change, > actual port 0 status = 0x2c0 > [ 2543.885307] hub 4-0:1.0: warm reset port 1 > [ 2544.050074] xhci_hcd 0000:02:00.0: xhci_hub_status_data: stopping > port polling. > [ 2548.139118] xhci_hcd 0000:02:00.0: Port Status Change Event for port 3 > [ 2548.139132] xhci_hcd 0000:02:00.0: handle_port_status: starting port polling. > > I've attached dmesg.txt which contains the output after mounting in > Thunar, ejecting in Thunar, and waiting a minute or two. I can't make much out of that, except that the warm reset seems suspicious. Maybe it will mean more to Sarah. > I should also mention that unmounting in Thunar or using umount seems > to work fine and causes no problems. Ejecting seems to trigger the > problem. What about the second part of my suggestion, capturing a usbmon trace? That will probably be more informative. 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
