[Kernel-packages] [Bug 2060727] Re: The keyboard does not work after latest kernel update
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.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2060727
Title:
The keyboard does not work after latest kernel update
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Committed
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
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
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2060727] Re: The keyboard does not work after latest kernel update
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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028274] [NEW] watchdog: BUG: soft lockup - CPU#10 stuck for 134s! [DyingLightGame_:4256]
Public bug reported: Playing Dying Light 2 through steam/proton on Ubuntu 22.04 with nvidia 535. Game is perfect until I press quit in Dying Light 2's menu. The computer totally locks up and I have to hold the power button down. It happens every time. Downgrading to 525 with 'sudo apt install nvidia-driver-525 nvidia- dkms-525' fixed the issue. journalctl Jul 20 10:56:28 desktop kernel: watchdog: BUG: soft lockup - CPU#10 stuck for 134s! [DyingLightGame_:4256] Jul 20 10:56:28 desktop kernel: Modules linked in: vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc nls_iso8859_1 snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_usb_audio snd_hda_codec_realtek intel_rapl_msr snd_compress intel_rapl_common snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_codec_hdmi snd_usbmidi_lib x86_pkg_temp_thermal intel_powerclamp snd_rawmidi snd_seq_device coretemp mc snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi kvm_intel snd_hda_codec snd_hda_core xpad mei_hdcp snd_hwdep snd_pcm ff_memless joydev snd_timer kvm snd mei_me soundcore mei ee1004 intel_cstate intel_wmi_thunderbolt gigabyte_wmi wmi_bmof nvidia_uvm(POE) mac_hid acpi_pad acpi_tad sch_fq_codel msr pstore_blk ramoops pstore_zone reed_solomon efi_pstore ip _tables x_tables Jul 20 10:56:28 desktop kernel: autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nvidia_drm(POE) nvidia_modeset(POE) hid_generic usbhid hid nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec aesni_intel rc_core crypto_simd cryptd drm r8169 ahci i2c_i801 xhci_pci i2c_smbus realtek libahci xhci_pci_renesas wmi video pinctrl_tigerlake Jul 20 10:56:28 desktop kernel: CPU: 10 PID: 4256 Comm: DyingLightGame_ Tainted: P OEL5.15.0-76-generic #83-Ubuntu Jul 20 10:56:28 desktop kernel: Hardware name: Gigabyte Technology Co., Ltd. H510M S2H/H510M S2H, BIOS F9 08/23/2021 Jul 20 10:56:28 desktop kernel: RIP: 0010:_nv039537rm+0x3b/0x80 [nvidia] Jul 20 10:56:28 desktop kernel: Code: d3 89 de 48 8d 55 0f c6 45 0f 00 e8 3f 4c 60 ff 80 7d 0f 00 41 89 c4 75 11 41 39 5d 10 76 20 49 8b 45 00 c1 eb 02 44 8b 24 98 <5b> 44 89 e0 41 5c 41 5d 48 83 c5 10 c3 0f 1f 84 00 00 00 00 00 be Jul 20 10:56:28 desktop kernel: RSP: 0018:bd0d839bf8f0 EFLAGS: 0202 Jul 20 10:56:28 desktop kernel: RAX: bd0d8200 RBX: 2440 RCX: 9100 Jul 20 10:56:28 desktop kernel: RDX: 952e995e596f RSI: 9100 RDI: 952de38c0008 Jul 20 10:56:28 desktop kernel: RBP: 952e995e5960 R08: 0020 R09: Jul 20 10:56:28 desktop kernel: R10: 9100 R11: 952e995e59c8 R12: 0001 Jul 20 10:56:28 desktop kernel: R13: 952de38c0bc8 R14: R15: Jul 20 10:56:28 desktop kernel: FS: 7fe4617b4040() GS:95355fc8() knlGS:7fee Jul 20 10:56:28 desktop kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 20 10:56:28 desktop kernel: CR2: 7f130400c000 CR3: 0001fca94005 CR4: 00770ee0 Jul 20 10:56:28 desktop kernel: PKRU: 5554 Jul 20 10:56:28 desktop kernel: Call Trace: Jul 20 10:56:28 desktop kernel: Jul 20 10:56:28 desktop kernel: ? _nv013076rm+0x10f/0x170 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv047477rm+0x20/0x30 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv030454rm+0x5a/0x110 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv030546rm+0x13f/0x340 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv030547rm+0x50/0x60 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv013174rm+0x86/0xc0 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv013170rm+0x3a4/0x400 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv044237rm+0xd1/0x1b0 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv041109rm+0x1e7/0x370 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv048377rm+0x40/0x95 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv035020rm+0x14d/0x2e0 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv048374rm+0xc5/0x460 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv002711rm+0xd/0x20 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv004074rm+0x19/0xb0 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv016053rm+0x51c/0x620 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv043216rm+0xab/0xe0 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv044933rm+0xac/0x130 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv044932rm+0x3e5/0x690 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv043119rm+0xd5/0x160 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv043120rm+0x41/0x70 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv000566rm+0x4d/0x60 [nvidia]
