On Tue, 31 Jul 2007, Kostas Peletidis wrote: > Hi Alan, > > I enabled CONFIG_USB_DEBUG and reproduced the problem but didn't see any > messages in the dmesg output. To ensure that the debug code was indeed > built in I unplugged the disk then plugged it back in. I got quite a few > messages, here are the last of them:
> I see most of these messages at boot time even with older 2.6 kernels. Yes, they are normal. > The problem appears after the "device scan complete" message is traced. > > The patch that caused this issue was added between the 2.6.21.5 and > 2.6.22 releases. The only patch that led to 2.6.21.6 had to do with > nf_conntrack_h323 so this leaves us with the patches between 2.6.21.6 > and 2.6.22. There are quite a few usb changes in that changelog so I was > hoping that someone might recognise/remember something relevant. I'd guess that this was caused by a change somewhere else in the kernel, not in the USB stack. My advice now is the same as Matt's was: turn on CONFIG_USB_STORAGE_DEBUG and see what you get. Alan Stern ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
