USB 3.0 Iomega eGO causes Kernel Panic when plugged into USB 3.0 port

[Ben Schroeder]

Ubuntu version Oneiric Ocelot

I have a Dell Precision M6600 with 2 USB 3.0 ports and when I plug in my Iomega eGO 1 TB External drive I get a kernel panic. I can plug that exact drive into the USB 2.0 ports on the same computer with no issues. I can also plug in non usb 3.0 devices into the usb 3.0 ports w/o errors. It is just when I plug in the USB 3.0 device into the 3.0 port that the kernel panics.

If there is more information needed to troubleshoot/diagnose please let me know.

thanks

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-12-generic 3.0.0-12.20
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: bschroeder 1924 F.... pulseaudio
 /dev/snd/controlC0: bschroeder 1924 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xe3960000 irq 50'
   Mixer name : 'IDT 92HD90BXX'
   Components : 'HDA:111d76e7,102804a4,00100102'
   Controls : 15
   Simple ctrls : 10
Card1.Amixer.info:
 Card hw:1 'Generic'/'HD-Audio Generic at 0xe3840000 irq 51'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Thu Nov 3 15:40:41 2011
HibernationDevice: RESUME=UUID=33e7df9b-ac15-4319-9198-1d212d95066e
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Dell Inc. Precision M6600
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=2418e8e9-3809-4731-99df-39ffe6f6555d ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-12-generic N/A
 linux-backports-modules-3.0.0-12-generic N/A
 linux-firmware 1.60
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/02/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 04YY4M
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/02/2011:svnDellInc.:pnPrecisionM6600:pvr01:rvnDellInc.:rn04YY4M:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M6600
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

[Joseph Salisbury (jsalisbury)]

Can you attach a screen shot of the kernel panic?

Also, would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). 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 by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.1-rc9 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.1-rc9'.

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

Thanks in advance.

[Fabio Rotondo (fabio-rotondo)]

Same problem happens to me too.
I have a Sony VAIO VPCF2390X.

I am downloading the kernel linux-image-3.1.0-030100-generic_3.1.0-030100.201110241006_i386.deb
(I am using 32bit kernel with PAE) to see if it works

[Fabio Rotondo (fabio-rotondo)]

Hi,

just finished trying the latest vanilla kernel. It panics like the others. :-(

[Ben Schroeder (tehtide)]

Sorry this took a bit...

see attached dmsg output from current ubuntu shipping kernel.

I'm hoping that this help.

I will test out the other kernel in a bit.

[Ben Schroeder (tehtide)]

Tried with upstream mainline kernel version 3.1.0 RC10 and it didn't kernel panic this time. However the device isn't recognized at all. DMESG is as follows:

 303.834142] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
[ 303.874921] xhci_hcd 0000:0a:00.0: WARN: short transfer on control ep
[ 303.880271] xhci_hcd 0000:0a:00.0: WARN: short transfer on control ep
[ 303.885762] xhci_hcd 0000:0a:00.0: WARN: short transfer on control ep
[ 303.891682] xhci_hcd 0000:0a:00.0: WARN: short transfer on control ep
[ 303.921316] xhci_hcd 0000:0a:00.0: WARN: short transfer on control ep
[ 303.928305] xhci_hcd 0000:0a:00.0: WARN: short transfer on control ep
[ 304.176114] xhci_hcd 0000:0a:00.0: WARN: short transfer on control ep
[ 304.176493] scsi6 : uas
[ 304.178033] usbcore: registered new interface driver uas
[ 304.185081] scsi 6:0:0:0: Direct-Access OEM Ext Hard Disk 0000 PQ: 0 ANSI: 5
[ 304.199282] Initializing USB Mass Storage driver...
[ 304.199479] usbcore: registered new interface driver usb-storage
[ 304.199485] USB Mass Storage support registered.
[ 304.343652] scsi 6:0:0:1: CD-ROM Virtual CDROM PQ: 0 ANSI: 0
[ 304.344384] sd 6:0:0:0: Attached scsi generic sg3 type 0
[ 304.445761] sr1: scsi-1 drive
[ 304.446245] sr 6:0:0:1: Attached scsi CD-ROM sr1
[ 304.446566] sr 6:0:0:1: Attached scsi generic sg4 type 5
[ 304.495594] sd 6:0:0:0: [sdc] Sector size 0 reported, assuming 512.
[ 304.495610] sd 6:0:0:0: [sdc] 1 512-byte logical blocks: (512 B/512 B)
[ 304.495616] sd 6:0:0:0: [sdc] 0-byte physical blocks
[ 304.589249] xhci_hcd 0000:0a:00.0: WARN: babble error on endpoint
[ 304.589424] xhci_hcd 0000:0a:00.0: WARN Set TR Deq Ptr cmd invalid because of stream ID configuration
[ 304.589473] xhci_hcd 0000:0a:00.0: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 318.000496] init: tty1 main process (1650) killed by INT signal
[ 318.000565] init: tty1 main process ended, respawning
[ 335.414588] sd 6:0:0:0: uas_eh_abort_handler tag 0
[ 335.414599] sr 6:0:0:1: uas_eh_abort_handler tag -1
[ 335.414616] sd 6:0:0:0: uas_eh_device_reset_handler tag 0
[ 335.414623] sr 6:0:0:1: uas_eh_device_reset_handler tag -1
[ 335.414629] sd 6:0:0:0: uas_eh_target_reset_handler tag 0
[ 335.414635] sr 6:0:0:1: uas_eh_bus_reset_handler tag -1
[ 335.534401] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 335.618255] xhci_hcd 0000:0a:00.0: WARN: short transfer on control ep
[ 335.618329] xhci_hcd 0000:0a:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88021c5e5d00
[ 335.618336] xhci_hcd 0000:0a:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88021c5e5d40
[ 335.618342] xhci_hcd 0000:0a:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88021c5e5d80
[ 335.618348] xhci_hcd 0000:0a:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88021c5e5dc0
[ 335.856949] usb 4-1: URB BAD STATUS -108
[ 335.860127] usb 4-1: URB BAD STATUS -108
[ 335.863405] sr 6:0:0:1: Device offlined - not ready after error recovery
[ 335.863412] sd 6:0:0:0: Device offlined - not ready after error recovery
[ 335.863490] sd 6:0:0:0: rejecting I/O to offli...

[alexandre (alexandre-bustico-g)]

I have the same problem.
Since usb3 works on the same computer with sysrescuecd or mandriva, i was thinking that the problem
comes from the kernel configuration, which is not the same between sysrescuecd and ubuntu

Bisecting the .config file, I have found that the problem is due to option CONFIG_USB_UAS.

when recompiling a kernel with CONFIG_USB_UAS disabled, usb3 works well and fast !

Since it's a kernel bug, it should be transmitted to the kernel team.

Alexandre

[Karel Vervaeke (karel-vervaeke)]

I'm having the same problem on a Dell Precision M4600.
The disk is an eGo 1TB.
My kernel is: 3.0.0-14-generic.
Recompiling without CONFIG_USB_UAS works for me as well (based on apt-get source linux-image-3.0.0-14).
Let me know if there's anything else I can do to help.

[penalvch (penalvch)]

Ben Schroeder, thank you for reporting this bug 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 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. Please let us know your results.

Thanks in advance.

[Launchpad Janitor (janitor)]

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

[José Benavente (jbenaventev)]

This bug is still present on the latest quantal kernel

$uname -a
Linux Daneel 3.5.0-18-generic #29-Ubuntu SMP Fri Oct 19 10:26:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

A better workaround than rebuilding the kernel is to blacklist the uas module in /etc/modprobe.d/blacklist.conf

[penalvch (penalvch)]

José Benavente, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

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