April 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1193599] intel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
by bugzilla_noreply＠suse.com 29 Apr '24

29 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1193599 https://bugzilla.suse.com/show_bug.cgi?id=1193599#c49 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(opendreas(a)gmail.c | |om) | --- Comment #49 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Andreas from comment #44) > > I'm building a test kernel for SLE15-SP6 in OBS home:tiwai:bsc1193599-sp6 > > repo. > > The package will appear later at > > http://download.opensuse.org/repositories/home:/tiwai:/bsc1193599-sp6/pool/ > > > > Please give it a try later. > The patch works, the errors have disappeared. OK, now I pushed those two patches to SLE15-SP6 branch, so that they'll be included in the Leap 15.6 update kernel. (They'll be missing in the installer kernel, though.) If any other crashes happen even with those patches, they are basically different issues, and better to be tracked in other bug reports. Please open another report in such a case. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1221607] New: Slowroll keeps reinstalling kernel and virtualbox on every zypper dup
by bugzilla_noreply＠suse.com 29 Apr '24

29 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221607 Bug ID: 1221607 Summary: Slowroll keeps reinstalling kernel and virtualbox on every zypper dup 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: llrainey15(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- zypper dup keeps installing the same 2 entries over and over slowroll:~ # zypper ref ; zypper -n dup Repository 'base-non-oss' is up to date. Repository 'base-oss' is up to date. Repository 'h264' is up to date. Repository 'packman' is up to date. Repository 'update' is up to date. All repositories have been refreshed. 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 2 NEW packages are going to be installed: kernel-default-6.7.4-1.1 virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1 The following package requires a system reboot: kernel-default-6.7.4-1.1 2 new packages to install. Overall download size: 166.3 MiB. Already cached: 0 B. After the operation, additional 242.7 MiB will be used. Note: System reboot required. Continue? [y/n/v/...? shows all options] (y): y Retrieving: kernel-default-6.7.4-1.1.x86_64 (base-oss) (1/2), 165.8 MiB Retrieving: kernel-default-6.7.4-1.1.x86_64.rpm .............[done (39.2 MiB/s)] Retrieving: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64 (base-oss) (2/2), 546.5 KiB Retrieving: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64.[done (1.9 MiB/s)] Checking for file conflicts: .............................................[done] dracut[I]: Executing: /usr/bin/dracut -f /boot/initrd-6.7.4-1-default 6.7.4-1-default Lines delete dracut[I]: *** Creating initramfs image file '/boot/initrd-6.7.4-1-default' done *** CA enrolled. Skip /etc/uefi/certs/1F673297.crt (1/2) Installing: kernel-default-6.7.4-1.1.x86_64 ........................[done] (2/2) Installing: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64 ......[done] Running post-transaction scripts .........................................[done] 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... Nothing to do. Mon Mar 18 07:15:26 CDT 2024 slowroll:~ # Broadcast message from root@slowroll on pts/5 (Mon 2024-03-18 07:16:41 CDT): The system will reboot now! Connection to llr2 closed by remote host. Connection to llr2 closed. llrainey@LLR2:~> t2x 06 Last login: Sun Mar 17 06:43:50 CDT 2024 from 10.0.2.2 on ssh Have a lot of fun... slowroll:~ # zypper ref ; zypper -n dup Repository 'base-non-oss' is up to date. Repository 'base-oss' is up to date. Repository 'h264' is up to date. Repository 'packman' is up to date. Repository 'update' is up to date. All repositories have been refreshed. 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 2 NEW packages are going to be installed: kernel-default-6.7.4-1.1 virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1 The following package requires a system reboot: kernel-default-6.7.4-1.1 2 new packages to install. Overall download size: 166.3 MiB. Already cached: 0 B. After the operation, additional 242.7 MiB will be used. Note: System reboot required. Continue? [y/n/v/...? shows all options] (y): y Retrieving: kernel-default-6.7.4-1.1.x86_64 (base-oss) (1/2), 165.8 MiB Retrieving: kernel-default-6.7.4-1.1.x86_64.rpm .............[done (39.2 MiB/s)] Retrieving: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64 (base-oss) (2/2), 546.5 KiB Retrieving: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64.[done (1.9 MiB/s)] Checking for file conflicts: .............................................[done] dracut[I]: Executing: /usr/bin/dracut -f /boot/initrd-6.7.4-1-default 6.7.4-1-default Lines delete dracut[I]: *** Creating initramfs image file '/boot/initrd-6.7.4-1-default' done *** CA enrolled. Skip /etc/uefi/certs/1F673297.crt (1/2) Installing: kernel-default-6.7.4-1.1.x86_64 ........................[done] (2/2) Installing: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64 ......[done] Running post-transaction scripts .........................................[done] 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... Nothing to do. Mon Mar 18 07:15:26 CDT 2024 slowroll:~ # Broadcast message from root@slowroll on pts/5 (Mon 2024-03-18 07:16:41 CDT): The system will reboot now! Connection to llr2 closed by remote host. Connection to llr2 closed. llrainey@LLR2:~> t2x 06 Last login: Mon Mar 18 07:14:23 CDT 2024 from 10.0.2.2 on ssh Have a lot of fun... slowroll:~ # zypper ref ; zypper -n dup Repository 'base-non-oss' is up to date. Repository 'base-oss' is up to date. Repository 'h264' is up to date. Repository 'packman' is up to date. Repository 'update' is up to date. All repositories have been refreshed. 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 2 NEW packages are going to be installed: kernel-default-6.7.4-1.1 virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1 The following package requires a system reboot: kernel-default-6.7.4-1.1 2 new packages to install. Overall download size: 166.3 MiB. Already cached: 0 B. After the operation, additional 242.7 MiB will be used. Note: System reboot required. Continue? [y/n/v/...? shows all options] (y): y Retrieving: kernel-default-6.7.4-1.1.x86_64 (base-oss) (1/2), 165.8 MiB Retrieving: kernel-default-6.7.4-1.1.x86_64.rpm .............[done (30.6 MiB/s)] Retrieving: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64 (base-oss) (2/2), 546.5 KiB Retrieving: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64.[done (2.1 MiB/s)] Checking for file conflicts: .............................................[done] dracut[I]: Executing: /usr/bin/dracut -f /boot/initrd-6.7.4-1-default 6.7.4-1-default Lines Delete dracut[I]: *** Creating initramfs image file '/boot/initrd-6.7.4-1-default' done *** CA enrolled. Skip /etc/uefi/certs/1F673297.crt (1/2) Installing: kernel-default-6.7.4-1.1.x86_64 ........................[done] (2/2) Installing: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64 ......[done] Running post-transaction scripts .........................................[done] 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... Nothing to do. Mon Mar 18 07:18:32 CDT 2024 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1222756] New: Bluetooth: auto-connected devices are not shown as connected
by bugzilla_noreply＠suse.com 27 Apr '24

27 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222756 Bug ID: 1222756 Summary: Bluetooth: auto-connected devices are not shown as connected 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: i(a)guoyunhe.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When a paired Bluetooth headset was auto-connected, the device works but system tray and bluetoothctl are not showing it as connected: bluetoothctl info 64:68:76:1C:E3:67 Device 64:68:76:1C:E3:67 (public) Name: 漫步者•花再 Free Pro Alias: 漫步者•花再 Free Pro Class: 0x00240404 (2360324) Icon: audio-headset Paired: yes Bonded: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: SDP (00000001-0000-1000-8000-00805f9b34fb) UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Cont.. (0000110f-0000-1000-8000-00805f9b34fb) UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb) UUID: Generic Audio (00001203-0000-1000-8000-00805f9b34fb) UUID: Vendor specific (66666666-6666-6666-6666-666666666666) UUID: Vendor specific (edf00000-edfe-dfed-fedf-edfedfedfedf) Battery Percentage: 0x32 (50) -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1222946] New: raise default inotify instance limit
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222946 Bug ID: 1222946 Summary: raise default inotify instance limit Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: obs(a)akr.yagii.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- especially when running Unison, I quite often experienced the following error: `Fatal error: exception Unix.Unix_error(Unix.EBADF, "set_nonblock", "")` Running "strace unison-fsmonitor" yielded: ``` fcntl(0, F_GETFL) = 0x802 (flags O_RDWR|O_NONBLOCK) fcntl(0, F_SETFL, O_RDWR|O_NONBLOCK) = 0 fcntl(1, F_GETFL) = 0x802 (flags O_RDWR|O_NONBLOCK) fcntl(1, F_SETFL, O_RDWR|O_NONBLOCK) = 0 inotify_init() = -1 EMFILE (Too many open files) fcntl(-1, F_GETFL) = -1 EBADF (Bad file descriptor) write(2, "Fatal error: exception Unix.Unix"..., 71Fatal error: exception Unix.Unix_error(Unix.EBADF, "set_nonblock", "")) = 71 exit_group(2) = ? +++ exited with 2 +++ ``` Sometimes closing open IDEs or Firefox has helped, but the culprit seems to be the standard value of fs.inotify.max_user_instances = 128 After doubling the number, I was able to use Unison, again. Others have observed this issue, too: https://intellij-support.jetbrains.com/hc/en-us/articles/15268110231826-Ino… ---quote For an intelligent IDE, it is essential to be in the know about any external changes in files it working with - e.g. changes made by VCS, or build tools, or code generators, etc. For that reason, the IntelliJ platform spins a background process to monitor such changes. The method it uses is platform-specific, and on Linux, it is the Inotify facility. Before operating, inotify requires an "instance" to be initialized. While the default per-user limit of instances used to be high enough, a growing number of programs that also use inotify may lead to instance shortage - in which case file watcher will be unable to start. If this is the case, the limit may be temporarily increased by the following command: sudo sh -c "echo 256 > /proc/sys/fs/inotify/max_user_instances" Don't forget to restart the IDE afterward. ---quote My workaround at present is: `sysctl -w fs.inotify.max_user_instances=256 >> /etc/sysctl.d/unison.conf` This is also documented at https://github.com/bcpierce00/unison/issues/1019 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1222946] raise default inotify instance limit
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222946 https://bugzilla.suse.com/show_bug.cgi?id=1222946#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- The default value is hardcoded to 128 even in the latest upstream code, and I see no big gain to have an extra kernel config for defining it when an easy tuning knob with sysctl is already present. I bet the suggestion to the upstream would be declined by that reason, too. You can statically set the value in /etc/sysctl.d/* instead. e.g. unison package may contain such a sysctl snippet. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223164] New: Unplugging charger while in s2idle sleep causes laptop to stop responding
by bugzilla_noreply＠suse.com 21 Apr '24

21 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223164 Bug ID: 1223164 Summary: Unplugging charger while in s2idle sleep causes laptop to stop responding 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: misawalach00(a)seznam.cz QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Specs: Laptop Model: Lenovo Ideapad 5 PRO 14ARH7 CPU: Ryzen 7 6800HS Creator Edition GPU: Integrated: AMD Radeon 680M RAM: 16 GB Wifi Card: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter Storage: 1TB M.2 NVME WD PC SN810 SDCPNRY-1T00-1101 This laptop supports s2idle sleep only. When the laptop is in sleep mode, everything works properly, there is almost no battery drain. However, when I plug in or unplug my charger, the laptop will no longer responds to any inputs and can no longer be woken up. The keyboard backlight briefly flashes and the laptop starts producing heat and the only way to get out of sleep mode is to hold the power button for 5 seconds to forcefully shut it down. Alt + Sysrq + b does nothing. I have tried setting TLP_ENABLE=0 and rebooting. That does not seem to help. The only thing that changes is that now the fans spin up once the laptop gets stuck and the keyboard backlight no longer flashes. There are no errors present in journalctl -b -1 after rebooting. The last message is that the laptop successfully entered s2idle sleep mode. I have tried the Live environment of a different distribution according to a few tips online. Fedora 39 live environment does not have this issue. Either this bug is specific to this distribution or I messed something up with my installation. I could not figure out what could cause this. This issue is present on kernel versions 6.5, 6.6, 6.7 and 6.8. I haven't tried any other versions. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1222917] [Kernel Bug] Wrong bluetooth connection status in KDE Applet
by bugzilla_noreply＠suse.com 21 Apr '24

21 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222917 https://bugzilla.suse.com/show_bug.cgi?id=1222917#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Flags|needinfo?(egor.kuznetsov.26 | |(a)gmail.com) | Resolution|--- |FIXED --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- OK, let's close now :) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222917] New: [Kernel Bug] Wrong bluetooth connection status in KDE Applet
by bugzilla_noreply＠suse.com 21 Apr '24

21 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222917 Bug ID: 1222917 Summary: [Kernel Bug] Wrong bluetooth connection status in KDE Applet 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: egor.kuznetsov.26(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Summary: After some kernel updates (seems from 6.8.2) bluetooth connection in KDE applet shows wrong status. If device connected, it works, but applet show, that device disconnected. Possible fix: I research kernel bugzilla and found this bug https://bugzilla.kernel.org/show_bug.cgi?id=218680 and see that patch was created, but at this moment it is not in upstream kernel branches. Can openSUSE kernel maintainers apply patch from Bagas Sanjaya (https://lore.kernel.org/all/20240404185022.1.Ic27505c8f1ca7d4a653b1dcc1b08c…) to openSUSE kernel? Thanks in advance for the answer! -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1220814] New: kernel 6.7.6-1-default Oops: unable to handle page faults and workqueue lockup (udev related?)
by bugzilla_noreply＠suse.com 21 Apr '24

21 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1220814 Bug ID: 1220814 Summary: kernel 6.7.6-1-default Oops: unable to handle page faults and workqueue lockup (udev related?) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: michael.burge77(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873182 --> https://bugzilla.suse.com/attachment.cgi?id=873182&action=edit full journalctl of the third crash I have an old portable with a wonky dc power jack which tends to generate a few quick AC0<->BAT0 events in succession. Starting with kernel 6.7.6-1-default the system locks up. Log is full of ``` Mar 01 17:34:02 ost (udev-worker)[23694]: AC0: Process '/usr/sbin/tlp auto' terminated by signal KILL. Mar 01 17:34:02 ost (udev-worker)[23694]: AC0: Failed to wait for spawned command '/usr/sbin/tlp auto': Input/output error Mar 01 17:34:02 ost (udev-worker)[23694]: AC0: Failed to execute '/usr/sbin/tlp auto', ignoring: Input/output error Mar 01 17:34:17 ost (udev-worker)[24044]: AC0: Process '/usr/sbin/tlp auto' terminated by signal KILL. Mar 01 17:34:17 ost (udev-worker)[24044]: AC0: Failed to wait for spawned command '/usr/sbin/tlp auto': Input/output error Mar 01 17:34:17 ost (udev-worker)[24044]: AC0: Failed to execute '/usr/sbin/tlp auto', ignoring: Input/output error Mar 01 17:34:17 ost plasmashell[2682]: plasma-pk-updates: acPluggedChanged onBattery: false -> true Mar 01 17:34:17 ost kernel: BUG: unable to handle page fault for address: 0000000000007b8a Mar 01 17:34:17 ost kernel: #PF: supervisor read access in kernel mode Mar 01 17:34:17 ost kernel: #PF: error_code(0x0000) - not-present page ``` until it locks up with ``` Mar 01 18:11:29 ost kernel: note: kworker/11:5[23457] exited with irqs disabled Mar 01 18:11:50 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:11:54 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:11:55 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:11:58 ost plasmashell[5912]: [5912:0301/181158.744595:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer. Mar 01 18:12:05 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:12:06 ost kernel: BUG: workqueue lockup - pool cpus=11 node=0 flags=0x0 nice=0 stuck for 37s! ``` at which point only holding down the power button works. -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 1222756] Bluetooth: auto-connected devices are not shown as connected
by bugzilla_noreply＠suse.com 20 Apr '24

20 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222756 https://bugzilla.suse.com/show_bug.cgi?id=1222756#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |i(a)guoyunhe.me, | |tiwai(a)suse.com Flags| |needinfo?(i(a)guoyunhe.me) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you try the latest 6.8.x kernel in OBS Kernel:stable repo? http://download.opensuse.org/repositories/Kernel:/stable/standard/ A possible fix has been already included in 6.8.7. -- You are receiving this mail because: You are the assignee for the bug.

1 0