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.
https://bugzilla.suse.com/show_bug.cgi?id=1189993
Bug ID: 1189993
Summary: Btrfs hogged one of the CPU cores for more than 30
minutes after a reboot (5.13.12-2-default, 33df9c6)
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: Other
Status: NEW
Severity: Minor
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: lpechacek(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 852174
--> https://bugzilla.suse.com/attachment.cgi?id=852174&action=edit
dmesg, SysRq-L, perf data, lsblk -f, snapper list
My CPU fan had a long high-intensity exercise this morning. The root cause
turned out to be a kworker thread doing "btrfs_preempt_reclaim_metadata_space".
The offending thread identification is "kworker/u16:11".
I've collected some data bits (dmesg, SysRq-L, perf data) during the event. It
is unclear to me, however, what triggered this long-running FS maintenance and
how I could stop it in case I needed to - i.e. if the laptop ran battery or if
I sat in a quiet room where the CPU fan disturbance would be unacceptable.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1189881
Bug ID: 1189881
Summary: warning:
/var/tmp/weak-modules2.7WPIFB/symvers-5.13.12-2-defaul
t not available
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: gp(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Running zypper dup on my Tumbleweed machine, I noticed the following in
the logs:
(121/203) Installing: kernel-default-5.13.12-2.1.x86_64 ....[done]
Additional rpm output:
warning: /var/tmp/weak-modules2.7WPIFB/symvers-5.13.12-2-default not available
It is probably benign, but still a bit confusing/worrisome. What do we
want to tell users here (that would be actionable)?
And/or is this indicative of some problem with the upgrade as such?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1188940
Bug ID: 1188940
Summary: bluetooth adapter fails to power on
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
Found By: ---
Blocker: ---
hramrach@naga:~> bluetoothctl
Agent registered
[CHG] Controller 00:E0:3C:87:B8:03 Pairable: yes
[bluetooth]# power on
Failed to set power on: org.bluez.Error.Failed
[bluetooth]# power on
Failed to set power on: org.bluez.Error.Busy
[bluetooth]# power on
Failed to set power on: org.bluez.Error.Busy
[bluetooth]# power on
Failed to set power on: org.bluez.Error.Busy
[bluetooth]#
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1188889
Bug ID: 1188889
Summary: crash is failing with 5.13 kernels
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: hare(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
When trying to run crash on a 5.13 or later kernel dump I get the error
message:
crash: invalid structure member offset: task_struct_state
FILE: task.c LINE: 5916 FUNCTION: task_state()
[/usr/bin/crash] error trace: 559027f7b785 => 559027f7b54d => 559027fffe94
=> 559027fffe0d
This has been fixed by upstream commit
d6b4f36d6b22b70fb14e692f36d20910ef5563c1.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1184718
Bug ID: 1184718
Summary: systemtap simple helloworld script execution fails in
Tumbleweed
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: openSUSE Tumbleweed
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: vasilios.anastasiadis(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 848350
--> https://bugzilla.suse.com/attachment.cgi?id=848350&action=edit
Related errors
Unable to run a simple systemtap helloworld.stp example script (provided with
systemtap-docs) in Tumbleweed. It works fine in SLE versions 12sp2-15sp3.
Steps to reproduce:
- Install systemtap, systemtap-docs, kernel-default-devel
- Run: stap /usr/share/doc/packages/systemtap/examples/general/helloworld.stp
See attached file for errors.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1188712
Bug ID: 1188712
Summary: VDSO change on PPC causes random segfaults in Go
applications
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: PowerPC-64
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: jkowalczyk(a)suse.com
Found By: ---
Blocker: ---
https://lwn.net/ml/linux-kernel/cover.1601365869.git.christophe.leroy@csgro…
changed the implementation of the VDSO from a PowerPC specific one to the
generic C version.
Apparently executables built with Go before 1.17 implicitly relied on the fact
that the VDSO did not mangle r30, but with the generic C implementation it now
does. This leads to random crashes in Go executables.
This is fixed with https://go-review.googlesource.com/c/go/+/334410/1 and I
submitted this to our go1.16 package with
https://build.opensuse.org/request/show/907807.
However, all executables built with a compiler which doesn't include that will
not work on kernel >= 5.13. This probably affects containerized workloads as
well. So it might be useful to raise awareness of this issue.
--
You are receiving this mail because:
You are the assignee for the bug.