On Mon, 22 Aug 2005, Dave North wrote: > Okay, did it, and I'm attaching three files. The first is the standard > boot dmesg from /var/log/dmesg.
That part doesn't really matter. > The second (dmesg.txt) is the dmesg > buffer after plugging in. Note this has filled the buffer because, > after the first time I plugged it in with the kernel patch, it has > failed at first (first time I did this it worked through enumeration > w/o complaint -- that seems to be a tradition with this hardware). This is the one that matters. But there's no debugging information from usb-storage! Did you turn on CONFIG_USB_STORAGE_DEBUG and rebuild the driver? If you end up filling the dmesg buffer, the regular syslog files should end up doing about as well. Just be sure that syslogd is configured to capture kernel debug-level messages somewhere. > The > third (dmesgfinal.txt) is the dmesg buffer after unplugging. This doesn't matter either. > I can probably figure out how to enlarge that buffer if this isn't > enough spew..! > > Dave (Brownell) indicated he wasn't interested in this, so I'm just > sending it to you. In a while I'll be rebuilding a newer kernel with an > updated patch, tested in stages. Send your messages to the mailing list as well as to me. That way other people can see them and they are available in the archives. Alan Stern ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
