November 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1217172] Logitech-Keyboard stops working after login
by bugzilla_noreply＠suse.com 17 Nov '23

17 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217172 https://bugzilla.suse.com/show_bug.cgi?id=1217172#c26 --- Comment #26 from Benjamin Brunner <bbrunner(a)suse.com> --- Seems like the naming of the led-class was really the reason. 6.6.1-1.g01080f1 works as well. Thank you very much for your efforts! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217172] Logitech-Keyboard stops working after login
by bugzilla_noreply＠suse.com 17 Nov '23

17 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217172 https://bugzilla.suse.com/show_bug.cgi?id=1217172#c25 --- Comment #25 from Takashi Iwai <tiwai(a)suse.com> --- Created attachment 870817 --> https://bugzilla.suse.com/attachment.cgi?id=870817&action=edit A workaround patch -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217172] Logitech-Keyboard stops working after login
by bugzilla_noreply＠suse.com 17 Nov '23

17 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217172 https://bugzilla.suse.com/show_bug.cgi?id=1217172#c24 --- Comment #24 from Takashi Iwai <tiwai(a)suse.com> --- OK, thanks, now finally I understood what's going on. The problem is that leds class gained the sysfs entry "color" in the commit c7d80059b086c4986cd994a1973ec7a5d75f8eea leds: class: Store the color index in struct led_classdev Meanwhile, hid-lg-g15 driver creates the own sysfs entry "color", and this conflicts with the new standard one in the above. A fix would be to rename either of them. I'm building a test kernel with the rename of the hid-lg-g15's one (from "color" to "kbd_color"), and this should avoid the conflict. Another test kernel with the patch is being built in OBS home:tiwai:bsc1217172-5 repo. Please give it a try later again. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217172] Logitech-Keyboard stops working after login
by bugzilla_noreply＠suse.com 17 Nov '23

17 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217172 https://bugzilla.suse.com/show_bug.cgi?id=1217172#c23 Benjamin Brunner <bbrunner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #870778|0 |1 is obsolete| | Attachment #870780|0 |1 is obsolete| | Attachment #870783|0 |1 is obsolete| | Attachment #870802|0 |1 is obsolete| | --- Comment #23 from Benjamin Brunner <bbrunner(a)suse.com> --- Created attachment 870816 --> https://bugzilla.suse.com/attachment.cgi?id=870816&action=edit hwinfo with working kernel 6.6.1-2.gc9735e0 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217172] Logitech-Keyboard stops working after login
by bugzilla_noreply＠suse.com 17 Nov '23

17 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217172 https://bugzilla.suse.com/show_bug.cgi?id=1217172#c22 Benjamin Brunner <bbrunner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #870777|0 |1 is obsolete| | Attachment #870779|0 |1 is obsolete| | Attachment #870782|0 |1 is obsolete| | Attachment #870801|0 |1 is obsolete| | --- Comment #22 from Benjamin Brunner <bbrunner(a)suse.com> --- Created attachment 870815 --> https://bugzilla.suse.com/attachment.cgi?id=870815&action=edit dmesg with working kernel 6.6.1-2.gc9735e0 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217172] Logitech-Keyboard stops working after login
by bugzilla_noreply＠suse.com 17 Nov '23

17 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217172 https://bugzilla.suse.com/show_bug.cgi?id=1217172#c21 --- Comment #21 from Benjamin Brunner <bbrunner(a)suse.com> --- I just tested 6.6.1-2.gc9735e0 and with ignoring the led class registration error, the keyboard works again! Thank you very much! I'll attach the hwinfo and dmesg of the working kernel and in case this is not the final fix, just let me know and I'll happily give it another test. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1216194] i915 drm: drivers/gpu/drm/drm_vblank.c:1310 drm_wait_one_vblank+0x1cb/0x1f0 (Intermittent complete freezes of the system)
by bugzilla_noreply＠suse.com 17 Nov '23

17 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1216194 https://bugzilla.suse.com/show_bug.cgi?id=1216194#c19 --- Comment #19 from Daniel Westermann <daniel.westermann(a)dbi-services.com> --- Small update: This is still happening from time to time -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217172] Logitech-Keyboard stops working after login
by bugzilla_noreply＠suse.com 16 Nov '23

16 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217172 https://bugzilla.suse.com/show_bug.cgi?id=1217172#c20 --- Comment #20 from Benjamin Brunner <bbrunner(a)suse.com> --- Thanks again for the fast reply. It seems OBS is down at the moment. I'll give it a try tomorrow morning. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217172] Logitech-Keyboard stops working after login
by bugzilla_noreply＠suse.com 16 Nov '23

16 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217172 https://bugzilla.suse.com/show_bug.cgi?id=1217172#c19 --- Comment #19 from Takashi Iwai <tiwai(a)suse.com> --- Hmm, it's puzzling. Then it means that the conflict happens within the same HID device probe? Now I added some debug prints and also let the driver to ignore the led class registration error. Another test kernel is being built in OBS home:tiwai:bsc1217172-4. Let's see. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217083] kernel-firmware (ucode-amd): snapshot 20231108 boot fails
by bugzilla_noreply＠suse.com 16 Nov '23

16 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217083 https://bugzilla.suse.com/show_bug.cgi?id=1217083#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Hm, then it smells really strange. In general, the microcode won't be updated unless it really matches with the CPU (the CPU itself checks). Since this is the only report -- although it should have hit to far more people -- I'm afraid that we're scratching the wrong surface. Could you double-check whether it's really ucode-amd package that really breaks? As mentioned, you can control the ucode loading via a boot option (so you can type in on GRUB menu at boot time). -- You are receiving this mail because: You are the assignee for the bug.

1 0