Adaptive keyboard breaks with sleep/resume

[Dean Henrichsmeyer]

I have a Lenovo X1 Carbon Gen2. It as the adaptive row of keys that change from function keys to volume, etc when you toggle the function key. It's always worked fine but with this kernel, after a few sleep/resumes, the entire row will go black. If I reboot it will return to normal. dmesg throws a bunch of these..

[29190.142959] thinkpad_acpi: EC reports that Thermal Table has changed
[30910.489925] thinkpad_acpi: unknown possible thermal alarm or keyboard event received
[30910.489931] thinkpad_acpi: unhandled HKEY event 0x60c0
[30910.489932] thinkpad_acpi: please report the conditions when this event happened to <email address hidden>
[30911.439252] thinkpad_acpi: unknown possible thermal alarm or keyboard event received
[30911.439258] thinkpad_acpi: unhandled HKEY event 0x60c0

though I'm not sure it's the cause of the failure.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-2-generic 4.4.0-2.16
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: dean 3316 F.... pulseaudio
 /dev/snd/controlC0: dean 3316 F.... pulseaudio
CurrentDesktop: Unity
Date: Fri Feb 5 08:34:46 2016
HibernationDevice: RESUME=UUID=5ce0185d-e833-4337-9655-9be9fcac3654
InstallationDate: Installed on 2015-11-03 (93 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 20A7002QUS
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-2-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-2-generic N/A
 linux-backports-modules-4.4.0-2-generic N/A
 linux-firmware 1.155
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2015-12-07 (59 days ago)
dmi.bios.date: 11/04/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: GRET46WW (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20A7002QUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 Pro
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7002QUS:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7002QUS:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20A7002QUS
dmi.product.version: ThinkPad X1 Carbon 2nd
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.5 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'.

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/v4.5-rc3-wily/

[Dean Henrichsmeyer (dean)]

Upstream kernel worked just fine - linux-image-4.5.0-040500rc3-generic_4.5.0-040500rc3.201602071930_amd64 is what I tested.

[penalvch (penalvch)]

Dean Henrichsmeyer, the next step is to fully reverse commit bisect from kernel 4.4 to 4.5-rc3 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

[Joseph Salisbury (jsalisbury)]

Thanks for testing, Dean. We next need to figure out if the fix came in with the -rc1 or rc2 kernel in 4.5. Can you test v4.5-rc1 and see if it fixes the bug? It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-rc1-wily/

If v4.5-rc1 exhibits the bug, then we should test v4.5-rc2 to see if it has the fix, or if it came with -rc3. v4.5-rc2 can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-rc2-wily/

If v4.5-rc1 does fix this bug, there is no need to test -rc2. We can bisect between v4.4 final and v4.5-rc1.

[Dean Henrichsmeyer (dean)]

4.5-rc1 exhibited the bug, I'm now testing 4.5-rc2

[Dean Henrichsmeyer (dean)]

Hi Joseph - I confirm this is fixed in 4.5-rc2.

[Dean Henrichsmeyer (dean)]

Also worth noting is that when running kernels that exhibit the bug, the LED backlighting of the keys on the keyboard doesn't work. On kernels where it's fixed (rc2, ga), the backlighting works fine.

[Joseph Salisbury (jsalisbury)]

I started a "Reverse" bisect between v4.5-rc1 and v4.5-rc2. The kernel bisect will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
d3f71ae711cebdeaff12989761f48bd4230e83d5

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1542188

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

[Dean Henrichsmeyer (dean)]

Hi Joseph - the test kernel up to d3f71ae711cebdeaff12989761f48bd4230e83d5 exhibits the bug, ready for the next one..

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, up to the following commit:
29d14f083522e5bc762256f68227d267118946c8

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1542188

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

[Dean Henrichsmeyer (dean)]

Sorry, kernel up to 29d14f083522e5bc762256f68227d267118946c8 also has the bug... next :)

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, up to the following commit:
d517be5fcf1a7feb06ce3d5f28055ad1ce17030b

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1542188

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

[Dean Henrichsmeyer (dean)]

Sorry, this one exhibits the bug as well..

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, up to the following commit:
54e3f3e30245abb0d47e3bc53a1b3c75434616f1

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1542188

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

[Dean Henrichsmeyer (dean)]

Hi Joseph,

I can confirm the kernel you built up to 54e3f3e30245abb0d47e3bc53a1b3c75434616f1 fixes the problem. That kernel does not exhibit the bug. :)

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, up to the following commit:
8c4e378e426d1b065a1e8d9f45b8bcc4905d3410

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1542188

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

[Dean Henrichsmeyer (dean)]

This kernel (up to 8c4e378e426d1b065a1e8d9f45b8bcc4905d3410) is also fine.

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, up to the following commit:
88867e3d0b7eea256c1cd432b0a3c7a21e8edf07

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1542188

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

[Dean Henrichsmeyer (dean)]

This kernel (88867e3d0b7eea256c1cd432b0a3c7a21e8edf07) exhibits the bug.

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, up to the following commit:
510ae0c994cb38fcf5033ad69eb8103552e335e8

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1542188

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

[Dean Henrichsmeyer (dean)]

This one (510ae0c994cb38fcf5033ad69eb8103552e335e8) has the bug. Thanks.

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, up to the following commit:
f3ca903fbbb0d26221a39cbebfe6dd4efbebd3ef

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1542188

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

[Dean Henrichsmeyer (dean)]

I can confirm that the latest xenial kernel (4.4.0-7-generic) doesn't exhibit the bug.

[Joseph Salisbury (jsalisbury)]

Thanks for the update, Dean. Would you say this bug is now resolved? If so, I can close it.

[Dean Henrichsmeyer (dean)]

Yep, current xenial kernel is all good (now 4.4.0-8). This can be closed.