January 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1219147] New: Kernel: NULL pointer dereference during boot, 5.14.21-150500.55.44, usb_unbind_interface
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219147 Bug ID: 1219147 Summary: Kernel: NULL pointer dereference during boot, 5.14.21-150500.55.44, usb_unbind_interface Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: frank.kuehndel(a)embedded-brains.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872149 --> https://bugzilla.suse.com/attachment.cgi?id=872149&action=edit Screen photos showing kernel oops and systemd output. Since the update to kernel 5.14.21-150500.55.44-default, I experience a spontaneous kernel bug during boot (for the first time on Monday 2024-Jan-22). This did not happen with kernel 5.14.21-150500.55.39-default or the kernels before. This bug appears in about 50% of all starts. This is the sequence of actions: * I power-on my Laptop (Lenovo 20QN-005YGE "P53", NVIDIA GPU) with USB-C docking station connected. * I get the Grub2 menu and let it start the default entry. * I get the usual green text screen to enter the password to decrypt the disk and enter the phrase (see img_1.jpg). * A moment later I see the green kernel oops message (attached as screen photo img_2.jpg). * When I press a key, I can see that systemd got to the point where it wanted to decrypt the disk but then hangs in a filesystem check (see img_4.jpg). * I power my Laptop off (waiting for 15 minutes has no effect). I "believe" the system fails to mount "/" and "/home". Consequently, I cannot find any entry of this oops or the boot at all in /var/log/messages, the journal or with "last". Workaround: * In the Grub2 menu, I choose the "Advanced" entry and boot kernel 5.14.21-150500.55.39-default. * In /etc/zypp/zypp.conf I changed one line multiversion.kernels = latest,latest-1,running to multiversion.kernels = latest,latest-1,running,5.14.21-150500.55.39 in order to prevent the "good" Kernel from beeing deleted. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1219132] [Build 20240123] [6.7.1] Sysctl Sysctl_kernel_sched_energy_aware
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219132 https://bugzilla.suse.com/show_bug.cgi?id=1219132#c1 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #1 from Jiri Slaby <jslaby(a)suse.com> --- This was deliberately changed by: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… to return an empty string in case EAS is not supported. See the commit log. So the test needs to be tuned. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219147] Kernel: NULL pointer dereference during boot, 5.14.21-150500.55.44, usb_unbind_interface
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219147 https://bugzilla.suse.com/show_bug.cgi?id=1219147#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- A known regression, some info found in bsc#1218948 (although the original issue of that bug entry is different from your issue). The latest SLE15-SP5 git branch already contains the fix. Try the kernel in OBS Kernel:SLE15-SP5 repo http://download.opensuse.org/repositories/Kernel:/SLE15-SP5/pool/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219137] New: qemu user space builds broken with kernel 6.7
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219137 Bug ID: 1219137 Summary: qemu user space builds broken with kernel 6.7 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: schwab(a)suse.de QA Contact: qa-bugs(a)suse.de CC: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Since commit 1c5976ef0f7a the kernel deregisters all binfmt_misc handler when the binfmt_misc filesystem is unmounted. The build script has this: # RPM specific post checks are in /usr/lib/build/checks if test -n "$RPMS" -a -d "$BUILD_ROOT/usr/lib/build/checks" ; then # workaround for broken 13.1 check scripts which umount /proc if test -n "$RUNNING_IN_VM" -a "$BUILD_ROOT" = / ; then umount -n $BUILD_ROOT/proc/sys/fs/binfmt_misc 2>/dev/null fi This means that after this point the emulation no longer works. [ 272s] ... checking for files with abuild user/group [ 272s] /.build/build: line 1922: /bin/env: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error According to the commit, this should be reported as a regression so that this behaviour is reverted for the initial binfmt_misc mount. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1219135] New: [Build 20240123] kernel 6.7.1 vs ltp: fanotify{14,15,16} and splice07 fail
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219135 Bug ID: 1219135 Summary: [Build 20240123] kernel 6.7.1 vs ltp: fanotify{14,15,16} and splice07 fail Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3889407/modules/fano tify14/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 Target Milestone: --- Found By: openQA Blocker: Yes ## Observation LTP Seems not yet fully ready for Kernel 6.7 (or kernel 6.7 really has bugs identified by LTP) openQA reporters these 4 errors: * fanotify14: fanotify14.c:303: TBROK: fanotify_mark(5, 0x101, 0x200, ..., mntpoint/file1) failed: EOPNOTSUPP (95) * fanotify15: fanotify15.c:88: TBROK: fanotify_mark(3, 0x101, 0x400007c2, ..., mntpoint/test_dir) failed: EOPNOTSUPP (95) Test process returned unkown none zero value (2). * fanotify16: fanotify16.c:289: TBROK: fanotify_mark(3, 0x101, 0x40000fc0, ..., fs_mnt) failed: EOPNOTSUPP (95) Test process returned unkown none zero value (2). * splice07: splice07.c:54: TFAIL: splice() on /dev/zero -> pipe write end succeeded openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-syscalls@uefi_virtio-2G fails in [fanotify14](https://openqa.opensuse.org/tests/3889407/modules/fanotify14/st… ## Test suite description ## Reproducible Fails since (at least) Build [20240123](https://openqa.opensuse.org/tests/3888826) ## Expected result Last good: [20240122](https://openqa.opensuse.org/tests/3886452) (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 1218948] kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156]
by bugzilla_noreply＠suse.com 23 Jan '24

23 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218948 https://bugzilla.suse.com/show_bug.cgi?id=1218948#c35 --- Comment #35 from Takashi Iwai <tiwai(a)suse.com> --- Also, is this a regression by the recent kernel updates? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218948] kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156]
by bugzilla_noreply＠suse.com 23 Jan '24

23 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218948 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(chris@computersal | |at.de) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218948] kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156]
by bugzilla_noreply＠suse.com 23 Jan '24

23 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218948 https://bugzilla.suse.com/show_bug.cgi?id=1218948#c34 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?, | |needinfo?(tiwai(a)suse.com) | --- Comment #34 from Takashi Iwai <tiwai(a)suse.com> --- OK, then the original issue of Christian's machine is completely different from others. The problem for others is about a regression of ax88179 driver (the actual crash), and this was already fixed in SLE15-SP5 git branch. Meanwhile, your problem seems related with i915 graphics driver. The hangup detected by the watchdog might be related with the firmware loading of i915. Could you try to boot with i915.enable_guc=0 boot option and see whether the problem still happens? The kernel warnings might still appear, but the hangup could be avoided by that. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218682] EFI aarch64 boot failure on honeycomb lx2
by bugzilla_noreply＠suse.com 23 Jan '24

23 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218682 https://bugzilla.suse.com/show_bug.cgi?id=1218682#c3 --- Comment #3 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Hi James, could you try suggestion from Stanimir? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191784] update of kernel shows message in dracut processing; no modules crc32c and bcm2835-sdhost
by bugzilla_noreply＠suse.com 22 Jan '24

22 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1191784 https://bugzilla.suse.com/show_bug.cgi?id=1191784#c5 Freek de Kruijf <freek(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Freek de Kruijf <freek(a)opensuse.org> --- No further reaction. Apparently fixed. -- You are receiving this mail because: You are the assignee for the bug.

1 0