USB 3.0 regression after upgrading to 3.2.0-64 kernel

Bug #1333229 reported by Roman Shipovskij
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

After upgrading to 3.2.0-64 kernel wireless mouse stopped working but keyboard still works
Problem occurred with next Wireless Kit (keyboard+mouse):
04f2:1123 Chicony Electronics Co., Ltd Asus Wireless Keyboard and Mouse
04f2:0836 Chicony Electronics Co., Ltd Pleomax Wireless Keyboard and Mouse

from dmesg:
# dmesg |grep generic-usb
[ 3.043949] generic-usb 0003:04F2:0963.0001: input,hidraw0: USB HID v1.11 Keyboard [Chicony 2.4G Multimedia Wireless Kit] on usb-0000:00:12.0-3/input0
[ 3.059228] generic-usb 0003:04F2:0963.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Chicony 2.4G Multimedia Wireless Kit] on usb-0000:00:12.0-3/input1
[ 635.024628] generic-usb 0003:04F2:0836.0003: input,hidraw2: USB HID v1.11 Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-0000:05:00.0-2/input0
[ 655.024520] generic-usb: probe of 0003:04F2:0836.0004 failed with error -110
[ 680.024656] generic-usb: probe of 0003:04F2:0836.0005 failed with error -110
[ 686.324531] generic-usb 0003:04F2:0836.0006: input,hidraw2: USB HID v1.11 Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-0000:05:00.0-2/input0
[ 706.324634] generic-usb: probe of 0003:04F2:0836.0007 failed with error -110
[ 731.328465] generic-usb: probe of 0003:04F2:0836.0008 failed with error -110
[ 732.155547] generic-usb 0003:04F2:0836.0009: input,hidraw2: USB HID v1.11 Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-0000:05:00.0-2/input0
[ 752.156459] generic-usb: probe of 0003:04F2:0836.000A failed with error -110
[ 777.156718] generic-usb: probe of 0003:04F2:0836.000B failed with error -110
[ 1236.880527] generic-usb 0003:04F2:0836.000C: input,hidraw2: USB HID v1.11 Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-0000:05:00.0-2/input0
[ 1256.880712] generic-usb: probe of 0003:04F2:0836.000D failed with error -110
[ 1281.880705] generic-usb: probe of 0003:04F2:0836.000E failed with error -110

With 3.2.0-63 kernel all works fine

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-64-generic-pae 3.2.0-64.97
ProcVersionSignature: Ubuntu 3.2.0-64.97-generic-pae 3.2.59
Uname: Linux 3.2.0-64-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 1: SB [HDA ATI SB], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb44000 irq 45'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 6
   Simple ctrls : 1
Card0.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Card1.Amixer.info:
 Card hw:1 'SB'/'HDA ATI SB at 0xfeb40000 irq 16'
   Mixer name : 'Realtek ALC269VB'
   Components : 'HDA:10ec0269,104384ff,00100100'
   Controls : 18
   Simple ctrls : 10
Date: Mon Jun 23 14:48:34 2014
HibernationDevice: RESUME=UUID=f22f0450-8574-4bb3-9992-fde733b437eb
MachineType: ASUSTeK Computer INC. ET2012A
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-64-generic-pae root=UUID=8e8ca8ab-ae5e-41bc-b008-7a15a613d9e0 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-64-generic-pae N/A
 linux-backports-modules-3.2.0-64-generic-pae N/A
 linux-firmware 1.79.14
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/30/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0306
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: ET2012A
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.01G
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0306:bd12/30/2011:svnASUSTeKComputerINC.:pnET2012A:pvr0306:rvnASUSTeKComputerINC.:rnET2012A:rvrRev1.01G:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: ET2012A
dmi.product.version: 0306
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
Roman Shipovskij (roman-shipovskij) wrote :
Revision history for this message
Roman Shipovskij (roman-shipovskij) wrote :

The problem occurs only when using USB 3.0 port

tags: added: regression-update
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Roman Shipovskij (roman-shipovskij) wrote :

With 3.2.0-65 kernel from proposed same problem

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.16 kernel[0].

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.16-rc1-utopic/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Roman Shipovskij (roman-shipovskij) wrote :

I think is a similar problem here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1330530

I will be able to test the latest upstream kernel after ~10 hours

Revision history for this message
Roman Shipovskij (roman-shipovskij) wrote :
tags: added: kernel-unable-to-test-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Maciej Puzio (maciej-puzio) wrote :

Roman, compared to bugs 1330530 and 1328984, you have a similar USB 3.0 controller: ASM1042 (this bug) vs ASM1042A (other bugs). So this may be the same issue. Would you be able to test the regression with other USB devices?

Revision history for this message
Roman Shipovskij (roman-shipovskij) wrote :

I tested next devices using USB 3.0 port with kernels 3.2.0-63/3.2.0-64:
04f2:1123 Chicony Electronics Co., Ltd Asus Wireless Keyboard and Mouse - works fine/doesn't works
04f2:0836 Chicony Electronics Co., Ltd Pleomax Wireless Keyboard and Mouse - works fine/doesn't works
04f2:0963 Chicony Electronics Co., Ltd Acer Wireless Keyboard and Mouse - works fine/works fine
046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse] - works fine/works fine
046d:08d7 Logitech, Inc. QuickCam Communicate STX - works fine/works fine
13fe:2240 Kingston Technology Company Inc. microSD card reader - works fine/doesn't works
0951:168e Kingston Technology DT Rubber 3.0 - works fine/works fine
04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] - works fine/works fine

all devices works fine using USB 2.0 port on both kernels

Revision history for this message
Maciej Puzio (maciej-puzio) wrote :

I'm trying to find similarities between this bug and the bugs I reported. Speaking about the devices mentioned above, but only those that cause problems:
1. Is any a USB 3.0 device?
2. If you boot with any of the problematic devices plugged in, do you experience boot problems of any kind (stuck, long delay, dropped to boot console, etc.)?
3. Does any of the problematic devices work after you give it sufficient time (in my testing, most devices would work after being plugged in for 18 minutes).
4. Do the error messages differ among problematic devices?
Thanks.

Revision history for this message
Roman Shipovskij (roman-shipovskij) wrote :

1. Only Kingston Technology DT Rubber 3.0, but it works
2. Only boot time longer for a couple of seconds
3. No, not working
4. I got next errors:

for 04f2:1123 Chicony Electronics Co., Ltd Asus Wireless Keyboard and Mouse:
[ 4231.386711] input: Chicony Wireless Device as /devices/pci0000:00/0000:00:15.3/0000:05:00.0/usb8/8-1/8-1:1.0/input/input12
[ 4231.387261] chicony 0003:04F2:1123.0006: input,hidraw2: USB HID v1.11 Keyboard [Chicony Wireless Device] on usb-0000:05:00.0-1/input0
[ 4251.384712] chicony: probe of 0003:04F2:1123.0007 failed with error -110

for 04f2:0836 Chicony Electronics Co., Ltd Pleomax Wireless Keyboard and Mouse:
[ 4477.019134] input: Chicony Samsung 2.4GHz Transceiver as /devices/pci0000:00/0000:00:15.3/0000:05:00.0/usb8/8-2/8-2:1.0/input/input13
[ 4477.024797] generic-usb 0003:04F2:0836.0008: input,hidraw2: USB HID v1.11 Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-0000:05:00.0-2/input0
[ 4497.024539] generic-usb: probe of 0003:04F2:0836.0009 failed with error -110

for 13fe:2240 Kingston Technology Company Inc. microSD card reader:
[ 4617.571196] scsi7 : usb-storage 8-2:1.0
[ 4618.569837] scsi 7:0:0:0: Direct-Access USB Reader 0001 PQ: 0 ANSI: 0 CCS
[ 4618.574382] sd 7:0:0:0: Attached scsi generic sg2 type 0
[ 4619.207133] sd 7:0:0:0: [sdc] 7733248 512-byte logical blocks: (3.95 GB/3.68 GiB)
[ 4650.185369] usb 8-2: reset high-speed USB device number 5 using xhci_hcd
[ 4650.205313] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep f3133600
[ 4650.205329] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep f313362c

As I see, when problematic device connected to USB 3.0 port it may cause problems for other devices connected to USB 3.0 port

Revision history for this message
Maciej Puzio (maciej-puzio) wrote :

This is interesting:
[ 4650.205313] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep f3133600
[ 4650.205329] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep f313362c

I am getting the same errors with most USB 3.0 devices that I tried. These errors come after a ~15 second delay, and this repeats in a loop for 18 minutes. Some other errors may also be thrown, usually related to udev or various timeouts.
However, with the USB3 SD reader that I tested, the errors came only once during boot, with only ~15 second total delay, and the boot then proceeded successfully, although the device subsequently did not work. This matches your observations.

This all suggests that we are experiencing the same root problem..

Revision history for this message
Maciej Puzio (maciej-puzio) wrote :

Problem has been identified and patch created. Please see the following link for details:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1330530/comments/15

Revision history for this message
Maciej Puzio (maciej-puzio) wrote :

The patch has been added to the upstream mainline kernel 3.17-rc3, and to the 3.16-stable tree. Please see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1330530/comments/16

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.