05e3:0732 [P8H77-M PRO] Read errors and kernel panic - genesys USB3 internal card reader

Bug #1125136 reported by Oliver Story
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I have an Astrotek USB 3.0 internal card reader in my new computer, plugged into the USB3 header on the mainboard. The reader is apparently controlled by the Genesys gl3220 chip. It has two LEDs on the front: one red to indicate power, the other green to indicate card access/read/write. It also has a USB3 port on the front, which seems to work fine with USB sticks.

I have a 16GB SD card from my camera. When I put it in the SD slot, I would expect the card to be detected with the option given to open it in Nautilus etc. Instead, the green light flashes on and off repeatedly. dmesg reports a series of messages related to xHCI followed by "Unhandled error code". I will attach an excerpt from dmesg from this incident, which was reliably repeatable.

I have tried some different BIOS settings for the USB system:
- Firstly I changed xHCI from "Smart Auto" to "Enabled", logged in, then tested again with an old 256MB SD card. This was mounted automatically but when I tried to create a folder on the card I received a dialogue box reporting an input/output error. Dmesg reported similar xHCI errors as when I tried the 16GB card. I began to file a bug report, and part way through was dumped to a text console with a kernel panic message (which appeared to stem from usb_storage). As I have no other USB devices plugged in I presume this is again from the card reader.

- Secondly I toggled the ASUS Bios "EHCI handoff", which I think was "disabled" by default and I set it to "enabled". With this set I got a kernel panic shortly after logging in, but without inserting a card in the card reader at all. I have screenshots of these kernel panics if they are of use.

I am writing this bug report having rebooted the computer, reset the USB BIOS settings and restarted and the card reader's red power light is not on at all, hence the ubuntu-bug-generated output may not show the card reader.

WORKAROUND: The card reader continues to work as expected if the BIOS USB setting "xHCI" is set to "enabled".

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-generic 3.5.0.23.29
ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic x86_64
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: oliver 1942 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CurrentDmesg: [ 5.927548] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Date: Thu Feb 14 22:37:43 2013
HibernationDevice: RESUME=UUID=d9056455-e6ff-497b-acd2-908669c21bc8
InstallationDate: Installed on 2013-02-06 (7 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: System manufacturer System Product Name
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-23-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-23-generic N/A
 linux-backports-modules-3.5.0-23-generic N/A
 linux-firmware 1.95
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/10/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1005
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H77-M PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1005:bd12/10/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Oliver Story (oliver-story) wrote :
Revision history for this message
Oliver Story (oliver-story) wrote :
Revision history for this message
Oliver Story (oliver-story) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: Read errors and kernel panic - Astrotek / genesys USB3 internal card reader

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.8 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

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'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc7-raring/

Changed in linux (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete
Revision history for this message
Oliver Story (oliver-story) wrote :

I have tested upstream 3.8.0-rc7

The bug can be reproduced upstream. However in the course of testing I have found settings that appear to work on both kernels.

It appears the bug is dependent not only on BIOS settings, but on whether the last boot was a hard boot or soft reset / shutdown -r

Hence my conclusion that BIOS setting "xHCI: enabled" caused a kernel panic appears incorrect.

I have played around some more with the BIOS settings and with the following both my SD cards are detected and working, both on upstream and current Ubuntu 12.10 kernel, 3.5.0:
EHCI: enabled
Legacy USB support: enabled
Legacy USB3 support: enabled
xHCI: enabled
EHCI handoff: disabled

A configuration that causes unhandled errors in dmesg when I insert an SD card, both upstream and Ubunty stock kernels, is:
EHCI: enabled
Legacy USB support: enabled
Legacy USB3 support: enabled
xHCI: auto
EHCI handoff: disabled

With this configuration I am also getting crashes / kernel panic after boot & login, which can happen when there is no activity at the terminal. Actually it's not clear if these are linked to the SD card problems, or a separate bug.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
marian szczepkowski (8-4arian-n) wrote :

I have a similar issue with a genesys USB hub, my dmesg produces this when it's acting up and will seem to crash my machine every time. As my keyboard is USB it may be that it just hangs the USB systems and that stops all input, the only solutuion is a button reset to get the machine working again. The resolution appears to be disabling all power to the hub, turning off power to the PC, plug the device in and then boot. The USB ports always maintain power so driver or something in the hub does not appear to reset the hub properly.

[ 63.056934] xhci_hcd 0000:02:00.0: Timeout while waiting for address device command
[ 63.260327] usb 9-1: device not accepting address 6, error -62
[ 63.260391] xhci_hcd 0000:02:00.0: Bad Slot ID 5
[ 63.260394] xhci_hcd 0000:02:00.0: Could not allocate xHCI USB device data structures
[ 63.260399] hub 9-0:1.0: couldn't allocate port 1 usb_device
[ 63.403893] usb 8-1: new full-speed USB device number 10 using xhci_hcd
[ 63.405480] usb 8-1: Device not responding to set address.
[ 63.608869] usb 8-1: Device not responding to set address.
[ 63.810676] usb 8-1: device not accepting address 10, error -71
[ 63.922358] usb 8-1: new full-speed USB device number 11 using xhci_hcd
[ 63.923922] usb 8-1: Device not responding to set address.
[ 64.127308] usb 8-1: Device not responding to set address.
[ 64.329131] usb 8-1: device not accepting address 11, error -71
[ 64.440807] usb 8-1: new full-speed USB device number 12 using xhci_hcd
[ 64.442359] usb 8-1: Device not responding to set address.
[ 64.645749] usb 8-1: Device not responding to set address.
[ 64.847600] usb 8-1: device not accepting address 12, error -71
[ 64.959259] usb 8-1: new full-speed USB device number 13 using xhci_hcd
[ 64.960775] usb 8-1: Device not responding to set address.
[ 65.164188] usb 8-1: Device not responding to set address.
[ 65.366047] usb 8-1: device not accepting address 13, error -71
[ 65.366064] hub 8-0:1.0: unable to enumerate USB device on port 1
[ 70.590506] xhci_hcd 0000:02:00.0: Timeout while waiting for address device command
[ 75.779078] xhci_hcd 0000:02:00.0: Timeout while waiting for address device command
[ 75.982469] usb 9-1: device not accepting address 7, error -62
[ 75.982540] xhci_hcd 0000:02:00.0: Bad Slot ID 6
[ 75.982542] xhci_hcd 0000:02:00.0: Could not allocate xHCI USB device data structures
[ 75.982545] hub 9-0:1.0: couldn't allocate port 1 usb_device

The

Revision history for this message
Aleksander (Sasza) Kijek (saszasasha) wrote :

Hi, I have a modecom usb 3.0 card reader, that's listed as Genesys Logic, Inc. through 'lsusb'.
Through 'dmesg' I get same info "Device not responding to set address" and "unable to eunmerate USB device on port 2".
The computer, dell xps 13, ubuntu 13.04 x86_64, kernel 3.8.0-26-generic.

This is what I get in 'dmesg' after disconnecting and connecting again:
[ 239.565612] usb 4-2: USB disconnect, device number 2
[ 239.570440] usb 4-2: Set SEL for device-initiated U1 failed.
[ 239.570444] usb 4-2: Set SEL for device-initiated U2 failed.
[ 243.953145] hub 3-0:1.0: unable to enumerate USB device on port 2
[ 244.193085] usb 4-2: new SuperSpeed USB device number 3 using xhci_hcd
[ 244.212557] usb 4-2: New USB device found, idVendor=05e3, idProduct=0732
[ 244.212568] usb 4-2: New USB device strings: Mfr=0, Product=1, SerialNumber=2
[ 244.212573] usb 4-2: Product: USB Storage
[ 244.215985] scsi7 : usb-storage 4-2:1.0
[ 245.212186] scsi 7:0:0:0: Direct-Access Generic STORAGE DEVICE 0542 PQ: 0 ANSI: 0
[ 245.214609] sd 7:0:0:0: Attached scsi generic sg1 type 0
[ 245.216832] sd 7:0:0:0: [sdb] Attached SCSI removable disk

penalvch (penalvch)
tags: added: bios-outdated-1101 needs-upstream-testing regression-potential
tags: added: kernel-bug-exists-upstream-v3.8-rc7
removed: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
summary: - Read errors and kernel panic - Astrotek / genesys USB3 internal card
- reader
+ 05e3:0732 [P8H77-M PRO] Read errors and kernel panic - genesys USB3
+ internal card reader
Revision history for this message
Oliver Story (oliver-story) wrote :

Hello Chris

I have installed the updated BIOS (1301).

I am now using Ubuntu 13.04, with stock kernel 3.8.0-30-generic x86_64. This test is with the stock kernel.

The card reader continues to work as expected if the BIOS USB setting "xHCI" is set to "enabled", as per comment #6. This means that when an SD card is inserted, I get a dialogue box asking me what action I want to take.

If I set xHCI to "auto" in the BIOS then when I insert an SD card into the card reader, it takes some seconds before anything happens. The green light on the card reader then starts flashing, as if the card is being read. Nothing happens on screen. The green light keeps flashing intermittently for several minutes. The card does not show up in the file browser. dmesg shows a series of errors, similar to those in comment #2. After a few minutes (as I was typing this) the computer went into a kernel panic (flashing lights on the keyboard; dumped to terminal; no response).

Output of the command showing bios version & date:

oliver@correa$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
[sudo] password for oliver:
1301
06/07/2013

Please let me know if I should repeat this test with the latest upstream kernel.

Regards
Oliver

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: latest-bios-1301
removed: bios-outdated-1101
description: updated
Revision history for this message
penalvch (penalvch) wrote :

Oliver Story, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc7

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: needs-crash-log
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
david.barbion (david-barbion) wrote :

For those who still have the problem (like me), I manage to fix it by upgrading the firmware of my card reader.
I attach the archive that permits to upgrade. Unfortunately, the program works only with windows but it works with virtualbox and USB sharing.

Changed in linux (Ubuntu):
status: Expired → Opinion
penalvch (penalvch)
Changed in linux (Ubuntu):
importance: High → Medium
status: Opinion → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.