September 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1199661] New: amd-pstate CPU Performance Scaling Driver
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199661 Bug ID: 1199661 Summary: amd-pstate CPU Performance Scaling Driver Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: reiokorn(a)tutanota.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, is there an easy way to activate the new amd-pstate driver on Tumbleweed? I've tried: kernel-parameters: amd_pstate.replace=1 and amd_pstate.shared_mem=1 additionally I created a file named /etc/modules-load.d/amd-pstate.conf inside: # Load amd pstate at boot amd_pstate However it still defaults to: cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver acpi-cpufreq Anything I'm missing here? Thanks for your help -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1203539] New: Boot hangs with update to kernel 5.14.21-15040.24.21-default
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1203539 Bug ID: 1203539 Summary: Boot hangs with update to kernel 5.14.21-15040.24.21-default Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jcarricksmith(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 861545 --> https://bugzilla.suse.com/attachment.cgi?id=861545&action=edit Outputs from journalctl -b -? After the latest kernel update, when booting the system the load stalls after the message "Apparmor profiles loaded" is shown on the boot screen. After a pause both the CAPS Lock and NUM Lock lights flash together. The only way to recover from the situation is to hold the power button down. Booting 5.14.21-150400.24.18-default works fine. In the attachment there is the output from a boot on ...24.21-... (badjournal) and the output from good session on ...24.18-... (goodjournal) Many thanks John -- You are receiving this mail because: You are the assignee for the bug.

1 21

[Bug 1201705] New: kernel-obs-build: include qemu_fw_cfg
by bugzilla_noreply＠suse.com 31 Oct '22

31 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1201705 Bug ID: 1201705 Summary: kernel-obs-build: include qemu_fw_cfg 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: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- To be able to pass options into the build vm, the qemu_fg_cfg system can be used. So the module needs to be included. See https://github.com/openSUSE/obs-build/pull/765 -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 1202386] New: after upgrade, pc randomly freezes with kernel panic and segfault in power management
by bugzilla_noreply＠suse.com 28 Oct '22

28 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1202386 Bug ID: 1202386 Summary: after upgrade, pc randomly freezes with kernel panic and segfault in power management Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: andrea.manzini(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 860780 --> https://bugzilla.suse.com/attachment.cgi?id=860780&action=edit extract from journalctl --system output after upgrade my laptop to OpenSuse TumbleWeed 20220813, with kernel 5.19.0-1-default , I experience random kernel panics (PC freezes with caps lock blinking) and in system logs I find some error message about power management (see attachment). Hardware name: LENOVO 20YRS2D84A/20YRS2D84A, BIOS N37ET39W (1.20 ) 04/15/2022 -- You are receiving this mail because: You are the assignee for the bug.

1 38

[Bug 1190764] New: [Build 20210920] btrfs: invalid qgroupid or subvolume path
by bugzilla_noreply＠suse.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1190764 Bug ID: 1190764 Summary: [Build 20210920] btrfs: invalid qgroupid or subvolume path Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1929805/modules/btrf s_qgroups/steps/24 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 Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_filesystem@64bit fails in [btrfs_qgroups](https://openqa.opensuse.org/tests/1929805/modules/btrfs_qgro… The openQA test code is this: assert_script_run "btrfs quota enable ."; # Create subvolumes, qgroups, assigns and limits # 2/1 # / \ # 1/1 1/2 # / \ / | \ # a b c d(k) assert_script_run "for c in {a..d}; do btrfs subvolume create \$c; done"; assert_script_run "for c in 1/1 1/2 2/1; do btrfs qgroup create \$c .; done"; assert_script_run "for c in a b; do btrfs qgroup assign \$c 1/1 .; done"; assert_script_run "for c in b c d; do btrfs qgroup assign \$c 1/2 .; done"; assert_script_run "for c in 1/1 1/2; do btrfs qgroup assign \$c 2/1 .; done"; And the last command here returns: ERROR: invalid qgroupid or subvolume path: a ERROR: invalid qgroupid or subvolume path: b ## Test suite description Maintainer: QE Core Filesystem related tests, for example snapper and btrfs features. ## Reproducible Fails since (at least) Build [20210920](https://openqa.opensuse.org/tests/1928938) ## Expected result Last good: [20210918](https://openqa.opensuse.org/tests/1927312) (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 4

[Bug 1203404] New: 60°C Idle Temperature on freshly installed openSUSE Tumbleweed AND Leap-15.4 as well
by bugzilla_noreply＠suse.com 19 Oct '22

19 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203404 Bug ID: 1203404 Summary: 60�C Idle Temperature on freshly installed openSUSE Tumbleweed AND Leap-15.4 as well Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: uwe.scheffer(a)scheffer-software.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I own several Lenovo Thinkpad W530 Laptops, all i7-3740QM, 32GB RAM, 512 GB SSD, all with Leap 15.2 KDE, so need to upgrade. After booting, idle temperatures typically are around 45�C, fan is at 0 rpm, using Thinkfan with simple customized configuration. The idle temperature around 45�C is valid for Leap 15.0 - 15.3 on all my Thinkpad W530 machines. However, if I install Leap 15.4 or TW, I am immediately getting idle temperatures around 60�C right after a fresh install, no matter what. -- You are receiving this mail because: You are the assignee for the bug.

1 21

[Bug 1187566] New: Display connected to Thunderbolt 3 Docking Station is not detected on cold boot
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1187566 Bug ID: 1187566 Summary: Display connected to Thunderbolt 3 Docking Station is not detected on cold boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: eecdc3.opensuse(a)coders-haven.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am using a HP Elitebook 1040 G4 notebook connected to a HP Thunderbolt 3 Docking Station, which in turn is connected to multiple USB devices and an external monitor via DisplayPort. Unfortunately, I am experiencing issues with this configuration as described below. I am using boltd from the hardware repository to authorize my Thunderbolt 3 Docking Station during startup. (Boot ACLs are not supported by my BIOS, as far as I can tell.) While devices connected to the docking station via USB will work afterwards, my external monitor, which is connected via DisplayPort, will not be detected automatically. Only when I manually reconnect the docking station after startup has completed, it will finally be detected (and awoken from standby). This leads me to believe that this issue is boot order related. (Previously, I was using openSUSE Leap 15.2 and a custom udev rule to authorize the docking station via sysfs and I did not experience this issue but the system would occasionally hang while booting instead. I have already tried the udev rule with openSUSE Leap 15.3 but this made the issue worse as the display was then only detected if I reconnected the external monitor itself.) Any help investigating this issue is appreciated as I do not have in-depth knowledge of the kernel or its Thunderbolt subsystem and cannot really make any progress towards a resolution on my own. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1200716] New: occasional "xHCI host controller not responding, assume dead' with Thunderbolt dock
by bugzilla_noreply＠suse.com 07 Oct '22

07 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200716 Bug ID: 1200716 Summary: occasional "xHCI host controller not responding, assume dead' with Thunderbolt dock 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: pujos.michael(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have a laptop with a TB2 dock connected via TB3 using the TB3->TB2 Apple adapter. It worked fine for a while but since a few kernels, the USB hub of the dock get (seemingly) randomly disconnected: [ 8524.631011] xhci_hcd 0000:09:00.0: xHCI host controller not responding, assume dead [ 8524.631039] xhci_hcd 0000:09:00.0: HC died; cleaning up [ 8524.631076] usb 3-4: 1:0: usb_set_interface failed (-110) [ 8524.631087] usb 3-4: Not enough bandwidth for altsetting 1 [ 8524.631093] usb 3-4: 1:1: usb_set_interface failed (-19) [ 8524.631101] usb 3-4: Not enough bandwidth for altsetting 0 [ 8524.631107] usb 3-4: 1:0: usb_set_interface failed (-19) [ 8524.631213] usb 3-4: Not enough bandwidth for altsetting 0 [ 8524.631220] usb 3-4: 1:0: usb_set_interface failed (-19) [ 8524.631226] usb 3-4: Not enough bandwidth for altsetting 1 [ 8524.631231] usb 3-4: 1:1: usb_set_interface failed (-19) [ 8524.631238] usb 3-4: Not enough bandwidth for altsetting 0 [ 8524.631243] usb 3-4: 1:0: usb_set_interface failed (-19) [ 8524.631294] usb 3-4: Not enough bandwidth for altsetting 0 [ 8524.631300] usb 3-4: 1:0: usb_set_interface failed (-19) [ 8524.631306] usb 3-4: Not enough bandwidth for altsetting 1 [ 8524.631311] usb 3-4: 1:1: usb_set_interface failed (-19) [ 8524.631317] usb 3-4: Not enough bandwidth for altsetting 0 [ 8524.631323] usb 3-4: 1:0: usb_set_interface failed (-19) [ 8524.631358] usb 3-4: Not enough bandwidth for altsetting 0 [ 8524.631364] usb 3-4: 1:0: usb_set_interface failed (-19) [ 8524.631370] usb 3-4: Not enough bandwidth for altsetting 1 [ 8524.631376] usb 3-4: 1:1: usb_set_interface failed (-19) [ 8524.631382] usb 3-4: Not enough bandwidth for altsetting 0 [ 8524.631387] usb 3-4: 1:0: usb_set_interface failed (-19) [ 8524.631430] usb 3-4: Not enough bandwidth for altsetting 0 [ 8524.631436] usb 3-4: 1:0: usb_set_interface failed (-19) [ 8524.631442] usb 3-4: Not enough bandwidth for altsetting 1 [ 8524.631447] usb 3-4: 1:1: usb_set_interface failed (-19) [ 8524.631453] usb 3-4: Not enough bandwidth for altsetting 0 [ 8524.631458] usb 3-4: 1:0: usb_set_interface failed (-19) [ 8524.631639] usb 3-4: USB disconnect, device number 2 The disconnections does not happen very frequently, but when it happens it is annoying as I usually have my keyboard connected to it and use its USB audio output. It also has a DisportPort port to which my external monitor is attached, but it is not affected. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1203815] New: Kernel library file /usr/lib64/../share/pocl/kernel-x86_64-suse-linux-avx_fma4.bc doesn't exist.
by bugzilla_noreply＠suse.com 04 Oct '22

04 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1203815 Bug ID: 1203815 Summary: Kernel library file /usr/lib64/../share/pocl/kernel-x86_64-suse-linux-avx_ fma4.bc doesn't exist. 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: rskunath(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is on the latest kernel - 5.19.10-1-default This previously worked but now creates this error on an application launch that needs pocl: Kernel library file /usr/lib64/../share/pocl/kernel-x86_64-suse-linux-avx_fma4.bc doesn't exist. This may be a module name change as the module is actually now named: /usr/share/pocl/kernel-x86_64-suse-linux-gnu-avx_fma4.bc and not kernel-x86_64-suse-linux-avx_fma4.bc To recreate, run Linrad from the command line: ./xlinrad64 You immediately get the error. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1202825] New: Haswell Laptop Completely Freezes After Waking up from Suspend
by bugzilla_noreply＠suse.com 03 Oct '22

03 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202825 Bug ID: 1202825 Summary: Haswell Laptop Completely Freezes After Waking up from Suspend Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ege.oz(a)tutanota.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 861132 --> http://bugzilla.opensuse.org/attachment.cgi?id=861132&action=edit Output of "inxi -F" Hello, Haswell laptop with the latest TW kernel completely freezes after waking from suspend. Downgrading to 5.14.21 from Leap 15.4 fixes this issue. I am unable to debug this is issue, as the previous boot's kernel log (journalct -b -1) abruptly ends without any indication regarding this issue. In fact, after attempting to wake up the system, even keyboard status LEDs are unresponsive. I have also attempted to SSH into the laptop after waking it up without any success. Thank you, Kind regards. -- You are receiving this mail because: You are the assignee for the bug.

1 11