December 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1212139] [amdgpu]] *ERROR* ring sdma0 timeout 0 - Steam deck
by bugzilla_noreply＠suse.com 22 Dec '23

22 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1212139 https://bugzilla.suse.com/show_bug.cgi?id=1212139#c13 --- Comment #13 from ted chang <monkeyboyted(a)yahoo.com> --- The commit is a workaround. Not a fix. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212139] [amdgpu]] *ERROR* ring sdma0 timeout 0 - Steam deck
by bugzilla_noreply＠suse.com 22 Dec '23

22 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1212139 https://bugzilla.suse.com/show_bug.cgi?id=1212139#c12 --- Comment #12 from ted chang <monkeyboyted(a)yahoo.com> --- Movement on the bug https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=… drm/amdgpu/sdma5.2: add begin/end_use ring callbacks commit ab4750332dbe535243def5dcebc24ca00c1f98ac upstream. Add begin/end_use ring callbacks to disallow GFXOFF when SDMA work is submitted and allow it again afterward. This should avoid corner cases where GFXOFF is erroneously entered when SDMA is still active. For now just allow/disallow GFXOFF in the begin and end helpers until we root cause the issue. This should not impact power as SDMA usage is pretty minimal and GFXOSS should not be active when SDMA is active anyway, this just makes it explicit. v2: move everything into sdma5.2 code. No reason for this to be generic at this point. v3: Add comments in new code Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2220 Reviewed-by: Mario Limonciello <mario.limonciello(a)amd.com> (v1) Tested-by: Mario Limonciello <mario.limonciello(a)amd.com> (v1) Reviewed-by: Christian König <christian.koenig(a)amd.com> Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> Cc: stable(a)vger.kernel.org # 5.15+ Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> I might close this bug since I cannot reproduce this bug myself. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218005] Leap 15.5 does not boot with any of the kernel-default from update repository
by bugzilla_noreply＠suse.com 21 Dec '23

21 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218005 https://bugzilla.suse.com/show_bug.cgi?id=1218005#c12 --- Comment #12 from Anders Stedtlund <falolaf+suse(a)gmail.com> --- Anything else I can provide to help trouble shoot this? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218187] New: tumbleweed crashes very quickly after 6.6 update
by bugzilla_noreply＠suse.com 20 Dec '23

20 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218187 Bug ID: 1218187 Summary: tumbleweed crashes very quickly after 6.6 update 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: meissner(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- tumbleweed seems to crash very quickly after the 6.6 update for me. I have a bit suspicision it might be noveau. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1218235] New: Built in Sreen won't wake up
by bugzilla_noreply＠suse.com 19 Dec '23

19 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218235 Bug ID: 1218235 Summary: Built in Sreen won't wake up Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mail(a)bewi.at QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello all! I’ve a problem with the wake up from screen sleep and latest kernels. When the computer screen goes to sleep it won’t wake up anymore. No mouse cursor nor i can change the tty (Strg + Alt + F1 …). The journals logs are also empty and only a hard reset helps. I’ve tested it with the lastest Linux Kernel 6.6.6 and 6.6.7. Funnily if the whole computer goes to sleep (for example Sleep, Hybrid Sleep and Hibernate), and i disable Screen Sleep before, the screen wakes up. The problem exists only when the screen goes to sleep. With older kernels (i don't know the exact version) it does work. Info for my System: Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics Memory: 30,1 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 21F80041GE System Version: ThinkPad T14s Gen 4 Maybe someone have an idea or an tip where i should submit a bug ticket. Thank you very much. Best regards! -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1218231] New: Hw virtualization enabled in BIOS of Intel Skylake i5-6200U, but lscpu says "VMX" disabled
by bugzilla_noreply＠suse.com 19 Dec '23

19 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218231 Bug ID: 1218231 Summary: Hw virtualization enabled in BIOS of Intel Skylake i5-6200U, but lscpu says "VMX" disabled Classification: openSUSE Product: openSUSE Distribution Version: Leap 16.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: el(a)horse64.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I boot with these kernel options for CPU security: "mitigations=auto,nosmt mds=full,nosmt", on a laptop with Skylake i5-6200U. However, in the BIOS/UEFI options I enabled all virtualization features of this CPU. This means VT-x/VMX should be available, since Skylake supports this according to product pages. The kernel's iTLB multihit mitigation documentation does NOT suggest that any mitigation option will ever disable VT-x/VMX fully. Therefore, I would strongly expect it to be enabled on this system with this configuration. Now here comes the problem: $ lscpu | grep VMX Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT disabled $ cat /sys/devices/system/cpu/vulnerabilities/itlb_multihit KVM: Mitigation: VMX disabled Something seems to be wrong here. As a semi naive uninformed user, I am guessing the following possible options for what happened: Option A: VMX is actually disabled by the kernel through some mitigation option. In this case this is a documentation issue, since the kernel help explaining this "KVM: Mitigation: VMX disabled" text ( https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/multihit.html ) is written like no mitigation would actively disable it, suggesting "VMX disabled" is only meant to show when the BIOS/UEFI turned it off. So the help page should then say what may mess with VMX on a kernel level beyond BIOS/UEFI. Option B: VMX is actually enabled, and the iTLB mitigation is set to "Split huge pages" (this would as far as I can tell be the "correct" option for this system). In this case, there seems to be some mostly benign iTLB info output bug. Option C: VMS is actually enabled, and the iTLB mitigation is NOT active and the device is vulnerable. This potential outcome is why I marked this as SECURITY ISSUE until it can be ruled out, since if that is true then lscpu clearly tells me I'm safe while I'm actually not. So this outcome could trick admins into making expensive hardening missteps. Option D: Maybe I'm just not smart enough to use my BIOS/UEFI, lol, or I misunderstand VMX/VT-x fundamentally. I'm not a kernel developer, after all. Vaguely related, this server fault post suggests this may also happen on many distributions: https://serverfault.com/questions/1073247/if-kvm-is-working-why-does-vmx-sh… (Not entirely sure though if it's the same cause) First seen with Fedora's 5.13.15-200.fc34.x86_64, still present with OpenSUSE slowroll's 6.5.9-1-default. Steps to reproduce: 1. Boot an Intel Skylake computer with Fedora installed. Ensure all virtualization features are enabled in the UEFI/BIOS options. 2. Once Linux has booted, change /etc/default/grub to add in "mitigations=auto,nosmt mds=full,nosmt" and update your generated grub2 files, and reboot. 3. Once inside Linux again, check "lscpu" output and /sys/devices/system/cpu/vulnerabilities/itlb_multihit output. Expected output would be something else than "VMX disabled". -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1211226] Eliminate the need for 'OBS source links': convert to _multibuild
by bugzilla_noreply＠suse.com 19 Dec '23

19 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1211226 Frederic Crozat <fcrozat(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1218184 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218133] enable regulator modules (REGULATOR_MT6323, REGULATOR_MT6380, MFD_MT6397)
by bugzilla_noreply＠suse.com 18 Dec '23

18 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218133 https://bugzilla.suse.com/show_bug.cgi?id=1218133#c1 Bob Goddard <opensuse(a)1.opensuse.bgcomp.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|enable regulator modules |enable regulator modules |(REGULATOR_MT6323, |(REGULATOR_MT6323, |MFD_MT6397) |REGULATOR_MT6380, | |MFD_MT6397) --- Comment #1 from Bob Goddard <opensuse(a)1.opensuse.bgcomp.co.uk> --- And also REGULATOR_MT6380. I think it would be better to enable them all if they can be build as modules. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218153] New: reduce SERIAL_8250_RUNTIME_UARTS?
by bugzilla_noreply＠suse.com 18 Dec '23

18 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218153 Bug ID: 1218153 Summary: reduce SERIAL_8250_RUNTIME_UARTS? 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: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- CONFIG_SERIAL_8250_RUNTIME_UARTS is currently set to 32 which leads to 32 /dev/ttyS*. The upstream default is 4. Is there a need to pre-create that many nodes? I noticed that it clutters the `systemd-analyze blame` quite a bit when looking for boot times. Maybe reduce it back to 4? Users that really need that many ports can set 8250.nr_uarts=32 on the kernel command line as documented upstream: https://github.com/torvalds/linux/blob/master/drivers/tty/serial/8250/Kconf… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218133] New: Missing modules
by bugzilla_noreply＠suse.com 17 Dec '23

17 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218133 Bug ID: 1218133 Summary: Missing modules 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: opensuse(a)1.opensuse.bgcomp.co.uk QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- There are quite a number of regulator modules not being built. Some of these at least depend on the multifunction device drivers. I am looking to get tumbleweed up and running on the BananaPi-R3, and perhaps the new BananaPi-R4 in the future. This needs REGULATOR_MT6323 enabled, at least as a module, and it depend on MFD_MT6397. There seems to be an awful lot of regulators not being build, mainly because the multi function devices have not been selected. As many of these can be built as modules, can these all be enables? As in all the PMICs? -- You are receiving this mail because: You are the assignee for the bug.

1 1