Description of problem: After the pendrive is plugged in, the following appears: SCSI device sda: 256001 512-byte hdwr sectors (131 MB) sda: Write Protect is off sda: Mode Sense: 03 00 00 04 sda: assuming drive cache: write through sda:end_request: I/O error, dev sda, sector 256000 Buffer I/O error on device sda, logical block 256000 After the device is unplugged there are further messages and a subsequent oops (see attached files). Version-Release number of selected component (if applicable): 2.6.8-1.541 How reproducible: Always. Additional info: This seems to be a more general problem of Fedora-like kernels or kernel configs, I can't reproduce it with a vanilla kernel using custom config.
Created attachment 104264 [details] kernel log with the oops recorded
Created attachment 104265 [details] usb-storage debug output Note: since kernel-source is gone and I don't have time to set up a proper testbox, this log is from a different kernel (2.6.7-10.0.aur.9 specifically) that also doesn't properly handle the device (but won't oops for what it matters).
This is a manifestation of "first wave" of those (Cancel->Offline). We're past those and are wrestling with "NULL->Offline" now. Should be ready Real Soon Now...
mass update for old bugs: Is this still a problem with the 2.6.9 based update kernel ?
2.6.9-1.681_FC3 here Plugging in a MuVo trashes the USB subsystem after the error message described in this bug report (Buffer I/O error on device sda, logical block 256000) Trashed = Most USB related stuff hangs, including the kernel thread khubd and software like 'lsusb'. Reboot seems to be the only fix. Meanwhile an Oops may happen (but I couldn't reproduce one while trying for the purposes of adding this bug report). If I disable hotplug before inserting the MuVo then everything seems fine, until I manually insert the USB Mass storage module 'usb-storage'. The insmod hangs, the Buffer I/O error is reported as above, and USB is again trashed. This seems like a problem in usb-storage.ko, are there any recent patches to address this sort of thing? The MuVo is not fundamentally very different from several other devices I own, which work fine. It has the same chip (Sigmatel's STMP3410 iirc) but with different firmware.
Upgraded to newly available 2.6.10-1.737_FC3 using up2date / yum from FC3 updates MuVo is now recognised, appears on GNOME desktop, and I was able to copy files to and from it just like my other STMP3410 devices. I see there were many USB storage changes pending in 2.6.10 any one of which could be relevant, therefore presumably resolve bug and list 2.6.10-1.737_FC3 as version with fix. Thanks
Indeed, 2.6.10-1.1109_FC4 also works fine. Incidentally, plugging and unplugging the pendrive on a fresh 2.6.9-1.1049_FC4 causes a series of 73 oopses before the final panic. Wow.
How does the FC4 work for you?
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you.
This bug has been automatically closed as part of a mass update. It had been in NEEDINFO state since July 2005. If this bug still exists in current errata kernels, please reopen this bug. There are a large number of inactive bugs in the database, and this is the only way to purge them. Thank you.