> I'm struggling a bit to work out if this is a scsi bug, a USB bug, an MMC bug > or whatever. But it's a bug. > > Michal, can you please track this as a post-2.6.22 regression? > > Others: can you please take a look at the dmesg output, see if we can work > out which subsystem is (newly) failing?
There's not enough info in the dmesg. We really need the dmesg when it's failing, not when it's booting up, so after the blockdev --rereadpt /dev/sda and the fdisk /dev/sda If no messages at all, that's also significant (and I'd guess problems with media change propagation). James ------------------------------------------------------------------------- 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
