July 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1219684] Illegal instruction in mariadb on VisionFive2
by bugzilla_noreply＠suse.com 18 Jul '24

18 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1219684 https://bugzilla.suse.com/show_bug.cgi?id=1219684#c2 Matthias Brugger <mbrugger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |mbrugger(a)suse.com Resolution|--- |DUPLICATE --- Comment #2 from Matthias Brugger <mbrugger(a)suse.com> --- Works fine with latest tumblweed, please see https://bugzilla.suse.com/show_bug.cgi?id=1222395 *** This bug has been marked as a duplicate of bug 1222395 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1228093] New: Secondary monitor does not come up with 6.10
by bugzilla_noreply＠suse.com 18 Jul '24

18 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228093 Bug ID: 1228093 Summary: Secondary monitor does not come up with 6.10 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 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 Target Milestone: --- Found By: --- Blocker: --- I bisected the issue to: commit 8b2cb32cf0c613fd937ebb49a331798985f50826 Author: Hersen Wu <hersenxs.wu(a)amd.com> Date: Mon Mar 11 18:18:34 2024 -0400 drm/amd/display: FEC overhead should be checked once for mst slot nums Now going to revert in stable temporarily and report to upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1228079] New: SRSO mitigation in microcode not passed through KVM VMs
by bugzilla_noreply＠suse.com 17 Jul '24

17 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228079 Bug ID: 1228079 Summary: SRSO mitigation in microcode not passed through KVM VMs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 URL: https://openqa.opensuse.org/tests/4344305/modules/jour nal_check/steps/9 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fvogt(a)suse.com, jeos-internal(a)suse.de, kernel-bugs(a)suse.de, mloviska(a)suse.com, nik.borisov(a)suse.com, tiwai(a)suse.com Depends on: 1227900 Target Milestone: --- Found By: openQA Blocker: Yes This is what bug 1227900 originally observed: Even though the host system loaded microcode with the feature enabled and uses it itself, guest systems think the functionality is not available. This may result in performance degradation. Some investigation reveals that the X86_FEATURE_IBPB_BRTYPE cpu feature is set in the host kernel, but the guest kernel does not see it in cpuid. +++ This bug was initially created as a clone of Bug #1227900 +++ ## Observation During the firstboot of the image, journal log scan on Minimal-VM's cloud image[1] shows below errors/warnings that we have never noticed before on other images that the same test case is being executed. I cannot reproduce the issue on my local openQA running on an intel machine. This snippet comes from opensuse worker (openqaworker20) running AMD EPYC 7543 32-Core Processor. Jul 16 04:26:30.176898 localhost> kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.9.9-1-default root=UUID=f6566395-dd79-43c7-9364-e040b2668a54 rw quiet systemd.show_status=1 console=ttyS0,115200 console=tty0 net.ifnames=0 > Jul 16 04:26:30.177796 localhost kernel: Calibrating delay loop (skipped) preset value.. 5602.32 BogoMIPS (lpj=9333326) > Jul 16 04:26:30.177805 localhost kernel: x86/cpu: User Mode Instruction Prevention (UMIP) activated > Jul 16 04:26:30.177814 localhost kernel: Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127 > Jul 16 04:26:30.177823 localhost kernel: Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0 > Jul 16 04:26:30.177834 localhost kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization > Jul 16 04:26:30.177849 localhost kernel: Spectre V2 : Mitigation: Retpolines > Jul 16 04:26:30.177859 localhost kernel: Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch > Jul 16 04:26:30.177869 localhost kernel: Spectre V2 : Spectre v2 / SpectreRSB : Filling RSB on VMEXIT > Jul 16 04:26:30.177879 localhost kernel: Spectre V2 : Enabling Restricted Speculation for firmware calls > Jul 16 04:26:30.177889 localhost kernel: Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier > Jul 16 04:26:30.177899 localhost kernel: Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl > Jul 16 04:26:30.177908 localhost kernel: Speculative Return Stack Overflow: IBPB-extending microcode not applied! > Jul 16 04:26:30.177919 localhost kernel: Speculative Return Stack Overflow: WARNING: See https://kernel.org/doc/html/latest/admin-guide/hw-vuln/srso.html for mitigation options. > Jul 16 04:26:30.177929 localhost kernel: Speculative Return Stack Overflow: Vulnerable: Safe RET, no microcode > Jul 16 04:26:30.177939 localhost kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Except the presence of these messages in the boot log, the test results do not show any other related issues. ## Tested image [1] openSUSE-Tumbleweed-Minimal-VM.x86_64-1.0.0-Cloud-Snapshot20240714.qcow2 openQA test in scenario opensuse-Tumbleweed-JeOS-for-OpenStack-Cloud-x86_64-jeos-no-cloud@64bit_virtio fails in [journal_check](https://openqa.opensuse.org/tests/4344305/modules/journal_ch… ## Reproducible The image was never tested before in openQA -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1227900] Speculative Store Bypass disabled via prctl
by bugzilla_noreply＠suse.com 17 Jul '24

17 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227900 https://bugzilla.suse.com/show_bug.cgi?id=1227900#c10 --- Comment #10 from Fabian Vogt <fvogt(a)suse.com> --- I switched to another affected host which is currently not used in production, so I don't have to be as careful with tests ;-) I installed kernel 6.10.0 from Kernel:stable:Backport and latest ucode-amd-20240712 and when booting that, the warning is gone from the host dmesg: openqaworker28:~ # journalctl -b | grep -E 'Mitigation|micro' Jul 17 08:27:54 openqaworker28 kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization Jul 17 08:27:54 openqaworker28 kernel: Spectre V2 : Mitigation: Retpolines Jul 17 08:27:54 openqaworker28 kernel: Spectre V2 : User space: Mitigation: STIBP always-on protection Jul 17 08:27:54 openqaworker28 kernel: Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl Jul 17 08:27:54 openqaworker28 kernel: Speculative Return Stack Overflow: Mitigation: Safe RET Jul 17 08:27:54 openqaworker28 kernel: microcode: Current revision: 0x0a001238 Jul 17 08:27:54 openqaworker28 kernel: microcode: Updated early from: 0x0a001229 FTR, with the 15.5 kernel the messages were: openqaworker28:~ # journalctl -b -1 | grep -E 'Mitigation|micro' Jul 17 08:20:16 openqaworker28 kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization Jul 17 08:20:16 openqaworker28 kernel: Spectre V2 : Mitigation: Retpolines Jul 17 08:20:16 openqaworker28 kernel: Spectre V2 : User space: Mitigation: STIBP always-on protection Jul 17 08:20:16 openqaworker28 kernel: Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp Jul 17 08:20:16 openqaworker28 kernel: Speculative Return Stack Overflow: IBPB-extending microcode not applied! Jul 17 08:20:16 openqaworker28 kernel: Speculative Return Stack Overflow: Mitigation: Safe RET Jul 17 08:20:16 openqaworker28 kernel: microcode: microcode updated early to new patch_level=0x0a001238 Jul 17 08:20:16 openqaworker28 kernel: microcode: CPU0: patch_level=0x0a001238 ... However, booting a TW VM on this host still causes the warning to appear inside. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1227900] Speculative Store Bypass disabled via prctl
by bugzilla_noreply＠suse.com 17 Jul '24

17 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227900 https://bugzilla.suse.com/show_bug.cgi?id=1227900#c9 --- Comment #9 from Nikolay Borisov <nik.borisov(a)suse.com> --- (In reply to Takashi Iwai from comment #8) > Interesting. Does the system show ibpb_brtype in /proc/cpuinfo flags? That feature is never exposed via /proc/cpuinfo. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1227720] infiniband bnxt_re0: Couldn't start port
by bugzilla_noreply＠suse.com 16 Jul '24

16 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227720 https://bugzilla.suse.com/show_bug.cgi?id=1227720#c2 Michael Heimann <michael(a)heimann.ws> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michael(a)heimann.ws --- Comment #2 from Michael Heimann <michael(a)heimann.ws> --- I've had the same exact error message on my Supermicro H13SSL-NT with an onboard BCM957416. Please also see this thread https://forum.proxmox.com/threads/broadcom-nics-down-after-pve-8-2-kernel-6… which helped me find the solution: upgrade the firmware to 229 or newer. A workaround is to blacklist bnxt_re. I *think* that the newer firmware just disables infiniband per default and thus bnxt_re isn't loaded anymore but that is fine for me since I don't need it and this way I didn't need a manual blacklist in my systems. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1226232] Going to sleep and Hibernate often fails with black screen
by bugzilla_noreply＠suse.com 16 Jul '24

16 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226232 https://bugzilla.suse.com/show_bug.cgi?id=1226232#c22 --- Comment #22 from Gui Do <guidopro(a)mailbox.org> --- Part of new log file: Every hour the device tries to hibernate after suspend: 16.07.24 02:11 kernel ACPI: PM: Preparing to enter system sleep state S3 16.07.24 02:11 kernel ACPI: PM: Waking up from system sleep state S3 16.07.24 02:11 kernel ahci 0000:00:17.0: port does not support device sleep 16.07.24 02:11 systemd-sleep System returned from sleep state. I do not know why ahci for the intel sunrise port does not support sleep anymore. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206767] kernel > 6.1 freezes loading rtw_8723de module NetworkManager
by bugzilla_noreply＠suse.com 16 Jul '24

16 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1206767 https://bugzilla.suse.com/show_bug.cgi?id=1206767#c32 Dave Plater <davejplater(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #32 from Dave Plater <davejplater(a)gmail.com> --- Kernel 6.4.0 has finally caught up with me via Leap:15.6 and most probably due to a firmware update, something being fixed or both. My wifi works 100%. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1227153] Leap 15.6 Linux 6.4.0.150600.23.7 boot hanger; former Linux ~.21 works
by bugzilla_noreply＠suse.com 16 Jul '24

16 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227153 https://bugzilla.suse.com/show_bug.cgi?id=1227153#c28 Peter Thoms <p.thoms(a)t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #28 from Peter Thoms <p.thoms(a)t-online.de> --- It works, thank you very much! Command line: zypper addrepo http://download.opensuse.org/repositories/Kernel:/SLE15-SP6/pool/ zypper refresh zypper install kernel-default-6.4.0-150600.251.1.g567c8c9.x86_64 Peter -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1227900] Speculative Store Bypass disabled via prctl
by bugzilla_noreply＠suse.com 16 Jul '24

16 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227900 https://bugzilla.suse.com/show_bug.cgi?id=1227900#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- Interesting. Does the system show ibpb_brtype in /proc/cpuinfo flags? -- You are receiving this mail because: You are the assignee for the bug.

1 0