kernel panic on "safely remove" USB 3.0 HDD

Bug #863092 reported by Tormod Volden
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux (Fedora)
Unknown
Unknown
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I experience a kernel panic on 3.0.0-12-generic-pae after clicking on "safely remove" of a USB drive partition. The drive is USB 3.0 but the panic happens both when connected to a USB 3.0 port and to a USB 2.0 port. The below messages are from the USB 2.0 port. The partition is NTFS. The disk also has a "virtual CD drive" with manuals and Windows drivers. I /think/ the panic can be avoided if I eject the virtual CD drive before the HDD partition.

I will attach a screenshot of the panic later. The panic is almost identical to the one in https://bugzilla.redhat.com/show_bug.cgi?id=739473#c5 and there is apparently a patch in https://lkml.org/lkml/2011/9/20/31

Sep 30 09:51:10 osmotormod kernel: [ 599.806195] usb 1-1.4: new high speed USB device number 4 using ehci_hcd
Sep 30 09:51:10 osmotormod kernel: [ 599.899419] scsi7 : usb-storage 1-1.4:1.0
Sep 30 09:51:16 osmotormod kernel: [ 605.295949] scsi 7:0:0:0: CD-ROM TOSHIBA Virtual CD Drive 0001 PQ: 0 ANSI: 6
Sep 30 09:51:16 osmotormod kernel: [ 605.297247] scsi 7:0:0:1: Direct-Access TOSHIBA STOR.E STEEL S 0001 PQ: 0 ANSI: 6
Sep 30 09:51:16 osmotormod kernel: [ 605.341069] sr0: scsi-1 drive
Sep 30 09:51:16 osmotormod kernel: [ 605.341073] cdrom: Uniform CD-ROM driver Revision: 3.20
Sep 30 09:51:16 osmotormod kernel: [ 605.341213] sr 7:0:0:0: Attached scsi CD-ROM sr0
Sep 30 09:51:16 osmotormod kernel: [ 605.341293] sr 7:0:0:0: Attached scsi generic sg7 type 5
Sep 30 09:51:16 osmotormod kernel: [ 605.341486] sd 7:0:0:1: Attached scsi generic sg8 type 0
Sep 30 09:51:16 osmotormod kernel: [ 605.345793] sd 7:0:0:1: [sdh] 1951477168 512-byte logical blocks: (999 GB/930 GiB)
Sep 30 09:51:16 osmotormod kernel: [ 605.346564] sd 7:0:0:1: [sdh] Write Protect is off
Sep 30 09:51:16 osmotormod kernel: [ 605.346570] sd 7:0:0:1: [sdh] Mode Sense: 1f 00 00 08
Sep 30 09:51:16 osmotormod kernel: [ 605.347312] sd 7:0:0:1: [sdh] No Caching mode page present
Sep 30 09:51:16 osmotormod kernel: [ 605.347317] sd 7:0:0:1: [sdh] Assuming drive cache: write through
Sep 30 09:51:16 osmotormod kernel: [ 605.349809] sd 7:0:0:1: [sdh] No Caching mode page present
Sep 30 09:51:16 osmotormod kernel: [ 605.349814] sd 7:0:0:1: [sdh] Assuming drive cache: write through
Sep 30 09:51:17 osmotormod kernel: [ 606.405361] sdh: sdh1
Sep 30 09:51:17 osmotormod kernel: [ 606.410419] sd 7:0:0:1: [sdh] No Caching mode page present
Sep 30 09:51:17 osmotormod kernel: [ 606.410424] sd 7:0:0:1: [sdh] Assuming drive cache: write through
Sep 30 09:51:17 osmotormod kernel: [ 606.410427] sd 7:0:0:1: [sdh] Attached SCSI disk
Sep 30 09:51:18 osmotormod ntfs-3g[2149]: Version 2010.3.6 external FUSE 28
Sep 30 09:51:18 osmotormod ntfs-3g[2149]: Mounted /dev/sdh1 (Read-Write, label "TOSHIBA HDD", NTFS 3.1)
Sep 30 09:51:18 osmotormod ntfs-3g[2149]: Cmdline options: rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=1000,dmask=0077
Sep 30 09:51:18 osmotormod ntfs-3g[2149]: Mount options: rw,nosuid,nodev,uhelper=udisks,silent,allow_other,nonempty,relatime,fsname=/dev/sdh1,blkdev,blksize=4096,default_permissions
Sep 30 09:51:18 osmotormod ntfs-3g[2149]: Global ownership and permissions enforced, configuration type 1
Sep 30 09:51:29 osmotormod ntfs-3g[2149]: Unmounting /dev/sdh1 (TOSHIBA HDD)

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 863092

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Tormod Volden (tormodvolden) wrote :

I run the Oneiric kernel on a Lucid system so if I run apport-collect this would be filed as a Lucid bug... Anyway, there are similar reports in bug 844957 and bug 835323. Also bug 852573 can be related. Bug 794117 has a reference to https://bugzilla.kernel.org/show_bug.cgi?id=36782 which can not be accessed at the moment.

If all these reports and confirmations are the same issue, it needs to be (manually) triaged and given higher importance than "medium".

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.0.0-12.19)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-12.19
Revision history for this message
Tormod Volden (tormodvolden) wrote :

Tested on linux-image-3.0.0-12-generic-pae_3.0.0-12.19_i386.deb

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.0.0-12.20)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-12.20
Revision history for this message
Tormod Volden (tormodvolden) wrote :

I am not retesting for this new kernel. Seriously, does anyone think this single, packaging change can do anything to this issue or the hundreds other bugs that gets this robot message? I think it is wasting a lot of people's time, which is quite respectless.

linux (3.0.0-12.20) oneiric-proposed; urgency=low

  [ Leann Ogasawara ]

  * Resolve linux-image-extra's install dependency
    - LP: #869270
 -- Leann Ogasawara <email address hidden> Mon, 26 Sep 2011 08:38:01 -0700

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Tormod Volden (tormodvolden) wrote :

There are some patches maybe addressing this in the Fedora bug. They say they have applied a new patch in the latest kernel, but unfortunately not which patch. Maybe it is this one: http://fsfla.org/svn/fsfla/software/linux-libre/freed-ora/current/f15/block-stray-block-put-after-teardown.patch

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

We would like to review the details of the panic. Do you have a screen shot or the text details of the panic that you could provide?

Revision history for this message
Tormod Volden (tormodvolden) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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