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.
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.
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.
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.