March 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1206833] New: Cannot load KMPs on armv7
by bugzilla_noreply＠suse.com 02 Mar '23

02 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206833 Bug ID: 1206833 Summary: Cannot load KMPs on armv7 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: armv7 OS: openSUSE Leap 15.4 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: james.hobson(a)oriel.ox.ac.uk QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- KMPs do not load on OpenSuse Leap 15.4 on armv7. This because the kernel-default/lpae package exports: Provides: ksym(...) = 5f For all kernel symbols, but kernel symbols are calculated correctly for KMP packages e.g. ksym(default:PDE_DATA) = 22e390 (made up hash) This means that when you install a KMP package with zypper, it says that it cannot resolve dependencies. More worryingly, this breaks OBS kiwi builds for the armv7 platform -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1208823] New: [Build 20230301] openQA test fails in fsconfig03
by bugzilla_noreply＠suse.com 02 Mar '23

02 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208823 Bug ID: 1208823 Summary: [Build 20230301] openQA test fails in fsconfig03 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3152360/modules/fsco nfig03/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation fsconfig03.c:62: TPASS: kernel seems to be fine on ext2 fsconfig03.c:62: TPASS: kernel seems to be fine on ext3 fsconfig03.c:62: TPASS: kernel seems to be fine on ext4 fsconfig03.c:62: TPASS: kernel seems to be fine on xfs fsconfig03.c:62: TPASS: kernel seems to be fine on btrfs fsconfig03.c:38: TBROK: fsopen() failed: ENODEV (19) Test process returned unkown none zero value (2). Test took approximately 0.251809949986637 seconds Some test output could not be parsed: 11 lines were ignored. openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-syscalls@uefi_virtio-2G fails in [fsconfig03](https://openqa.opensuse.org/tests/3152360/modules/fsconfig03/st… ## Test suite description ## Reproducible Fails since (at least) Build [20230301](https://openqa.opensuse.org/tests/3152041) ## Expected result Last good: [20230228](https://openqa.opensuse.org/tests/3150859) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1188896] "BUG: Bad rss-counter state mm:00000000e555b579 type:MM_FILEPAGES val:-256" during build of cross-epiphany-gcc11-bootstrap
by bugzilla_noreply＠suse.com 01 Mar '23

01 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1188896 https://bugzilla.suse.com/show_bug.cgi?id=1188896#c73 Ihno Krumreich <ihno(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(ro(a)suse.com) --- Comment #73 from Ihno Krumreich <ihno(a)suse.com> --- Hi Rudi, can you rety it with panic_on_taint=0x20 ? (In reply to LTC BugProxy from comment #65) > ------- Comment From geraldsc(a)de.ibm.com 2022-02-18 09:58 EDT------- > (In reply to comment #61) > > > This should not be a problem when we have a dump with panic_on_taint setting, > > > as that would immediately stop the system at the interesting part, and not have > > > all the follow-on messages. > > > > well, as you can see in the buildlog file, panic_on_taint=5 is set in the > > kernel commandline, it just did not have any effect. > > Sorry, after looking more closely to the kernel code, TAINT_BAD_PAGE has bit > number 5, but the panic_on_taint parameter has to be the "Hexadecimal > bitmask representing the set of TAINT flags that will cause the kernel to > panic". So that would mean that we need a "panic_on_taint=0x20" parameter > instead. > > BTW, the buildlog also shows a "panic=1" parameter, which would add a 1 sec > delay before panic. Since we want to be as close as possible to the > detection of "Bad page", you might want to remove that. Is there a reason > for setting this timeout? > > Also, buildlog shows that the "Bad page" did occur, again before all the > rest went wrong. It also shows this: > > [ 84s] Increasing log level from now on... > [ 84s] [ 27.967679][ T383] sysrq: Changing Loglevel > [ 84s] [ 27.967746][ T383] sysrq: Loglevel set to 4 > > Would it be possible to set the loglevel to 8, or at least 5, so that you > would also see KERN_WARNING messages? All the interesting stuff after "Bad > page" will be printed with KERN_WARNING, only the "Bad page" line itself is > printed with KERN_ALERT, which is why we only see this line in the buildlog. > > Given that you seem to have such troubles accessing the kernel message log, > I would recommend to permanently change the loglevel to at least 5, better > 8, to catch them all in your buildlog. Not sure where you'd need to change > that, as it seems to be set during run-time and not by kernel parameter. Or > add "ignore_loglevel" kernel parameter, but not entirely sure if run-time > setting might override this again. > > OTOH, you probably have reasons to reduce loglevel, but at least using 5 > instead of 4 would give so much more useful kernel messages printed with > KERN_WARNING ... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208724] Video Intel awaking w wrong Brightness level
by bugzilla_noreply＠suse.com 01 Mar '23

01 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208724 https://bugzilla.suse.com/show_bug.cgi?id=1208724#c2 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |jslaby(a)suse.com, | |marco.calistri(a)yahoo.com.br Resolution|FIXED |--- Assignee|kernel-bugs(a)opensuse.org |jslaby(a)suse.com Flags| |needinfo?(marco.calistri@ya | |hoo.com.br) --- Comment #2 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Marco Calistri from comment #1) > GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/disk/by-uuid/4ff65e75-c664-43d8-ab25- > 25d85336f6b8 mitigations=auto quiet acpi_backlight=native" Could you attach the output of dmidecode, so that we can hardwire it to the kernel and not everyone has to specify this parameter for this PC model? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208750] New: kernel fails to access EFI runtime services, efibootmgr fails to run as a result
by bugzilla_noreply＠suse.com 01 Mar '23

01 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208750 Bug ID: 1208750 Summary: kernel fails to access EFI runtime services, efibootmgr fails to run as a result Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865153 --> https://bugzilla.suse.com/attachment.cgi?id=865153&action=edit dmesg-virt75-6.2.0-1.g89e2785-default.txt virt75 is a GIGABYTE G242-P34-00 It was possible to run Tumbleweed in the past. It runs SLE15 fine, modulo bug#1198682 The kernel 6.1 and 6.2 is unable to use the EFI runtime services: [ 0.722100] [Firmware Bug]: Unable to handle paging request in EFI runtime service -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1208766] Kernel 6.2.1 does not suspend/hibernate anymore for AMD Ryzen 7 Pro
by bugzilla_noreply＠suse.com 01 Mar '23

01 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208766 https://bugzilla.suse.com/show_bug.cgi?id=1208766#c2 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com Assignee|kernel-bugs(a)opensuse.org |jlee(a)suse.com --- Comment #2 from Jiri Slaby <jslaby(a)suse.com> --- Joey, how to enable hibernate support with lockdown again? -- You are receiving this mail because: You are the assignee for the bug.

1 0