January 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

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

29 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c10 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|X.Org |Kernel Assignee|gfx-bugs(a)suse.de |kernel-bugs(a)opensuse.org Summary|mouse & keyboard not |mouse & keyboard not |available in X/plasma after |available after a reboot |a reboot (needs replug the |(needs replug the devices) |devices) | QA Contact|gfx-bugs(a)suse.de |qa-bugs(a)suse.de Flags|needinfo?(opensuse(a)mike.fra | |nken.de) | --- Comment #10 from Stefan Dirsch <sndirsch(a)suse.com> --- 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. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199195] pinebook pro wake-up from hibernation hangs on root fs
by bugzilla_noreply＠suse.com 28 Jan '23

28 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1199195 http://bugzilla.opensuse.org/show_bug.cgi?id=1199195#c4 Bj�rn Bidar <bjorn.bidar(a)thaodan.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bjorn.bidar(a)thaodan.de --- Comment #4 from Bj�rn Bidar <bjorn.bidar(a)thaodan.de> --- I noticed that there is a timeout in the initramfs phase for waiting for nvme devices it might be related I think. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1201112] WiFi not available on pinebook pro
by bugzilla_noreply＠suse.com 28 Jan '23

28 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1201112 http://bugzilla.opensuse.org/show_bug.cgi?id=1201112#c8 Bj�rn Bidar <bjorn.bidar(a)thaodan.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bjorn.bidar(a)thaodan.de --- Comment #8 from Bj�rn Bidar <bjorn.bidar(a)thaodan.de> --- I installed a clean image on an usb flash drive, wifi works without any modifications. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188352] New: Can't enter LUKS password since kernel 5.13 on Pinebook Pro
by bugzilla_noreply＠suse.com 28 Jan '23

28 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1188352 Bug ID: 1188352 Summary: Can't enter LUKS password since kernel 5.13 on Pinebook Pro Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jonasdcdm(a)mailbox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 851029 --> http://bugzilla.opensuse.org/attachment.cgi?id=851029&action=edit dmesg Since the upgrade to kernel 5.13 it's no longer possible to enter the LUKS password on boot. The physical keyboard works fine in GRUB, but the LUKS prompt won't see it, it doesn't register any key press. Entering the password via serial console works, and the Pinebook Pro boots to the desktop, where the physical keyboard works again. Kernel 5.12.13-1 is still working fine. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1189826] Severe screen flickering with kernel 5.13.12-1-default and i915
by bugzilla_noreply＠suse.com 28 Jan '23

28 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1189826 https://bugzilla.suse.com/show_bug.cgi?id=1189826#c20 Javier Llorente <javier(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(javier(a)opensuse.o | |rg) | --- Comment #20 from Javier Llorente <javier(a)opensuse.org> --- Upstream issue: https://gitlab.freedesktop.org/drm/intel/-/issues/7971 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1201121] New: kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash
by bugzilla_noreply＠suse.com 28 Jan '23

28 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1201121 Bug ID: 1201121 Summary: kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting with the Tumbleweed snapshot installed on June 7th I get kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash in my journal on every boot. Running fwupdmgr I get fwupd[6102]: 12:26:06:0015 FuPluginDfu truncated DFU interface data, no bcdDFUVersion The daemon nevertheless is starting. Because there is no newer firmware for any of my devices I am not able to test, if an update would work despite these error messages. This is a XPS 13 9310 2-in-1/0NVVG0, BIOS 2.8.1 02/25/2022. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1185174] [i815] kernel 5.11: Xorg fails to run: open /dev/dri/card0: No such file or directory; (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory)
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1185174 http://bugzilla.opensuse.org/show_bug.cgi?id=1185174#c14 --- Comment #14 from Felix Miata <mrmazda(a)earthlink.net> --- (In reply to Jiri Slaby from comment #13) > As advertised. I understand the rationale for WONTFIX, but not what was "advertised", or where. My gx150 is dead. My Coppermine gx110 is a living fossil, but still able to boot, last upgraded to TW20230108. Debian testing (12/Bookworm) still boots too. :p -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189826] Severe screen flickering with kernel 5.13.12-1-default and i915
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1189826 https://bugzilla.suse.com/show_bug.cgi?id=1189826#c19 --- Comment #19 from Javier Llorente <javier(a)opensuse.org> --- (In reply to Jiri Slaby from comment #18) > Does this still happen? Have you tried to bisect the issue? Or report > upstream? It looks the bug bitrot after such a long time :/. Yes, it still happens with TW 20230123. I haven't tried to bisect the issue nor reported it upstream. I seldomly poweroff/reboot (I suspend it a lot), so I don't get to see the issue a lot. I have created an account at freesdesktop.org (pending approval by admin). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207703] dracut fails to create initrd, and leaves faulty symlink
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207703 https://bugzilla.suse.com/show_bug.cgi?id=1207703#c1 Antonio Feijoo <antonio.feijoo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |antonio.feijoo(a)suse.com Assignee|kernel-bugs(a)opensuse.org |dracut-maintainers(a)suse.de --- Comment #1 from Antonio Feijoo <antonio.feijoo(a)suse.com> --- Could you attach the output of the command `dracut -f --debug`? Thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189469] Linux Kernel 5.14.6 Crashes during docker container usage
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1189469 https://bugzilla.suse.com/show_bug.cgi?id=1189469#c19 --- Comment #19 from Mario Manno <mmanno(a)suse.com> --- Not happening on newer kernels for me. -- You are receiving this mail because: You are the assignee for the bug.

1 0