Can't read CTR while initializing i8042

[Ozgur Kara]

i8042.c: Can't read CTR while initializing i8042

[Brian Murray (brian-murray)]

Thanks for your bug report. Where exactly did you see this error message? Additionally what version of Ubuntu did you see this error message in?

[MightyMan (mightyman002)]

I've got the same problem and I can't handle it. I used my machine in the evening, no modifications have made to it, synaptic, apt-get, automatix, aptitude were not run, and the next morning strange things occured!
While the OS was booting as usually, lot of @ signs appeared. Yet I was not affraid, since I've seen them while X was booting. But the Xserver didn't want to boot. Often the above was the only message I got, but the console was running great, so I could log in. And an other strange thing is that if I reinstall the nvidia driver, and give the startx command, X boots and the graphical interface works again. Next reboot or shutdown kill the things again, and the game begins! Reinstall nvidia driver, startx!
I'm using Edgy! Someone please help me!

[Tormod Volden (tormodvolden)]

This also prevents PS2 keyboards from working.

[Pascal De Vuyst (pascal-devuyst)]

Ozgur Karatas,
Do you still have this problem with Ubuntu 7.04 (Feisty) or with the latest Gutsy live CD?
If you still have the problem, please provide the minimal information as described here: https://wiki.ubuntu.com/KernelTeamBugPolicies and a good description of the problem you are facing.

MightyMan and Tormod Volden:
These kind off bugs are very machine/hardware specific and without minimal logs from the reporter it is very difficult to tell if this is the exact same problem that you are facing.
Please open seperate bug reports and provide the minimal information and a good description of the problem.

[Pascal De Vuyst (pascal-devuyst)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[David Oxland (doxland)]

Affects me using 16.04 just started a few days ago; Every boot.

[David Oxland (doxland)]

Still affecting me
Lenovo with AMD A10
 Don't know how to re open the bug
 No other apparent bad effects except that Wallch doesn't operate properly.

[Mkrapp (mkrapp)]

I got a new ASUS Zenbook 14 UM524UA. Unfortunately keyboard is not at all working in latest Tumbleweed with kernel 5.14.0-1-default.

I: Bus=0018 Vendor=04f3 Product=3134 Version=0100
  N: Name="ASUE140A:00 04F3:3134 Keyboard"
  P: Phys=i2c-ASUE140A:00
  S: Sysfs=/devices/platform/AMDI0010:03/i2c-0/i2c-ASUE140A:00/0018:04F3:3134.0001/input/input8
  U: Uniq=
  H: Handlers=sysrq kbd leds event5
  B: PROP=0
  B: EV=120013
  B: KEY=1000000000007 ff800000000007ff febeffdfffefffff fffffffffffffffe
  B: MSC=10
  B: LED=1f

It's recognized during boot:

> Aug 31 20:00:01 localhost kernel: input: ASUE140A:00 04F3:3134 Mouse as /devices/platform/AMDI0010:03/i2c-0/i2c-ASUE140A:00/0018:04F3:3134.0001/input/input3
> Aug 31 20:00:01 localhost kernel: input: ASUE140A:00 04F3:3134 Touchpad as /devices/platform/AMDI0010:03/i2c-0/i2c-ASUE140A:00/0018:04F3:3134.0001/input/input4
> Aug 31 20:00:01 localhost kernel: input: ASUE140A:00 04F3:3134 Keyboard as /devices/platform/AMDI0010:03/i2c-0/i2c-ASUE140A:00/0018:04F3:3134.0001/input/input5
> Aug 31 20:00:01 localhost kernel: hid-generic 0018:04F3:3134.0001: input,hidraw0: I2C HID v1.00 Mouse [ASUE140A:00 04F3:3134] on i2c-ASUE140A:00

but not working at all. no events created when pressing/releasing keys.
The touchpad works fine, albeit I didn't try to get the extra function working (numpad on touchpad) yet.
I'll attach hwinfo and journal in a minute.

Any idea how I can get the keyboard working?

[Mkrapp (mkrapp)]

Created attachment 852344
hwinfo

[Mkrapp (mkrapp)]

Created attachment 852345
Journal

[Mkrapp (mkrapp)]

Correction: Keyboard does not work after a cold boot.
Rebooting from login screen then makes the keyboard miraculously work.

[Mkrapp (mkrapp)]

and another one, keyboard also works in SLE-15-SP3 rescue system.

[Tiwai-r (tiwai-r)]

Could you get the dmesg output as well as hwinfo output from both working and non-working cases to compare? Often this kind of problem depends on the pinctrl driver, but in your case, the device it self was detected, so I'm not quite sure.

[Mkrapp (mkrapp)]

Let me reboot a couple times ;-)

What I spotted in dmesg when keyboard was NOT working:

[ 0.512668] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[ 0.512672] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 1.033609] i8042: Can't read CTR while initializing i8042
[ 1.033632] i8042: probe of i8042 failed with error -5
[ 1.033869] mousedev: PS/2 mouse device common for all mice

Compared to WORKING:

[ 0.491163] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[ 0.491166] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 0.492699] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.492884] mousedev: PS/2 mouse device common for all mice

I'll upload dmesg and hwinfo now

[Mkrapp (mkrapp)]

Created attachment 852400
dmesg where keyboard is not working

[Mkrapp (mkrapp)]

Created attachment 852401
hwinfo where keyboard is not working

[Mkrapp (mkrapp)]

Created attachment 852402
dmesg - keyboard is working

[Mkrapp (mkrapp)]

Created attachment 852403
hwinfo - keyboard is working

[Tiwai-r (tiwai-r)]

Thanks. So this is about PS/2 keyboard and by some unknown reason the initialization fails at the cold boot. Unfortunately it's not trivial to re-probe because of the built-in driver.

I rebuilt the latest stable kernel with changing the PS2 keyboard and mouse drivers to modules, which will allow you to reload after the boot.
The test kernel is found in OBS home:tiwai:bsc1190256 repo.
  http://download.opensuse.org/repositories/home:/tiwai:/bsc1190256/standard/

Could you give it a try? Prepare a USB keyboard while testing, as PS/2 modules might be not loaded automatically.
The modules to be tested are i8042, atkbd and psmouse. Check lsmod and load the missing one.

An interesting part is that, if those have been loaded but not working in the same way, try to unload and reload again.

[Mkrapp (mkrapp)]

Thank you, Takashi

That kernel worked out of the box

micha@susi:~> lsmod |egrep "(i8042|atkb|psmouse)"
atkbd 36864 0
libps2 20480 1 atkbd
i8042 32768 1 asus_nb_wmi

I'll do some more reboots, hopefully I get a another failure

[Tiwai-r (tiwai-r)]

OK, then it's likely a hairy timing issue. By moving the drivers from built-in to modules, the initialization of those devices are delayed, and this already made the things working.

As a final solution, we'd need to ask upstream. Let's see.

[Tiwai-r (tiwai-r)]

I'm building yet another test kernel with a hackish patch to re-probe the i8042 driver at the error. It's being built in OBS home:tiwai:bsc1190256-2 repo.
Please give it a try later.

[Mkrapp (mkrapp)]

Thanks, no luck unfortunately.
i8042 still is erroring out upon cold boot.

I bootet with i8042.debug=1 i8042.notimeout=1
dmesg snippets:

NON working:

[ 0.428604] ACPI: \_SB_.PLTF.P00F: Found 3 idle states
[ 0.428970] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 0.430325] Non-volatile memory driver v1.3
[ 0.430356] Linux agpgart interface v0.103
[ 0.494005] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[ 0.494054] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 0.494142] i8042: [0] 20 -> i8042 (command)
[ 0.497899] i8042: [0] -- i8042 (wait read timeout)
[ 1.015008] i8042: Can't read CTR while initializing i8042
[ 1.015028] i8042 i8042: probe deferral not supported
[ 1.015276] mousedev: PS/2 mouse device common for all mice

WORKING (after warm reboot)

[ 0.435691] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 0.436741] Non-volatile memory driver v1.3
[ 0.436771] Linux agpgart interface v0.103
[ 0.497612] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[ 0.497637] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 0.497724] i8042: [0] 9c <- i8042 (flush, kbd)
[ 0.497766] i8042: [0] 20 -> i8042 (command)
[ 0.498036] i8042: [0] 65 <- i8042 (return)
[ 0.498091] i8042: [0] 20 -> i8042 (command)
[ 0.498411] i8042: [0] 65 <- i8042 (return)
[ 0.498416] i8042: [0] 60 -> i8042 (command)
[ 0.498890] i8042: [0] 74 -> i8042 (parameter)
[ 0.499039] i8042: [1] 60 -> i8042 (command)
[ 0.499200] i8042: [1] 65 -> i8042 (parameter)
[ 0.499202] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.499365] mousedev: PS/2 mouse device common for all mice
[ 0.499399] i8042: [1] f2 -> i8042 (kbd-data)
[ 0.499436] rtc_cmos 00:01: RTC can wake from S4
[ 0.499772] rtc_cmos 00:01: registered as rtc0
[ 0.499863] rtc_cmos 00:01: setting system clock to 2021-09-10T19:33:29 UTC (1631302409)
[ 0.499916] rtc_cmos 00:01: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[ 0.499967] i8042: [1] fa <- i8042 (interrupt, 0, 1)
[ 0.500523] ledtrig-cpu: registered to indicate activity on CPUs
[ 0.500546] EFI Variables Facility v0.08 2004-May-17
[ 0.501990] hid: raw HID events driver (C) Jiri Kosina
[ 0.502058] drop_monitor: Initializing network drop monitor service
[ 0.502085] i8042: [1] ab <- i8042 (interrupt, 0, 1)
[ 0.502191] NET: Registered PF_INET6 protocol family
[ 0.505164] i8042: [2] 83 <- i8042 (interrupt, 0, 1)
[ 0.505205] i8042: [2] f5 -> i8042 (kbd-data)
[ 0.505525] i8042: [2] fa <- i8042 (interrupt, 0, 1)
[ 0.505565] i8042: [2] ed -> i8042 (kbd-data)
[ 0.506092] i8042: [2] fa <- i8042 (interrupt, 0, 1)
[ 0.506143] i8042: [2] 00 -> i8042 (kbd-data)
[ 0.506592] i8042: [3] fa <- i8042 (interrupt, 0, 1)
[ 0.506627] i8042: [3] f3 -> i8042 (kbd-data)
[ 0.507214] i8042: [3] fa <- i8042 (interrupt, 0, 1)
[ 0.507263] i8042: [3] 00 -> i8042 (kbd-data)
[ 0.507535] i8042: [3] fa <- i8042 (interrupt, 0, 1)
[ 0.507606] i8042: [3] f4 -> i8042 (kbd-data)
[ 0.508415...

[Tiwai-r (tiwai-r)]

Thanks. It turned out that the previous change wasn't sufficient, and now the upstream dev gave another piece to try.

I updated the same OBS repo home:tiwai:bsc1190256-2 again with the new patch. The test kernel is being built, which will be 5.14.2-*.g70babd3.
Please give it a try later again.

[Mkrapp (mkrapp)]

Created attachment 852445
dmesg, no kbd, kernel 5.14.2-2.g70babd3, warm reboot

Doesn't work, unfortunately.

Now keyboard does not work at all anymore, not even after a warm reboot.

From dmesg (cold boot):

[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.14.2-2.g70babd3-default root=UUID=5fb3cc61-c68e-452f-8c55-a535662ce163 splash=verbose mitigations=auto i8042.debug=1
[ 0.016568] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.14.2-2.g70babd3-default root=UUID=5fb3cc61-c68e-452f-8c55-a535662ce163 splash=verbose mitigations=auto i8042.debug=1
[ 0.488793] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[ 0.488818] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 0.488906] i8042: [0] 9c <- i8042 (flush, kbd)

WARM boot:

[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.14.2-2.g70babd3-default root=UUID=5fb3cc61-c68e-452f-8c55-a535662ce163 splash=verbose mitigations=auto i8042.debug=1
[ 0.016655] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.14.2-2.g70babd3-default root=UUID=5fb3cc61-c68e-452f-8c55-a535662ce163 splash=verbose mitigations=auto i8042.debug=1
[ 0.499830] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[ 0.499855] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 0.499943] i8042: [0] 9c <- i8042 (flush, kbd)

[Tiwai-r (tiwai-r)]

Thanks. The upstream gave yet another try for the approach, and a new kernel is being built again on the same OBS repo, home:tiwai:bsc1190256-2.

Also, I'm building one more another test kernel with a different change, just move the input init to a bit later. That's being built in OBS home:tiwai:bsc1190256-3 repo.

It'd be appreciated if you can test them later.

[Mkrapp (mkrapp)]

Sorry, been off for a few days.

(In reply to Takashi Iwai from comment #18)
> Thanks. The upstream gave yet another try for the approach, and a new
> kernel is being built again on the same OBS repo, home:tiwai:bsc1190256-2.

That one worked despite the CTR error:

[ 0.000000] Linux version 5.14.2-3.g9458b22-default (geeko@buildhost) (gcc (SUSE Linux) 11.2.1 20210816 [revision 056e324ce46a7924b5cf10f61010cf9dd2ca10e9], GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.36.1.20210326-4) #1 SMP Sun Sep 12 20:15:58 UTC 2021 (9458b22)
[ 0.484315] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[ 0.484318] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 1.005361] i8042: Can't read CTR while initializing i8042
[ 1.477053] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.503700] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2

Seems it takes more than a secod to initialize, ugh

> Also, I'm building one more another test kernel with a different change,
> just move the input init to a bit later. That's being built in OBS
> home:tiwai:bsc1190256-3 repo.

This one did NOT work on cold boot, but on the warm reboot after:

[ 0.000000] Linux version 5.14.2-1.gcf0b6a8-default (geeko@buildhost) (gcc (SUSE Linux) 11.2.1 20210816 [revision 056e324ce46a7924b5cf10f61010cf9dd2ca10e9], GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.36.1.20210326-4) #1 SMP Sun Sep 12 20:23:35 UTC 2021 (cf0b6a8)
[ 0.502135] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[ 0.502137] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 1.023109] i8042: Can't read CTR while initializing i8042
[ 1.023133] i8042: probe of i8042 failed with error -5

WARM reboot:

[ 0.000000] Linux version 5.14.2-1.gcf0b6a8-default (geeko@buildhost) (gcc (SUSE Linux) 11.2.1 20210816 [revision 056e324ce46a7924b5cf10f61010cf9dd2ca10e9], GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.36.1.20210326-4) #1 SMP Sun Sep 12 20:23:35 UTC 2021 (cf0b6a8)
[ 0.514367] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[ 0.514369] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 0.515812] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.525691] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0

On the warm reboot it seems to initialize much faster

[Tiwai-r (tiwai-r)]

(In reply to Michael Krapp from comment #19)
> Sorry, been off for a few days.
>
> (In reply to Takashi Iwai from comment #18)
> > Thanks. The upstream gave yet another try for the approach, and a new
> > kernel is being built again on the same OBS repo, home:tiwai:bsc1190256-2.
>
> That one worked despite the CTR error:
>
> [ 0.000000] Linux version 5.14.2-3.g9458b22-default (geeko@buildhost)
> (gcc (SUSE Linux) 11.2.1 20210816 [revision
> 056e324ce46a7924b5cf10f61010cf9dd2ca10e9], GNU ld (GNU Binutils; openSUSE
> Tumbleweed) 2.36.1.20210326-4) #1 SMP Sun Sep 12 20:15:58 UTC 2021 (9458b22)
> [ 0.484315] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
> [ 0.484318] i8042: PNP: PS/2 appears to have AUX port disabled, if this
> is incorrect please boot with i8042.nopnp
> [ 1.005361] i8042: Can't read CTR while initializing i8042
> [ 1.477053] serio: i8042 KBD port at 0x60,0x64 irq 1
> [ 1.503700] input: AT Translated Set 2 keyboard as
> /devices/platform/i8042/serio0/input/input2
>
> Seems it takes more than a secod to initialize, ugh

Could you give the full dmesg output? (Not needed for the second kernel that failed.)

[Mkrapp (mkrapp)]

Created attachment 852567
dmesg, cold boot with 5.14.2-3.g9458b22

(In reply to Takashi Iwai from comment #20)
> (In reply to Michael Krapp from comment #19)
...
> > That one worked despite the CTR error:
> >
> > [ 0.000000] Linux version 5.14.2-3.g9458b22-default (geeko@buildhost)
> > (gcc (SUSE Linux) 11.2.1 20210816 [revision
...
> Could you give the full dmesg output? (Not needed for the second kernel
> that failed.)

Here is a fresh one

[Tiwai-r (tiwai-r)]

I refreshed OBS home:tiwai:bsc1190256-2 repo with the latest patch. The 5.15.0 kernel is being built there, could you give it a try and verify that it works later? Once after confirming, I'll try to submit the fix to the upstream.

[Mkrapp (mkrapp)]

Created attachment 853721
dmesg, cold boot with 5.15.0-1.g8b20058

That one works like a charm :)
I tried several times and it worked at every boot.

Thank you!

[Tiwai-r (tiwai-r)]

Thanks for testing. I submitted the fix now and will backport it to TW kernel.

[Jcheung (jcheung)]

I see the below patch is just backported and submitted to 15 SP4 kernel

commit 0a16328b172b9c25243f925338af97e5d25e7969
Author: Takashi Iwai <email address hidden>
Date: Wed Nov 17 07:49:57 2021 +0100

    Input: i8042 - Add deferred probe support (bsc#1190256).

[Swamp-a (swamp-a)]

openSUSE-SU-2022:0169-1: An update that solves 10 vulnerabilities and has 32 fixes is now available.

Category: security (important)
Bug References: 1065729,1071995,1154353,1154492,1156395,1167773,1176447,1176774,1177437,1190256,1191271,1191929,1192931,1193255,1193328,1193660,1193669,1193727,1193901,1193927,1194001,1194027,1194087,1194094,1194302,1194493,1194516,1194517,1194518,1194529,1194578,1194580,1194584,1194586,1194587,1194589,1194590,1194591,1194592,1194888,1194953,1194985
CVE References: CVE-2021-4083,CVE-2021-4135,CVE-2021-4149,CVE-2021-4197,CVE-2021-4202,CVE-2021-45485,CVE-2021-45486,CVE-2021-46283,CVE-2022-0185,CVE-2022-0322
JIRA References:
Sources used:
openSUSE Leap 15.3 (src): kernel-azure-5.3.18-150300.38.37.1, kernel-source-azure-5.3.18-150300.38.37.1, kernel-syms-azure-5.3.18-150300.38.37.1

[Swamp-a (swamp-a)]

SUSE-SU-2022:0169-1: An update that solves 10 vulnerabilities and has 32 fixes is now available.

Category: security (important)
Bug References: 1065729,1071995,1154353,1154492,1156395,1167773,1176447,1176774,1177437,1190256,1191271,1191929,1192931,1193255,1193328,1193660,1193669,1193727,1193901,1193927,1194001,1194027,1194087,1194094,1194302,1194493,1194516,1194517,1194518,1194529,1194578,1194580,1194584,1194586,1194587,1194589,1194590,1194591,1194592,1194888,1194953,1194985
CVE References: CVE-2021-4083,CVE-2021-4135,CVE-2021-4149,CVE-2021-4197,CVE-2021-4202,CVE-2021-45485,CVE-2021-45486,CVE-2021-46283,CVE-2022-0185,CVE-2022-0322
JIRA References:
Sources used:
SUSE Linux Enterprise Module for Public Cloud 15-SP3 (src): kernel-azure-5.3.18-150300.38.37.1, kernel-source-azure-5.3.18-150300.38.37.1, kernel-syms-azure-5.3.18-150300.38.37.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.

[Swamp-a (swamp-a)]

SUSE-SU-2022:0198-1: An update that solves 10 vulnerabilities and has 33 fixes is now available.

Category: security (important)
Bug References: 1065729,1071995,1154353,1154492,1156395,1167773,1176447,1176774,1177437,1190256,1191271,1191929,1192931,1193255,1193328,1193660,1193669,1193727,1193901,1193927,1194001,1194027,1194087,1194094,1194266,1194302,1194493,1194516,1194517,1194518,1194529,1194578,1194580,1194584,1194586,1194587,1194589,1194590,1194591,1194592,1194888,1194953,1194985
CVE References: CVE-2021-4083,CVE-2021-4135,CVE-2021-4149,CVE-2021-4197,CVE-2021-4202,CVE-2021-45485,CVE-2021-45486,CVE-2021-46283,CVE-2022-0185,CVE-2022-0322
JIRA References:
Sources used:
SUSE MicroOS 5.1 (src): kernel-default-5.3.18-150300.59.43.1, kernel-default-base-5.3.18-150300.59.43.1.150300.18.27.1
SUSE Linux Enterprise Workstation Extension 15-SP3 (src): kernel-default-5.3.18-150300.59.43.1, kernel-preempt-5.3.18-150300.59.43.1
SUSE Linux Enterprise Module for Live Patching 15-SP3 (src): kernel-default-5.3.18-150300.59.43.1, kernel-livepatch-SLE15-SP3_Update_12-1-150300.7.3.1
SUSE Linux Enterprise Module for Legacy Software 15-SP3 (src): kernel-default-5.3.18-150300.59.43.1
SUSE Linux Enterprise Module for Development Tools 15-SP3 (src): kernel-docs-5.3.18-150300.59.43.1, kernel-obs-build-5.3.18-150300.59.43.1, kernel-preempt-5.3.18-150300.59.43.1, kernel-source-5.3.18-150300.59.43.1, kernel-syms-5.3.18-150300.59.43.1
SUSE Linux Enterprise Module for Basesystem 15-SP3 (src): kernel-64kb-5.3.18-150300.59.43.1, kernel-default-5.3.18-150300.59.43.1, kernel-default-base-5.3.18-150300.59.43.1.150300.18.27.1, kernel-preempt-5.3.18-150300.59.43.1, kernel-source-5.3.18-150300.59.43.1, kernel-zfcpdump-5.3.18-150300.59.43.1
SUSE Linux Enterprise High Availability 15-SP3 (src): kernel-default-5.3.18-150300.59.43.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.

[Swamp-a (swamp-a)]

openSUSE-SU-2022:0198-1: An update that solves 10 vulnerabilities and has 33 fixes is now available.

Category: security (important)
Bug References: 1065729,1071995,1154353,1154492,1156395,1167773,1176447,1176774,1177437,1190256,1191271,1191929,1192931,1193255,1193328,1193660,1193669,1193727,1193901,1193927,1194001,1194027,1194087,1194094,1194266,1194302,1194493,1194516,1194517,1194518,1194529,1194578,1194580,1194584,1194586,1194587,1194589,1194590,1194591,1194592,1194888,1194953,1194985
CVE References: CVE-2021-4083,CVE-2021-4135,CVE-2021-4149,CVE-2021-4197,CVE-2021-4202,CVE-2021-45485,CVE-2021-45486,CVE-2021-46283,CVE-2022-0185,CVE-2022-0322
JIRA References:
Sources used:
openSUSE Leap 15.4 (src): dtb-aarch64-5.3.18-150300.59.43.1, kernel-preempt-5.3.18-150300.59.43.1
openSUSE Leap 15.3 (src): dtb-aarch64-5.3.18-150300.59.43.1, kernel-64kb-5.3.18-150300.59.43.1, kernel-debug-5.3.18-150300.59.43.1, kernel-default-5.3.18-150300.59.43.1, kernel-default-base-5.3.18-150300.59.43.1.150300.18.27.1, kernel-docs-5.3.18-150300.59.43.1, kernel-kvmsmall-5.3.18-150300.59.43.1, kernel-obs-build-5.3.18-150300.59.43.1, kernel-obs-qa-5.3.18-150300.59.43.1, kernel-preempt-5.3.18-150300.59.43.1, kernel-source-5.3.18-150300.59.43.1, kernel-syms-5.3.18-150300.59.43.1, kernel-zfcpdump-5.3.18-150300.59.43.1

[Ming-Long Huang (kouakitaki)]

There was a new kernel parameter added recently called i8042.probe_defer, which solved the issue for me on Thinkpad X13 AMD Gen 1.

See this for more details: https://lkml.org/lkml/2021/12/27/796

[Swamp-a (swamp-a)]

SUSE-SU-2022:0288-1: An update that solves 9 vulnerabilities, contains 7 features and has 30 fixes is now available.

Category: security (important)
Bug References: 1065729,1071995,1154353,1154492,1156395,1167773,1176447,1176774,1177437,1190256,1191271,1192931,1193255,1193328,1193669,1193727,1193767,1193901,1193927,1194001,1194027,1194302,1194493,1194516,1194517,1194518,1194529,1194580,1194584,1194586,1194587,1194589,1194590,1194591,1194592,1194888,1194953,1194985,1195062
CVE References: CVE-2021-4083,CVE-2021-4135,CVE-2021-4149,CVE-2021-4197,CVE-2021-4202,CVE-2021-44733,CVE-2021-46283,CVE-2022-0185,CVE-2022-0322
JIRA References: SLE-13294,SLE-13533,SLE-14777,SLE-15172,SLE-16683,SLE-23432,SLE-8464
Sources used:
SUSE Linux Enterprise Module for Realtime 15-SP3 (src): kernel-rt-5.3.18-150300.71.1, kernel-rt_debug-5.3.18-150300.71.1, kernel-source-rt-5.3.18-150300.71.1, kernel-syms-rt-5.3.18-150300.71.1
SUSE Linux Enterprise Micro 5.1 (src): kernel-rt-5.3.18-150300.71.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.

[Khris10 (khris10)]

I think i've found it after a few very long hours try i8042.probe_defer
this commit was made for UX425UA but it helped on my QA version
https://lore.kernel.org/lkml/2021111218 … suse.de/T/

[Khris10 (khris10)]

(In reply to Krzysztof Para from comment #38)
> I think i've found it after a few very long hours try i8042.probe_defer
> this commit was made for UX425UA but it helped on my QA version
> https://lore.kernel.org/lkml/2021111218 … suse.de/T/

https://<email address hidden>/T/

[Tiwai-r (tiwai-r)]

(In reply to Krzysztof Para from comment #39)
> (In reply to Krzysztof Para from comment #38)
> > I think i've found it after a few very long hours try i8042.probe_defer
> > this commit was made for UX425UA but it helped on my QA version
> > https://lore.kernel.org/lkml/2021111218 … suse.de/T/
>
> https://<email address hidden>/T/

Could you give the hwinfo output from your device? The quirk entry needs to be extended to match with yours.

[Omegalulelegiggle (omegalulelegiggle)]

(In reply to Takashi Iwai from comment #40)
> (In reply to Krzysztof Para from comment #39)
> > (In reply to Krzysztof Para from comment #38)
> > > I think i've found it after a few very long hours try i8042.probe_defer
> > > this commit was made for UX425UA but it helped on my QA version
> > > https://lore.kernel.org/lkml/2021111218 … suse.de/T/
> >
> > https://<email address hidden>/T/
>
> Could you give the hwinfo output from your device? The quirk entry needs to
> be extended to match with yours.

Hi, I have the UM425QA as well, however I'm not too sure how to get the hwinfo output.

If I run 'cat /sys/class/dmi/id/product_name' I get 'ZenBook UX425QA_UM425QA'

And 'cat /sys/class/dmi/id/board_vendor' gives me 'ASUSTek COMPUTER INC.'

Maybe this is enough information for you to add the quirk entry. If not, please let me know on what I need to do.

Thanks

[Tiwai-r (tiwai-r)]

Thanks. Now I modified the DMI quirk table to adapt more ZenBook models.

A test TW kernel is being built in OBS home:tiwai:bsc1190256-3 repo. It'll be available later at
  http://download.opensuse.org/repositories/home:/tiwai:/bsc1190256-3/standard/

Please give it a try (without probe_defer option). If it's confirmed to work, I'll submit to the upstream and merge to TW and SLE15-SP4 kernels.

[Omegalulelegiggle (omegalulelegiggle)]

(In reply to Takashi Iwai from comment #42)
> Thanks. Now I modified the DMI quirk table to adapt more ZenBook models.
>
> A test TW kernel is being built in OBS home:tiwai:bsc1190256-3 repo. It'll
> be available later at
>
> http://download.opensuse.org/repositories/home:/tiwai:/bsc1190256-3/standard/
>
> Please give it a try (without probe_defer option). If it's confirmed to
> work, I'll submit to the upstream and merge to TW and SLE15-SP4 kernels.

Yes, it is working now! Tried multiple cold boots, keyboard worked fine each time. Did not use probe_defer. I do get the 'Can't read CTR while initializing i8042' on cold boots.

Thanks

[Tiwai-r (tiwai-r)]

OK, thanks for quick testing.

I submitted the fix patch to the upstream, and also backported to stable branch.
Hopefully it'll get merged soon later.

Let's close.

[Swamp-a (swamp-a)]

SUSE-SU-2022:2722-1: An update that solves 5 vulnerabilities, contains 9 features and has 31 fixes is now available.

Category: security (important)
Bug References: 1190256,1190497,1198410,1198829,1199086,1199291,1199364,1199665,1199670,1200015,1200465,1200494,1200644,1200651,1201258,1201323,1201381,1201391,1201427,1201458,1201471,1201524,1201592,1201593,1201595,1201596,1201635,1201651,1201675,1201691,1201705,1201725,1201846,1201930,1201954,1201958
CVE References: CVE-2021-33655,CVE-2022-1462,CVE-2022-21505,CVE-2022-29581,CVE-2022-32250
JIRA References: SLE-18130,SLE-20183,SLE-21132,SLE-24569,SLE-24570,SLE-24571,SLE-24578,SLE-24635,SLE-24682
Sources used:
openSUSE Leap 15.4 (src): kernel-azure-5.14.21-150400.14.10.1, kernel-source-azure-5.14.21-150400.14.10.1, kernel-syms-azure-5.14.21-150400.14.10.1
SUSE Linux Enterprise Module for Public Cloud 15-SP4 (src): kernel-azure-5.14.21-150400.14.10.1, kernel-source-azure-5.14.21-150400.14.10.1, kernel-syms-azure-5.14.21-150400.14.10.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.

[Swamp-a (swamp-a)]

SUSE-SU-2022:2803-1: An update that solves 5 vulnerabilities, contains 7 features and has 16 fixes is now available.

Category: security (important)
Bug References: 1190256,1190497,1199291,1199356,1199665,1201258,1201323,1201391,1201458,1201592,1201593,1201595,1201596,1201635,1201651,1201691,1201705,1201726,1201846,1201930,1202094
CVE References: CVE-2021-33655,CVE-2022-21505,CVE-2022-2585,CVE-2022-26373,CVE-2022-29581
JIRA References: SLE-21132,SLE-24569,SLE-24570,SLE-24571,SLE-24578,SLE-24635,SLE-24682
Sources used:
openSUSE Leap 15.4 (src): dtb-aarch64-5.14.21-150400.24.18.1, kernel-64kb-5.14.21-150400.24.18.1, kernel-debug-5.14.21-150400.24.18.1, kernel-default-5.14.21-150400.24.18.1, kernel-default-base-5.14.21-150400.24.18.1.150400.24.5.4, kernel-docs-5.14.21-150400.24.18.1, kernel-kvmsmall-5.14.21-150400.24.18.1, kernel-obs-build-5.14.21-150400.24.18.1, kernel-obs-qa-5.14.21-150400.24.18.1, kernel-source-5.14.21-150400.24.18.1, kernel-syms-5.14.21-150400.24.18.1, kernel-zfcpdump-5.14.21-150400.24.18.1
SUSE Linux Enterprise Workstation Extension 15-SP4 (src): kernel-default-5.14.21-150400.24.18.1
SUSE Linux Enterprise Module for Live Patching 15-SP4 (src): kernel-default-5.14.21-150400.24.18.1, kernel-livepatch-SLE15-SP4_Update_2-1-150400.9.5.2
SUSE Linux Enterprise Module for Legacy Software 15-SP4 (src): kernel-default-5.14.21-150400.24.18.1
SUSE Linux Enterprise Module for Development Tools 15-SP4 (src): kernel-docs-5.14.21-150400.24.18.1, kernel-obs-build-5.14.21-150400.24.18.1, kernel-source-5.14.21-150400.24.18.1, kernel-syms-5.14.21-150400.24.18.1
SUSE Linux Enterprise Module for Basesystem 15-SP4 (src): kernel-64kb-5.14.21-150400.24.18.1, kernel-default-5.14.21-150400.24.18.1, kernel-default-base-5.14.21-150400.24.18.1.150400.24.5.4, kernel-source-5.14.21-150400.24.18.1, kernel-zfcpdump-5.14.21-150400.24.18.1
SUSE Linux Enterprise High Availability 15-SP4 (src): kernel-default-5.14.21-150400.24.18.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.

[Mkubecek (mkubecek)]

The patch might be obsoleted by mainline commit ff946268a081 ("Input: i8042 -
merge quirk tables") in upcoming 6.0-rc1 but I can't say for sure. If it's
not, it will need to be replaced by a different one after said commit.

Once 6.0-rc1 reaches Kernel:HEAD, could someone with affected hardware check
if the issue does not reappear?

[Tiwai-r (tiwai-r)]

(In reply to Michal Kubeček from comment #55)
> The patch might be obsoleted by mainline commit ff946268a081 ("Input: i8042 -
> merge quirk tables") in upcoming 6.0-rc1 but I can't say for sure. If it's
> not, it will need to be replaced by a different one after said commit.

The patch needs to be refreshed to the original version I posted that already takes the suggested commit into account:
 https://<email address hidden>/

The patch currently found in our master/stable branches is a modified version for the older kernels.

Maybe I need to ping the upstream.

[Mkubecek (mkubecek)]

Sorry for the noise, when checking why the patch stopped applying yesteday,
I noticed only the part of commit ff946268a081 where the match was removed

> {
> - /* ASUS ZenBook UX425UA */
> .matches = {
> - DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
> - DMI_MATCH(DMI_PRODUCT_NAME, "ZenBook UX425UA"),
> + DMI_MATCH(DMI_CHASSIS_TYPE, "10"), /* Notebook */
> },
> },

but I somehow managed to completely miss this part:

> {
> + /* ASUS ZenBook UX425UA */
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
> - DMI_MATCH(DMI_PRODUCT_NAME, "X750LN"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "ZenBook UX425UA"),
> },
> + .driver_data = (void *)(SERIO_QUIRK_PROBE_DEFER | SERIO_QUIRK_RESET_NEVER)
> },

so I thought upstream switched to matching by a diffent key.

[Mkrapp (mkrapp)]

(In reply to Michal Kubeček from comment #55)
> The patch might be obsoleted by mainline commit ff946268a081 ("Input: i8042 -
> merge quirk tables") in upcoming 6.0-rc1 but I can't say for sure. If it's
> not, it will need to be replaced by a different one after said commit.
>
> Once 6.0-rc1 reaches Kernel:HEAD, could someone with affected hardware check
> if the issue does not reappear?

Is that the version you were looking for?
Linux susi.krapp.internal 6.0.0-rc1-1.gc35dc38-default #1 SMP PREEMPT_DYNAMIC Mon Aug 15 00:08:48 UTC 2022 (c35dc38) x86_64 x86_64 x86_64 GNU/Linux

Worksforme :-)

micha@susi:~> sudo journalctl -b|grep i8042
Aug 16 00:54:48 susi kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
Aug 16 00:54:48 susi kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Aug 16 00:54:48 susi kernel: i8042: Can't read CTR while initializing i8042
Aug 16 00:54:48 susi kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Aug 16 00:54:48 susi kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0

[Mkubecek (mkubecek)]

(In reply to Michael Krapp from comment #58)
> Is that the version you were looking for?
> Linux susi.krapp.internal 6.0.0-rc1-1.gc35dc38-default #1 SMP
> PREEMPT_DYNAMIC Mon Aug 15 00:08:48 UTC 2022 (c35dc38) x86_64 x86_64 x86_64
> GNU/Linux
>
> Worksforme :-)

That's surprising as this snapshot does not have Takashi's refresh of the
patch (only disabled previous version) so that it's not supposed to work.

[Tiwai-r (tiwai-r)]

Maybe not tested after the cold boot? Or it might have been fixed in BIOS side :) The quirk is about instability and retrying the probe.

[Mkrapp (mkrapp)]

Created attachment 860795
dmesg - Kernel 6.0.0-rc1-1.gc35dc38-default - Cold boot

No, I did test it. :) Again this morning, cold and warm boot. Still works
The only difference is that I disabled secure boot for kernel 6.0

BIOS is still the same, ASUS didn't release a new version yet.
See dmesg (cold boot) attached, let me know if you want a hwinfo also, please

[Tiwai-r (tiwai-r)]

Interesting. So the recent driver works somehow better in this regard although the fix wasn't intended. We may drop the quirk patch, then.

[Jslaby-h (jslaby-h)]

What's the state of this? The patch is still enabled in master and stable. So can it be dropped?

[Tiwai-r (tiwai-r)]

Possibly, but I believe it's still safer to keep the workaround. It's always a timing issue.

The upstreamed patch was somehow forgotten since it was submitted during the big change in i8042 quirk handling. I'll try to resubmit.

[Comphi (comphi)]

Hello,
my Zenbook has the same issue.
cat /sys/class/dmi/id/product_name gives ZenBook UX325SA_UM325SA
cat /sys/class/dmi/id/board_vendor gives ASUSTek COMPUTER INC.
It would be nice if you could add them to the patch as well.
Thanks

[Tiwai-r (tiwai-r)]

(In reply to Phi from comment #65)
> Hello,
> my Zenbook has the same issue.
> cat /sys/class/dmi/id/product_name gives ZenBook UX325SA_UM325SA
> cat /sys/class/dmi/id/board_vendor gives ASUSTek COMPUTER INC.
> It would be nice if you could add them to the patch as well.

Does the problem happen with the latest TW kernel, too?

[Comphi (comphi)]

(In reply to Takashi Iwai from comment #66)
> (In reply to Phi from comment #65)
> > Hello,
> > my Zenbook has the same issue.
> > cat /sys/class/dmi/id/product_name gives ZenBook UX325SA_UM325SA
> > cat /sys/class/dmi/id/board_vendor gives ASUSTek COMPUTER INC.
> > It would be nice if you could add them to the patch as well.
>
> Does the problem happen with the latest TW kernel, too?

Luckily, it somehow works now, at least in TW.
I found out that there is a bios update so I applied it. I also disabled secure boot and did a fresh install of TW (6.0.8). Not sure which part fixed it, but the problem is gone now.

I also installed arch 6.0.8, and the problem still happens there, but I guess that is a different story. Maybe 6.1 will fix it

[Martin00greco (martin00greco)]

Hi, I'm struggling with same issue but in ASUS Q408UG model.. I'd like to try if this kernel works.. The problem is that I don't have a clue how to download and install it.. If someone could give me a hand, I'd appreciate a lot

[Tiwai-r (tiwai-r)]

(In reply to Martin Greco from comment #68)
> Hi, I'm struggling with same issue but in ASUS Q408UG model.. I'd like to
> try if this kernel works.. The problem is that I don't have a clue how to
> download and install it.. If someone could give me a hand, I'd appreciate a
> lot

You can try to pass i8042.probe_defer=1 boot option for the recent kernels.
If this solves the problem, we may add the similar quirk entry. If it doesn't, it must be another problem.

[Swamp-a (swamp-a)]

SUSE-SU-2022:4504-1: An update that solves 22 vulnerabilities, contains 7 features and has 26 fixes is now available.

Category: security (important)
Bug References: 1065729,1156395,1164051,1184350,1189297,1190256,1193629,1194869,1202341,1203183,1204631,1204636,1204693,1204810,1204850,1205007,1205100,1205111,1205128,1205130,1205149,1205153,1205220,1205331,1205428,1205473,1205514,1205617,1205653,1205744,1205764,1205796,1205882,1205993,1206035,1206036,1206037,1206046,1206047,1206051,1206056,1206057,1206113,1206114,1206147,1206149,1206207,1206273
CVE References: CVE-2022-2602,CVE-2022-3176,CVE-2022-3566,CVE-2022-3567,CVE-2022-3635,CVE-2022-3643,CVE-2022-3707,CVE-2022-3903,CVE-2022-4095,CVE-2022-4129,CVE-2022-4139,CVE-2022-41850,CVE-2022-41858,CVE-2022-42328,CVE-2022-42329,CVE-2022-42895,CVE-2022-42896,CVE-2022-4378,CVE-2022-43945,CVE-2022-45869,CVE-2022-45888,CVE-2022-45934
JIRA References: PED-1573,PED-1706,PED-1936,PED-2684,PED-611,PED-824,PED-849
Sources used:
openSUSE Leap 15.4 (src): kernel-azure-5.14.21-150400.14.28.1, kernel-source-azure-5.14.21-150400.14.28.1, kernel-syms-azure-5.14.21-150400.14.28.1
SUSE Linux Enterprise Module for Public Cloud 15-SP4 (src): kernel-azure-5.14.21-150400.14.28.1, kernel-source-azure-5.14.21-150400.14.28.1, kernel-syms-azure-5.14.21-150400.14.28.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.

[Swamp-a (swamp-a)]

SUSE-SU-2022:4585-1: An update that solves 22 vulnerabilities, contains 7 features and has 52 fixes is now available.

Category: security (important)
Bug References: 1065729,1156395,1164051,1184350,1189297,1190256,1193629,1194869,1202341,1203183,1203391,1203511,1203960,1204228,1204405,1204414,1204631,1204636,1204693,1204780,1204810,1204850,1205007,1205100,1205111,1205113,1205128,1205130,1205149,1205153,1205220,1205264,1205282,1205331,1205332,1205427,1205428,1205473,1205507,1205514,1205521,1205567,1205616,1205617,1205653,1205671,1205679,1205683,1205700,1205705,1205709,1205711,1205744,1205764,1205796,1205882,1205993,1206035,1206036,1206037,1206045,1206046,1206047,1206048,1206049,1206050,1206051,1206056,1206057,1206113,1206114,1206147,1206149,1206207
CVE References: CVE-2022-2602,CVE-2022-3176,CVE-2022-3566,CVE-2022-3567,CVE-2022-3635,CVE-2022-3643,CVE-2022-3707,CVE-2022-3903,CVE-2022-4095,CVE-2022-4129,CVE-2022-4139,CVE-2022-41850,CVE-2022-41858,CVE-2022-42328,CVE-2022-42329,CVE-2022-42895,CVE-2022-42896,CVE-2022-4378,CVE-2022-43945,CVE-2022-45869,CVE-2022-45888,CVE-2022-45934
JIRA References: PED-1573,PED-1706,PED-1936,PED-2684,PED-611,PED-824,PED-849
Sources used:
openSUSE Leap Micro 5.3 (src): kernel-default-5.14.21-150400.24.38.1, kernel-default-base-5.14.21-150400.24.38.1.150400.24.13.2
openSUSE Leap 15.4 (src): dtb-aarch64-5.14.21-150400.24.38.1, kernel-64kb-5.14.21-150400.24.38.1, kernel-debug-5.14.21-150400.24.38.1, kernel-default-5.14.21-150400.24.38.1, kernel-default-base-5.14.21-150400.24.38.1.150400.24.13.2, kernel-docs-5.14.21-150400.24.38.1, kernel-kvmsmall-5.14.21-150400.24.38.1, kernel-obs-build-5.14.21-150400.24.38.1, kernel-obs-qa-5.14.21-150400.24.38.1, kernel-source-5.14.21-150400.24.38.1, kernel-syms-5.14.21-150400.24.38.1, kernel-zfcpdump-5.14.21-150400.24.38.1
SUSE Linux Enterprise Workstation Extension 15-SP4 (src): kernel-default-5.14.21-150400.24.38.1
SUSE Linux Enterprise Module for Live Patching 15-SP4 (src): kernel-default-5.14.21-150400.24.38.1, kernel-livepatch-SLE15-SP4_Update_6-1-150400.9.3.2
SUSE Linux Enterprise Module for Legacy Software 15-SP4 (src): kernel-default-5.14.21-150400.24.38.1
SUSE Linux Enterprise Module for Development Tools 15-SP4 (src): kernel-docs-5.14.21-150400.24.38.1, kernel-obs-build-5.14.21-150400.24.38.1, kernel-source-5.14.21-150400.24.38.1, kernel-syms-5.14.21-150400.24.38.1
SUSE Linux Enterprise Module for Basesystem 15-SP4 (src): kernel-64kb-5.14.21-150400.24.38.1, kernel-default-5.14.21-150400.24.38.1, kernel-default-base-5.14.21-150400.24.38.1.150400.24.13.2, kernel-source-5.14.21-150400.24.38.1, kernel-zfcpdump-5.14.21-150400.24.38.1
SUSE Linux Enterprise Micro 5.3 (src): kernel-default-5.14.21-150400.24.38.1, kernel-default-base-5.14.21-150400.24.38.1.150400.24.13.2
SUSE Linux Enterprise High Availability 15-SP4 (src): kernel-default-5.14.21-150400.24.38.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.

[Swamp-a (swamp-a)]

SUSE-SU-2022:4617-1: An update that solves 96 vulnerabilities, contains 50 features and has 246 fixes is now available.

Category: security (important)
Bug References: 1023051,1032323,1065729,1071995,1152472,1152489,1156395,1164051,1177471,1184350,1185032,1188238,1189297,1189999,1190256,1190497,1190969,1192968,1193629,1194023,1194592,1194869,1194904,1195480,1195917,1196018,1196444,1196616,1196632,1196867,1196869,1197158,1197391,1197659,1197755,1197756,1197757,1197763,1198189,1198410,1198577,1198702,1198971,1199086,1199364,1199515,1199670,1199904,1200015,1200058,1200268,1200288,1200301,1200313,1200431,1200465,1200494,1200544,1200567,1200622,1200644,1200651,1200692,1200788,1200845,1200868,1200869,1200870,1200871,1200872,1200873,1201019,1201308,1201309,1201310,1201361,1201427,1201442,1201455,1201489,1201610,1201675,1201725,1201726,1201768,1201865,1201940,1201941,1201948,1201954,1201956,1201958,1202095,1202096,1202097,1202113,1202131,1202154,1202187,1202262,1202265,1202312,1202341,1202346,1202347,1202385,1202393,1202447,1202471,1202558,1202623,1202636,1202672,1202681,1202685,1202686,1202700,1202710,1202711,1202712,1202713,1202715,1202716,1202757,1202758,1202759,1202761,1202762,1202763,1202764,1202765,1202766,1202767,1202768,1202769,1202770,1202771,1202773,1202774,1202775,1202776,1202778,1202779,1202780,1202781,1202782,1202783,1202822,1202823,1202824,1202860,1202867,1202872,1202874,1202898,1202914,1202960,1202989,1202992,1202993,1203002,1203008,1203036,1203039,1203041,1203063,1203066,1203067,1203098,1203101,1203107,1203116,1203117,1203138,1203139,1203159,1203183,1203197,1203208,1203229,1203263,1203290,1203338,1203360,1203361,1203389,1203391,1203410,1203435,1203505,1203511,1203514,1203552,1203606,1203664,1203693,1203699,1203767,1203769,1203770,1203794,1203798,1203802,1203829,1203893,1203902,1203906,1203908,1203922,1203935,1203939,1203960,1203969,1203987,1203992,1203994,1204017,1204051,1204059,1204060,1204092,1204125,1204132,1204142,1204166,1204168,1204170,1204171,1204183,1204228,1204241,1204289,1204290,1204291,1204292,1204353,1204354,1204355,1204402,1204405,1204413,1204414,1204415,1204417,1204424,1204428,1204431,1204432,1204439,1204470,1204479,1204486,1204498,1204533,1204569,1204574,1204575,1204576,1204619,1204624,1204631,1204635,1204636,1204637,1204646,1204647,1204650,1204653,1204693,1204705,1204719,1204728,1204745,1204753,1204780,1204810,1204850,1204868,1204926,1204933,1204934,1204947,1204957,1204963,1204970,1205007,1205100,1205111,1205113,1205128,1205130,1205149,1205153,1205220,1205257,1205264,1205282,1205313,1205331,1205332,1205427,1205428,1205473,1205496,1205507,1205514,1205521,1205567,1205616,1205617,1205653,1205671,1205679,1205683,1205700,1205705,1205709,1205711,1205744,1205764,1205796,1205882,1205993,1206035,1206036,1206037,1206045,1206046,1206047,1206048,1206049,1206050,1206051,1206056,1206057,1206113,1206114,1206147,1206149,1206207,1206273,1206391
CVE References: CVE-2016-3695,CVE-2020-16119,CVE-2020-36516,CVE-2021-33135,CVE-2021-4037,CVE-2022-1184,CVE-2022-1263,CVE-2022-1882,CVE-2022-20368,CVE-2022-20369,CVE-2022-2153,CVE-2022-2586,CVE-2022-2588,CVE-2022-2602,CVE-2022-26373,CVE-2022-2639,CVE-2022-2663,CVE-2022-28356,CVE-2022-28693,CVE-20...

[Comphi (comphi)]

Hi,
Kernel 6.1 has completely fixed this bug for my machine. The keyboard is now working flawlessly on my Arch install as well, using the default 6.1.1.arch1-1 kernel without any boot options. Thanks for fixing it

[Jslaby-h (jslaby-h)]

As per comment 88.

[Francesco Castellana (xfranky)]

This is also affecting me on a Thinkpad X13 Gen 1, where the devices seem to randomly take too long to initialize, especially after a cold boot, but not only.
Adding i8402.probe_defer fixed keyboard, mousepad, and trackpad even though the message still appears as the first probing fails.
I guess this could be added as a quirk for this specific platform