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. thank you. On Thu, Oct 31, 2013 at 11:15 AM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > On Thu, 31 Oct 2013, Prasad Koya wrote: > >> I tried usbmon before forcing crash: > >> As this USB is on bus 1, I tried below: >> >> cat /sys/kernel/debug/usb/usbmon/1u >> >> I didn't see anything till I copied a file or did some activity on it. >> While cat'ing above, I copied a file to that flash with dd in another >> terminal and I got this: > > ... > >> But I'm seeing the issue in early boot. So is there any other way to >> get the usbmon traces out? > > That makes it more difficult. You can't use usbmon during early boot, > so your only option is to enable CONFIG_USB_STORAGE_DEBUG. The output > is more verbose, but we should be able to see what's going on. > > Alan Stern >
Attachment:
dmesg_with_usb_debug_config.gz
Description: GNU Zip compressed data
Attachment:
dmesg_with_usb_storage_debug.gz
Description: GNU Zip compressed data
