Hi I'm attaching dmesg with old_scheme_first=1 and CONFIG_USB_STORAGE_DEBUG enabled. I compiled code with old_scheme_first set to 1. I see that it doesn't do get descriptor early in the loop so it doesn't run into khubd time out. But as I mentioned earlier usb-storage runs into some sort of error and resets the device 20s later it was first initialized. Thanks for looking. [ 1.787606] usb-storage: *** thread sleeping. [ 22.816061] usb-storage: command_abort called [ 22.816066] usb-storage: usb_stor_stop_transport called [ 22.816068] usb-storage: -- cancelling URB [ 22.816117] usb-storage: Status code -104; transferred 0/31 [ 22.816120] usb-storage: -- transfer cancelled [ 22.816122] usb-storage: Bulk command transfer result=4 [ 22.816125] usb-storage: -- command was aborted [ 22.816129] usb-storage: usb_stor_pre_reset [ 22.928057] usb 1-3: reset high speed USB device using ehci_hcd and address 2 [ 22.928062] usb 1-3: old_scheme_first 1 USE_NEW_SCHEME 0 retry_counter 0 [ 22.949263] usb-storage: usb_stor_post_reset [ 22.949270] usb-storage: usb_reset_device returns 0 [ 22.949274] usb-storage: scsi command aborted On Sun, Nov 3, 2013 at 8:22 AM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > On Sat, 2 Nov 2013, Prasad Koya wrote: > >> Hi >> >> I didn't have luck reproducing with both CONFIG_USB_DEBUG and >> CONFIG_USB_STORAGE_DEBUG. I could reproduce with each of them enabled >> separately. Am attaching the whole dmesg of both as zip files. If I >> should send them in different format, please let me know. I didn't see >> anything warnings or errors with USB_STORAGE_DEBUG enabled. The USB in >> question is "usb 1-3" on hub 1 and bus 1. I see no errors or warnings >> in that 5s timeout. Am trying with both 3.4 kernel and our older >> 2.6.32 kernel based images on bunch of setups. > > It looks like you didn't use usbcore.old_scheme_first=1. > > Alan Stern >
Attachment:
dmesg_config_usb_storage_old_scheme_first.gz
Description: GNU Zip compressed data
