USB Mass Storage I/O Error

[Chris MacDonald]

I have both Intel D945GCLF and D510MO motherboards which produce I/O errors after running for a variable amount of time (usually inside of 72 hours). These motherboards are running with 1GB of RAM and a 4GB Micron eUSB SSD installed with Ubuntu 10.10. The Ubuntu installation is a server installation (no X) with Postgres and the OpenJDK JDK running my application (both Postgres and the application run as a non-root user).

After the device has been up for a certain amount of time, I/O errors and filesystem errors are printed to the terminal and each time the offending sector(s) is/are different. After this, I no longer have access to the file system and the vast majority of commands simply drop me back to the bash prompt without any output. These errors aren't logged in any system logs (the error attached was captured using serial output), there is no kernel oops or panic, nor does the system reboot but the system is rendered more or less unusable.

These errors started occurring for me with 10.04. I have several of these devices in the field and rolling them back to 9.10 has mitigated these errors. Since then, I've tried with 10.10 and the same errors have occurred. It is also worth noting that I've tried with both EXT3 and EXT4, both produce the same results. I've also set up a test case using a SATA hard drive connected to a SATA-to-USB bridge (05e3:0718 in lsusb) with the same results, which leads me to believe this isn't strictly a problem with the Micron eUSB modules I'm using.

If more information is required, please let me know. I have access to many of these devices so testing suggestions or fixes is not a problem. I started a thread on the Ubuntu Users list a while ago, for reference it can be found here: https://lists.ubuntu.com/archives/ubuntu-users/2010-November/233693.html
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse: Error: [Errno 2] No such file or directory
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xe0280000 irq 22'
   Mixer name : 'Realtek ALC662 rev1'
   Components : 'HDA:10ec0662,8086d625,00100101'
   Controls : 28
   Simple ctrls : 16
DistroRelease: Ubuntu 10.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: [Errno 2] No such file or directory
Package: linux (not installed)
ProcCmdLine: initrd=/initrd.img console=ttyS0,57600n8 root=UUID=dbedb55f-80fc-44e5-9b25-c615c73fb2a5 rootwait ro BOOT_IMAGE=/vmlinuz
ProcEnviron: SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Regression: Yes
RelatedPackageVersions: linux-firmware 1.34
Reproducible: Yes
RfKill: Error: [Errno 2] No such file or directory
Tags: lucid kconfig regression-release needs-upstream-testing
Uname: Linux 2.6.32-21-generic i686
UserGroups:

dmi.bios.date: 09/13/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: MWPNT10N.86A.0069.2010.0913.1432
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: D525MW
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE93082-301
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrMWPNT10N.86A.0069.2010.0913.1432:bd09/13/2010:svn:pn:pvr:rvnIntelCorporation:rnD525MW:rvrAAE93082-301:cvn:ct2:cvr:

[Jeremy Foshee (jeremyfoshee)]

Hi Chris,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 672751

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Chris MacDonald (chris-fourthandvine)]

apport information

[Chris MacDonald (chris-fourthandvine)]

apport information

[Chris MacDonald (chris-fourthandvine)]

apport information

[Chris MacDonald (chris-fourthandvine)]

apport information

[Chris MacDonald (chris-fourthandvine)]

apport information

[Chris MacDonald (chris-fourthandvine)]

apport information

[Chris MacDonald (chris-fourthandvine)]

apport information

[Chris MacDonald (chris-fourthandvine)]

apport information

[Chris MacDonald (chris-fourthandvine)]

apport information

[Chris MacDonald (chris-fourthandvine)]

apport information

[Chris MacDonald (chris-fourthandvine)]

apport information

[Chris MacDonald (chris-fourthandvine)]

apport information

[Chris MacDonald (chris-fourthandvine)]

apport information

[Chris MacDonald (chris-fourthandvine)]

apport information

[Chris MacDonald (chris-fourthandvine)]

Apologies for the delay, I have time on my hands to test this again. I've recreated the issue with the same hardware (same models, different physical units) and wil be testing the mainline kernel for Lucid shortly...

[Chris MacDonald (chris-fourthandvine)]

Attached are the copies of kernel output I get on successive tests as I do them, I'll update as I go. In this copy, over the weekend I ran the hardware using EXT3 rather than EXT4 just to be sure it wasn't a filesystem issue and sure enough I was able to produce the error on both.

With a mainline kernel installed I'm starting the test again, expect an update in the next day or two. For reference, this is what I've installed in terms of kernels:

ii linux-image-2.6.32-02063221-generic 2.6.32-02063221.201008271307 Linux kernel image for version 2.6.32 on x86
ii linux-image-2.6.32-21-generic 2.6.32-21.32 Linux kernel image for version 2.6.32 on x86

As an aside, I've switched to a D525MW from the D510MO, the apport submission above was done on the 525, the logs attached are from a 525 and from here on out I'll be sticking to the 525.

[Chris MacDonald (chris-fourthandvine)]

Well that didn't take long... using the mainline kernel produce the same error only minutes after startup (though the error does tend to produce itself after a unspecified length of time so I doubt much can be gleaned from this).

Attached is my updated error listing. Any direction here would be appreciated, I suspect that having tested with the mainline kernel the next step is to go upstream with my issues...

[Chris MacDonald (chris-fourthandvine)]

After looking around I found this...

https://bugzilla.kernel.org/show_bug.cgi?id=32432

Which looks suspiciously similar so I'm now running what I believe is the daily mainline kernel

ii linux-image-3.1.0-999-generic 3.1.0-999.201108220905

and we'll see what happens.

[penalvch (penalvch)]

Chris MacDonald, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.