June 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1180591] New: Display backlight stuck at 100%
by bugzilla_noreply＠suse.com 08 Aug '22

08 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1180591 Bug ID: 1180591 Summary: Display backlight stuck at 100% 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: maurizio.galli(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 844855 --> http://bugzilla.opensuse.org/attachment.cgi?id=844855&action=edit system information I have just upgraded my device to Tumbleweed and now backlight brightness is stuck at 100% with no way to change it. I have tried several methods, including xbacklight and Xfce settings. Backlight control used to work fine with Kernel 5.3 shipped by Leap. I found a recent report using similar hardware that could suggest a regression in the kernel: https://discuss.getsol.us/d/6039-brightness-control-not-working-on-apple-di… I attached information about my system but please let me know what else I can provide. -- You are receiving this mail because: You are the assignee for the bug.

1 24

[Bug 1199848] New: kernel crash / error_code(0x0000) - not-present page
by bugzilla_noreply＠suse.com 05 Aug '22

05 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199848 Bug ID: 1199848 Summary: kernel crash / error_code(0x0000) - not-present page Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: obs(a)akr.yagii.de QA Contact: qa-bugs(a)suse.de CC: hare(a)suse.com, obs(a)akr.yagii.de, rtsvetkov(a)suse.com, sweiberg(a)suse.com, tiwai(a)suse.com Depends on: 1196213 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1196213 +++ Opening new bug as suggested there. I have observed two more crashes with kernel 5.14.21-150400.122.ga565947-default, both again with [26800.044019] #PF: error_code(0x0000) - not-present page Circumstances have been different though: the attached crash dmesg occurred when trying to boot off an inserted USB-Stick attached to a QEMU-KVM VM or when attaching the new USB Host device to a running VM. The same happens for the SLE15-SP4 kernel 5.14.21-150400.139.g11e974a-default. dmesg submitted with Bug #1196213. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1200306] New: USB Mouse responds poorly when high bandwidth used by USB Ethernet adapter
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200306 Bug ID: 1200306 Summary: USB Mouse responds poorly when high bandwidth used by USB Ethernet adapter Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: php4fan(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Steps to reproduce: - plug a usb ethernet adapter and connect to an Etherent LAN - plug a USB mouse (in my case, a wireless one) - stream video, download something heavy, or do a speedtest at speedtest.net or similar, and move the mouse meanwhile Expected: the mouse should always respond smoothly no matter what Observed: when network bandwidth usage is high, the mouse responds sluggishly This actually looks like the initial symptoms of bug 1184817 (which I had stopped observing and assumed was fixed), although for now I'm only experiencing mouse unsersponsiveness and not the whole system falling apart. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1200989] New: system crash on simultaneous power-on of two monitors
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1200989 Bug ID: 1200989 Summary: system crash on simultaneous power-on of two monitors 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: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I had this already with 15.3, now tried again with 15.4 ... I have this PN50 with two monitors attached, it is always on but I power off the monitors in the evening and turn them on when I get to the system in the morning. If I turn on one monitor, wait for a picture and then turn on the second one, all is fine. If I turn on both at the same time the system freezes completely, does not even ping anymore. AMD Ryzen 7 4800U, AMD Renoir GPU, 2 LG 27 UHD monitors. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1200584] New: Alien:Isolation crashes to desktop after upgrade to 5.17.9
by bugzilla_noreply＠suse.com 01 Aug '22

01 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200584 Bug ID: 1200584 Summary: Alien:Isolation crashes to desktop after upgrade to 5.17.9 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: Michael.Zapf(a)mizapf.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 859634 --> http://bugzilla.opensuse.org/attachment.cgi?id=859634&action=edit snapper status Alien:Isolation (game ported by Feral, run in Steam) crashes to desktop after some seconds in the game. Console output says segmentation fault, but no other helpful information. The crash occurs since the upgrade to 5.17.9 on 2022-05-24. The previous release that still works (verified by booting as a snapshot) is 5.17.7 of 2022-05-16. Later releases (5.18.x) are also affected. I attach a snapper status output between the last working and the first non-working release as available on my computer. My apologies if this bug tracker is not appropriate for this issue. As always, issues of this kind are difficult to report; you don't even know where to report first: distributor, video drivers, game, ... -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1200647] New: TW 20220614: MT7921K (RZ608) Wi-Fi (14c3:0608) fails to initialize with "probe of 0000:06:00.0 failed with error -5"
by bugzilla_noreply＠suse.com 27 Jul '22

27 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200647 Bug ID: 1200647 Summary: TW 20220614: MT7921K (RZ608) Wi-Fi (14c3:0608) fails to initialize with "probe of 0000:06:00.0 failed with error -5" 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: develop7(a)develop7.info QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Repro: 1. Have a MediaTek's MT7921K (RZ608) wireless adapter (onboard in my case) 2. Boot openSUSE Tumbleweed Expected: the wireless adapter gets picked up because it's recognized by a kernel since 5.17 Instead: the adapter fails to initialize, citing following kernel log messages (filtered): ``` Fri 2022-06-17 10:44:55.928623 CEST [s=63f81405409f47938b3898fedbbf5334;i=c2aba0;b=ef5ffbd5c3d84acf800cb529f2f9f4b9;m=68a5b1;t=5e1a0c4c6bb2f;x=ef38ece4e198f878] _MACHINE_ID=4ee51e58105a4f0da4915e69b1ba2c63 _HOSTNAME=linux-4kt6 PRIORITY=6 _TRANSPORT=kernel SYSLOG_FACILITY=0 SYSLOG_IDENTIFIER=kernel _KERNEL_SUBSYSTEM=pci _KERNEL_DEVICE=+pci:0000:06:00.0 _UDEV_SYSNAME=0000:06:00.0 MESSAGE=mt7921e 0000:06:00.0: enabling device (0000 -> 0002) _BOOT_ID=ef5ffbd5c3d84acf800cb529f2f9f4b9 _SOURCE_MONOTONIC_TIMESTAMP=7014740 Fri 2022-06-17 10:44:57.120626 CEST [s=63f81405409f47938b3898fedbbf5334;i=c2ac1b;b=ef5ffbd5c3d84acf800cb529f2f9f4b9;m=7ad5f3;t=5e1a0c4d8eb72;x=6d724dccc54a1a] _MACHINE_ID=4ee51e58105a4f0da4915e69b1ba2c63 _HOSTNAME=linux-4kt6 _TRANSPORT=kernel SYSLOG_FACILITY=0 SYSLOG_IDENTIFIER=kernel PRIORITY=3 _KERNEL_SUBSYSTEM=pci _KERNEL_DEVICE=+pci:0000:06:00.0 _UDEV_SYSNAME=0000:06:00.0 MESSAGE=mt7921e 0000:06:00.0: driver own failed _BOOT_ID=ef5ffbd5c3d84acf800cb529f2f9f4b9 _SOURCE_MONOTONIC_TIMESTAMP=8206250 Fri 2022-06-17 10:44:57.120769 CEST [s=63f81405409f47938b3898fedbbf5334;i=c2ac1c;b=ef5ffbd5c3d84acf800cb529f2f9f4b9;m=7ad682;t=5e1a0c4d8ec01;x=ac1fa6e037cee22d] _MACHINE_ID=4ee51e58105a4f0da4915e69b1ba2c63 _HOSTNAME=linux-4kt6 _TRANSPORT=kernel SYSLOG_FACILITY=0 SYSLOG_IDENTIFIER=kernel PRIORITY=4 MESSAGE=mt7921e: probe of 0000:06:00.0 failed with error -5 _BOOT_ID=ef5ffbd5c3d84acf800cb529f2f9f4b9 _SOURCE_MONOTONIC_TIMESTAMP=8206256 ``` https://linux-hardware.org/?id=pci:14c3-0608-14c3-0608 proves kernel supports it already, https://linux-hardware.org/?probe=83733f81bd#d35 proves it didn't initialize for me -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1188934] New: bluetooth not automatically powered on
by bugzilla_noreply＠suse.com 22 Jul '22

22 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1188934 Bug ID: 1188934 Summary: bluetooth not automatically powered 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: --- There is yet another way to make bluetooth devices unusable. The beluetooth adapter is by default powered off, and has to be manually powered on to be able to connect devices. [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# power on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady Failed to set power on: org.bluez.Error.Failed [DEL] Controller 00:E0:3C:87:B8:03 naga [default] [NEW] Controller 00:E0:3C:87:B8:03 naga [default] [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 0000111f-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 00001200-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 00001112-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 00001108-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 00001800-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 00001801-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb [bluetooth]# power on [CHG] Controller 00:E0:3C:87:B8:03 Class: 0x006c010c Changing power on succeeded [CHG] Controller 00:E0:3C:87:B8:03 Powered: yes [bluetooth]# scan on Discovery started I think that it's quite clear you wanted your adapter powered on if you tried to scan for devices. The Linux kernel got automatic power management ages ago. Can't that apply to bluetooth as well? -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kernel-bugs] [Bug 1174622] New: System not reconnecting to WLAN after suspend/resume
by bugzilla_noreply＠suse.com 22 Jul '22

22 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1174622 Bug ID: 1174622 Summary: System not reconnecting to WLAN after suspend/resume Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: holgi(a)suse.com QA Contact: qa-bugs(a)suse.de CC: tiwai(a)suse.com Found By: Development Blocker: --- Created attachment 840122 --> https://bugzilla.suse.com/attachment.cgi?id=840122&action=edit Output of hwinfo --netcard System with NetworkManger is connected to a wifi network. After suspend and resume later, it is not able to reconnect to the same wifi network. After a reboot, system is connecting to the same wifi network without any problems. -- You are receiving this mail because: You are the assignee for the bug.

1 27

[kernel-bugs] [Bug 1174868] New: Upgrade to LEAP 15.2 makes Thinkpad 480s sometimes completely freezes, 20°C warmer and journal is trimmed
by bugzilla_noreply＠suse.com 20 Jul '22

20 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1174868 Bug ID: 1174868 Summary: Upgrade to LEAP 15.2 makes Thinkpad 480s sometimes completely freezes, 20°C warmer and journal is trimmed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: markus.zimmermann(a)symflower.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- One of our machines here a Thinkpad T480s on openSUSE 15.2 kernel 5.3.18-lp152.33-default. In general this machine was upgraded from LEAP 15.1 to 15.2 and then the problems started to show. The CPU is constantly hotter while working. by 20°C. This machine now freezes sometimes completely. The machine is then - not pingable - no keyboard interaction works - lid close/open does nothng - no mouse interaction works - the notebook is really warm - When a freeze happens also a trim of the journal happens... e.g. we loose the whole journal for the day. - We SSH'ed into the machine and watched via "htop", "journal -f" and "sensors". WHen the machine freezes, there is no significant load via htop seeable, there are no interesting logs in journal and sensors shows that it is simply hotter. Interestingly, we upgraded another machine before (also a Thinkpad T480s) and this does not have any problems. We are btw on the latest firmwares using fwupdmgr. What should we try? How can we debug it? -- You are receiving this mail because: You are the assignee for the bug.

1 20

[Bug 1198565] New: 5.17.2-1-default shows ACPI BIOS Errors - 5.17.1-1-default did not.
by bugzilla_noreply＠suse.com 19 Jul '22

19 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1198565 Bug ID: 1198565 Summary: 5.17.2-1-default shows ACPI BIOS Errors - 5.17.1-1-default did not. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: daniel.becker(a)quippy.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 858213 --> http://bugzilla.opensuse.org/attachment.cgi?id=858213&action=edit acpidump > acpidump.raw After latest update to kernel 5.17.2-1 today, boot shows ACPI BIOS Errors: Apr 18 13:33:20 ****** kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) Apr 18 13:33:20 ****** kernel: ACPI Error: Aborting method \_SB.PR01._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Apr 18 13:33:20 ****** kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) Apr 18 13:33:20 ****** kernel: ACPI Error: Aborting method \_SB.PR02._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Apr 18 13:33:20 ****** kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) Apr 18 13:33:20 ****** kernel: ACPI Error: Aborting method \_SB.PR03._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Apr 18 13:33:20 ****** kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) Apr 18 13:33:20 ****** kernel: ACPI Error: Aborting method \_SB.PR04._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Apr 18 13:33:20 ****** kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) Apr 18 13:33:20 ****** kernel: ACPI Error: Aborting method \_SB.PR05._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Previous 5.17.1-1-default did not show these. I added "acpidump > acpidump.raw" to this error report. uname -a shows: Linux quippy 5.17.2-1-default #1 SMP PREEMPT Sat Apr 9 06:30:15 UTC 2022 (b49cf22) x86_64 x86_64 x86_64 GNU/Linux Does not seem to be a show stopper, but something changed and could be wrong now so someone might want to look into this. -- You are receiving this mail because: You are the assignee for the bug.

1 28