June 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1188487] New: BUG: workqueue lockup
by bugzilla_noreply＠suse.com 26 Jan '23

26 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188487 Bug ID: 1188487 Summary: BUG: workqueue lockup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: tdevries(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I started seeing this bug on my tumbleweed system: ... 2021-07-07T16:24:41.803560+02:00 lena kernel: [1053710.804959] CPU: 3 PID: 31988 Comm: gdb Tainted: G D 5.12.10-1-default #1 openSUSE Tumbleweed Message from syslogd@lena at Jul 19 16:18:29 ... kernel:[722585.589404] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for inted: G D 5.12.10-1-default #1 openSUSE Tumbleweed 2021-07-07T16:24:41.803561+02:00 lena kernel: [1053710.804964] Hardware name: LENOVO 20F5S0KF00/20F5S0KF00, BIOS R02ET73W (1.46 ) 01/08/2020 2021-07-07T16:24:41.803563+02:00 lena kernel: [1053710.804966] Call Trace: 2021-07-07T16:24:41.803564+02:00 lena kernel: [1053710.804971] dump_stack+0x76/0x94 2021-07-07T16:24:41.803566+02:00 lena kernel: [1053710.804978] bad_page.cold+0x9b/0xa0 2021-07-07T16:24:41.803567+02:00 lena kernel: [1053710.804983] get_page_from_freelist+0x739/0x13a0 2021-07-07T16:24:41.803568+02:00 lena kernel: [1053710.804990] __alloc_pages_nodemask+0x161/0x310 2021-07-07T16:24:41.803569+02:00 lena kernel: [1053710.804993] pagecache_get_page+0x14c/0x4f0 2021-07-07T16:24:41.803570+02:00 lena kernel: [1053710.805000] grab_cache_page_write_begin+0 7-07T16:24:41.803572+02:00 lena kernel: [1053710.805009] iomap_write_actor+0x9f/0x1a0 2021-07-07T16:24:41.803573+02:00 lena kernel: [1053710.805013] iomap_apply+0x111/0x2e0 2021-07-07T16:24:41.803575+02:00 lena kernel: [1053710.805015] ? iomap_write_end+0x260/0x260 2021-07-07T16:24:41.803576+02:00 lena kernel: [1053710.805020] iomap_file_buffered_write+0x5c/0x80 2021-07-07T16:24:41.803577+02:00 lena kernel: [1053710.805023] ? iomap_write_end+0x260/0x260 2021-07-07T16:24:41.803578+02:00 lena kernel: [1053710.805026] xfs_file_buffered_write+0xbd/0x2b0 [xfs] 2021-07-07T16:24:41.803579+02:00 lena kernel: [1053710.805122] ? _flat_send_IPI_mask+0x21/0x40 2021-07-07T16:24:41.803580+02:00 lena kernel: [1053710.805128] ? generic_exec_single+0x50/0xc0 2021-07-07T16:24:41.803582+02:00 lena kernel: [1053710.805133] ? smp_call_function_single_async+0x17/0x20 2021-07-07T16:24:41.803583+02:00 lena kernel: [1053710.805138] new_sync_write+0x11c/0x1b0 2021-07-07T16:24:41.803583+02:00 lena kernel: [1053710.805143] vfs_write+0x1b8/0x270 2021-07-07T16:24:41.803585+02:00 lena kernel: [1053710.805146] ksys_write+0x5f/0xe0 2021-07-07T16:24:41.803586+02:00 lena kernel: [1053710.805150] do_syscall_64+0x33/0x80 2021-07-07T16:24:41.803587+02:00 lena kernel: [1053710.805155] entry_SYSCALL_64_after_hwframe+0x44/0xae 2021-07-07T16:24:41.803588+02:00 lena kernel: [1053710.805159] RIP: 0033:0x7fc4b3b4539f 2021-07-07T16:24:41.803589+02:00 lena kernel: [1053710.805162] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 b9 49 f9 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 0c 4a f9 ff 48 2021-07-07T16:24:41.803590+02:00 lena kernel: [1053710.805167] RSP: 002b:00007fff61dfb5f0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 2021-07-07T16:24:41.803592+02:00 lena kernel: [1053710.805171] RAX: ffffffffffffffda RBX: 0000000000001000 RCX: 00007fc4b3b4539f 2021-07-07T16:24:41.803592+02:00 lena kernel: [1053710.805174] RDX: 0000000000001000 RSI: 0000000001f9fe90 RDI: 000000000000000e 2021-07-07T16:24:41.803593+02:00 lena kernel: [1053710.805177] RBP: 0000000001f9fe90 R08: 0000000000000000 R09: 00007fff61dfbb30 2021-07-07T16:24:41.803594+02:00 lena kernel: [1053710.805180] R10: 0000000001a44440 R11: 0000000000000293 R12: 0000000000001000 2021-07-07T16:24:41.803596+02:00 lena kernel: [1053710.805182] R13: 00000000018442a0 R14: 0000000000001000 R15: 00007fc4b3c18700 ... This is with kernel: ... $ uname -a Linux lena 5.12.13-1-default #1 SMP Mon Jun 28 06:37:23 UTC 2021 (74bd8c0) x86_64 x86_64 x86_64 GNU/Linux ... It happens during a build and test run of gdb. I've updated and rebooted to kernel version 5.13.0-1-default, but ran into the same bug. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1193931] New: unexpectedly, the system freezes very much
by bugzilla_noreply＠suse.com 26 Jan '23

26 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1193931 Bug ID: 1193931 Summary: unexpectedly, the system freezes very much 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: suse(a)rop.cx QA Contact: qa-bugs(a)suse.de Group: novellonly, SUSE Security Internal Found By: --- Blocker: --- Created attachment 854712 --> https://bugzilla.suse.com/attachment.cgi?id=854712&action=edit full dmesg usually nothing works and only sometimes works very slowly for a few seconds, but the cursor is working properly, usually without delay -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1192623] New: ltp_nfs FCNTL_LOCKTESTS test causes stack trace in dmesg
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1192623 Bug ID: 1192623 Summary: ltp_nfs FCNTL_LOCKTESTS test causes stack trace in dmesg 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: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Tumbleweed Build 20211110 kernel 5.14.14-2-default (2b5383f) (but it might have been failing in 5.13 and older kernels) https://openqa.opensuse.org/tests/2029105/file/serial0.txt Prints really long stack trace, which begins: [ 5211.445898][ C0] sysrq: Show State [ 5211.446508][ C0] task:systemd state:S stack: 0 pid: 1 ppid: 0 flags:0x00000000 [ 5211.447686][ C0] Call Trace: [ 5211.448216][ C0] __schedule+0x325/0x1530 [ 5211.448874][ C0] ? kmem_cache_alloc+0x151/0x480 [ 5211.449593][ C0] schedule+0x44/0xa0 [ 5211.450202][ C0] schedule_hrtimeout_range_clock+0x10b/0x120 [ 5211.451077][ C0] ? kfree+0xba/0x3c0 [ 5211.451934][ C0] ? sock_poll+0x4f/0xe0 [ 5211.452914][ C0] ? ep_done_scan+0xa7/0xf0 [ 5211.453723][ C0] do_epoll_wait+0x542/0x700 [ 5211.454594][ C0] ? wait_woken+0x70/0x70 [ 5211.455511][ C0] __x64_sys_epoll_wait+0x60/0x100 [ 5211.456475][ C0] ? syscall_exit_to_user_mode+0x18/0x40 [ 5211.457467][ C0] do_syscall_64+0x5c/0x80 [ 5211.458342][ C0] ? syscall_exit_to_user_mode+0x18/0x40 [ 5211.459302][ C0] ? do_syscall_64+0x69/0x80 [ 5211.460048][ C0] ? ksys_read+0x5f/0xe0 [ 5211.460755][ C0] ? syscall_exit_to_user_mode+0x18/0x40 [ 5211.461615][ C0] ? do_syscall_64+0x69/0x80 [ 5211.462361][ C0] ? syscall_exit_to_user_mode+0x18/0x40 [ 5211.463276][ C0] ? do_syscall_64+0x69/0x80 [ 5211.464043][ C0] ? exc_page_fault+0x68/0x130 [ 5211.464821][ C0] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 5211.465736][ C0] RIP: 0033:0x7fe070700c1e [ 5211.466480][ C0] RSP: 002b:00007ffc484b5ed0 EFLAGS: 00000293 ORIG_RAX: 00000000000000e8 [ 5211.467713][ C0] RAX: ffffffffffffffda RBX: 0000562627698e40 RCX: 00007fe070700c1e [ 5211.468853][ C0] RDX: 00000000000000ae RSI: 000056262788a3e0 RDI: 0000000000000004 [ 5211.469999][ C0] RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000006 [ 5211.471147][ C0] R10: 00000000ffffffff R11: 0000000000000293 R12: 0000000000000352 [ 5211.472315][ C0] R13: 00000000000000ae R14: 0000000000000055 R15: 0000562627698fd0 [ 5211.473472][ C0] task:kthreadd state:S stack: 0 pid: 2 ppid: 0 flags:0x00004000 [ 5211.474773][ C0] Call Trace: [ 5211.475449][ C0] __schedule+0x325/0x1530 [ 5211.476249][ C0] ? kernel_thread+0x55/0x70 [ 5211.477068][ C0] schedule+0x44/0xa0 [ 5211.477836][ C0] kthreadd+0x2c0/0x2e0 [ 5211.478647][ C0] ? kthread_is_per_cpu+0x30/0x30 [ 5211.479670][ C0] ret_from_fork+0x22/0x30 [ 5211.480495][ C0] task:rcu_gp state:I stack: 0 pid: 3 ppid: 2 flags:0x00004000 -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1192624] New: ltp_nfs nfs05 (NFS stress test with make) fails
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1192624 Bug ID: 1192624 Summary: ltp_nfs nfs05 (NFS stress test with make) fails 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: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Tumbleweed Build 20211110 kernel 5.14.14-2-default (2b5383f) [1] (but it might have been failing in 5.13 and older kernels) fails to run all nfs*_05 tests which run shell script nfs05 [2] which runs nfs05_make_tree.c [3] (NFS stress test with make). Test output: # nfs05 -v 4 -t tcp; echo "### TEST nfs4_05 COMPLETE >>> $?" nfs05 1 TINFO: timeout per run is 0h 5m 0s nfs05 1 TINFO: setup NFSv4, socket type tcp nfs05 1 TINFO: Mounting NFS: mount -v -t nfs -o proto=tcp,vers=4 10.0.0.2:/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp /tmp/LTP_nfs05.G8q7DLN0j0/4/0 nfs05 1 TINFO: start nfs05_make_tree -d 20 -f 50 -t 8 tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s Test timed out, sending SIGTERM! If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 Terminated nfs05 1 TBROK: test terminated nfs05 1 TINFO: Cleaning up testcase umount.nfs4: /tmp/LTP_nfs05.G8q7DLN0j0/4/0: device is busy Test is still running... 10 Test is still running... 9 Test is still running... 8 make[6]: *** No rule to make target '26445.6.20.c', needed by '26445.6.20'. Stop. make[5]: *** [makefile:9: dir] Error 2 make[4]: *** [makefile:9: dir] Error 2 make[3]: *** [makefile:9: dir] Error 2 make[2]: *** [makefile:9: dir] Error 2 make[1]: *** [makefile:9: dir] Error 2 make: *** [makefile:9: dir] Error 2 tst_cmd.c:109: TBROK: 'make' exited with a non-zero code 2 at tst_cmd.c:109 Test is still running... 7 ... make: *** [makefile:9: dir] Error 2 Test is still running... 1 rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26445/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26446/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26447/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26448/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26449/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26450/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26452/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26451/dir/dir/dir/dir/dir/dir': Directory not empty make[6]: *** No rule to make target '26451.6.46.c', needed by '26451.6.46'. Stop. make[5]: *** [makefile:9: dir] Error 2 make[4]: *** [makefile:9: dir] Error 2 make[3]: *** [makefile:9: dir] Error 2 make[2]: *** [makefile:9: dir] Error 2 make[1]: *** [makefile:9: dir] Error 2 make: *** [makefile:9: dir] Error 2 rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/0': Device or resource busy rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/0': Is a directory There is probably no stack trace in dmesg related to this test (in attached dmesg there is really long Call Trace related to FCNTL_LOCKTESTS reported in #1192623). [1] https://openqa.opensuse.org/tests/2029105 [2] https://github.com/linux-test-project/ltp/blob/master/testcases/network/nfs… [3] https://github.com/linux-test-project/ltp/blob/master/testcases/network/nfs… -- You are receiving this mail because: You are the assignee for the bug.

1 5

[kernel-bugs] [Bug 1176026] New: bond interface should not invent mac address by default
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1176026 Bug ID: 1176026 Summary: bond interface should not invent mac address by default 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: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- since 5.8.4 (unsure about last digit): when setting up a bond if kernel chooses a random mac removing and readding the slave gets back to the used behaviour: obs-arm-1:~ # modprobe bonding 3: enP2p1s0v1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 1c:1b:0d:60:ee:8b brd ff:ff:ff:ff:ff:ff 7: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 9e:29:55:da:aa:0e brd ff:ff:ff:ff:ff:ff obs-arm-1:~ # echo +enP2p1s0v1 > /sys/class/net/bond0/bonding/slaves 7: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 9e:29:55:da:aa:0e brd ff:ff:ff:ff:ff:ff obs-arm-1:~ # echo -enP2p1s0v1 > /sys/class/net/bond0/bonding/slaves obs-arm-1:~ # echo +enP2p1s0v1 > /sys/class/net/bond0/bonding/slaves 7: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 1c:1b:0d:60:ee:8b brd ff:ff:ff:ff:ff:ff -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1193417] New: using a Bluetooth keyboard slows down going to sleep for a few seconds
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1193417 Bug ID: 1193417 Summary: using a Bluetooth keyboard slows down going to sleep for a few seconds 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: suse(a)rop.cx QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- when I have a Bluetooth keyboard connected and I press the switch to sleep mode, then at first the screen simply locks, stays in this state for about 4-6 seconds and only then goes to sleep mode Kernel logs: 06/12/2021 01:57 systemd-logind Power key pressed. 06/12/2021 01:57 dbus-daemon [session uid=1000 pid=1840] Activating service name='org.kde.LogoutPrompt' requested by ':1.13' (uid=1000 pid=1991 comm="/usr/bin/ksmserver ") 06/12/2021 01:57 dbus-daemon [session uid=1000 pid=1840] Successfully activated service 'org.kde.LogoutPrompt' 06/12/2021 01:57 NetworkManager <info> [1638745075.7552] manager: sleep: sleep requested (sleeping: no enabled: yes) 06/12/2021 01:57 ModemManager <info> [sleep-monitor] system is about to suspend 06/12/2021 01:57 kded5 bluedevil: About to suspend 06/12/2021 01:57 kded5 plasma-nm: Unhandled active connection state change: 3 06/12/2021 01:57 dbus-daemon [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=1166 comm="/usr/sbin/NetworkManager --no-daemon ") 06/12/2021 01:57 dbus-daemon [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.53' (uid=1000 pid=2018 comm="/usr/bin/plasmashell ") 06/12/2021 01:57 systemd Starting Network Manager Script Dispatcher Service... 06/12/2021 01:57 systemd Starting PackageKit Daemon... 06/12/2021 01:57 PackageKit daemon start 06/12/2021 01:57 dbus-daemon [system] Successfully activated service 'org.freedesktop.nm_dispatcher' 06/12/2021 01:57 systemd Started Network Manager Script Dispatcher Service. 06/12/2021 01:57 kernel wlp0s20f3: deauthenticating from f8:f0:82:6d:a9:5a by local choice (Reason: 3=DEAUTH_LEAVING) 06/12/2021 01:57 dbus-daemon [system] Successfully activated service 'org.freedesktop.PackageKit' 06/12/2021 01:57 plasmashell plasma-pk-updates: Daemon changed 06/12/2021 01:57 kscreenlocker_greet Qt: Session management error: networkIdsList argument is NULL 06/12/2021 01:57 kded5 plasma-nm: Not emitting connection deactivated notification as we're about to suspend 06/12/2021 01:57 kded5 plasma-nm: Network connectivity limited, scheduling notification 06/12/2021 01:57 kscreenlocker_greet file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:47:9: Unable to assign [undefined] to bool 06/12/2021 01:57 systemd Reached target Sleep. 06/12/2021 01:57 systemd Starting System Suspend... 06/12/2021 01:57 kscreenlocker_greet file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:535: TypeError: Cannot read property 'longName' of undefined 06/12/2021 01:57 systemd-sleep INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend 06/12/2021 01:57 systemd-sleep Entering sleep state 'suspend'... 06/12/2021 01:57 kernel PM: suspend entry (s2idle) 06/12/2021 01:57 kernel Filesystems sync: 0.008 seconds 06/12/2021 01:57 kscreenlocker_greet qt.virtualkeyboard.hunspell: Hunspell dictionary is missing for "en_GB" . Search paths ("/usr/share/qt5/qtvirtualkeyboard/hunspell", "/usr/share/hunspell", "/usr/share/myspell/dicts") 06/12/2021 01:57 org_kde_powerdevil QObject::disconnect: Unexpected nullptr parameter 06/12/2021 01:57 org_kde_powerdevil QObject::disconnect: Unexpected nullptr parameter 06/12/2021 02:00 kernel Bluetooth: hci0: Timed out waiting for suspend events 06/12/2021 02:00 kernel Bluetooth: hci0: Suspend timeout bit: 6 06/12/2021 02:00 kernel Bluetooth: hci0: Suspend notifier action (3) failed: -110 06/12/2021 02:00 kernel Freezing user space processes ... (elapsed 0.003 seconds) done. 06/12/2021 02:00 kernel OOM killer disabled. 06/12/2021 02:00 kernel Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. 06/12/2021 02:00 kernel printk: Suspending console(s) (use no_console_suspend to debug) 06/12/2021 02:00 kernel ACPI: EC: interrupt blocked 06/12/2021 02:00 kernel ACPI: EC: interrupt unblocked 06/12/2021 02:00 kernel OOM killer enabled. 06/12/2021 02:00 kernel Restarting tasks ... 06/12/2021 02:00 kernel mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) 06/12/2021 02:00 bluetoothd Controller resume with wake event 0x0 06/12/2021 02:00 systemd-sleep System returned from sleep state. 06/12/2021 02:00 systemd Started Timeline of Snapper Snapshots. 06/12/2021 02:00 kernel done. 06/12/2021 02:00 kernel PM: suspend exit 06/12/2021 02:00 systemd-sleep INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend 06/12/2021 02:00 systemd systemd-suspend.service: Deactivated successfully. 06/12/2021 02:00 systemd Finished System Suspend. 06/12/2021 02:00 systemd Stopped target Sleep. 06/12/2021 02:00 systemd Reached target Suspend. 06/12/2021 02:00 systemd Stopped target Suspend. 06/12/2021 02:00 systemd-logind Operation 'sleep' finished. So, probably problem in: 06/12/2021 02:00 kernel Bluetooth: hci0: Timed out waiting for suspend events 06/12/2021 02:00 kernel Bluetooth: hci0: Suspend timeout bit: 6 06/12/2021 02:00 kernel Bluetooth: hci0: Suspend notifier action (3) failed: -110 (timed out) -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1190411] New: USB devices missing after kexec reboot with XHCI enabled
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1190411 Bug ID: 1190411 Summary: USB devices missing after kexec reboot with XHCI enabled 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: roger.whittaker(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852446 --> https://bugzilla.suse.com/attachment.cgi?id=852446&action=edit hwinfo, dmesg, usb-devices and lsusb with and without XHCI enabled in BIOS, normal boot and kexec boot Hardware is an Intel NUC (D54250WYK). With XHCI enabled in the UEFI BIOS, USB devices are not available after a kexec reboot. Hence the boot failed in the initrd when I had USB attached disks referenced in /etc/fstab. When I commented these out, the boot succeeded but the keyboard and mouse did not work after a kexec reboot. With XHCI disabled in the BIOS, kexec works as expected. On this hardware using Tumbleweed at some time in the past (but I'm afraid I don't know when) kexec worked with XHCI enabled. Linux jabberwock 5.14.0-1-default #1 SMP Mon Aug 30 07:01:36 UTC 2021 (dc06e24) x86_64 x86_64 x86_64 GNU/Linux NAME="openSUSE Tumbleweed" # VERSION="20210908" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20210908" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20210908" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo" -- You are receiving this mail because: You are the assignee for the bug.

1 23

[Bug 1190738] New: kernel-default-base does not contain kernel changelog
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1190738 Bug ID: 1190738 Summary: kernel-default-base does not contain kernel changelog 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: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jeos-internal(a)suse.de Found By: --- Blocker: --- kernel-default-base is built from a separate set of .spec and .changes files, making use of the kernel-subpackage facilities. This however means that the changelog of the original kernel packages (kernel-default, -vanilla, etc.) does not end up in the changelog of kernel-default-base. This is especially visible in updates, which only change the binary content and the version number in an unobvious way. There is no mention of any relevant fixed bugs (bsc#, CVE-). It would be very useful to include the kernel changelog in the kernel-default-base package. I don't think it can (or should) be interleaved with the subpackage .changes file, but it could be included as file. The target systems usually have excludedocs enabled though, so marking the file as %doc means it won't get installed. That makes it more complex and annoying... -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1191924] New: kernel-source.git/README outdated
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1191924 Bug ID: 1191924 Summary: kernel-source.git/README outdated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 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: --- There is a section "Before You Commit -- Things To Check" in kernel-source.git/README, it will likely not work out of the box. According to rpm/kernel-binary.spec.in, at least three more packages beside the obvious gcc/make/patch need to be installed: BuildRequires: libopenssl-devel BuildRequires: libelf-devel BuildRequires: dwarves >= 1.21 Furthermore rapidquilt is not mentioned. It is not strictly required, but one can hardly live without it. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1188589] New: libbpf: failed to find valid kernel BTF
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188589 Bug ID: 1188589 Summary: libbpf: failed to find valid kernel BTF 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: mrostecki(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since the update to the TW snapshot with the kernel 5.13.2-1, I see the following errors when trying to load BPF CO-RE skeletons with libbpf: libbpf: failed to find valid kernel BTF libbpf: Error loading vmlinux BTF: -3 The full example - I'm trying to load BPF programs which I have in this project: https://github.com/rancher-sandbox/lockc and the full output is: �� sudo ./out/lockcd libbpf: elf: skipping unrecognized data section(9) .rodata.str1.1 libbpf: failed to find valid kernel BTF libbpf: Error loading vmlinux BTF: -3 libbpf: failed to load object 'lockc_bpf' libbpf: failed to load BPF skeleton 'lockc_bpf': -3 Error: libbpf error Caused by: System error, errno: 3 Most likely, the solution for them would be setting the following kernel parameters to "y": CONFIG_DEBUG_INFO_REDUCED CONFIG_DEBUG_INFO_SPLIT But I'm not entirely sure yet. trying to test that... -- You are receiving this mail because: You are the assignee for the bug.

1 7

2023

2022

2021

2020

openSUSE Kernel Bugs June 2022