April 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[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

[Bug 1223083] Kernel:HEAD 6.9rc breaks iwlwifi on Thinkpad T480
by bugzilla_noreply＠suse.com 20 Apr '24

20 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223083 https://bugzilla.suse.com/show_bug.cgi?id=1223083#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |UPSTREAM Status|NEW |RESOLVED --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Thanks for the info! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223083] New: Kernel:HEAD 6.9rc breaks iwlwifi on Thinkpad T480
by bugzilla_noreply＠suse.com 20 Apr '24

20 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223083 Bug ID: 1223083 Summary: Kernel:HEAD 6.9rc breaks iwlwifi on Thinkpad T480 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: seife(a)novell.slipkontur.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I'm running current Tumbleweed on my "new" Thinkpad T480 using iwlwifi. I have both KOTD kernel-default-6.9-rc and Tumbleweed's kernel-vanilla-6.8.x installed, the latter as a way to recover if KOTD breaks :-) Since the first 6.9-rc releases, my WIFI does not work. mixi:~ # uname -a Linux mixi 6.9.0-rc4-2.g4804f5c-default #1 SMP PREEMPT_DYNAMIC Mon Apr 15 08:48:25 UTC 2024 (4804f5c) x86_64 x86_64 x86_64 GNU/Linux mixi:~ # ip link set up dev wlp3s0 RTNETLINK answers: Invalid argument mixi:~ # rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth tpacpi_bluetooth_sw blocked unblocked 1 wlan phy0 unblocked unblocked mixi:~ # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: wlp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 92:df:96:3e:36:0b brd ff:ff:ff:ff:ff:ff permaddr 38:ba:f8:f4:ed:63 3: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 8c:16:45:fc:09:b0 brd ff:ff:ff:ff:ff:ff seife@mixi:~> dmesg|grep iwl [ 9.948811] iwlwifi 0000:03:00.0: Detected crf-id 0xbadcafe, cnv-id 0x10 wfpm id 0x80000000 [ 9.948978] iwlwifi 0000:03:00.0: PCI dev 24fd/0010, rev=0x230, rfid=0xd55555d5 [ 10.187732] iwlwifi 0000:03:00.0: loaded firmware version 36.ca7b901d.0 8265-36.ucode op_mode iwlmvm [ 10.637788] iwlwifi 0000:03:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230 [ 10.701153] iwlwifi 0000:03:00.0: base HW address: 38:ba:f8:f4:ed:63, OTP minor version: 0x4 [ 10.779246] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [ 10.784000] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0 [ 17.419360] iwlwifi 0000:03:00.0: Registered PHC clock: iwlwifi-PTP, with index: 1 The dmesg regarding anything wifi (not only iwlwifi) does not differ from the working 6.8.x kernels, no additional error or missing line or anything. I have no idea how to debug this any further, I would not even know what to report upstream ;-) The Thinkpad T480 should still be in use in high numbers, so I wonder how I can be the only one seeing this issue? hwinfo for the card: 41: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: Mqes.ndpeucax6V1 Parent ID: hAO_.xdVuDfcpKg9 SysFS ID: /class/net/wlp3s0 SysFS Device Link: /devices/pci0000:00/0000:00:1c.6/0000:03:00.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "iwlwifi" Driver Modules: "iwlwifi" Device File: wlp3s0 HW Address: 92:df:96:3e:36:0b Permanent HW Address: 38:ba:f8:f4:ed:63 Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #1 (Ethernet controller) -- You are receiving this mail because: You are the assignee for the bug.

1 2