Bug #1894017 “Keyboard not working” : Bugs : linux package : Ubuntu

Revision history for this message

Nicholas Demosthenous (demosnk) wrote on 2020-09-03:

#1

AlsaInfo.txt Edit (30.8 KiB, text/plain; charset="utf-8")
AudioDevicesInUse.txt Edit (290 bytes, text/plain; charset="utf-8")
CRDA.txt Edit (252 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (67.4 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.5 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (579 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (10.9 KiB, text/plain; charset="utf-8")
Lspci-vt.txt Edit (1.0 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (495 bytes, text/plain; charset="utf-8")
Lsusb-t.txt Edit (687 bytes, text/plain; charset="utf-8")
Lsusb-v.txt Edit (44.5 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (4.1 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (331 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (3.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (9.3 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (11.2 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (112 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (203.9 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (98.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2020-09-03: Status changed to Confirmed

#2

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Robert Lambourne (robertlambourne) wrote on 2020-09-14:

#3

Having the same problem Bug #1894125

Revision history for this message

g.maverick (giannamelo) wrote on 2020-09-21:

#4

+1

Revision history for this message

Sam N (colorful-shirts8573) wrote on 2020-09-21:

#5

Same here.

Same computer as original bug report (Hewlett-Packard HP Pavilion 11 x360 PC)
But different distro release (Xubuntu 20.04)

Laptop keyboard and trackpad totally nonfunctional on any kernel higher than 5.4.0.42. Starting with 5.4.0-45 and all further kernels to today (2020-09-22) the problem persists. External (USB) mice and keyboards work fine.

Revision history for this message

Sam N (colorful-shirts8573) wrote on 2020-09-23:

#6

After testing out various kernels, I've found that the keyboard and trackpad gain functionality in kernel 5.4.18-050418-generic.

No luck in the latest (5.8~) yet, but as 5.4 is a LTS kernel for now I'll just stick with booting to 5.4.18 as that's only a few point releases behind current stable anyway. Hope this info helps others.

Revision history for this message

Carlos (fridugiso) wrote on 2020-09-26:

#7

I can confirm both the bug and it being fixed in 5.4.18. Thanks!

Revision history for this message

Carlos (fridugiso) wrote on 2020-09-30:

#8

Following a tip from [1] (the user there suspects their laptop is erroneously entering tablet mode) I blacklisted the kernel module intel_vbtn and it seems to do the trick, my laptop keyboard works again on kernel 5.4.0-48.

I found a few other bug reports which may be related or duplicates. One ([2]) suggests some kernel parameters as a partial fix, the others ([3], [4], [5]) have no solution

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=208525#c9
[2]: https://bugzilla.kernel.org/show_bug.cgi?id=208945
[3]: https://bugzilla.kernel.org/show_bug.cgi?id=208853
[4]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894012
[5]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894125

Revision history for this message

Igor (prigoryan) wrote on 2020-10-05:

#9

I have exactly same bug on Acer Aspire E5-511G

Revision history for this message

Hans de Goede (j-w-r-degoede) wrote on 2020-10-06:

#10

This should be fixed by this upstream commit, which landed in Linus' tree a couple of hours ago:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/platform/x86?id=8169bd3e6e193497cab781acddcff8fde5d0c416

Note for the Ubuntu kernel devs: a similar bug was introduced in 5.8 in the asus-nb-wmi code, so when fixing this you really should also pick-up this fix:

https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=fixes&id=1797d588af15174d4a4e7159dac8c800538e4f8c

This one will hopefully be merged by Linus real soon (I have send out a pull-req for it to Linus).

Revision history for this message

Hans de Goede (j-w-r-degoede) wrote on 2020-10-06:

#11

For everyone who is seeing this issue with the intel-vbtn driver,
if you do:

cat /sys/class/dmi/id/chassis_type

On your laptop, and the output is NOT "31" or "32" then the
fix, which I linked above, should work for you.

If the output actually is "31" or "32 (which I do not expect),
then please let me know, because then we need a different fix.

Revision history for this message

Igor (prigoryan) wrote on 2020-10-06:

#12

Confirmed:
cat /sys/class/dmi/id/chassis_type returns 10 on Acer Aspire E5-511G (Intel Celeron N2940)

Revision history for this message

Peter Horn (handyboy) wrote on 2020-10-08:

#13

I can confirm that cat /sys/class/dmi/id/chassis_type returns 10 on Hewlett-Packard HP Pavilion 11 x360 PC.
I had the same issue using Ubuntu 18.04 and got around it by using kernel 5.4.0-42. When I upgraded to Ubuntu 20.04 I found the same issue and get around it using kernel 5.4.0-42 again.

see my original Question on AskUbuntu here: https://askubuntu.com/questions/1272818/built-in-laptop-keyboard-not-working-today-on-hp-convertible-x360-with-ubuntu-18.

Does anyone know if the fixes described by Hans De Goede above have resolved this issue or should I wait to see what Linus comes up with ?

Revision history for this message

Hans de Goede (j-w-r-degoede) wrote on 2020-10-09:

#14

@handyboy, my fix for this has been merged by Linus for inclusion into 5.9. If one of the Ubuntu devs can add the 2 mentioned fixes to the next 20.04 kernel build then this issue should be resolved/fixed.

Revision history for this message

Hans de Goede (j-w-r-degoede) wrote on 2020-10-09:

#15

I just got an email from gkh that both patches have also been added to the various stable kernel series, including 5.4.x and 5.8.y, so they should show up in the next stable series release for those kernels.

Thus if the Ubuntu kernel follows the stable series then this will get fixed through that.

Revision history for this message

Peter Horn (handyboy) wrote on 2020-10-10:

#16

Thank you for this Hans - it is really appreciated by me.
I will wait and see if the stable series release fixes this (hopefully soon ! ).

Revision history for this message

Peter Horn (handyboy) wrote on 2020-10-15:

#17

I received kernel 5.4.0-51 yesterday (2020.10.15) but it still hass the same issue. I have reverted to using 5.4.0-42 to get my Ubuntu 20.4 going. Does any one know when the next stable series release will happen ?

Revision history for this message

piotrek (piotrek359) wrote on 2020-10-19:

#18

I'm experiencing identical problem with HP Pavilion 11 x360. For me, still only solution is to use kernel version -42. Installing 5.4.0-51 didn't solve the issue. Anyone know is solution is planed by Ubuntu team?

Revision history for this message

Hans de Goede (j-w-r-degoede) wrote on 2020-10-19:

#19

This has been fixed in the upstream 5.4.71 stable series release, so as soon as the Ubuntu kernels pick up the fixes from that release then this should be resolved.

Revision history for this message

Peter Horn (handyboy) wrote on 2020-10-25:

#20

I have since received kernel 5.4.0-52 but this still has the same issue (Keyboard AND Mouse not working).
I will continue to use 5.4.0-42 until this can be fixed - my only other option is to revert to Windows (ugh!).

Revision history for this message

piotrek (piotrek359) wrote on 2020-10-27:

#21

5.4.71!? Realy? And how long can it take when 5.4.0-55 is available? Years? OMG That's very bad news for me.

Revision history for this message

Carlos (fridugiso) wrote on 2020-10-27:

#22

Have you tried blacklisting the kernel module "intel_vbtn" as a workaround?

By the way, on Chuwi Minibook m3-8100Y, "cat /sys/class/dmi/id/chassis_type" returns "3", so all good in that regard.

Thanks, Hans!

Revision history for this message

John Pitt (burritojohn) wrote on 2020-10-28:

#23

Affected too, with an asus x751BP laptop on groovy.
Blacklisting intel_vbtn doesn't change anything (not active with lsmod after the blacklist bug the bug's still there). Still there with the latest kernel from the update manager (5.8.0-26-generic) received today. The integrated keyboard/mouse work fine with 5.4.0-52-generic, and "cat /sys/class/dmi/id/chassis_type" returns 10.

Thanks for reading me !

Revision history for this message

Hans de Goede (j-w-r-degoede) wrote on 2020-10-28:

#24

@burritojohn, if you are seeing this on an Asus device then you are hit by a different variant of what is in essence the same bug.

The Asus case is fixed by this upstream commit:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1797d588af15174d4a4e7159dac8c800538e4f8c

Which has also been cherry-picked into the 5.8.y stable series (it is there since the v5.8.15 release).

So to fix this for you (and many many other Asus users!) the Ubuntu kernels should pickup the upstream fix for this.

Revision history for this message

Kevin Tang (dacto) wrote on 2020-11-25:

#25

System: HP Convertible x360 11-ab0XX
$ cat /sys/class/dmi/id/chassis_type
31

Keyboard was working in 5.4.0-42.
Broken with update to 5.4.0-54.
Still broken in 5.9.10.
Working in 5.4.75.

Is 5.9.10 missing the fix that was included in 5.4.75 for chassis_type 31?

Revision history for this message

Hans de Goede (j-w-r-degoede) wrote on 2020-11-26:

#26

chassis_type 31 is "Convertible", so we expect the intel-vbtn SW_TABLET_MODE reporting to work there.

There was one other HP model which had a bit of a weird issue, this was fixed by:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d823346876a970522ff9e4d2b323c9b734dcc4de

But that workaround got dropped when we switched to ignoring SW_TABLET_MODE on all devices where the chassis_type is not 31 or 32, since the model which needed that fix ("HP Pavilion 11 x360") uses a chassis_type of 10, so that workaround was no longer needed.

So now it seems that we should not have dropped the workaround as possibly more HP models need it. If you can build your own 5.9.10 kernel with the linked workaround applied, and test it that would be great.

There should be docs somewhere on how to build an ubuntu kernel with patches applied yourself. If you do not feel up to doing this yourself, then please say so, then one of the Ubuntu devs should be able to provide a test kernel with the patch added for you.

Revision history for this message

piotrek (piotrek359) wrote on 2020-11-30:

#27

System: HP Convertible x360 11-ab0XX
$ cat /sys/class/dmi/id/chassis_type 10
Ubuntu 20.04 LTS.

Last available for download 5.4.0-54. No new karnel updates are detected. I'm confused because of what "Kevin Tang (dacto) wrote on 2020-11-25: #25" wrote. Not only because of new kernels available (that my computer doesn't see?)but of the fact that something works, stop's working, than is fixed and stops working again...

For me to use keyboard and touch-pad 5.4.0-42. is only solution available. :( I wanted to ask how to get those new kernels mentioned in previous posts, bout now seems no point in doing it?

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2020-11-30:

#28

The fix pointed by Hans is included in Ubuntu kernel 5.4.0-55.61 and onward.

Revision history for this message

Hans de Goede (j-w-r-degoede) wrote on 2020-12-02:

#29

@kaihengfeng, can you perhaps build a 5.9.xx kernel with:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d823346876a970522ff9e4d2b323c9b734dcc4de added for @dacto from comment 25 to test ?

His device gets intel-vbtn SW_TABLET_MODE support enabled based on the chassis-type, yet it seems to always report SW_TABLET_MODE=1, I want to know if the mentioned commit fixes this. This commit was a workaround introduced before we switched to an allow list (which includes certain chassis-types). This workaround was reverted after switching to the allow list, but since @dacto is still seeing this with 5.9.10 it looks like we may need the workaround even with the new allow-list approach.

@dacto, 2 questions:

1. What happens with 5.9.10 if you fold the 2-in-1 into tablet mode and then back into laptop/clamshell mode again, does that fix the kbd and touchpad not working ?

2. Can you provide an acpidump of your device? Run:

sudo acpidump -o acpidump.HP-Convertible-x360-11-ab0XX

And then attach the generated acpidump.HP-Convertible-x360-11-ab0XX file here, or send it directly to me: <email address hidden> .

###

So looking closer at the difference between 5.4.75 and 5.9.10, 5.9.10 has:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=21d64817c72470ed69483f59279ce557c0658826

Which 5.4.75 does not have, so this strongly suggests that despite switching to the allow list we still need the workaround for some HP models and it should be re-added (undoing the revert / undoing the dropping of the workaround).

I can take care of getting this re-added but first I would like to see some confirmation that this is indeed the problem.

Ideally you (@dacto) would test a 5.9.10 (or .11 or .12) kernel with the patch added, but I can also confirm that this patch needs to be re-added by looking at an acpidump.

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2020-12-03:

#30

5.9.12 + commit d823346876a970522ff9e4d2b323c9b734dcc4de:
https://people.canonical.com/~khfeng/lp1894017/

Revision history for this message

mark (pleasework12345) wrote on 2020-12-23:

#31

I am seeing a similar reproduction, but earlier at the FDE passphrase screen. My system apparently (at least under liveusb) reports /sys/class/dmi/id/chassis_type==31

Seems related, but i've posted a new bug due to the chassis type being "correct" (?) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909056

Revision history for this message

Carlos (fridugiso) wrote on 2020-12-23:

#32

This bug is fixed for me in kernel 5.4.0-58-lowlatency, Chuwi Minibook m3-8100Y. (The new bugs referred to above don't affect me, so far.)

Revision history for this message

Ashwin Ram kumar (ashrk) wrote on 2021-01-18:

#33

I just received an patch yesterday on Live patch for Ubuntu 20.04.1, the kernel version in my Laptop is 5.8.0-38-generic, but still I am having this same bug from Ubuntu. Did try blacklisting intel_vbtn "sudoedit /etc/modprobe.d/blacklist-intel_vbtn.conf" but the bug continues on my Dell Inspiron 15 5558.

This "cat /sys/class/dmi/id/chassis_type" give me a number: 9.

Is there anyother fix? and any potential dates the patch for the same is released

Revision history for this message

Ashwin Ram kumar (ashrk) wrote on 2021-01-18:

#34

And somehow my windows is behaving in the same way as well. Oh, and another thing, there is stream of b's (bbbbbbbbbbbbbbbbbbb) being generated on both OS on my Latop. Any help, would be great

Revision history for this message

Sasa J. (sipankh) wrote on 2021-02-19:

#35

I have the exact same problem; the keyboard type 10 and blacklistng intel_vbtn kernel module in /etc/modprobe.d/blacklist.conf and reboot didn't fix it. Tech info re hardware and OS: Distributor ID: Ubuntu Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 (had the same issue with 20.10 version and few other kernel versions)) Codename: hirsute Kernel running is 5.11.0-051100-generic Laptop is Lenovo W550s.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2021-02-19:

#36

Download full text (20.7 KiB)

This bug was fixed in the package linux - 5.10.0-14.15

---------------
linux (5.10.0-14.15) hirsute; urgency=medium

* hirsute/linux: 5.10.0-14.15 -proposed tracker (LP: #1913724)

* Restore palm ejection on multi-input devices (LP: #1913520)
- HID: multitouch: Apply MT_QUIRK_CONFIDENCE quirk for multi-input devices

* intel-hid is not loaded on new Intel platform (LP: #1907160)
- platform/x86: intel-hid: add Rocket Lake ACPI device ID

  * Hirsute update: v5.10.11 upstream stable release (LP: #1913430)
    - scsi: target: tcmu: Fix use-after-free of se_cmd->priv
    - mtd: rawnand: gpmi: fix dst bit offset when extracting raw payload
    - mtd: rawnand: nandsim: Fix the logic when selecting Hamming soft ECC engine
    - i2c: tegra: Wait for config load atomically while in ISR
    - i2c: bpmp-tegra: Ignore unknown I2C_M flags
    - platform/x86: ideapad-laptop: Disable touchpad_switch for ELAN0634
    - ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info()
    - ALSA: hda/realtek - Limit int mic boost on Acer Aspire E5-575T
    - ALSA: hda/via: Add minimum mute flag
    - crypto: xor - Fix divide error in do_xor_speed()
    - dm crypt: fix copy and paste bug in crypt_alloc_req_aead
    - ACPI: scan: Make acpi_bus_get_device() clear return pointer on error
    - btrfs: don't get an EINTR during drop_snapshot for reloc
    - btrfs: do not double free backref nodes on error
    - btrfs: fix lockdep splat in btrfs_recover_relocation
    - btrfs: don't clear ret in btrfs_start_dirty_block_groups
    - btrfs: send: fix invalid clone operations when cloning from the same file
      and root
    - fs: fix lazytime expiration handling in __writeback_single_inode()
    - pinctrl: ingenic: Fix JZ4760 support
    - mmc: core: don't initialize block size from ext_csd if not present
    - mmc: sdhci-of-dwcmshc: fix rpmb access
    - mmc: sdhci-xenon: fix 1.8v regulator stabilization
    - mmc: sdhci-brcmstb: Fix mmc timeout errors on S5 suspend
    - dm: avoid filesystem lookup in dm_get_dev_t()
    - dm integrity: fix a crash if "recalculate" used without "internal_hash"
    - dm integrity: conditionally disable "recalculate" feature
    - drm/atomic: put state on error path
    - drm/syncobj: Fix use-after-free
    - drm/amdgpu: remove gpu info firmware of green sardine
    - drm/amd/display: DCN2X Find Secondary Pipe properly in MPO + ODM Case
    - drm/i915/gt: Prevent use of engine->wa_ctx after error
    - drm/i915: Check for rq->hwsp validity after acquiring RCU lock
    - ASoC: Intel: haswell: Add missing pm_ops
    - ASoC: rt711: mutex between calibration and power state changes
    - SUNRPC: Handle TCP socket sends with kernel_sendpage() again
    - HID: sony: select CONFIG_CRC32
    - dm integrity: select CRYPTO_SKCIPHER
    - x86/hyperv: Fix kexec panic/hang issues
    - scsi: ufs: Relax the condition of UFSHCI_QUIRK_SKIP_MANUAL_WB_FLUSH_CTRL
    - scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback
    - scsi: qedi: Correct max length of CHAP secret
    - scsi: scsi_debug: Fix memleak in scsi_debug_init()
    - scsi: sd: Suppress spurious errors when WRITE SAME is being disabled
    - riscv: ...

This bug was fixed in the package linux - 5.10.0-14.15

---------------
linux (5.10.0-14.15) hirsute; urgency=medium

* hirsute/linux: 5.10.0-14.15 -proposed tracker (LP: #1913724)

* Restore palm ejection on multi-input devices (LP: #1913520)
    - HID: multitouch: Apply MT_QUIRK_CONFIDENCE quirk for multi-input devices

* intel-hid is not loaded on new Intel platform (LP: #1907160)
    - platform/x86: intel-hid: add Rocket Lake ACPI device ID

* Hirsute update: v5.10.11 upstream stable release (LP: #1913430)
    - scsi: target: tcmu: Fix use-after-free of se_cmd->priv
    - mtd: rawnand: gpmi: fix dst bit offset when extracting raw payload
    - mtd: rawnand: nandsim: Fix the logic when selecting Hamming soft ECC engine
    - i2c: tegra: Wait for config load atomically while in ISR
    - i2c: bpmp-tegra: Ignore unknown I2C_M flags
    - platform/x86: ideapad-laptop: Disable touchpad_switch for ELAN0634
    - ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info()
    - ALSA: hda/realtek - Limit int mic boost on Acer Aspire E5-575T
    - ALSA: hda/via: Add minimum mute flag
    - crypto: xor - Fix divide error in do_xor_speed()
    - dm crypt: fix copy and paste bug in crypt_alloc_req_aead
    - ACPI: scan: Make acpi_bus_get_device() clear return pointer on error
    - btrfs: don't get an EINTR during drop_snapshot for reloc
    - btrfs: do not double free backref nodes on error
    - btrfs: fix lockdep splat in btrfs_recover_relocation
    - btrfs: don't clear ret in btrfs_start_dirty_block_groups
    - btrfs: send: fix invalid clone operations when cloning from the same file
      and root
    - fs: fix lazytime expiration handling in __writeback_single_inode()
    - pinctrl: ingenic: Fix JZ4760 support
    - mmc: core: don't initialize block size from ext_csd if not present
    - mmc: sdhci-of-dwcmshc: fix rpmb access
    - mmc: sdhci-xenon: fix 1.8v regulator stabilization
    - mmc: sdhci-brcmstb: Fix mmc timeout errors on S5 suspend
    - dm: avoid filesystem lookup in dm_get_dev_t()
    - dm integrity: fix a crash if "recalculate" used without "internal_hash"
    - dm integrity: conditionally disable "recalculate" feature
    - drm/atomic: put state on error path
    - drm/syncobj: Fix use-after-free
    - drm/amdgpu: remove gpu info firmware of green sardine
    - drm/amd/display: DCN2X Find Secondary Pipe properly in MPO + ODM Case
    - drm/i915/gt: Prevent use of engine->wa_ctx after error
    - drm/i915: Check for rq->hwsp validity after acquiring RCU lock
    - ASoC: Intel: haswell: Add missing pm_ops
    - ASoC: rt711: mutex between calibration and power state changes
    - SUNRPC: Handle TCP socket sends with kernel_sendpage() again
    - HID: sony: select CONFIG_CRC32
    - dm integrity: select CRYPTO_SKCIPHER
    - x86/hyperv: Fix kexec panic/hang issues
    - scsi: ufs: Relax the condition of UFSHCI_QUIRK_SKIP_MANUAL_WB_FLUSH_CTRL
    - scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback
    - scsi: qedi: Correct max length of CHAP secret
    - scsi: scsi_debug: Fix memleak in scsi_debug_init()
    - scsi: sd: Suppress spurious errors when WRITE SAME is being disabled
    - riscv: Fix kernel time_init()
    - riscv: Fix sifive serial driver
    - riscv: Enable interrupts during syscalls with M-Mode
    - HID: logitech-dj: add the G602 receiver
    - HID: Ignore battery for Elan touchscreen on ASUS UX550
    - clk: tegra30: Add hda clock default rates to clock driver
    - ALSA: hda/tegra: fix tegra-hda on tegra30 soc
    - riscv: cacheinfo: Fix using smp_processor_id() in preemptible
    - arm64: make atomic helpers __always_inline
    - xen: Fix event channel callback via INTX/GSI
    - x86/xen: Add xen_no_vector_callback option to test PCI INTX delivery
    - x86/xen: Fix xen_hvm_smp_init() when vector callback not available
    - dts: phy: fix missing mdio device and probe failure of vsc8541-01 device
    - dts: phy: add GPIO number and active state used for phy reset
    - riscv: defconfig: enable gpio support for HiFive Unleashed
    - drm/amdgpu/psp: fix psp gfx ctrl cmds
    - drm/amd/display: disable dcn10 pipe split by default
    - HID: logitech-hidpp: Add product ID for MX Ergo in Bluetooth mode
    - drm/amd/display: Fix to be able to stop crc calculation
    - drm/nouveau/bios: fix issue shadowing expansion ROMs
    - drm/nouveau/privring: ack interrupts the same way as RM
    - drm/nouveau/i2c/gm200: increase width of aux semaphore owner fields
    - drm/nouveau/mmu: fix vram heap sizing
    - drm/nouveau/kms/nv50-: fix case where notifier buffer is at offset 0
    - io_uring: flush timeouts that should already have expired
    - libperf tests: If a test fails return non-zero
    - libperf tests: Fail when failing to get a tracepoint id
    - RISC-V: Set current memblock limit
    - RISC-V: Fix maximum allowed phsyical memory for RV32
    - x86/xen: fix 'nopvspin' build error
    - nfsd: Fixes for nfsd4_encode_read_plus_data()
    - nfsd: Don't set eof on a truncated READ_PLUS
    - gpiolib: cdev: fix frame size warning in gpio_ioctl()
    - pinctrl: aspeed: g6: Fix PWMG0 pinctrl setting
    - pinctrl: mediatek: Fix fallback call path
    - RDMA/ucma: Do not miss ctx destruction steps in some cases
    - btrfs: print the actual offset in btrfs_root_name
    - scsi: megaraid_sas: Fix MEGASAS_IOC_FIRMWARE regression
    - scsi: ufs: ufshcd-pltfrm depends on HAS_IOMEM
    - scsi: ufs: Fix tm request when non-fatal error happens
    - crypto: omap-sham - Fix link error without crypto-engine
    - bpf: Prevent double bpf_prog_put call from bpf_tracing_prog_attach
    - powerpc: Use the common INIT_DATA_SECTION macro in vmlinux.lds.S
    - powerpc: Fix alignment bug within the init sections
    - arm64: entry: remove redundant IRQ flag tracing
    - bpf: Reject too big ctx_size_in for raw_tp test run
    - drm/amdkfd: Fix out-of-bounds read in kdf_create_vcrat_image_cpu()
    - RDMA/umem: Avoid undefined behavior of rounddown_pow_of_two()
    - RDMA/cma: Fix error flow in default_roce_mode_store
    - printk: ringbuffer: fix line counting
    - printk: fix kmsg_dump_get_buffer length calulations
    - iov_iter: fix the uaccess area in copy_compat_iovec_from_user
    - i2c: octeon: check correct size of maximum RECV_LEN packet
    - drm/vc4: Unify PCM card's driver_name
    - platform/x86: intel-vbtn: Drop HP Stream x360 Convertible PC 11 from allow-
      list
    - platform/x86: hp-wmi: Don't log a warning on HPWMI_RET_UNKNOWN_COMMAND
      errors
    - gpio: sifive: select IRQ_DOMAIN_HIERARCHY rather than depend on it
    - xsk: Clear pool even for inactive queues
    - selftests: net: fib_tests: remove duplicate log test
    - can: dev: can_restart: fix use after free bug
    - can: vxcan: vxcan_xmit: fix use after free bug
    - can: peak_usb: fix use after free bugs
    - perf evlist: Fix id index for heterogeneous systems
    - i2c: sprd: depend on COMMON_CLK to fix compile tests
    - iio: common: st_sensors: fix possible infinite loop in st_sensors_irq_thread
    - iio: ad5504: Fix setting power-down state
    - drivers: iio: temperature: Add delay after the addressed reset command in
      mlx90632.c
    - iio: adc: ti_am335x_adc: remove omitted iio_kfifo_free()
    - counter:ti-eqep: remove floor
    - powerpc/64s: fix scv entry fallback flush vs interrupt
    - cifs: do not fail __smb_send_rqst if non-fatal signals are pending
    - irqchip/mips-cpu: Set IPI domain parent chip
    - x86/fpu: Add kernel_fpu_begin_mask() to selectively initialize state
    - x86/topology: Make __max_die_per_package available unconditionally
    - x86/mmx: Use KFPU_387 for MMX string operations
    - x86/setup: don't remove E820_TYPE_RAM for pfn 0
    - proc_sysctl: fix oops caused by incorrect command parameters
    - mm: memcg/slab: optimize objcg stock draining
    - mm: memcg: fix memcg file_dirty numa stat
    - mm: fix numa stats for thp migration
    - io_uring: iopoll requests should also wake task ->in_idle state
    - io_uring: fix SQPOLL IORING_OP_CLOSE cancelation state
    - io_uring: fix short read retries for non-reg files
    - intel_th: pci: Add Alder Lake-P support
    - stm class: Fix module init return on allocation failure
    - serial: mvebu-uart: fix tx lost characters at power off
    - ehci: fix EHCI host controller initialization sequence
    - USB: ehci: fix an interrupt calltrace error
    - usb: gadget: aspeed: fix stop dma register setting.
    - USB: gadget: dummy-hcd: Fix errors in port-reset handling
    - usb: udc: core: Use lock when write to soft_connect
    - usb: bdc: Make bdc pci driver depend on BROKEN
    - usb: cdns3: imx: fix writing read-only memory issue
    - usb: cdns3: imx: fix can't create core device the second time issue
    - xhci: make sure TRB is fully written before giving it to the controller
    - xhci: tegra: Delay for disabling LFPS detector
    - drivers core: Free dma_range_map when driver probe failed
    - driver core: Fix device link device name collision
    - driver core: Extend device_is_dependent()
    - drm/i915: s/intel_dp_sink_dpms/intel_dp_set_power/
    - drm/i915: Only enable DFP 4:4:4->4:2:0 conversion when outputting YCbCr
      4:4:4
    - x86/entry: Fix noinstr fail
    - x86/cpu/amd: Set __max_die_per_package on AMD
    - cls_flower: call nla_ok() before nla_next()
    - netfilter: rpfilter: mask ecn bits before fib lookup
    - tools: gpio: fix %llu warning in gpio-event-mon.c
    - tools: gpio: fix %llu warning in gpio-watch.c
    - drm/i915/hdcp: Update CP property in update_pipe
    - sh: dma: fix kconfig dependency for G2_DMA
    - sh: Remove unused HAVE_COPY_THREAD_TLS macro
    - locking/lockdep: Cure noinstr fail
    - ASoC: SOF: Intel: fix page fault at probe if i915 init fails
    - octeontx2-af: Fix missing check bugs in rvu_cgx.c
    - net: dsa: mv88e6xxx: also read STU state in mv88e6250_g1_vtu_getnext
    - selftests/powerpc: Fix exit status of pkey tests
    - sh_eth: Fix power down vs. is_opened flag ordering
    - nvme-pci: refactor nvme_unmap_data
    - nvme-pci: fix error unwind in nvme_map_data
    - cachefiles: Drop superfluous readpages aops NULL check
    - lightnvm: fix memory leak when submit fails
    - skbuff: back tiny skbs with kmalloc() in __netdev_alloc_skb() too
    - kasan: fix unaligned address is unhandled in kasan_remove_zero_shadow
    - kasan: fix incorrect arguments passing in kasan_add_zero_shadow
    - tcp: fix TCP socket rehash stats mis-accounting
    - net_sched: gen_estimator: support large ewma log
    - udp: mask TOS bits in udp_v4_early_demux()
    - ipv6: create multicast route with RTPROT_KERNEL
    - net_sched: avoid shift-out-of-bounds in tcindex_set_parms()
    - net_sched: reject silly cell_log in qdisc_get_rtab()
    - ipv6: set multicast flag on the multicast route
    - net: mscc: ocelot: allow offloading of bridge on top of LAG
    - net: Disable NETIF_F_HW_TLS_RX when RXCSUM is disabled
    - net: dsa: b53: fix an off by one in checking "vlan->vid"
    - tcp: do not mess with cloned skbs in tcp_add_backlog()
    - tcp: fix TCP_USER_TIMEOUT with zero window
    - net: mscc: ocelot: Fix multicast to the CPU port
    - net: core: devlink: use right genl user_ptr when handling port param get/set
    - pinctrl: qcom: Allow SoCs to specify a GPIO function that's not 0
    - pinctrl: qcom: No need to read-modify-write the interrupt status
    - pinctrl: qcom: Properly clear "intr_ack_high" interrupts when unmasking
    - pinctrl: qcom: Don't clear pending interrupts when enabling
    - x86/sev: Fix nonistr violation
    - tty: implement write_iter
    - tty: fix up hung_up_tty_write() conversion
    - net: systemport: free dev before on error path
    - x86/sev-es: Handle string port IO to kernel memory properly
    - tcp: Fix potential use-after-free due to double kfree()
    - drm/i915/hdcp: Get conn while content_type changed
    - bpf: Local storage helpers should check nullness of owner ptr passed
    - kernfs: implement ->read_iter
    - kernfs: implement ->write_iter
    - kernfs: wire up ->splice_read and ->splice_write
    - interconnect: imx8mq: Use icc_sync_state
    - fs/pipe: allow sendfile() to pipe again
    - Commit 9bb48c82aced ("tty: implement write_iter") converted the tty layer to
      use write_iter. Fix the redirected_tty_write declaration also in n_tty and
      change the comparisons to use write_iter instead of write. also in n_tty and
      change the comparisons to use write_iter instead of write.
    - mm: fix initialization of struct page for holes in memory layout
    - Revert "mm: fix initialization of struct page for holes in memory layout"
    - Linux 5.10.11

* High load from process irq/65-i2c-INT3  - kernel module tps6598x
    (LP: #1883511) // Hirsute update: v5.10.11 upstream stable release
    (LP: #1913430)
    - platform/x86: i2c-multi-instantiate: Don't create platform device for
      INT3515 ACPI nodes

* Hirsute update: v5.10.10 upstream stable release (LP: #1913429)
    - Revert "kconfig: remove 'kvmconfig' and 'xenconfig' shorthands"
    - x86/hyperv: Initialize clockevents after LAPIC is initialized
    - drm/amdgpu/display: drop DCN support for aarch64
    - bpf: Fix signed_{sub,add32}_overflows type handling
    - X.509: Fix crash caused by NULL pointer
    - nfsd4: readdirplus shouldn't return parent of export
    - bpf: Don't leak memory in bpf getsockopt when optlen == 0
    - bpf: Support PTR_TO_MEM{,_OR_NULL} register spilling
    - bpf: Fix helper bpf_map_peek_elem_proto pointing to wrong callback
    - net: ipa: modem: add missing SET_NETDEV_DEV() for proper sysfs links
    - net: fix use-after-free when UDP GRO with shared fraglist
    - udp: Prevent reuseport_select_sock from reading uninitialized socks
    - netxen_nic: fix MSI/MSI-x interrupts
    - net: ipv6: Validate GSO SKB before finish IPv6 processing
    - tipc: fix NULL deref in tipc_link_xmit()
    - mlxsw: core: Add validation of transceiver temperature thresholds
    - mlxsw: core: Increase critical threshold for ASIC thermal zone
    - net: mvpp2: Remove Pause and Asym_Pause support
    - rndis_host: set proper input size for OID_GEN_PHYSICAL_MEDIUM request
    - esp: avoid unneeded kmap_atomic call
    - net: dcb: Validate netlink message in DCB handler
    - net: dcb: Accept RTM_GETDCB messages carrying set-like DCB commands
    - rxrpc: Call state should be read with READ_ONCE() under some circumstances
    - i40e: fix potential NULL pointer dereferencing
    - net: stmmac: Fixed mtu channged by cache aligned
    - net: sit: unregister_netdevice on newlink's error path
    - net: stmmac: fix taprio schedule configuration
    - net: stmmac: fix taprio configuration when base_time is in the past
    - net: avoid 32 x truesize under-estimation for tiny skbs
    - dt-bindings: net: renesas,etheravb: RZ/G2H needs tx-internal-delay-ps
    - net: phy: smsc: fix clk error handling
    - net: dsa: clear devlink port type before unregistering slave netdevs
    - rxrpc: Fix handling of an unsupported token type in rxrpc_read()
    - net: stmmac: use __napi_schedule() for PREEMPT_RT
    - can: mcp251xfd: mcp251xfd_handle_rxif_one(): fix wrong NULL pointer check
    - drm/panel: otm8009a: allow using non-continuous dsi clock
    - mac80211: do not drop tx nulldata packets on encrypted links
    - mac80211: check if atf has been disabled in __ieee80211_schedule_txq
    - net: dsa: unbind all switches from tree when DSA master unbinds
    - cxgb4/chtls: Fix tid stuck due to wrong update of qid
    - spi: fsl: Fix driver breakage when SPI_CS_HIGH is not set in spi->mode
    - spi: cadence: cache reference clock rate during probe
    - Linux 5.10.10

* Remove scary stack trace from Realtek WiFi driver (LP: #1913263)
    - rtw88: reduce the log level for failure of tx report

* Packaging resync (LP: #1786013)
    - update dkms package versions

* Introduce the new NVIDIA 460-server series and update the 460 series
    (LP: #1913200)
    - [Config] dkms-versions -- add the 460-server nvidia driver

* backlight parsing for VBT 234+ (LP: #1912157)
    - drm/i915/vbt: Fix backlight parsing for VBT 234+
    - drm/i915/vbt: Update the version and expected size of
      BDB_GENERAL_DEFINITIONS map
    - drm/i915/vbt: Add VRR VBT toggle

* Support CML-S CPU + TGP PCH (LP: #1909457)
    - drm/i915/dg1: gmbus pin mapping
    - drm/i915/dg1: Don't program PHY_MISC for PHY-C and PHY-D
    - drm/i915/dg1: add hpd interrupt handling
    - drm/i915/display/ehl: Limit eDP to HBR2
    - drm/i915/jsl: Split EHL/JSL platform info and PCI ids
    - drm/i915: Add PORT_TCn aliases to enum port
    - drm/i915: s/PORT_TC/TC_PORT_/
    - drm/i915/rkl: new rkl ddc map for different PCH
    - SAUCE: drm/i915/gen9_bc : Add TGP PCH support

* Fix the video can't output through WD19TB connected with TGL platform during
    cold-boot (LP: #1910211)
    - SAUCE: drm/i915/dp: Prevent setting LTTPR mode if no LTTPR is detected

* Stop using get_scalar_status command in Dell AIO uart backlight driver
    (LP: #1865402)
    - SAUCE: platform/x86: dell-uart-backlight: add get_display_mode command

* Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable (LP: #1879633)
    - SAUCE: ath11k: add 64bit check before reading msi high addr
    - SAUCE: ath11k: pci: support platforms with one MSI vector
    - SAUCE: ath11k: dp_rx: fix monitor status dma unmap direction
    - SAUCE: ath11k: hook mhi suspend and resume
    - SAUCE: ath11k: implement hif suspend and resume functions.
    - SAUCE: ath11k: read select_window register to ensure write is finished
    - SAUCE: ath11k: implement htc suspend related callbacks
    - SAUCE: ath11k: put target to suspend when system enters suspend state
    - SAUCE: ath11k: pci: print a warning if firmware crashed
    - SAUCE: ath11k: qmi: print allocated memory segment addresses and sizes
    - SAUCE: HACK: ath11k: add delays to suspend and resume handlers
    - SAUCE: ath11k: put hw to DBS using WMI_PDEV_SET_HW_MODE_CMDID
    - SAUCE: ath11k: fix pcie link unstable issue
    - SAUCE: ath11k: fix PCI L1ss clock unstable problem
    - SAUCE: ath11k: disable OTP write privilege
    - SAUCE: ath11k: disable ASPM L0sLs before downloading firmware
    - SAUCE: ath11k: purge rx pktlog when entering suspend
    - SAUCE: ath11k: set credit_update flag for flow controlled ep only
    - SAUCE: ath11k: implement wow enable and wow wakeup command
    - SAUCE: ath11k: add ce irq enable and disable hif layer functions
    - SAUCE: ath11k: put target to wow state when suspend happens
    - SAUCE: ath11k: vdev delete synchronization with firmware
    - SAUCE: ath11k: peer delete synchronization with firmware

* Add support for Intel Bluetooth Device Typhoon Peak (8087:0032)
    (LP: #1890130)
    - SAUCE: Bluetooth: btintel: Fix endianness issue for TLV version information
    - SAUCE: Bluetooth: btusb: Add *setup* function for new generation Intel
      controllers
    - SAUCE: Bluetooth: btusb: Define a function to construct firmware filename
    - SAUCE: Bluetooth: btusb: Helper function to download firmware to Intel
      adapters
    - SAUCE: Bluetooth: btusb: Map Typhoon peak controller to BTUSB_INTEL_NEWGEN

* failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training
    Unsuccessful (LP: #1903969)
    - SAUCE: drm/i915: s/old_crtc_state/crtc_state/
    - SAUCE: drm/i915: Make intel_dp_process_phy_request() static
    - SAUCE: drm/i915: Shove the PHY test into the hotplug work
    - SAUCE: drm/i915: Split ICL combo PHY buf trans per output type
    - SAUCE: drm/i915: Split ICL MG PHY buf trans per output type
    - SAUCE: drm/i915: Split EHL combo PHY buf trans per output type
    - SAUCE: drm/i915: Split TGL combo PHY buf trans per output type
    - SAUCE: drm/i915: Split TGL DKL PHY buf trans per output type
    - SAUCE: drm/i915: Plumb crtc_state to link training
    - SAUCE: drm/i915: Fix DP link training pattern mask
    - SAUCE: drm/i915: Simplify the link training functions
    - SAUCE: drm/i915: Factor out a helper to disable the DPCD training pattern
    - SAUCE: drm/dp: Add LTTPR helpers
    - SAUCE: drm/i915: Switch to LTTPR transparent mode link training
    - SAUCE: drm/i915: Switch to LTTPR non-transparent mode link training

* switch to an autogenerated nvidia series based core via dkms-versions
    (LP: #1912803)
    - [Packaging] nvidia -- use dkms-versions to define versions built
    - [Packaging] update-version-dkms -- maintain flags fields
    - [Config] dkms-versions -- add transitional/skip information for nvidia
      packages

* Miscellaneous Ubuntu changes
    - [Config] Move some CONFIG_INTERCONNECT_QCOM_* options to different menu
    - SAUCE: selftests/seccomp: Accept any valid fd in user_notification_addfd
    - [Config] updateconfigs following v5.10.11 import
    - abi: gc bdc_pci module
    - zfs-modules.ignore: add zzstd

* Miscellaneous upstream changes
    - selftests/powerpc: Only test lwm/stmw on big endian

-- Paolo Pisati <paolo.pisati@canonical.com>  Fri, 29 Jan 2021 14:23:04 +0100

Changed in linux (Ubuntu):
status:	Confirmed → Fix Released

Revision history for this message

Nemo Fang (fyj123121) wrote on 2021-08-14:

#37

I still experience the problem on ubuntu 20.04 with Lenovo Slim 9 14ITL5. The kennel is: 5.11.0-25-generic, and "cat /sys/class/dmi/id/chassis_type" give me a number: 10. blacklisting intel_vbtn doesn't fix the problem for me.

Revision history for this message

Hans de Goede (j-w-r-degoede) wrote on 2021-08-30:

#38

Download full text (3.3 KiB)

I just typed a long email in reply to someone asking about the keyboard not working by email. The contents of that email are likely useful for other people who are still experiencing the keyboard not working too, so I've copy and pasted my entire reply below.

If you still need help with this please follow the provided debug instructions and provide the requested info.

###

First of all lets see if we can find the root cause. Bug 1894017
is about the keyboard events being discarded in userspace, because
userspace thinks the device is folded in tablet mode with the
keyboard behind the display (and any key-presses are thus done
accidentally).

Please install evemu and then run:

sudo evemu-record

This will give you a list of available input devices. The problems
reported in bug #1894017 are caused by a false-positive
reporting of SW_TABLET_MODE with a value of 1. By one of the
following input-devices:

"Intel HID events"
"Intel HID switches"
"Intel Virtual Buttons"
"Intel Virtual Switches"

Or something like this, you can select a device by typing the
number of its /dev/input/event# node.

After selecting a device evemu-record will print which events the
device can report. If it can report SW_TABLET_MODE then the
output will also contain the current value of SW_TABLET_MODE,
if this is 1 then that is the cause.

(press CTRL+c to exit evemu-record)

But you write "seems to stop responding at random" where as with
the SW_TABLET_MODE problem I would expect it to simply not work
at all (with certain kernel versions).

So you may very well have a different problem then the one described
in launchpad issue 1894017.

What you can also try is running "sudo evemu-record" and then selecting
the "AT Translated Set 2 keyboard" keyboard. After this if you type some
keys on the keyboard they should show up in evemu-record as key-presses.

If this works, then try doing it again (over e.g. ssh, or with an
external usb kbd) when the keyboard has stopped responding. I suspect
that you will find that at this point evemu-record will also no longer
report keys, which means that the problem is happening at a lower
level.

I suspect that you will find that the problem indeed is happening at
a lower-level and that you need something like this:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=addab6febc42ed94e4eee1abbe486150e4f8b9e9
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e5b1032a656e9aa4c7a4df77cb9156a2a651a5f9

In order to determine what is necessary to fix things I need
a number of things:

1. output of: "grep . /sys/class/dmi/id/* 2> /dev/null" run from a terminal

2. Install acpica-tools and then run: "sudo acpidump -o acpidump.txt" and then
attach the generated acpidump.txt file to your next email

3. It would help a lot if we can go from
"seems to stop responding at random" to "stops responding when I do a,
followed by b..." some ideas here are:
3.1 perhaps it stops responding after folding the display past 180 degrees
(so a little beyond it lyinf fully flat on the table) and then back again?
3.2 perhaps it stops responding after folding the display all the way back
so that the device ...

Ubuntu
linux package

Keyboard not working

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntulinux package

Keyboard not working

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package