046d:c52b [XFX MI-A78S-8209] USB keyboard and mouse not detected with newer kernels

Bug #1265947 reported by Kyle Echols
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux
Unknown
Unknown
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

I have a Logitech wireless keyboard/mouse combo that uses a unifying receiver ([Logitech Unifying Device. Wireless PID:101b). Using Mythbuntu 12.04.3, fully patched, kernel version 3.8.0-35-generic the receiver, keyboard, and mouse all function correctly. Using ubuntu 14.04 (12/28 Daily) and 13.10, these devices do not work reliably. Sometimes they are not available after a reboot, other times, they will just stop responding after not being used for a few minutes. In either case, at least one reboot is required to get the keyboard and mouse to be detected and work again. I found this issue while troubleshooting a separate bug, 1264636 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1264636), from the research I've done, this appears to be similar to https://bugzilla.kernel.org/show_bug.cgi?id=60507

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.12.0-7-generic 3.12.0-7.15
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
Uname: Linux 3.12.0-7-generic x86_64
ApportVersion: 2.12.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 2907 F.... pulseaudio
CasperVersion: 1.336ubuntu1
Date: Sat Jan 4 00:51:35 2014
LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131228)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.12.0-7-generic N/A
 linux-backports-modules-3.12.0-7-generic N/A
 linux-firmware 1.117
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/05/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MI-A78S-8209
dmi.board.vendor: XFX
dmi.board.version: Ver1.1
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd01/05/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnXFX:rnMI-A78S-8209:rvrVer1.1:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
Kyle Echols (kyleechols) 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
Kyle Echols (kyleechols)
description: updated
penalvch (penalvch)
summary: - usb keyboard and mouse not detected with newer kernels
+ 046d:c52b [XFX MI-A78S-8209] USB keyboard and mouse not detected with
+ newer kernels
Revision history for this message
penalvch (penalvch) wrote :

Kyle Echols, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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.13-rc6

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-bisect needs-upstream-testing regression-release
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Kyle Echols (kyleechols) wrote :

The keyboard and mouse are working with Mythbuntu 12.04.3 using kernel 3.13-rc6-trusty, HDMI audio is also working. However, the nvidia binary driver versions 3.04 and 3.31 are failing to load with this kernel, so I'm without desktop acceleration.

tags: added: kernel-fixed-upstream kernel-fixed-upstream-v3.13-rc6
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Kyle Echols, thank you for performing the requested test. As the latest Trusty is based on v3.12.4-trusty, the next step is to fully reverse commit bisect from:
v3.13-rc6-trusty/
v3.13-rc5-trusty/
v3.13-rc4-trusty/
v3.13-rc3-trusty/
v3.13-rc2-trusty/
v3.13-rc1-trusty/
v3.12.6-trusty/
v3.12.5-trusty/
v3.12.4-trusty/

In order to find the fix commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

tags: added: needs-reverse0bisect
removed: needs-bisect
tags: added: needs-reverse-bisect
removed: needs-reverse0bisect
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Kyle Echols (kyleechols) wrote :

I have booted through the following kernels, with the results listed:
Current -RC build - works
3.12.6-trusty - works
3.12.5-trusty - works
3.12.4-trusty - wouldn't boot, No init found -- confirmed boot settings matched working 3.8 kernels in grub configs, ran update-grub, still didn't boot
3.12.3-trusty - works
3.12.0-saucy - works

Please let me know if I need to continue testing further back.

Revision history for this message
penalvch (penalvch) wrote :

Kyle Echols, thank you for performing the requested tests. Given this problem is reproducible in the Ubuntu downstream kernel, but not the upstream kernel it was rebased from, I'll mark this Triaged for now, as the issue would seem to be due to a downstream patch/configuration.

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