Ubuntu does not recognized wireless mouse and keyboard after startup for couple of minutes

Bug #1534260 reported by Piotr Wieczorek
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
High
Unassigned

Bug Description

Looks like a regression after recent kernel upgrade.
After starting up the system ubuntu fails to recognize the wireless keyboard and mouse for about 2 minutes.
Afterwards it works correctly.

The integrated keyboard+mouse model is Logitech k400r

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-generic 4.2.0.23.25
ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
Uname: Linux 4.2.0-23-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pwiecz 2004 F.... pulseaudio
 /dev/snd/controlC1: pwiecz 2004 F.... pulseaudio
CurrentDesktop: Unity
Date: Thu Jan 14 19:40:27 2016
InstallationDate: Installed on 2014-02-02 (711 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Gigabyte Technology Co., Ltd. H87N-WIFI
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic.efi.signed root=UUID=98e2c9a3-1a1a-4d21-b370-79d0cde7b5f2 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-23-generic N/A
 linux-backports-modules-4.2.0-23-generic N/A
 linux-firmware 1.149.3
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to wily on 2015-10-23 (83 days ago)
dmi.bios.date: 05/02/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F7
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87N-WIFI
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd05/02/2014:svnGigabyteTechnologyCo.,Ltd.:pnH87N-WIFI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87N-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: H87N-WIFI
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Piotr Wieczorek (pwiecz-f) 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
Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-bisect
penalvch (penalvch)
tags: added: bios-outdated-f9
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Piotr Wieczorek (pwiecz-f) wrote :

1) output of the command:
F9
08/18/2015

2) Unfortunately there was no improvement

The keyboard works correctly if I run Windows instead of Ubuntu Linux.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Piotr Wieczorek, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: latest-bios-f9
removed: bios-outdated-f9
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Piotr Wieczorek (pwiecz-f) wrote :

I've installed kernel 4.5rc1 and the problem vanished.

When I was installing the kernel it complained that it may not be able to install i915 firmware (I'm not sure if it succeeded).

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Piotr Wieczorek (pwiecz-f) wrote :

Because of problems with graphics on v4.5-rc1 (maybe because I'm using intel-linux-graphics-installer, or maybe it's the i915 drivers issues) I've tried earlier kernels.

On v4.4 the bug seem to be fixed (complains about i915 firmware)
On v4.3.4 the bug is still there (does not complain about the firmware)

On both of them there were some display issues (flickering screen), so I had to go back to the standard 15.10 kernel.

penalvch (penalvch)
tags: added: kernel-fixed-upstream kernel-fixed-upstream-4.5-rc1
Revision history for this message
penalvch (penalvch) wrote :

Piotr Wieczorek, the next step is to fully reverse commit bisect from kernel 4.2 to 4.5-rc1 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

After the fix commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

tags: added: needs-reverse-bisect
removed: needs-bisect
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Piotr Wieczorek (pwiecz-f) wrote :

$ git bisect good ae35b56e367b9fef7f5de701cf8c1c3dd954dded
3d8acd1f667b45c531401c8f0c2033072e32a05d is the first bad commit
...

As "bad" means "good" in the case of reverse bisect, the commit containing the fix seems to be 3d8acd1f667b45c531401c8f0c2033072e32a05d

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: cherry-pick reverse-bisect-done
removed: needs-reverse-bisect
Changed in linux (Ubuntu):
importance: Medium → High
status: Confirmed → 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.