[Feisty] non-fatal kernel oops after re-plugging a USB drive

Bug #112718 reported by reini
2
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Brian Murray

Bug Description

Binary package hint: linux-source-2.6.20

I probably provoked this crash by removing a USB harddrive from a USB port and shortly afterwards plugging it back into the slot it was inserted into before.
The crash was non-fatal, i.e. apart from USB not working anymore, I could notice no ill effects on the system as a whole. Trying a 'sudo rmmod usbcore' resulted in rmmod hanging. I was able to reboot without noticing any further problems.
I have not been able to reproduce this crash.

Revision history for this message
reini (rrumberger) wrote :
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug does not meet the criteria for a stable release update and is being marked as Won't Fix for this particular version of the kernel. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates .
However, the issue that you reported is one that should be possible to test with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed kernel. You can find out more about the development release at http://www.ubuntu.com/testing/ .
If you do decide to test with the development release of Ubuntu please comment on this bug report and include at least the minimal information requested at http://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help.

Changed in linux-source-2.6.20:
assignee: nobody → brian-murray
importance: Undecided → Medium
status: New → Won't Fix
Revision history for this message
reini (rrumberger) wrote :

I've tried your suggestion and wasn't able to reproduce the bug.
I have however noticed that after the "waiting for device to settle before scanning" step, some error occures when the wait wasn't long enough. If I pull the USB drive straight away, the oops occurs. I guess increasing the "waiting before scanning" time will work around the issue.
(I can't find the exact error message in any of the logs and can't reproduce the problem here, so I'll try again when I'm home and write it down.)

Revision history for this message
reini (rrumberger) wrote :

For those interested, the error message I get via syslog is:

udevd-event[10845]: wait_for_sysfs: waiting for '/sys/devices/pci000:00/000:00:1d.7/usb5/5-1/5-1:1.0/host3/target3:0:0/3:0:0:0/ioerr_cnt' failed

It is possible to mount the device manually.
If I wait for some time, the crash doesn't seem to occur.
The crash doesn't seem occur at all in Gutsy.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.