October 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1204160] New: Screen freezes after waking from hibernation with kernel 6.0 and amdgpu
by bugzilla_noreply＠suse.com 09 Oct '22

09 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204160 Bug ID: 1204160 Summary: Screen freezes after waking from hibernation with kernel 6.0 and amdgpu Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 URL: https://gitlab.freedesktop.org/drm/amd/-/issues/2164 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fkrueger(a)mailbox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since upgrading to kernel 6.0 (via kernel:stable repo) the machine (AMD Ryzen 7 PRO 4750U) does not resume completely after hibernation and returns a black screen. Switching to tty works. Kernel 5.19.X just works fine. The issue might be releated to the following error messages: Oct 09 08:26:22 kernel: amdgpu: Move buffer fallback to memcpy unavailable Oct 09 08:26:22 kernel: amdgpu 0000:07:00.0: amdgpu: 000000008818ffe0 pin failed Oct 09 08:26:22 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -19 This might be related to https://gitlab.freedesktop.org/drm/amd/-/issues/2164. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204155] New: Unable to login into any virtual console second appearing
by bugzilla_noreply＠suse.com 08 Oct '22

08 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204155 Bug ID: 1204155 Summary: Unable to login into any virtual console second appearing 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: gnallgo(a)mailbox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0 Build Identifier: I got the same bug as here: https://bugzilla.opensuse.org/show_bug.cgi?id=1120391 the thread: https://forums.opensuse.org/showthread.php/534256-Unable-to-login-to-text-t… giving user password on tty 01 to 06 ends with no chance to give the password and the message apperars three times: Login incorrect. After that ther is the login promt again. course of events: He comes with kernel (or update) 5.19.12.xxx to which tumbleweed updated on october the 4th. Update on 05.10. with Kernel 5.19.13.xxx brings no luck. Exact the bug as descriped here in the thread. But the best is: Updating on 06.10.22 to Kernel 6.0.0.1 broke the automatic login i had and i got a tty01 on screen with our bug. System not accesable. actual system after rollback: Operating System: openSUSE Tumbleweed 20221003 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.13-1-default (64-bit) Graphics Platform: X11 Processors: 24 � AMD Ryzen Threadripper 2920X 12-Core Processor Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce GT 1030/PCIe/SSE2 Reproducible: Always Steps to Reproduce: 1. on boot 2. on reeboot 3. on ctrl-alt-F1 to F6 Actual Results: giving user password on tty 01 to 06 ends with no chance to give the password and the message apperars three times: Login incorrect. After that ther is the login promt again. Expected Results: able to give password after username and logging in. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204143] New: Nvidia G06 drivers fail to build against kernel 6.0.0
by bugzilla_noreply＠suse.com 07 Oct '22

07 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204143 Bug ID: 1204143 Summary: Nvidia G06 drivers fail to build against kernel 6.0.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: brunopitrus(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrade to kernel-default 6.0.0-1.2, the nvidia-gfxG06-kmp-default kernel modules version 515.65.01_k5.18.15_1 fail to rebuild: CC [M] /usr/src/kernel-modules/nvidia-515.65.01-default/nvidia-drm/nvidia-drm-helper.o /usr/src/kernel-modules/nvidia-515.65.01-default/nvidia-drm/nvidia-drm-helper.c: In function ��__nv_drm_framebuffer_put��: /usr/src/kernel-modules/nvidia-515.65.01-default/nvidia-drm/nvidia-drm-helper.c:47:5: error: implicit declaration of function ��drm_framebuffer_put�� [-Werror=implicit-function-declaration] 47 | drm_framebuffer_put(fb); | ^~~~~~~~~~~~~~~~~~~ cc1: some warnings being treated as errors -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1200716] New: occasional "xHCI host controller not responding, assume dead' with Thunderbolt dock
by bugzilla_noreply＠suse.com 07 Oct '22

07 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200716 Bug ID: 1200716 Summary: occasional "xHCI host controller not responding, assume dead' with Thunderbolt dock 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: pujos.michael(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have a laptop with a TB2 dock connected via TB3 using the TB3->TB2 Apple adapter. It worked fine for a while but since a few kernels, the USB hub of the dock get (seemingly) randomly disconnected: [ 8524.631011] xhci_hcd 0000:09:00.0: xHCI host controller not responding, assume dead [ 8524.631039] xhci_hcd 0000:09:00.0: HC died; cleaning up [ 8524.631076] usb 3-4: 1:0: usb_set_interface failed (-110) [ 8524.631087] usb 3-4: Not enough bandwidth for altsetting 1 [ 8524.631093] usb 3-4: 1:1: usb_set_interface failed (-19) [ 8524.631101] usb 3-4: Not enough bandwidth for altsetting 0 [ 8524.631107] usb 3-4: 1:0: usb_set_interface failed (-19) [ 8524.631213] usb 3-4: Not enough bandwidth for altsetting 0 [ 8524.631220] usb 3-4: 1:0: usb_set_interface failed (-19) [ 8524.631226] usb 3-4: Not enough bandwidth for altsetting 1 [ 8524.631231] usb 3-4: 1:1: usb_set_interface failed (-19) [ 8524.631238] usb 3-4: Not enough bandwidth for altsetting 0 [ 8524.631243] usb 3-4: 1:0: usb_set_interface failed (-19) [ 8524.631294] usb 3-4: Not enough bandwidth for altsetting 0 [ 8524.631300] usb 3-4: 1:0: usb_set_interface failed (-19) [ 8524.631306] usb 3-4: Not enough bandwidth for altsetting 1 [ 8524.631311] usb 3-4: 1:1: usb_set_interface failed (-19) [ 8524.631317] usb 3-4: Not enough bandwidth for altsetting 0 [ 8524.631323] usb 3-4: 1:0: usb_set_interface failed (-19) [ 8524.631358] usb 3-4: Not enough bandwidth for altsetting 0 [ 8524.631364] usb 3-4: 1:0: usb_set_interface failed (-19) [ 8524.631370] usb 3-4: Not enough bandwidth for altsetting 1 [ 8524.631376] usb 3-4: 1:1: usb_set_interface failed (-19) [ 8524.631382] usb 3-4: Not enough bandwidth for altsetting 0 [ 8524.631387] usb 3-4: 1:0: usb_set_interface failed (-19) [ 8524.631430] usb 3-4: Not enough bandwidth for altsetting 0 [ 8524.631436] usb 3-4: 1:0: usb_set_interface failed (-19) [ 8524.631442] usb 3-4: Not enough bandwidth for altsetting 1 [ 8524.631447] usb 3-4: 1:1: usb_set_interface failed (-19) [ 8524.631453] usb 3-4: Not enough bandwidth for altsetting 0 [ 8524.631458] usb 3-4: 1:0: usb_set_interface failed (-19) [ 8524.631639] usb 3-4: USB disconnect, device number 2 The disconnections does not happen very frequently, but when it happens it is annoying as I usually have my keyboard connected to it and use its USB audio output. It also has a DisportPort port to which my external monitor is attached, but it is not affected. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1186729] Hibernation stopped working after update 04 May 2020
by bugzilla_noreply＠suse.com 07 Oct '22

07 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1186729 https://bugzilla.suse.com/show_bug.cgi?id=1186729#c5 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |NORESPONSE --- Comment #5 from Jiri Slaby <jslaby(a)suse.com> --- If you provide the data requested, feel free to reopen. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200716] occasional "xHCI host controller not responding, assume dead' with Thunderbolt dock
by bugzilla_noreply＠suse.com 07 Oct '22

07 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1200716 https://bugzilla.suse.com/show_bug.cgi?id=1200716#c3 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pujos.michael(a)gmail.com Flags| |needinfo?(pujos.michael@gma | |il.com) --- Comment #3 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Michael Pujos from comment #0) > [ 8524.631458] usb 3-4: 1:0: usb_set_interface failed (-19) > [ 8524.631639] usb 3-4: USB disconnect, device number 2 Can you identify (from the logs) when this started to happen? Something like grep -E 'Linux.version|usb_set_interface failed' run on the logs. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200716] occasional "xHCI host controller not responding, assume dead' with Thunderbolt dock
by bugzilla_noreply＠suse.com 07 Oct '22

07 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1200716 https://bugzilla.suse.com/show_bug.cgi?id=1200716#c2 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #2 from Jiri Slaby <jslaby(a)suse.com> --- I agree this was broken recently -- I myself saw it too. But I was never able to identify the source of the problem. It happens for me too rarely. Does this happen with 6.0? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202571] kernel 5.19.1 shuts down after waking from suspend
by bugzilla_noreply＠suse.com 06 Oct '22

06 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1202571 https://bugzilla.suse.com/show_bug.cgi?id=1202571#c5 --- Comment #5 from Tristan Miller <psychonaut(a)nothingisreal.com> --- (In reply to Takashi Iwai from comment #4) > TW is already moving to 6.0, and the fix for 5.19 won't be handled any > longer. > Could try 6.0 and verify whether the issue persists or not? > > If yes, we need to report it to the upstream somehow. OK, I tried kernel-default-6.0.0-2.1.g1195759.x86_64 from the Kernel:stable repository. With this kernel, I cannot reproduce the problem. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203968] Kernel 5.14.21.15400.24.21.2 long time to boot " a start job..." and udev fails
by bugzilla_noreply＠suse.com 06 Oct '22

06 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1203968 https://bugzilla.suse.com/show_bug.cgi?id=1203968#c2 Richard Farthing <rf(a)keynet-technology.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #2 from Richard Farthing <rf(a)keynet-technology.com> --- Latest kernel was OK. However I then reverted to test with 5.14.21.15400.24.21.2 again, and now that is also working as expected, after using earlier kernel 5.14.21.15400.22.1 for a few days with autoupdates etc. Something must have has changed, so I think this is no longer traceable - I closed it -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204064] bluetooth,connecting a smartphone (bt 4.2) and the PC (bt 5.3), we get only HSP not A2DP
by bugzilla_noreply＠suse.com 06 Oct '22

06 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204064 http://bugzilla.opensuse.org/show_bug.cgi?id=1204064#c6 --- Comment #6 from Episteme PROMENEUR <epistemepromeneur(a)free.fr> --- Sorry, accessing to the folder tree works well. So, there is only a problem with the protocols HSP and A2DP. -- You are receiving this mail because: You are the assignee for the bug.

1 0