October 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1204172] kernel crash in drm ( [Build 20221010-1] openQA test fails in updates_packagekit_gpk )
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1204172 https://bugzilla.suse.com/show_bug.cgi?id=1204172#c5 --- Comment #5 from Marcus Meissner <meissner(a)suse.com> --- actually it is 15.3 with the SLE15-SP3 kernel. bug open seleected the wrong opensuse -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204172] kernel crash in drm ( [Build 20221010-1] openQA test fails in updates_packagekit_gpk )
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1204172 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Leap 42.3 |Leap 15.3 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204172] New: kernel crash in drm ( [Build 20221010-1] openQA test fails in updates_packagekit_gpk )
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204172 Bug ID: 1204172 Summary: kernel crash in drm ( [Build 20221010-1] openQA test fails in updates_packagekit_gpk ) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://openqa.opensuse.org/tests/2790642/modules/upda tes_packagekit_gpk/steps/39 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: meissner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-15.3-DVD-Updates-x86_64-gnome@64bit-2G fails in [updates_packagekit_gpk](https://openqa.opensuse.org/tests/2790642/modules/u… ## Test suite description Revert schedule to working settings - dleuenberger, 20211117 ## Reproducible Fails since (at least) Build [20221010-1](https://openqa.opensuse.org/tests/2790642) (current job) ## Expected result Last good: [20221009-1](https://openqa.opensuse.org/tests/2790325) (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 1204179] New: udev naming scheme not documented
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1204179 Bug ID: 1204179 Summary: udev naming scheme not documented Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: cgoll(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The command `sudo udevadm test-builtin net_id /sys/class/net/eth0 2>&1 | grep "naming scheme"` reveals that e.g. openSUSE Leap 15.4 (the same holds true for SLES) uses the naming scheme 'sle15-sp4'. This scheme is compiled into the kernel and there is absolute no documentation about this. At least the man page `systemd.net-naming-scheme` should have an entry about it. P.S. The naming scheme is defined by ``` -Dextra-net-naming-schemes=sle15-sp4=v238+bridge_no_slot+slot_function_id+16bit_index ``` -- You are receiving this mail because: You are the assignee for the bug.

1 1

[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 1204164] New: QCOM kernel drivers fail to update
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204164 Bug ID: 1204164 Summary: QCOM kernel drivers fail to update 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: alanhants(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 862052 --> http://bugzilla.opensuse.org/attachment.cgi?id=862052&action=edit Update log For the last couple of TW update iterations, the kernel-firmware-qcom package has thrown an error when it is being updated. Ignoring this error does not seem to mess the system up, but it requires a manual intervention that was unnecessary before. Attached is the applicable part of the update log (extracted from the output of "tumbleweed update"). Note that no other errors are reported during the update process. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1204163] New: Cannot zypper dup: Installation of kernel-firmware-qcom-20220930-1.1.noarch failed
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204163 Bug ID: 1204163 Summary: Cannot zypper dup: Installation of kernel-firmware-qcom-20220930-1.1.noarch failed 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: jas.61803(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 862051 --> http://bugzilla.opensuse.org/attachment.cgi?id=862051&action=edit Just a screenshot .. colorized text may be easier to see stuff Hey, all, I am currently running Tumbleweed 20221006, and have been running Tumbleweed on my 3 systems for years (two desktops and a laptop). Lately, I cannot update my systems via "zypper dup" because when I do I get the following error that "kernel-firmware-qcom-20220930-1.1.noarch" failed installation. Full session example below: ========================================================================= [20:03 root@buddy ~]# zypper dup Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... The following 66 packages are going to be upgraded: MozillaThunderbird chromium ffmpeg-4 glibc glibc-devel glibc-extra glibc-locale glibc-locale-base kernel-firmware-all kernel-firmware-amdgpu kernel-firmware-ath10k kernel-firmware-ath11k kernel-firmware-atheros kernel-firmware-bluetooth kernel-firmware-bnx2 kernel-firmware-brcm kernel-firmware-chelsio kernel-firmware-dpaa2 kernel-firmware-i915 kernel-firmware-intel kernel-firmware-iwlwifi kernel-firmware-liquidio kernel-firmware-marvell kernel-firmware-media kernel-firmware-mediatek kernel-firmware-mellanox kernel-firmware-mwifiex kernel-firmware-network kernel-firmware-nfp kernel-firmware-nvidia kernel-firmware-platform kernel-firmware-prestera kernel-firmware-qcom libavcodec58_134 libavcodec59 libavdevice58_13 libavfilter7_110 libavformat58_76 libavformat59 libavresample4_0 libavutil56_70 libavutil57 libffi8 liblzma5 libpostproc55_9 libswresample3_9 libswresample4 libswscale5_9 libswscale6 libsystemd0 libudev1 mediainfo nscd openSUSE-release openSUSE-release-appliance-custom python310-jupyterlab-widgets python38-jupyterlab-widgets snapd systemd systemd-doc systemd-sysvcompat udev vlc-codecs xz yast2-ruby-bindings yt-dlp The following product is going to be upgraded: openSUSE Tumbleweed 20221006-0 -> 20221008-0 The following NEW package is going to be installed: kernel-default-6.0.0-1.2 The following package requires a system reboot: kernel-default-6.0.0-1.2 66 packages to upgrade, 1 new. Overall download size: 0 B. Already cached: 702.1 MiB. After the operation, additional 277.9 MiB will be used. Note: System reboot required. Continue? [y/n/v/...? shows all options] (y): y In cache glibc-2.36-6.1.x86_64.rpm , 2.4 MiB ( 2.7 MiB unpacked) Checking for file conflicts: .......................................................................................................[done] ( 1/67) Installing: glibc-2.36-6.1.x86_64 ..........................................................................................[done] ( 2/67) Installing: glibc-extra-2.36-6.1.x86_64 ....................................................................................[done] error: unpacking of archive failed on file /usr/lib/firmware/qcom/LENOVO/21BX;63438c74: cpio: File from package already exists as a directory in system error: kernel-firmware-qcom-20220930-1.1.noarch: install failed error: kernel-firmware-qcom-20220902-1.1.noarch: erase skipped ( 3/67) Installing: kernel-firmware-qcom-20220930-1.1.noarch ......................................................................[error] Installation of kernel-firmware-qcom-20220930-1.1.noarch failed: Error: Subprocess failed. Error: RPM failed: Command exited with status 1. Abort, retry, ignore? [a/r/i] (a): a Warning: %posttrans scripts skipped while aborting: kernel-firmware-qcom-20220930-1.1.noarch.rpm Problem occurred during or after installation or removal of packages: Installation has been aborted as directed. Please see the above error message for a hint. [20:07 root@buddy ~]# ========================================================================= This has been going on for several days now. Let me know if I've left anything out or if there is any more information I can provide. Thank you. uname -a: Linux buddy 5.19.12-1-default #1 SMP PREEMPT_DYNAMIC Wed Sep 28 10:51:18 UTC 2022 (95fa5b8) x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1203974] New: Suspend succeeds, system refuses to wake up.
by bugzilla_noreply＠suse.com 09 Oct '22

09 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203974 Bug ID: 1203974 Summary: Suspend succeeds, system refuses to wake up. 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: genes1122(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- My Dell Inspiron 16 3525 laptop refuses to wake from suspend. After many kernel upgrades and two BIOS updates. the problem still persists. This problem is well known on Dell's website, with all versions of linux. What I've found so far is that after forcing a power off and rebooting, the command: journalctl -b -1 | tail Oct 03 14:44:52 Mobile-PC chronyd[1133]: Source 137.190.2.4 offline Oct 03 14:44:52 Mobile-PC chronyd[1133]: Source 2600:3c01::f03c:91ff:fe55:215c offline Oct 03 14:44:52 Mobile-PC chronyd[1133]: Can't synchronise: no selectable sources Oct 03 14:44:52 Mobile-PC chronyd[1133]: Source 162.159.200.123 offline Oct 03 14:44:53 Mobile-PC NetworkManager[1109]: <info> [1664833493.2332] device (wlp2s0): set-hw-addr: reset MAC address to 38:D5:7A:53:49:D7 (unmanage) Oct 03 14:44:53 Mobile-PC systemd[1]: Reached target Sleep. Oct 03 14:44:53 Mobile-PC systemd[1]: Starting System Suspend... Oct 03 14:44:53 Mobile-PC systemd-sleep[2459]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend Oct 03 14:44:53 Mobile-PC systemd-sleep[2457]: Entering sleep state 'suspend'... Oct 03 14:44:53 Mobile-PC kernel: PM: suspend entry (s2idle) This shows that the system successfully entered s2idle sleep, but was unable to wake up. I have tried enabling wakeup for all possible inputs in powertop, but nothing changed. This command shows that the kernel thinks this laptop supports s2idle sleep: > cat /sys/power/mem_sleep [s2idle] However, this Windows 11 command says otherwise: powercfg /A It tells me that my hardware only supports Standby (S0 Low Power Idle), and specifically that s2idle is not supported. So, after every kernel or BIOS update, I check /sys/power/mem_sleep and Windows 11 command, powercfg /A, to see if anything has changed. Here's my hardware: > inxi -b System: Host: Mobile-PC Kernel: 6.0.0-1.ga7dafe3-default arch: x86_64 bits: 64 Desktop: MATE v: 1.26.0 Distro: openSUSE Tumbleweed 20220930 Machine: Type: Laptop System: Dell product: Inspiron 15 3525 v: 1.4.0 serial: <superuser required> Mobo: Dell model: 0R9JV9 v: A00 serial: <superuser required> UEFI: Dell v: 1.4.0 date: 08/11/2022 Battery: ID-1: BAT1 charge: 40.8 Wh (100.0%) condition: 40.8/40.8 Wh (100.0%) CPU: Info: 8-core AMD Ryzen 7 5825U with Radeon Graphics [MT MCP] speed (MHz): avg: 1750 min/max: 1600/4547 Graphics: Device-1: AMD Barcelo driver: amdgpu v: kernel Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo Display: x11 server: X.org v: 1.21.1.4 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: amdgpu resolution: 1920x1080~120Hz OpenGL: renderer: RENOIR (renoir LLVM 14.0.6 DRM 3.48 6.0.0-1.ga7dafe3-default) v: 4.6 Mesa 22.2.0 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Drives: Local Storage: total: 942.7 GiB used: 87.43 GiB (9.3%) Info: Processes: 365 Uptime: 0h 17m Memory: 14.98 GiB used: 1.85 GiB (12.3%) Shell: Bash inxi: 3.3.21 As you can see above, I'm testing the latest kernel from branch master, but it produces the same behavior as all the previous 5.19.x kernels. Is there some way to switch from s2idle to S0 Low Powr Idle suspend? Thanks, Gene -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1204161] New: kernel-firmware-qcom-20220930-1.1.noarch did not install as update, directory already exists
by bugzilla_noreply＠suse.com 09 Oct '22

09 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204161 Bug ID: 1204161 Summary: kernel-firmware-qcom-20220930-1.1.noarch did not install as update, directory already exists 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: frerk.meyer(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The update of kernel-firmware-qcom-20220930-1.1.noarch failed because it said the destination directory already existed. Yes it existed, and had updates from the 7. September 2022: moby:/usr/lib/firmware/qcom/LENOVO/21BX # ll total 7576 -rw-r--r-- 1 root root 320 Sep 7 11:14 adspr.jsn.xz -rw-r--r-- 1 root root 324 Sep 7 11:14 adspua.jsn.xz -rw-r--r-- 1 root root 304 Sep 7 11:14 battmgr.jsn.xz -rw-r--r-- 1 root root 300 Sep 7 11:14 cdspr.jsn.xz -rw-r--r-- 1 root root 4666640 Sep 7 11:14 qcadsp8280.mbn.xz -rw-r--r-- 1 root root 1029448 Sep 7 11:14 qccdsp8280.mbn.xz -rw-r--r-- 1 root root 2420 Sep 7 11:14 qcdxkmsuc8280.mbn.xz -rw-r--r-- 1 root root 2034264 Sep 7 11:14 qcslpi8280.mbn.xz Workaround: I became root and moved /usr/lib/firmware/qcom/LENOVO to /usr/lib/firmware/qcom/LENOVO.bak Then I installed the update and it worked. The directory now looks like this: moby:/usr/lib/firmware/qcom/LENOVO/21BX # ll total 7576 -rw-r--r-- 1 root root 320 Oct 4 20:54 adspr.jsn.xz -rw-r--r-- 1 root root 324 Oct 4 20:54 adspua.jsn.xz -rw-r--r-- 1 root root 304 Oct 4 20:54 battmgr.jsn.xz -rw-r--r-- 1 root root 300 Oct 4 20:54 cdspr.jsn.xz -rw-r--r-- 1 root root 4666640 Oct 4 20:54 qcadsp8280.mbn.xz -rw-r--r-- 1 root root 1029448 Oct 4 20:54 qccdsp8280.mbn.xz -rw-r--r-- 1 root root 2420 Oct 4 20:53 qcdxkmsuc8280.mbn.xz -rw-r--r-- 1 root root 2034264 Oct 4 20:54 qcslpi8280.mbn.xz (Nothing seems to have changed?) I deleted /usr/lib/firmware/qcom/LENOVO.bak because it worked. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1204141] New: [RPi4] kernel: thermal_sys: Failed to find 'trips' node
by bugzilla_noreply＠suse.com 09 Oct '22

09 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204141 Bug ID: 1204141 Summary: [RPi4] kernel: thermal_sys: Failed to find 'trips' node Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/2783031/modules/jour nal_check/steps/11 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, dmueller(a)suse.com, mbrugger(a)suse.com Found By: openQA Blocker: Yes With update to kernel 6.0, openQA found a new kernel error message: Sep 21 00:00:01.144055 localhost kernel: thermal_sys: Failed to find 'trips' node See: https://openqa.opensuse.org/tests/2783031/modules/journal_check/steps/11 -- You are receiving this mail because: You are the assignee for the bug.

1 2