Ubuntu
linux-source-2.6.17 package

vfat fs corruption on USB attached drive with Kubuntu edgy

Bug #66184 reported by Ralf Muehlen on 2006-10-14

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Invalid	Undecided	Unassigned
	linux-source-2.6.17 (Ubuntu)	Won't Fix	Undecided	Unassigned

Bug Description

Binary package hint: linux-image-2.6.17-10-386

Kubuntu edgy corrupted the vfat filesystem on 2 usb mass storage devices (Sandisk MP3 player 512 MB).

In both cases writing or deleting files did not finish after waiting 10 or more minutes. Killing the cp or rm commands did not work, so I disconnected the drives. In one case I was able to fsck the drive under dapper. fsck on the other drive fails with an malloc error.

My hunch is the the cause lies with the USB subsystem. After a few hours after reboot the USB mouse stops working, and any newly connected USB devices won't work.

dmesg:
[17185436.908000] Initializing USB Mass Storage driver...
[17185436.908000] scsi2 : SCSI emulation for USB Mass Storage devices
[17185436.908000] usb-storage: device found at 2
[17185436.908000] usb-storage: waiting for device to settle before scanning
[17185436.908000] usbcore: registered new driver usb-storage
[17185436.908000] USB Mass Storage support registered.
[17185441.908000] usb-storage: device scan complete
[17185441.916000] Vendor: SanDisk Model: Sansa m230 Rev: 1.30
[17185441.916000] Type: Direct-Access ANSI SCSI revision: 00
[17185441.968000] SCSI device sdb: 1009664 512-byte hdwr sectors (517 MB)
[17185442.056000] sdb: Write Protect is off
[17185442.056000] sdb: Mode Sense: 37 00 00 08
[17185442.056000] sdb: assuming drive cache: write through
[17185442.124000] SCSI device sdb: 1009664 512-byte hdwr sectors (517 MB)
[17185442.212000] sdb: Write Protect is off
[17185442.212000] sdb: Mode Sense: 37 00 00 08
[17185442.212000] sdb: assuming drive cache: write through
[17185442.212000] sdb: sdb1
[17185442.224000] sd 2:0:0:0: Attached scsi removable disk sdb
[17185442.224000] sd 2:0:0:0: Attached scsi generic sg1 type 0
[17185482.324000] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!

dmesg, after USB stopped working:
disconnecting USB mouse and drive
[17185979.956000] usb 3-2: USB disconnect, address 2
[17190331.120000] usb 1-2: USB disconnect, address 2

reconnecting mouse
[17190335.120000] ohci_hcd 0000:00:13.0: IRQ INTR_SF lossage

reconnecting USB drive
[17190335.680000] usb 1-2: new low speed USB device using ohci_hcd and address 3
Note that the OS know considers the drive to be "low speed".

Revision history for this message

Ralf Muehlen (launchpad-muehlen) wrote on 2006-10-14:

lshal Edit (77.8 KiB, text/plain)

Attached is the output of lshal. This is after an dist-upgrade and reboot however.

Revision history for this message

bazzdee (bazz-dee) wrote on 2006-12-15:

I'm experiencing the same problem with my usb mouse on my notebook.
dmesg is the same.

[17180384.988000] usb 1-1: USB disconnect, address 3
[17180388.988000] ohci_hcd 0000:00:13.0: IRQ INTR_SF lossage
[17180389.272000] ohci_hcd 0000:00:13.0: bad entry 179d2080

But my usb wlan stick keeps working for days.

Revision history for this message

Brian Murray (brian-murray) wrote on 2008-04-25:

We are sorry that we didn't get to your bug report earlier, but the 18 month support period for Edgy Eft, 6.10, has reached it's end of life and we are marking the linux-source-2.6.17 task as Won't fix. However, please note that I am opening a linux task for the actively developed kernel. It would be helpful if you could test your bug with the recently released version of Ubuntu - Hardy Heron. You should be able to test this bug with a Live CD which you can get from http://www.ubuntu.com/getubuntu/download . Thanks again and we appreciate your help.

Changed in linux-source-2.6.17:
status:	New → Won't Fix
Changed in linux:
status:	New → Incomplete

Revision history for this message

Brian Murray (brian-murray) wrote on 2008-05-27:

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.