April 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[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 1221504] New: bluetooth errors on every kernel starting
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221504 Bug ID: 1221504 Summary: bluetooth errors on every kernel starting Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opendreas(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have a Dell Precision 7530 with Intel Wireless-AC 9260 Bluetooth Adapter and kernel 6.4.0-150600.9.2. Errors constantly appear when booting the system, but bluetooth works with my headphones, although there are some audio artifacts at the beginning when playing sound. Mär 16 17:49:38 precision bluetoothd[1073]: Bluetooth daemon 5.71 Mär 16 17:49:38 precision bluetoothd[1073]: Starting SDP server Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support csip plugin Mär 16 17:49:38 precision bluetoothd[1073]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support micp plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support vcp plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support mcp plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support bass plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support bap plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support admin plugin Mär 16 17:49:38 precision bluetoothd[1073]: Bluetooth management interface 1.22 initialized Mär 16 17:49:38 precision dbus-daemon[1074]: [system] Activating systemd to hand-off: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1' (uid=0 pid=1073 comm="/usr/lib/bluetooth/bluetoothd ") Mär 16 17:49:38 precision bluetoothd[1073]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Battery Provider Manager created Mär 16 17:49:38 precision bluetoothd[1073]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution Mär 16 17:49:38 precision bluetoothd[1073]: Failed to clear UUIDs: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Too small Add Device complete event Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision (smartd)[1105]: smartd.service: Referenced but unset environment variable evaluates to an empty string: smartd_opts Looks like this is the error https://bugzilla.kernel.org/show_bug.cgi?id=217651 Here's a fix https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.gi… -- You are receiving this mail because: You are the assignee for the bug.

1 21

[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

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

20 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222917 https://bugzilla.suse.com/show_bug.cgi?id=1222917#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(egor.kuznetsov.26 | |(a)gmail.com) CC| |egor.kuznetsov.26(a)gmail.com | |, tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- The fix is already contained in 6.8.7 kernel. Could you try the latest one in OBS Kernel:stable repo? http://download.opensuse.org/repositories/Kernel:/stable/standard/ -- You are receiving this mail because: You are the assignee for the bug.

1 0