March 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1190261] New: Kernel scriptlets: XXX: Only call mokutil if UEFI and shim are used
by bugzilla_noreply＠suse.com 21 Mar '23

21 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1190261 Bug ID: 1190261 Summary: Kernel scriptlets: XXX: Only call mokutil if UEFI and shim are used Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Spin-off from bug 1189841. From https://github.com/openSUSE/suse-module-tools/pull/33: @mwilck: so why not test this? e.g. like this: if [ "$(mokutil --sb-state 2>/dev/null)" = "SecureBoot enabled" ]; then ... fi @hramrach: ??? The part that github displays as context for this comment does not look relevant @hramrach hramrach 21 hours ago Member Right, if you refer to XXX: Only call mokutil if UEFI and shim are used then I have no opinion on that. Should be probably handled in a separate bug and the implications of any possible check discussed to death. @hramrach hramrach 21 hours ago Member Actually, there is the problem that on arm64 you suddenly get from no shim to shim on SP update without any warning so this is really hairy to get right. Really deserves a separate bug. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1209540] New: Kernel update hangs on boot
by bugzilla_noreply＠suse.com 21 Mar '23

21 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209540 Bug ID: 1209540 Summary: Kernel update hangs on boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bugz57(a)top.geek.nz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865704 --> http://bugzilla.opensuse.org/attachment.cgi?id=865704&action=edit console output when hanging The kernel update a few days ago to kernel-default-5.14.21-150400.24.49.3.x86_64 hangs on boot, after the grub menu has been and gone. I have photos of the console output when booting the recovery version of the kernel. At that point console output just stops. Keyboard numlock/capslock do nothing, but sysrq sequences work (r e i s u b) and allow to reboot however cleanly. I had recently fiddled with the bios but can't find any settings that make this kernel boot. There is no change to USB devices connected. There was no change to any hardware. There is an nvidia graphics card but no nvidia driver nor nv are loaded; the card is unused. In any case, the previous kernel kernel-default-5.14.21-150400.24.46.1.x86_64 boots OK with any bios setting and with all USB devices connected. In 4 years no kernel has ever hung on boot on this box. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1209436] I915 hangs on Kernel vmlinuz-5.14.21-150400.24.49
by bugzilla_noreply＠suse.com 21 Mar '23

21 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 Jeffrey Cheung <jcheung(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |jcheung(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208728] New: Thinkpad X1 Carbon Gen 10 won't enter S3 sleep on kernel 6
by bugzilla_noreply＠suse.com 21 Mar '23

21 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208728 Bug ID: 1208728 Summary: Thinkpad X1 Carbon Gen 10 won't enter S3 sleep on kernel 6 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: victorfuga(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting with kernel 6, my thinkpad x1 carbon will not enter s3 sleep even when set as the default sleep option. Checked a few distros and noted it was working using kernel 5.19 "LTS" in manjaro. Currently running Tumbleweed snapshot 20230226, sleep mode is set to "Linux" in the bios. Checked on lid close, sleep button in KDE, and Fn + 4 key combo. $ cat /sys/power/mem_sleep s2idle [deep] $ sudo journalctl | grep "PM: suspend" | tail -2 2�� 27 18:29:09 reisen kernel: PM: suspend entry (s2idle) 2�� 27 18:29:11 reisen kernel: PM: suspend exit -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1200983] mouse & keyboard not available after a reboot (needs replug the devices)
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c14 --- Comment #14 from Michael Hirmke <opensuse(a)mike.franken.de> --- (In reply to Takashi Iwai from comment #13) > (In reply to Michael Hirmke from comment #12) > > (In reply to Stefan Dirsch from comment #10) > > > Thanks for testing. Indeed this makes it a kernel issue. You could also test > > > the mouse on the Linux console via 'evtest /dev/input/eventXX', but this is > > > a bit complicated to figure out the right device. So I only wanted to > > > mention keyboard here. > > > > Keyboard and mouse both have problems one the console, too. > > The keyboard vanishes after a few seconds and returns, as soon as a key is > > pressed, but the first keypress is not shown. The mouse never works on the > > console - no events are shown. > > What do you mean "vanishes" here? It means that the /dev/input/event* device > is gone? no, there is no mouse pointer and the keyboard light is off. > > The point to check here is whether the device file persists and can > read/write from a user-space (no matter whether it's processed or not). Or > is the (USB?) audio device itself disappears and reappears automatically. Because the keyboard also has problems, this isn't easy to debug. What exactly would you like me to test? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207915] amdgpu 0000:00:01.0: amdgpu: GPU fault detected: 147 0x00422002 for process sddm-greeter pid 2186 thread sddm-greet:cs0 pid 2193
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207915 http://bugzilla.opensuse.org/show_bug.cgi?id=1207915#c4 John Shand <jshand2013(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #4 from John Shand <jshand2013(a)gmail.com> --- i think this was a once off. i will close it -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208756] Goodix GDIX1003/GT9110P i2c device is Unsupported
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208756 https://bugzilla.suse.com/show_bug.cgi?id=1208756#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you give hwinfo output? Also the output of acpidump. GDX10003 seems to be a new chip, so you'll likely need to do trial-and-error approach with the customized kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207915] amdgpu 0000:00:01.0: amdgpu: GPU fault detected: 147 0x00422002 for process sddm-greeter pid 2186 thread sddm-greet:cs0 pid 2193
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207915 https://bugzilla.suse.com/show_bug.cgi?id=1207915#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jshand2013(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(jshand2013@gmail. | |com) --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Sounds like a one-off issue. Is the problem reproduced? If not, let's close. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200983] mouse & keyboard not available after a reboot (needs replug the devices)
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c13 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Michael Hirmke from comment #12) > (In reply to Stefan Dirsch from comment #10) > > Thanks for testing. Indeed this makes it a kernel issue. You could also test > > the mouse on the Linux console via 'evtest /dev/input/eventXX', but this is > > a bit complicated to figure out the right device. So I only wanted to > > mention keyboard here. > > Keyboard and mouse both have problems one the console, too. > The keyboard vanishes after a few seconds and returns, as soon as a key is > pressed, but the first keypress is not shown. The mouse never works on the > console - no events are shown. What do you mean "vanishes" here? It means that the /dev/input/event* device is gone? The point to check here is whether the device file persists and can read/write from a user-space (no matter whether it's processed or not). Or is the (USB?) audio device itself disappears and reappears automatically. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209197] Kernel 6.2.2 with older NVIDIA graphics won't boot (freeze after 4.5 sec into boot process)
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209197 https://bugzilla.suse.com/show_bug.cgi?id=1209197#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sddrossy(a)aol.com, | |tiwai(a)suse.com Flags| |needinfo?(sddrossy(a)aol.com) --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Seems to be a problem of nouveau. Could you report rather to the upstream, gitlab.freedesktop.org Issues? -- You are receiving this mail because: You are the assignee for the bug.

1 0