September 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1190594] No dvb modules in kernel-default in 15.3
by bugzilla_noreply＠suse.com 17 Sep '21

17 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190594 https://bugzilla.suse.com/show_bug.cgi?id=1190594#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com, | |wagner-thomas(a)gmx.at Flags| |needinfo?(wagner-thomas@gmx | |.at) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Did you install kernel-default-extra and kernel-default-optional? On Leap 15.3, kernel package was split to three sub-packages, and some of them are put in *-extra or *-optional. Usually all of those are installed via zypper recommends, but those are not mandatory. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190594] New: No dvb modules in kernel-default in 15.3
by bugzilla_noreply＠suse.com 17 Sep '21

17 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190594 Bug ID: 1190594 Summary: No dvb modules in kernel-default in 15.3 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: wagner-thomas(a)gmx.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading openSUSE Leap 15.2 to 15.3, there are no dvb modules in /lib/modules/$(uname -r)/kernel/drivers/media Thus, no TV-card can be operated under Leap 15.3. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190461] loading initial rumdisk 5.14
by bugzilla_noreply＠suse.com 17 Sep '21

17 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190461 http://bugzilla.opensuse.org/show_bug.cgi?id=1190461#c4 --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Then please give hwinfo output from the working 5.13.x boot. Then try to boot 5.14.x kernel with nomodeset boot option to see whether it boots better or not. The OBS Kernel:stable tree contains much newer kernel than on TW snapshot. It's still worth to try. But note that it's an unofficial build, hence it won't boot with Secure Boot. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190322] New: Thinkpad T530 regression kernel 5.14 suspend to RAM broken
by bugzilla_noreply＠suse.com 17 Sep '21

17 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190322 Bug ID: 1190322 Summary: Thinkpad T530 regression kernel 5.14 suspend to RAM broken Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: sb56637(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852386 --> http://bugzilla.opensuse.org/attachment.cgi?id=852386&action=edit hwinfo Thinkpad T530 Hi there, there is a regression with kernel 5.14 on my Thinkpad T530 laptop (hwinfo attached). The laptop will no longer suspend to RAM. The screen turns off and the WiFI light does too, but the system remains powered-on. It is repeatable every time. Reverting to a 5.13.x kernel does not produce this bug. Thanks for the help! -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1190461] loading initial rumdisk 5.14
by bugzilla_noreply＠suse.com 16 Sep '21

16 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190461 http://bugzilla.opensuse.org/show_bug.cgi?id=1190461#c3 --- Comment #3 from Mikhail Glumov <frostalien(a)gmail.com> --- (In reply to Takashi Iwai from comment #2) > Which kernel did you test exactly? > > Also please try the latest 5.14.x kernel in OBS Kernel:stable repo, too. My system halted only first 5.14 kernel have been updated. After that I try boot from USB with fresh 5.14.1 with same result -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185744] System hangs at reboot and shutdown, waiting for network
by bugzilla_noreply＠suse.com 16 Sep '21

16 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1185744 https://bugzilla.suse.com/show_bug.cgi?id=1185744#c14 --- Comment #14 from Takashi Iwai <tiwai(a)suse.com> --- TW is a rolling distro, and a daily update may invalidate the things of yesterday :) In this case, the major kernel version changed in between; hence we cannot fix anything about your tested 5.13.x kernel, as the package is already built from a newer version, i.e. a completely new code base. It was too old, literally. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 1190567] New: vmlinuz is no longer present on /boot/ breaking separate boot partitions
by bugzilla_noreply＠suse.com 16 Sep '21

16 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190567 Bug ID: 1190567 Summary: vmlinuz is no longer present on /boot/ breaking separate boot partitions 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: dcermak(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The kernel packaging in Tumbleweed changed "recently" (at some point in the last months): vmlinuz is no longer on /boot/ but is now in /usr/lib/modules. I guess that this has been introduced as part of the usrmerge effort. However, this breaks images build by kiwi that use a separate boot partition, as now all these symlinks are dead when booting from that separate partition. This leads to booting issues like: Loading Linux 5.14.1-1-default ... error: ../../grub-core/fs/fshelp.c:257:file `/vmlinuz-5.14.1-1-default' not found. Loading initial ramdisk ... error: ../../grub-core/loader/i386/linux.c:1053:you need to load the kernel first. Example disk image: - https://build.opensuse.org/package/show/Virtualization:Appliances:Images:Te… - https://build.opensuse.org/package/show/Virtualization:Appliances:Images:Te… -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1185744] System hangs at reboot and shutdown, waiting for network
by bugzilla_noreply＠suse.com 16 Sep '21

16 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1185744 https://bugzilla.suse.com/show_bug.cgi?id=1185744#c13 David Kerkhof <dutchkind(a)txoriaskea.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME Flags|needinfo?(dutchkind@txorias | |kea.org) | --- Comment #13 from David Kerkhof <dutchkind(a)txoriaskea.org> --- You must be kidding, way too old kernel? In Tumbleweed that is daily kept up-to-date? Anyway, I tested with the latest kernel that was pushed just over a week ago and the problem seems to be solved, I haven't had anymore hangs, thanks -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 1190561] OOPS / Invalid RIP in when attaching XDP program to veth interface
by bugzilla_noreply＠suse.com 16 Sep '21

16 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190561 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190563] New: Problems with acpi_call package
by bugzilla_noreply＠suse.com 16 Sep '21

16 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190563 Bug ID: 1190563 Summary: Problems with acpi_call package 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: popov895(a)ukr.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm using a ThinkPad which supports advanced battery management via TLP, like charging thresholds and recalibration. To enable these features, I followed the instructions in the TLP docs (https://linrunner.de/tlp/installation/opensuse.html) and installed packages tlp, tlp-rdw and acpi_call (to install acpi_call I added repository https://download.opensuse.org/repositories/Base:System/openSUSE_Tumbleweed/…) But after that `sudo tlp-stat -b` reported me that acpi_call is not installed: > $ sudo tlp-stat -b > --- TLP 1.3.1 -------------------------------------------- > > +++ Battery Features: Charge Thresholds and Recalibrate > natacpi = active (data, thresholds) > tpacpi-bat = inactive (kernel module 'acpi_call' not installed) > tp-smapi = inactive (ThinkPad not supported) > > +++ ThinkPad Battery Status: BAT0 > /sys/class/power_supply/BAT0/manufacturer = LGC > /sys/class/power_supply/BAT0/model_name = 01AV445 > /sys/class/power_supply/BAT0/cycle_count = 250 > /sys/class/power_supply/BAT0/energy_full_design = 45000 [mWh] > /sys/class/power_supply/BAT0/energy_full = 38140 [mWh] > /sys/class/power_supply/BAT0/energy_now = 38140 [mWh] > /sys/class/power_supply/BAT0/power_now = 0 [mW] > /sys/class/power_supply/BAT0/status = Full > > /sys/class/power_supply/BAT0/charge_start_threshold = 65 [%] > /sys/class/power_supply/BAT0/charge_stop_threshold = 65 [%] > > Charge = 100.0 [%] > Capacity = 84.8 [%] > > +++ Recommendations > * Install acpi_call kernel module for ThinkPad battery recalibration Also `sudo modprobe acpi_call` reported me that acpi_call kernel module was not found: > $ sudo modprobe acpi_call > modprobe: FATAL: Module acpi_call not found in directory /lib/modules/5.14.1-1-default After that, using `rpm -ql acpi_call`, I found that acpi_call doesn't install the kernel module: > $ rpm -ql acpi_call > /usr/libexec/modules-load.d > /usr/libexec/modules-load.d/acpi_call.conf > /usr/share/doc/packages/acpi_call > /usr/share/doc/packages/acpi_call/README.md Further, after some researching, I found that in addition to acpi_call I need to install acpi_call-kmp-default package, which actually installs the required kernel module: > $ rpm -ql acpi_call > /lib/modules/5.14.1-1-default > /lib/modules/5.14.1-1-default/updates > /lib/modules/5.14.1-1-default/updates/acpi_call.ko But now the output of `sudo tlp-stat -b` looks like this: > $ sudo tlp-stat -b > /usr/share/tlp/func.d/35-tlp-func-batt: line 25: 6070 Killed $TPACPIBAT -g FD 1 > /dev/null 2>&1 > --- TLP 1.3.1 -------------------------------------------- > > +++ Battery Features: Charge Thresholds and Recalibrate > natacpi = active (data, thresholds) > tpacpi-bat = unknown status > tp-smapi = inactive (ThinkPad not supported) > > /usr/share/tlp/func.d/35-tlp-func-batt: line 25: 6117 Killed $TPACPIBAT -g FD 1 > /dev/null 2>&1 > /usr/share/tlp/func.d/35-tlp-func-batt: line 25: 6163 Killed $TPACPIBAT -g FD 1 > /dev/null 2>&1 > +++ ThinkPad Battery Status: BAT0 > /sys/class/power_supply/BAT0/manufacturer = LGC > /sys/class/power_supply/BAT0/model_name = 01AV445 > /sys/class/power_supply/BAT0/cycle_count = 250 > /sys/class/power_supply/BAT0/energy_full_design = 45000 [mWh] > /sys/class/power_supply/BAT0/energy_full = 38140 [mWh] > /sys/class/power_supply/BAT0/energy_now = 37400 [mWh] > /sys/class/power_supply/BAT0/power_now = 0 [mW] > /sys/class/power_supply/BAT0/status = Unknown > > /sys/class/power_supply/BAT0/charge_start_threshold = 65 [%] > /sys/class/power_supply/BAT0/charge_stop_threshold = 65 [%] > > Charge = 98.1 [%] > Capacity = 84.8 [%] > > /usr/share/tlp/func.d/35-tlp-func-batt: line 25: 6263 Killed $TPACPIBAT -g FD 1 > /dev/null 2>&1 As you can see, I am getting error "/usr/share/tlp/func.d/35-tlp-func-batt: line 25: xxxx Killed $TPACPIBAT -g FD 1 > /dev/null 2>&1". The TLP developer told me that I should use a recent version of acpi_call (https://github.com/linrunner/TLP/issues/571#issuecomment-920318813) Actually, I guess that the following should be done to fix this issue: 1. Update acpi_call to the recent version 2. Install the acpi_call-kmp-default package as a dependency of the acpi_call package System information > $ lsb_release -a > LSB Version: n/a > Distributor ID: openSUSE > Description: openSUSE Tumbleweed > Release: 20210913 > Codename: n/a > $ uname -a > Linux localhost.localdomain 5.14.1-1-default #1 SMP Sat Sep 4 08:22:51 UTC 2021 (67af907) x86_64 x86_64 x86_64 GNU/Linux > $ zypper info acpi_call > Information for package acpi_call: > ---------------------------------- > Repository : Base:System Factory Devel Project (openSUSE_Tumbleweed) > Name : acpi_call > Version : 1.1.0-3.112 > Arch : x86_64 > Vendor : obs://build.opensuse.org/Base:System > Installed Size : 3,0 KiB > Installed : Yes > Status : up-to-date > Source package : acpi_call-1.1.0-3.112.src > Summary : The acpi-call kernel module > Description : > A kernel simple module that enables you to call ACPI methods by writing the method name followed by arguments to /proc/acpi/call. > > This module is to be considered a proof-of-concept and has been superseeded by projects like bbswitch. It allows you to tamper with your system and should be used with caution. > $ zypper info acpi_call-kmp-default > Information for package acpi_call-kmp-default: > ---------------------------------------------- > Repository : Base:System Factory Devel Project (openSUSE_Tumbleweed) > Name : acpi_call-kmp-default > Version : 1.1.0_k5.14.1_1-3.112 > Arch : x86_64 > Vendor : obs://build.opensuse.org/Base:System > Installed Size : 15,2 KiB > Installed : Yes > Status : up-to-date > Source package : acpi_call-1.1.0-3.112.src > Summary : The acpi-call kernel module > Description : > A kernel simple module that enables you to call ACPI methods by writing the method name followed by arguments to /proc/acpi/call. > > This module is to be considered a proof-of-concept and has been superseeded by projects like bbswitch. It allows you to tamper with your system and should be used with caution. -- You are receiving this mail because: You are the assignee for the bug.

1 1