System freezes after plugging in a usb flash drive

[bled]

As soon as I plug in a usb flash drive (any mass storage media) the whole system freezes. I cannot even switch to the terminal and SysRQ keys also don't work.
I am using the Asus A8N-SLI Premium 939 motherboard.

ProblemType: Bug
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bled 2385 F.... pulseaudio
 /dev/snd/pcmC0D0p: bled 3167 F...m banshee-1
 /dev/snd/timer: bled 3167 f.... banshee-1
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'CK804'/'NVidia CK804 with ALC850 at irq 22'
   Mixer name : 'Realtek ALC850 rev 0'
   Components : 'AC97a:414c4790'
   Controls : 42
   Simple ctrls : 27
Card1.Amixer.info:
 Card hw:1 'UART'/'MPU-401 UART at 0x330, irq 10'
   Mixer name : ''
   Components : ''
   Controls : 0
   Simple ctrls : 0
Card1.Amixer.values:

Date: Mon Nov 16 09:59:53 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=ae2aed80-3e96-4f9a-ad03-2371e6cbbcb1
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: root=UUID=6901cc6a-3d2b-4bf7-b87d-265d3f9735c5 ro quiet splash vga=795
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:

SourcePackage: linux
Uname: Linux 2.6.31-14-generic x86_64
UserAsoundrc:
 # ALSA library configuration file

 # Include settings that are under the control of asoundconf(1).
 # (To disable these settings, comment out this line.)
 </home/bled/.asoundrc.asoundconf>
WpaSupplicantLog:

dmi.bios.date: 01/18/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS A8N-SLI Premium ACPI BIOS 1011-005
dmi.board.name: A8N-SLI Premium
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.02
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-SLIPremiumACPIBIOS1011-005:bd01/18/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-SLIPremium:rvr1.02:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[josarn (barefoot4087)]

Seems the "usb_storage" isn't loaded for some reason, the "sudo modprobe usb_storage" solved the issue for me so I included the module in /etc/modules so it will load at startup.

[josarn (barefoot4087)]

Forget what I said. It worked once but no more... How can it be that loading the "usb_storage" module works only once?

[bled (bledproject)]

I tried your approach and it didn't work for me (not once). This bug is really annoying. I really hope for a solution.

[josarn (barefoot4087)]

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/313603

Thought this bug report could be somehow related but including the ehci_hcd module in "/etc/initramfs-tools/modules" didn't work for me plus I realised afterwards that Bled has a nvidia chipset. Just to give all those notified something to read, don't mean to intrude...

[josarn (barefoot4087)]

Booted into Ubuntu from the installation CD as found in Ubuntu's homepage, and was able to plug USB storage device without the freezing issue (more than once this time... twice)

[bled (bledproject)]

I have tried plugging in a usb flash drive today and it was automatically mounted without problems. Seems like the last kernel update fixed the problem's cause.
Just for the record, the kernel I'm currently using:
2.6.31-17-generic #54-Ubuntu SMP

[josarn (barefoot4087)]

The kernel that is in use in my system is: "2.6.31-18-generic". Booted with kernel "2.6.31-17-generic" to confirm the issue was solved but the system still freezes when a USB storage device is plugged in (on both accounts).

[Poldi (poldi)]

I have the same problem on karmic and 2.6.31-17-generic. This started with the upgrade from 2.6.31-16-generic.

One other thing I noticed was that if I boot into recovery mode, the system keeps working when I plug in the usb drive and the log file looks like the attached 'works.txt'.

When booting normally, I get no errors (see attached 'hangs.txt', but the system hangs (ie. cursor freezes, cannot get to console, etc).

[josarn (barefoot4087)]

Issue persists. Kernel in use: 2.6.31-20-generic

[bled (bledproject)]

Contrary to what I reported a few weeks ago, I am still experiencing this issue, too. However, sometimes it seems to work without freezing and other times it does not. It works about once out of three of four times.
Kernel: 2.6.31-19-generic

[Poldi (poldi)]

Just happend to 'freeze' again when I plugged in an external USB drive.

The only message I get is as follows:

-------------------------------------
Feb 14 13:15:18 LeosLinux kernel: [ 31.484139] usb 3-3: usbfs: interface 1 claimed by usblp while 'usb' sets config #1
Feb 14 13:15:18 LeosLinux hp[2905]: io/hpmud/pp.c 627: unable to read device-id ret=-1
------------------------------------
 but as bled wrote this is intermittent.

[josarn (barefoot4087)]

All drives I had tried had FAT32 or NTFS filesystems. I have just tried a drive with an ext4 filesystem and the issue is still there, so I suppose it isn't related to a faulty filesystem support.

[Poldi (poldi)]

Just happened again. This time there were no messages in any of the log; it just hung until I rebooted.

I have so far seen the following behaviour plugging in the same external USB disk:

1) Everything work
2) System hangs. There is a message in the syslog relating to the USB drive having been plugged in. Removing drive and rebooting ok; everything works
3) System hangs. There are no messages in any logs about the USB dive having been plugged in. When rebooting, my RAID1 is being resynced!

In addition, what do we have to do so somebody takes notice of this and responds? I appreciate that only three people seem to be affected, but any hints would be helpful.

Cheers,

[josarn (barefoot4087)]

I am not very optimistic about seeing a solution to the issue soon. Once by mistake I configured my launchpad profile so I would recieve a copy of every new bug found in the different releases of Ubuntu and notified here. I don't now how big the Ubuntu's bug team is, but I am sure they have to priorize to an extreme.

[Poldi (poldi)]

I tend to agree with you. The question is, what's the alternative.

[josarn (barefoot4087)]

I had to find a way to keep backups, that's the main nuisance this issue causes me. Apart from the desktop affected by this, I have a netbook that is issue free (maybe because it is 32 bit cpu). I have two options, use the netbook as the backup device or use the netbook as a bridge between the desktop and usb storage devices. All in all, I am eager for a solution.

[josarn (barefoot4087)]

I have been comparing the output of dmesg of issue-free systems and others with this issue and the one big difference is this line that appears in systems with the problem: "ehci_hcd: cache line size of 64 is not supported".

[Poldi (poldi)]

Found a reference to this (very) old bug at https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/21613. Haven't tried the suggested fix, but will let you know outcome when I do.

[josarn (barefoot4087)]

kernel: [ 16.301442] Info fld=0x2b6, ILI
kernel: [ 16.301443] sr 2:0:0:0: [sr0] Add. Sense: Illegal mode for this track
kernel: [ 16.336351] sr 2:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
kernel: [ 16.336353] sr 2:0:0:0: [sr0] Sense Key : Illegal Request [current]

This apperead in the messages log files a few times when I inserted a USB Stick before the system freezing. As fas as I understand it, the USB Stick was identified as a CDROM by the system. So I had the stick inserted when accessing the BIOS because of this feature of the mobo (hope it is not widespread) where you can specify how the usb device should be configured. Changed the bios option from "Auto" to "Hard Disk" and rebooted with the stick still inserted. The BIOS tried to boot from the stick instead of the SATA hard drive, so I removed the stick and rebooted. Once Ubuntu was loaded I inserted the stick again and the usual messages from echi-hcd detecting a new high speed device appeared before the system freezing again.

[josarn (barefoot4087)]

Switched the Plug & Play OS from "yes" to "no", still freezes but no more CDROM confusion...

[josarn (barefoot4087)]

The last CDROM entry before the freeze was that of an actual CD, no entry was recorded for the USB device before the freeze... seems the confused one around here is me. Sorry...

[Jeremy Foshee (jeremyfoshee)]

Hi bled,

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 483483

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.]

[Poldi (poldi)]

I'll download the latest release and run off the live cd.

One problem, though, is that I cannot generate a report if the problem persists since the system freezes (as per my comment #9)

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

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