The keyboard does not work after latest kernel update

[Ganton]

The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not work after the latest kernel update and its subsequent reboot of the laptop. Nothing else is connected to the laptop.

--------------------------------------------------------------------------

In /var/log/apt/history.log , the latest we can see is:

Start-Date: 2024-04-09 12:37:28
Commandline: apt full-upgrade
Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
End-Date: 2024-04-09 12:37:51

--------------------------------------------------------------------------

$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10

$ # Note: It's Kubuntu 23.10

--------------------------------------------------------------------------

$ uname -a
Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

SRU Justification:
======================
[Impact]
Keyboard is lost after updated to 6.5.0-27 and oem-6.5-1019 kernel
versions.

[Fix]
Regression commit is found commit:
936e4d49ecbc ("Input: atkbd - skip ATKBD_CMD_GETID in translated mode")

Fixes:
9cf6e24c9fbf1 Input: atkbd - do not skip atkbd_deactivate() when
skipping ATKBD_CMD_GETID
683cd8259a9b8 Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping
ATKBD_CMD_GETID

[Test]
Tested on hardware, keyboard works fine after bootup.

The regression commit is only in 6.5 stable, so SRU for 6.5 only.

[Where problems could occur]
It may break keyboard.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/2060727/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Ganton (ganton)]

The (integrated) trackpoint works, although the integrated keyboard does not work.

With an external USB keyboard, the computer can be used (if you have an external USB keyboard near...).

I attach a part of what is seen after executing `journalctl.txt`.

[Ganton (ganton)]

This recent bug report is possibly related:

> I can suspend the computer with the laptop keyboard and, upon waking,
> the laptop keyboard does not type characters into the password box.
> Then I connect the external keyboard and I CAN enter the password and
> get to the desktop.

https://bugs.launchpad.net/ubuntu/+bug/2060736

[Launchpad Janitor (janitor)]

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

[Ganton (ganton)]

In this "duplicate" bug report, the user utilizes Xubuntu 22.04.3 and gives additional information:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060866

[Aussems J.a.c. (ramcsir)]

------------------------------------

I changed in file '/etc/default/grub' the lines:

GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=-1

I used the command 'sudo update-grub' and Reboot the computer.
The grub menu is now shown and I can still use the internal keyboard.

I can choose between kernel version:

- Linux 6.5.0.-1019-oem
- Linux 6.5.0.-1018-oem

When I choose the kernel, 1019, the keyboard does not functions after booting
When I choose the kernel, 1018, the keyboard workes after booting.

So this shows that the problem is caused by the 1019 kernel.

[Aussems J.a.c. (ramcsir)]

My history log give the entry below when the problem occurs:

Start-Date: 2024-04-08 14:38:34
Commandline: aptdaemon role='role-commit-packages' sender=':1.79'
Install: linux-image-6.5.0-1019-oem:amd64 (6.5.0-1019.20, automatic), linux-modules-6.5.0-1019-oem:amd64 (6.5.0-1019.20, automatic), linux-image-oem-22.04d:amd64 (6.5.0.1019.21, automatic), linux-oem-22.04d:amd64 (6.5.0.1019.21, automatic), linux-headers-oem-22.04d:amd64 (6.5.0.1019.21, automatic), linux-headers-6.5.0-1019-oem:amd64 (6.5.0-1019.20, automatic), linux-oem-6.5-headers-6.5.0-1019:amd64 (6.5.0-1019.20, automatic)
Upgrade: linux-headers-oem-22.04:amd64 (6.5.0.1018.20, 6.5.0.1019.21), linux-image-oem-22.04c:amd64 (6.1.0.1036.37, 6.5.0.1019.21), linux-oem-22.04c:amd64 (6.1.0.1036.37, 6.5.0.1019.21), linux-oem-22.04:amd64 (6.5.0.1018.20, 6.5.0.1019.21), linux-headers-oem-22.04c:amd64 (6.1.0.1036.37, 6.5.0.1019.21), linux-image-oem-22.04:amd64 (6.5.0.1018.20, 6.5.0.1019.21), linux-libc-dev:amd64 (5.15.0-101.111, 5.15.0-102.112)
End-Date: 2024-04-08 14:38:57

[Aussems J.a.c. (ramcsir)]

I found the solution to boot an older kernel, 'https://askubuntu.com/questions/216398/set-older-kernel-as-default-grub-entry'.

Open the file '/etc/default/grub with your preferred editor.

Change the line 'GRUB_DEFAULT=0' -> GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux 6.5.0-1018-oem"

Save and Close the editor.

Run the command 'sudo update-grub' and reboot the system.

The system now boots the kernel 'Linux 6.5.0-1018-oem' in my case.

Maybe you could also use this solution for the moment waiting on a final solution.

[James Fox (jfox950)]

I have a Dell XPS 13 running Kubuntu 22.04. Keyboard works fine on fresh boot but the keyboard doesnt work at all after resuming from suspend.

linux-image-6.5.0-27-generic is the kernel I started having the problem with.

Booting an older 6.5 kernel and keyboard works again after resume.

[AaronMa (mapengyu)]

CPU0: 13th Gen Intel(R) Core(TM) i7-1360P
ThinkPad BIOS R24ET27W (1.10 ), EC R24HT20W
Not reproduced on BIOS version above on kernel 6.5.0-1019 and 6.5.0-27.

Will try to update BIOS and verify again.

[Aussems J.a.c. (ramcsir)]

I use the ThinkPad L15 Gen4, BIOS version R24ET38W(1.21) together with
kernel 6.5.0-1019-oem, the CPU type is i7-1355U. This combination gives a
not working keybord after booting.

On Tue, Apr 16, 2024 at 8:15 AM AaronMa <email address hidden> wrote:

> CPU0: 13th Gen Intel(R) Core(TM) i7-1360P
> ThinkPad BIOS R24ET27W (1.10 ), EC R24HT20W
> Not reproduced on BIOS version above on kernel 6.5.0-1019 and 6.5.0-27.
>
> Will try to update BIOS and verify again.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2060727
>
> Title:
> The keyboard does not work after latest kernel update
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not
> work after the latest kernel update and its subsequent reboot of the
> laptop. Nothing else is connected to the laptop.
>
>
> --------------------------------------------------------------------------
>
> In /var/log/apt/history.log , the latest we can see is:
>
> Start-Date: 2024-04-09 12:37:28
> Commandline: apt full-upgrade
> Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28,
> automatic), linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic),
> linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic),
> linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic),
> linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
> Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27),
> linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64
> (6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
> End-Date: 2024-04-09 12:37:51
>
>
> --------------------------------------------------------------------------
>
> $ lsb_release -rd
> No LSB modules are available.
> Description: Ubuntu 23.10
> Release: 23.10
>
> $ # Note: It's Kubuntu 23.10
>
>
> --------------------------------------------------------------------------
>
> $ uname -a
> Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7
> 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+subscriptions
>
>

--
RISC OS Select Adjust, that other system.
See also, http://www.riscos.com

[Aussems J.a.c. (ramcsir)]

I use the ThinkPad L15 Gen4, BIOS version R24ET38W(1.21) together with kernel 6.5.0-1019-oem, the CPU type is i7-1355U. This combination gives a not working keybord after booting.

[Ganton (ganton)]

Following that conversation: In my case, the bug happens with:

$ sudo lshw | grep -A8 '*-firmware'
    *-firmware
        description: BIOS
        vendor: LENOVO
        physical id: 14
        version: R24ET38W (1.21 )
        date: 03/01/2024
        size: 128KiB
        capacity: 32MiB
        capabilities: pci pnp upgrade shadowing cdboot bootselect edd int13floppy720 int5printscreen int9keyboard int14serial int17printer int10video acpi usb biosbootspecification uefi

$ uname -a
    Linux hostname 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

$ LANG=C lscpu
    Architecture: x86_64
    CPU op-mode(s): 32-bit, 64-bit
    Address sizes: 39 bits physical, 48 bits virtual
    Byte Order: Little Endian
    CPU(s): 12
    On-line CPU(s) list: 0-11
    Vendor ID: GenuineIntel
    Model name: 13th Gen Intel(R) Core(TM) i7-1355U
    (...)

[AaronMa (mapengyu)]

The regression commit is:
commit a6cb9c9b40551d61bb6fb3b24ef27563947360b7
Author: Hans de Goede <email address hidden>
Date: Fri Nov 24 19:59:24 2023 -0800

    Input: atkbd - skip ATKBD_CMD_GETID in translated mode

    BugLink: https://bugs.launchpad.net/bugs/2055199

    [ Upstream commit 936e4d49ecbc8c404790504386e1422b599dec39 ]

It's in v6.8-rc1. The fix might be in v6.8-rc3:

commit 9cf6e24c9fbf17e52de9fff07f12be7565ea6d61
Author: Hans de Goede <email address hidden>
Date: Fri Jan 26 17:07:24 2024 +0100

    Input: atkbd - do not skip atkbd_deactivate() when skipping ATKBD_CMD_GETID

[Aussems J.a.c. (ramcsir)]

Today the system has upgraded the kernel to Linux version 6.5.0-1020-oem this should solves the keyboard problem introduced in kernel 6.5.0-1019-oem and already reported in:

- https://bugs.launchpad.net/bugs/2060727
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060866

This bug fix does not work, I still have no internal keyboard.

I made a new bug report, 2062545.

Is this new kernel working for you Ganton?

[Ganton (ganton)]

> Is this new kernel working for you, Ganton?

No, it does not.

I've updated the kernel:
    $ uname -a
    Linux hostname 6.5.0-28-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 28 23:46:48 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
although in the end, after rebooting, I have experimented the same problem.

[James Fox (jfox950)]

The fix hasn't been released yet.

"Fix Committed" status means the source has been updated but hasn't been released in a package.

"Fix Released" status means the new package has the fix.

[Aussems J.a.c. (ramcsir)]

Good to know, then we will wait and see whether the problem will be solved with the next kernel update.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-oem-6.5/6.5.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-done-jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy-linux-oem-6.5'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Aussems J.a.c. (ramcsir)]

I tryed yesterday to setup my system to receive the -proposed kernel update using the link, https://wiki.ubuntu.com/Testing/EnableProposed. The system got some developers updates, but not the kernel update jammy-linux-oem-6.5. So I am indoubt, did I do something wrong or did I forget something settingup before I could test the new kernel solotion? A response from your side would be appreciated.

[AaronMa (mapengyu)]

@ramcsir,

Your Ubuntu is 23.10.
Would you mind try to add the following line to "/etc/apt/sources.list":
deb http://archive.ubuntu.com/ubuntu/ jammy-proposed main

$ sudo apt update
$ sudo apt install linux-image-6.5.0-1021-oem linux-modules-6.5.0-1021-oem

After you test, the line and packages can be removed.

Thanks.

[Atlas Yu (pseudoc)]

I tested linux-image-6.5.0-1021-oem on ThinkPad L15 Gen4 with 10 boots(20 suspends/resumes for each boot).
Cannot reproduce this bug anyway, considered fixed.

---
To: Aussems J.a.c. (ramcsir)
To: Ganton (ganton)

The SKU we hold here, rarely reproduces this issue on the previous kernels, we would be much appreciated if you can help to verify the fix as well according to #20 and #22.

[Aussems J.a.c. (ramcsir)]

Hallo AaronMa (mapengyu),

In the first line of the file "/etc/apt/sources.list" file I can read:

# deb cdrom:[Xubuntu 22.04.3 LTS _Jammy Jellyfish_ - Release amd64 (20230807.1)]/ jammy main multiverse restricted universe

I follow the steps that you suggested.
I can tell you the good news, my keyboard is working again in kernel linux-image-6.5.0-1021-oem.

I notice during booting I get several error messages on the screen displayed, see attachted photo.
What is the source of these messages, BIOS or kernel, and could these be suppressed or solved so that they doesn't appear on the screen.