ubuntu 1404_HWE_EOL kernel breaks Thinkpad T530 keyboard backlight operation

[rich painter]

Using kernel 3.19.0-66-generic the keyboard backlight and screen-top illuminator work.

However, after upgrading to kernel 4.4 the keyboard backlight and screen-top illuminator come on without hitting the special keys. When it returns from screen saver when I hit the return key these lights come on also.

---
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: painter 3092 F.... pulseaudio
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=05f2d9dc-173d-41bc-8332-7d0a6e7394fa
InstallationDate: Installed on 2014-11-23 (741 days ago)
InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: LENOVO 2359CTO
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic root=UUID=349d96ad-2412-45a5-b1d9-46eb9050bce1 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-51.72~14.04.1-generic 4.4.30
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-51-generic N/A
 linux-backports-modules-4.4.0-51-generic N/A
 linux-firmware 1.127.22
Tags: trusty
Uname: Linux 4.4.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 09/10/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: G4ETA5WW (2.65 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2359CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2359CTO
dmi.product.version: ThinkPad T530
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1645985

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[rich painter (painterengr)]

should the apport command be run AFTER installing the offending
1404_HWE_EOL update?

I/m guessing so.. but please confirm.
thanks
rich

On Tue, Nov 29, 2016 at 10:01 PM, Brad Figg <email address hidden> wrote:

> This bug is missing log files that will aid in diagnosing the problem.
> >From a terminal window please run:
>
> apport-collect 1645985
>
> and then change the status of the bug to 'Confirmed'.
>
> If, due to the nature of the issue you have encountered, you are unable
> to run this command, please add a comment stating that fact and change
> the bug status to 'Confirmed'.
>
> This change has been made by an automated script, maintained by the
> Ubuntu Kernel Team.
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> ** Tags added: trusty
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1645985
>
> Title:
> ubuntu 1404_HWE_EOL kernel breaks Thinkpad T530 keyboard backlight
> operation
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> System: Lenovo Thinkpad T530 laptop
> OS: ubuntu 14.04 LTS, kernel 3.19.0-66-generic 64bit
> lsb_release -rd
> Description: Ubuntu 14.04.5 LTS
> Release: 14.04
>
> With the above configuration the keyboard backlights and screen-top
> illuminator work as they are supposed to.
>
> In August I received the 1404_HWE_EOL update popup. Image taken today is
> attached.
> I installed the ubuntu 1404_HWE_EOL which installed (I think) some 4.4
> kernel.
>
> After installing, the keyboard backlights and screen-top illuminator
> come on without hitting the special keys. When it returns from screen
> saver when I hit the return key these lights come on also.
>
> If I reboot to the old kernel all is well. So something is broken in
> the kernel that is installed with the 1404_HWE_EOL
>
> So I deleted this new kernel for now.
>
> The popup comes up constantly for almost 4 months now, many many times
> per day. This is a huge annoyance.
>
> More seriously is that no other updates are coming in. This poses
> security issues at a minimum.
>
> Accepting the update causes the backlights and screen-top illuminator
> to go on with every screen saver operation which is just as annoying.
>
>
> This was reported here without any response to date:
> http://askubuntu.com/questions/817383/ubuntu-1404-hwe-eol-kernel-breaks-
> thinkpad-t530-keyboard-backlight
>
> This was reported here without any response to date:
> https://forums.lenovo.com/t5/Linux-Discussion/T530-
> Keyboard-backlight-comes-on-when-screen-saver-goes-off-
> once/m-p/3457674#M112494
>
> Lenovo T530 BIOS info:
>
> Package (ID) UEFI BIOS (BIOS ID) ECP (ECP ID) Rev. Issue Date
> -------------------- ------------------- --------------- ---- -----------
> 2.67 (G4UJ31UC) 2.67 (G4ETA7WW) 1.13 (G4HT39WW) 01 2016/09/09
>
> I hope someone can fix this so I can move forward and stop the
> annoyances to boot.
> regards
>
> oldunixguy
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1645985/+subscriptions
>

--
Richar...

[Joseph Salisbury (jsalisbury)]

Yes, please run apport after installing the update. Also, check to see if there are any additional updates after installing the one requested.

[rich painter (painterengr)]

very fine.

my worry is how do I reverse any changes and updates once I do this to
collect the apport data... this problem is HIGHLY annoying.

I was able to uninstall the 1404_HWE_EOL update immediately after the
checkout and discovery of the backlight problem... So I dont know what will
happen if I let additional update flow in following rerunning
1404_HWE_EOL...

do you have any insight on this risk?

thanks
rich

On Wed, Nov 30, 2016 at 9:19 AM, Joseph Salisbury <
<email address hidden>> wrote:

> Yes, please run apport after installing the update. Also, check to see
> if there are any additional updates after installing the one requested.
>
> ** Tags added: kernel-da-key
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1645985
>
> Title:
> ubuntu 1404_HWE_EOL kernel breaks Thinkpad T530 keyboard backlight
> operation
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> System: Lenovo Thinkpad T530 laptop
> OS: ubuntu 14.04 LTS, kernel 3.19.0-66-generic 64bit
> lsb_release -rd
> Description: Ubuntu 14.04.5 LTS
> Release: 14.04
>
> With the above configuration the keyboard backlights and screen-top
> illuminator work as they are supposed to.
>
> In August I received the 1404_HWE_EOL update popup. Image taken today is
> attached.
> I installed the ubuntu 1404_HWE_EOL which installed (I think) some 4.4
> kernel.
>
> After installing, the keyboard backlights and screen-top illuminator
> come on without hitting the special keys. When it returns from screen
> saver when I hit the return key these lights come on also.
>
> If I reboot to the old kernel all is well. So something is broken in
> the kernel that is installed with the 1404_HWE_EOL
>
> So I deleted this new kernel for now.
>
> The popup comes up constantly for almost 4 months now, many many times
> per day. This is a huge annoyance.
>
> More seriously is that no other updates are coming in. This poses
> security issues at a minimum.
>
> Accepting the update causes the backlights and screen-top illuminator
> to go on with every screen saver operation which is just as annoying.
>
>
> This was reported here without any response to date:
> http://askubuntu.com/questions/817383/ubuntu-1404-hwe-eol-kernel-breaks-
> thinkpad-t530-keyboard-backlight
>
> This was reported here without any response to date:
> https://forums.lenovo.com/t5/Linux-Discussion/T530-
> Keyboard-backlight-comes-on-when-screen-saver-goes-off-
> once/m-p/3457674#M112494
>
> Lenovo T530 BIOS info:
>
> Package (ID) UEFI BIOS (BIOS ID) ECP (ECP ID) Rev. Issue Date
> -------------------- ------------------- --------------- ---- -----------
> 2.67 (G4UJ31UC) 2.67 (G4ETA7WW) 1.13 (G4HT39WW) 01 2016/09/09
>
> I hope someone can fix this so I can move forward and stop the
> annoyances to boot.
> regards
>
> oldunixguy
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1645985/+subscriptions
>

--
Richard A. Painter, P.E....

[rich painter (painterengr)]

apport information

[rich painter (painterengr)]

apport information

[rich painter (painterengr)]

apport information

[rich painter (painterengr)]

apport information

[rich painter (painterengr)]

apport information

[rich painter (painterengr)]

apport information

[rich painter (painterengr)]

apport information

[rich painter (painterengr)]

apport information

[rich painter (painterengr)]

apport information

[rich painter (painterengr)]

apport information

[rich painter (painterengr)]

apport information

[rich painter (painterengr)]

apport information

[rich painter (painterengr)]

apport information

[rich painter (painterengr)]

apport information

[rich painter (painterengr)]

Installed "ubuntu 1404_HWE_EOL" update. Other packages updated with it since nothing has been updating since Aug because ubuntu 1404_HWE_EOL update was holding it up.

Problem still exists with the keyboard backlight coming on when the screen saver restores the normal desktop upon hitting the Enter key.

[rich painter (painterengr)]

Kernel 4.4.0-53, the latest kernel update, flowed in today.
This kernel also exhibits the keyboard and screen-top illuminators bug.

Booting the last 3.x kernel, 3.19.0-77, makes the illuminators to work correctly.

[penalvch (penalvch)]

rich painter, 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.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Thank you for your help.

[rich painter (painterengr)]

will do
If I can just install a kernel I think I have room. I dont have space for a
separate partition for a complete and separate installation.
thanks
rich

On Sun, Dec 18, 2016 at 7:01 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> rich painter, 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.
>
> Also, you don't need to apport-collect further unless specifically
> requested to do so.
>
> It is most helpful that after testing of the latest upstream kernel is
> complete, you mark this report Status Confirmed.
>
> Lastly, to keep this issue relevant to upstream, please continue to test
> the latest mainline kernel as it becomes available.
>
> Thank you for your help.
>
> ** Tags added: bios-outdated-2.67 regression-release
>
> ** Description changed:
>
> - System: Lenovo Thinkpad T530 laptop
> - OS: ubuntu 14.04 LTS, kernel 3.19.0-66-generic 64bit
> - lsb_release -rd
> - Description: Ubuntu 14.04.5 LTS
> - Release: 14.04
> + Using kernel 3.19.0-66-generic the keyboard backlight and screen-top
> + illuminator work.
>
> - With the above configuration the keyboard backlights and screen-top
> - illuminator work as they are supposed to.
> + However, after upgrading to kernel 4.4 the keyboard backlight and
> + screen-top illuminator come on without hitting the special keys. When it
> + returns from screen saver when I hit the return key these lights come on
> + also.
>
> - In August I received the 1404_HWE_EOL update popup. Im...

[rich painter (painterengr)]

downloaded into new directory:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/linux-headers-4.9.0-040900_4.9.0-040900.201612111631_all.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/linux-headers-4.9.0-040900-generic_4.9.0-040900.201612111631_amd64.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/linux-image-4.9.0-040900-generic_4.9.0-040900.201612111631_amd64.deb

Followed instructions here https://wiki.ubuntu.com/Kernel/MainlineBuilds

sudo dpkg -i *.deb

got some errors that I ignored since the kernel was installed OK for grub.

rebooted 4.9 and it exhibited the same backlight problem reported here.

[penalvch (penalvch)]

rich painter, the next step is to fully commit bisect from kernel 3.19 to 4.4 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

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

Also, the kernel release names are irrelevant for the purposes of bisecting.

It is most helpful that after the fix commit (not kernel version) has been identified, you then mark this report Status Confirmed.

Thank you for your help.

[rich painter (painterengr)]

After bisecting the kernel releases I have determined when this bug was injected.
Release 4.4.39 is OK
Release 4.5-rc1 is BROKEN

64-bit Generic versions were used.

After testing many releases I have discovered one additional aspect of this bug of the backlight inappropriately coming on following the exiting of the screen saver.

In the broken kernels the backlight will illuminate during the "traveling dots" while the desktop GUI is starting. It remains on until manually disabled or when the screen saver exits.

[rich painter (painterengr)]

4.5-rc1 and above bug exists
kernel-bug-exists-upstream-4.5-rc1

[rich painter (painterengr)]

Sorry, I don't know how to edit an entry....
Previous entry stated "It remains on until manually disabled or when the screen saver exits."

It should read:
It remains on until manually disabled just the same as when the screen saver exits.

[penalvch (penalvch)]

rich painter, as noted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645985/comments/25 what is needed is the offending commit (not the version).

Could you please advise?

[rich painter (painterengr)]

I'm not sure how to provide this. You sent me to http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D to obtain the various kernels to test. This is the kernel releases I bisected...

Note that I do not know "git" and haven't built unix kernels since 1990, only download prebuilt kernels for at the link you provided (shown above).

In the release that fails (and above) the index file http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-rc1-wily/ reports this near the top about "commit":

v4.5-rc1 (92e963f50fc74041b5e9e744c330dca48e04f08d)

Is this what you are referring to?
And where do I put it in launchpad if not in this post?

[penalvch (penalvch)]

rich painter, could you please read https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645985/comments/25 in its entirety, and then advise if this answered your question?

[rich painter (painterengr)]

I already read #25 4 or more times and it did not provide sufficient details to tell me what to do in conjunction with your other direction. So I provided the details of what I did and asked my questions when you balked.... Your reply doesn't help when it doesn't even answer these follow up questions. I went to the place where you pointed and bisected all the versions between the latest and the one I started with. I found the one that started the failure. I dug into the index for that version and pulled out the "commit" as you asked and all you reply with is to point me to the same #25 I have already read a bunch.

Do you or do you not want the commit string I got from the version that failed out of the index file that plainly stated:

These binary packages represent builds of the mainline or stable Linux kernel tree at the commit below:
v4.5-rc1 (92e963f50fc74041b5e9e744c330dca48e04f08d)

You initially stated "the next step is to fully commit bisect from kernel 3.19 to 4.4 in order to identify the last good kernel commit, followed immediately by the first bad one".

I understand "bisecting" of lists to locate one of interest and have been doing this for over 40 years. However, "fully commit bisect" is vague and you don't explain what you want. The reference to "https://wiki.ubuntu.com/Kernel/KernelBisection" I read too. But that too is confusing. Since you sent me to "http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D" I used THIS to get the kernels to bisect. You have not said one way or the other whether you sent me to the wrong place to get this stuff to bisect. Reading "https://wiki.ubuntu.com/Kernel/KernelBisection" and using "http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D" I followed your instructions.

I did not find any fields or boxes on this web page to put something referred to as a "fully commit" or even "commit".

If this is not what you want then you have to at least answer my questions and point me to a different file tree other than "http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D" to find whatever else I am to find and how to report to you what that is that correlates to what I tested.

I cannot get src and build kernels with my current setup. So I have to rely on the fully built .deb packages. I did this and isolated what worked and what didn't from "http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D". I reported the "commit" data from this.

How about a more specific description of what you want that is different from what I produced and how I'm to report it differently from how I have already reported?

[penalvch (penalvch)]

rich painter, providing a commit string of a kernel version bisect is unfortunately not helpful here, and is not the requested commit bisect.

As per comment #25, one would follow https://wiki.ubuntu.com/Kernel/KernelBisection . Folks who have read this from start to finish find it answers the types of questions you have been asking.

[Launchpad Janitor (janitor)]

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

[rich painter (painterengr)]

As I previously reported, my SSD is full and cannot build kernels. I have made several attempts to upgrade to a larger SSD but the grub2 installer refuses to install so I'm still not able to build kernels. Since you don't care to help you will have to wait until I can find someone to help correct the Ubuntu 14.04 LTS grub2 problem for me to be able to get the space so I can work on this kernel bug.