November 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1217512] New: [RPi4] kernel: vc4_hdmi fef00700.hdmi: Could not register PCM component: -517
by bugzilla_noreply＠suse.com 11 Dec '23

11 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217512 Bug ID: 1217512 Summary: [RPi4] kernel: vc4_hdmi fef00700.hdmi: Could not register PCM component: -517 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/3760808/modules/jour nal_check/steps/11 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: ivan.ivanov(a)suse.com Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-RPi-aarch64-jeos@RPi4 fails in [journal_check](https://openqa.opensuse.org/tests/3760808/modules/journal_ch… On Raspberry Pi 4, with latest updates, we now have the following kernel trace in journal: kernel: vc4_hdmi fef00700.hdmi: Could not register PCM component: -517 Related updates: raspberrypi-firmware (2023.04.25 -> 2023.11.21) raspberrypi-firmware-config (2023.04.25 -> 2023.11.21) raspberrypi-firmware-dt (2023.05.02 -> 2023.11.21) ## Test suite description Maintainer: fvogt, mnowak Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64. ## Reproducible Fails since (at least) Build [20231123](https://openqa.opensuse.org/tests/3754946) ## Expected result Last good: [20231122](https://openqa.opensuse.org/tests/3750512) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1216841] New: [ build 28.1] openQA test fails in fanotify16 (LTP)
by bugzilla_noreply＠suse.com 05 Dec '23

05 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1216841 Bug ID: 1216841 Summary: [ build 28.1] openQA test fails in fanotify16 (LTP) Classification: SUSE Linux Enterprise Server Product: SUSE Linux Enterprise Server 15 SP6 Version: unspecified Hardware: x86-64 URL: https://openqa.opensuse.org/tests/2353240/modules/fano tify16/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)suse.de Reporter: wegao(a)suse.com CC: guillaume.gardet(a)arm.com, kernel-bugs(a)opensuse.org, petr.vorel(a)gmail.com, qa-bugs(a)suse.de Depends on: 1199618 Target Milestone: --- Group: SUSE Enterprise Partner Found By: openQA Blocker: Yes I clone issue to 15sp6 since i found this issue not exist on Tumbleweed now, but still exist on latest result for 15sp6, see following openqa job, i suppose some fix need backport to sle15sp6. https://openqa.suse.de/tests/12752058#step/fanotify16/7 +++ This bug was initially created as a clone of Bug #1199618 +++ ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos-ltp-syscalls@aarch64-HD24G fails in [fanotify16](https://openqa.opensuse.org/tests/2353240/modules/fanotify16/st… Error log: fanotify.h:336: TBROK: fanotify_mark (3, FAN_MARK_ADD, ..., AT_FDCWD, ".") failed: EXDEV (18) Test process returned unkown none zero value (2). Test took approximately 0.581575272008195 seconds Some test output could not be parsed: 9 lines were ignored. ## Test suite description ## Reproducible Fails since (at least) Build [20220302](https://openqa.opensuse.org/tests/2224057) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1196438] Consider switching to 300HZ default
by bugzilla_noreply＠suse.com 30 Nov '23

30 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1196438 https://bugzilla.suse.com/show_bug.cgi?id=1196438#c19 --- Comment #19 from Dirk Mueller <dmueller(a)suse.com> --- (In reply to Yousaf Kaukab from comment #17) > So for SLE the consensus is to keep CONFIG_HZ=250. I assume you mean SLE15 here? I think the discussion should be open ended with SLE16. > Cyril recommended to keep CONFIG_HZ=250 citing the bug fixed by commit c7fcb99877f9 and Mel > recommended to keep SLE and ALP aligned which implies CONFIG_HZ=250 for ALP > as well. I'm sorry, but that means there can be no progress of anything anywhere ever. But the matter of fact is that we are improving the config continuously based on feedback. > So I agree we should revert the change. Objections? Well, what about the original suggestion to use a value that is evenly divisible for the user space metrics? I checked again, and RHEL9/10 is going with 100 HZ. So if your concern is that the number of tick interrupts is causing performance issues, why not go to the *same* value across all architectures, and pick a value that is evenly divisible by 100 (the userspace HZ)? Like 100? (or 300, for that matter) I picked 300 because it was closest to the original 250 which I thought is the least concern overall. There were no conclusive benchmarks showing it would be a problem. Why can we not run with that to see partner and customer feedback prior release? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196438] Consider switching to 300HZ default
by bugzilla_noreply＠suse.com 30 Nov '23

30 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1196438 https://bugzilla.suse.com/show_bug.cgi?id=1196438#c18 --- Comment #18 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Yousaf Kaukab from comment #17) > Objections? Just setting a timeout: If not, let me revert TW to 250 after 8th Dec (next Fri). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196438] Consider switching to 300HZ default
by bugzilla_noreply＠suse.com 29 Nov '23

29 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1196438 https://bugzilla.suse.com/show_bug.cgi?id=1196438#c17 --- Comment #17 from Yousaf Kaukab <yousaf.kaukab(a)suse.com> --- (In reply to Jiri Slaby from comment #11) > So at last, neither ALP nor Leap will adopt 300. So I think we should switch > the TW back to 250 to be consistent with all our other distros. So for SLE the consensus is to keep CONFIG_HZ=250. Cyril recommended to keep CONFIG_HZ=250 citing the bug fixed by commit c7fcb99877f9 and Mel recommended to keep SLE and ALP aligned which implies CONFIG_HZ=250 for ALP as well. So I agree we should revert the change. Objections? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196438] Consider switching to 300HZ default
by bugzilla_noreply＠suse.com 29 Nov '23

29 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1196438 https://bugzilla.suse.com/show_bug.cgi?id=1196438#c16 Yousaf Kaukab <yousaf.kaukab(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yousaf.kaukab(a)suse.com --- Comment #16 from Yousaf Kaukab <yousaf.kaukab(a)suse.com> --- For the for the sake of completeness I am adding response from Takashi in <87jzt4g3s6.wl-tiwai(a)suse.de> to the internal kernel ML: On 9/5/23 15:15, Takashi Iwai wrote: > FYI, the switch to HZ=300 was done on TW via bsc#1196438. > There were no major performance degrade, but yes, there can be hidden > corner cases like that, so switching HZ is likely no-go for SLE. But > the question is about ALP. If we rather want to be conservative, > HZ=250 can be used as well. OTOH, there are inconsistent HZ values > among all archs on SLE, and that's another point to consider. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217512] [RPi4] kernel: vc4_hdmi fef00700.hdmi: Could not register PCM component: -517
by bugzilla_noreply＠suse.com 28 Nov '23

28 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217512 https://bugzilla.suse.com/show_bug.cgi?id=1217512#c7 --- Comment #7 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Yes, as suspected update of raspberrypi-firmware-dt makes thing break. I will have to take closer look why this is happening... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217512] [RPi4] kernel: vc4_hdmi fef00700.hdmi: Could not register PCM component: -517
by bugzilla_noreply＠suse.com 28 Nov '23

28 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217512 https://bugzilla.suse.com/show_bug.cgi?id=1217512#c6 --- Comment #6 from Patrik Jakobsson <patrik.jakobsson(a)suse.com> --- We don't see any issues in the nightly IGT tests so this is likely a firmware or DT issue. Can someone test by rolling back the DT but not the firmware and config packages? That way we can isolate the problem further. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211117] New: 50-check-kernel-build-id fails to extract vmlinux
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1211117 Bug ID: 1211117 Summary: 50-check-kernel-build-id fails to extract vmlinux Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When looking at build log from random stable kernel build I get this: [17308s] ... running 50-check-kernel-build-id [17309s] ... Verifying kernel build-ids for kernel-default 6.3.1-1.gdd8cfff s390x [17309s] ... Processing kernel rpms in '//home/abuild/rpmbuild/RPMS/s390x' [17909s] ... Unable to extract ./usr/lib/modules/6.3.1-1.gdd8cfff-default/vmlinux.xz from //home/abuild/rpmbuild/RPMS/s390x/kernel-default-debuginfo-6.3.1-1.1.gdd8cfff.s390x.rpm [17910s] Giving up vmlinux.xz is in kernel-default, not kernel-default-debuginfo. Either the message is misleading or the script is looking in the wrong place. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1212467] New: i915 Xorg display flashing in 2k mode
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1212467 Bug ID: 1212467 Summary: i915 Xorg display flashing in 2k mode 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: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867636 --> https://bugzilla.suse.com/attachment.cgi?id=867636&action=edit dmesg every few seconds the display would flash I suspect buffer swap synchronization error Linux localhost.localdomain 6.3.8-lp154.2.g627a49e-default #1 SMP PREEMPT_DYNAMIC Wed Jun 14 10:30:38 UTC 2023 (627a49e) x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are the assignee for the bug.

1 12