January 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1190027] ima: Can not allocate sha384 (reason: -2)
by bugzilla_noreply＠suse.com 24 Jan '23

24 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1190027 https://bugzilla.suse.com/show_bug.cgi?id=1190027#c1 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com, | |opensuse(a)trummer.xyz Flags| |needinfo?(opensuse@trummer. | |xyz) --- Comment #1 from Jiri Slaby <jslaby(a)suse.com> --- Does this still happen? It looks the bug bitrot after such a long time :/. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188394] Unable to use USB3 port on Rock64
by bugzilla_noreply＠suse.com 24 Jan '23

24 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188394 https://bugzilla.suse.com/show_bug.cgi?id=1188394#c8 Jonas del Campo <jonasdcdm(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #8 from Jonas del Campo <jonasdcdm(a)mailbox.org> --- I no longer have this device unfortunately, so this might as well be fixed already. I'm closing it for now, thanks anyway! -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

24 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188352 https://bugzilla.suse.com/show_bug.cgi?id=1188352#c7 Jonas del Campo <jonasdcdm(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #7 from Jonas del Campo <jonasdcdm(a)mailbox.org> --- Unfortunately I no longer have the device to try this or debug further. I'm closing it for now. If someone experiments this issue one day, this information might be useful. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189993] New: Btrfs hogged one of the CPU cores for more than 30 minutes after a reboot (5.13.12-2-default, 33df9c6)
by bugzilla_noreply＠suse.com 24 Jan '23

24 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1189993 Bug ID: 1189993 Summary: Btrfs hogged one of the CPU cores for more than 30 minutes after a reboot (5.13.12-2-default, 33df9c6) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lpechacek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852174 --> https://bugzilla.suse.com/attachment.cgi?id=852174&action=edit dmesg, SysRq-L, perf data, lsblk -f, snapper list My CPU fan had a long high-intensity exercise this morning. The root cause turned out to be a kworker thread doing "btrfs_preempt_reclaim_metadata_space". The offending thread identification is "kworker/u16:11". I've collected some data bits (dmesg, SysRq-L, perf data) during the event. It is unclear to me, however, what triggered this long-running FS maintenance and how I could stop it in case I needed to - i.e. if the laptop ran battery or if I sat in a quiet room where the CPU fan disturbance would be unacceptable. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1207149] brightness keys not working on Lenovo ideapad 3
by bugzilla_noreply＠suse.com 24 Jan '23

24 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207149 https://bugzilla.suse.com/show_bug.cgi?id=1207149#c8 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(tuxuser@quantentu | |nnel.de) | --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- Good to hear! Now I merged the backport patches to SLE15-SP4 branch, as well as stable branch. FWIW, the relevant upstream commits are: 7a9d74e7e403cb2e60d4d00c05f2f3ab2a33d0c3 ACPICA: include/acpi/acpixf.h: Fix indentation 54c516aeb8b39eeae6450b7d8076d381568dca46 ACPICA: Allow address_space_handler Install and _REG execution as 2 separate steps a5072078dbfaa9d70130805766dfa34bbb7bf2a7 ACPI: EC: Fix EC address space handler unregistration ab4620f58d38206687b9f99d9d2cc1d5a2640985 ACPI: EC: Fix ECDT probe ordering issues -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189881] New: warning: /var/tmp/weak-modules2.7WPIFB/symvers-5.13.12-2-default not available
by bugzilla_noreply＠suse.com 24 Jan '23

24 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1189881 Bug ID: 1189881 Summary: warning: /var/tmp/weak-modules2.7WPIFB/symvers-5.13.12-2-defaul t not available 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: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Running zypper dup on my Tumbleweed machine, I noticed the following in the logs: (121/203) Installing: kernel-default-5.13.12-2.1.x86_64 ....[done] Additional rpm output: warning: /var/tmp/weak-modules2.7WPIFB/symvers-5.13.12-2-default not available It is probably benign, but still a bit confusing/worrisome. What do we want to tell users here (that would be actionable)? And/or is this indicative of some problem with the upgrade as such? -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1182556] i915 [DRM] Random window/background flickering
by bugzilla_noreply＠suse.com 24 Jan '23

24 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1182556 https://bugzilla.suse.com/show_bug.cgi?id=1182556#c22 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |UPSTREAM Severity|Critical |Major --- Comment #22 from Jiri Slaby <jslaby(a)suse.com> --- If this issue still persists, care to open an upstream bug report: https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs You can try our linux-next instead of their suggested drm-tip: https://download.opensuse.org/repositories/Kernel:/linux-next/standard/x86_… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207115] New: qemu VMs are getting stuck with 6.1
by bugzilla_noreply＠suse.com 24 Jan '23

24 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207115 Bug ID: 1207115 Summary: qemu VMs are getting stuck with 6.1 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: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 864078 --> https://bugzilla.suse.com/attachment.cgi?id=864078&action=edit processes in blocked state I was unable to set up kdump properly (see bug 1207114). This was reported upstream as: https://lore.kernel.org/all/b8017e09-f336-3035-8344-c549086c2340@kernel.org/ After I updated the host from 6.0 to 6.1 (being at 6.1.4 ATM), my qemu VMs started stalling (and the host at the same point too). It doesn't happen right after boot, maybe a suspend-resume cycle is needed (or longer uptime, or a couple of qemu VM starts, or ...). But when it happens, it happens all the time till the next reboot. Older guest's kernels/distros are affected as well as Win10. In guests, I see for example stalls in memset_orig or smp_call_function_many_cond. qemu-kvm-7.1.0-13.34.x86_64. I dumped blocked tasks (sysrq-w) on _host_ and everything seems to stall on mmap_read_lock() or mmap_write_lock_killable(). There should be enough free memory (note caches at 8G): total used free shared buff/cache available Mem: 15Gi 10Gi 400Mi 2,5Gi 8,0Gi 5,0Gi Swap: 0B 0B 0B I rmmoded kvm-intel now, so: qemu-kvm: failed to initialize kvm: No such file or directory qemu-kvm: falling back to tcg and it behaves the same (more or less expected). -- You are receiving this mail because: You are the assignee for the bug.

1 6

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

24 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188352 https://bugzilla.suse.com/show_bug.cgi?id=1188352#c6 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonasdcdm(a)mailbox.org, | |jslaby(a)suse.com Flags| |needinfo?(jonasdcdm@mailbox | |.org) --- Comment #6 from Jiri Slaby <jslaby(a)suse.com> --- If the issue still persists, could you attach the output of: cat /proc/bus/input/devices ? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188421] Kernel crash immediately after y2controlcenter crashes with GPU
by bugzilla_noreply＠suse.com 24 Jan '23

24 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188421 https://bugzilla.suse.com/show_bug.cgi?id=1188421#c5 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |UPSTREAM --- Comment #5 from Jiri Slaby <jslaby(a)suse.com> --- Ok, thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 0