January 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1165047] CD tray closed immediately after ejecting media
by bugzilla_noreply＠suse.com 04 Jan '22

04 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1165047 http://bugzilla.opensuse.org/show_bug.cgi?id=1165047#c18 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Basesystem Version|Leap 15.1 |Leap 15.4 Assignee|kernel-bugs(a)opensuse.org |martin.wilck(a)suse.com --- Comment #18 from Michal Suchanek <msuchanek(a)suse.com> --- https://github.com/openSUSE/suse-module-tools/pull/58 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1165047] CD tray closed immediately after ejecting media
by bugzilla_noreply＠suse.com 04 Jan '22

04 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1165047 http://bugzilla.opensuse.org/show_bug.cgi?id=1165047#c17 --- Comment #17 from Michal Suchanek <msuchanek(a)suse.com> --- You should be able to fix with echo options cdrom autoclose=0 > /etc/modprobe.d/cdrom.conf dracut -f -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1132926] Intel i915 graphics driver issues with external monitor when laptop in docking station
by bugzilla_noreply＠suse.com 04 Jan '22

04 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1132926 https://bugzilla.suse.com/show_bug.cgi?id=1132926#c40 Miroslav Bene�� <mbenes(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrik.jakobsson(a)suse.com --- Comment #40 from Miroslav Bene�� <mbenes(a)suse.com> --- Ok, thanks for the update. Could you also try the latest kernel from Kernel:HEAD repo? It contains 5.16-rc8 now with the latest drm-tip branch and you could share the results in the upstream bug report. I am afraid we cannot help much besides that. Patrik might have an idea. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193822] bluetooth disabled - unable to enable bluetooth after latest update
by bugzilla_noreply＠suse.com 04 Jan '22

04 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1193822 https://bugzilla.suse.com/show_bug.cgi?id=1193822#c3 --- Comment #3 from Pieter Burm <pieter(a)burmstuer.com> --- issue fixed itself after the latest updates from last week. sorry i kind of forgot i logged a case here. (wont happen again) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1132926] Intel i915 graphics driver issues with external monitor when laptop in docking station
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1132926 https://bugzilla.suse.com/show_bug.cgi?id=1132926#c39 --- Comment #39 from Otrebor Igorig <otrebor(a)hispeed.ch> --- I now have upgraded the system to Leap 15.3 with Kernel 5.3.18-59.37-default. The behavior is different now. Better from a users perspective, but still not where I would expect it to be. I'm now able to initialize the external monitor and get it to work. However, this only works in a usable manner, when making the monitor a display mirror of the internal one with the very same resolution in place (1920x1080). Using any other resolution or making the external monitor a virtual screen extension does not work in any usable way. Also, the KDE screen config utility gets confused about the state of the monitor. When it *is* working, it reports it as disabled and vice versa. So, I need multiple attempts when activating it, to use it as a mirrored screen in the end. So I'm only doing it when I *really* do need it, which is less now as it used to be. I've also guessed, that it may have something to do, that the graphics chipset is rather old by now. But occasionally the monitor is able to display its full 4k resolution with the internal one being at 1920x1080, rarely though. btw. I've changed employer in the meantime. They handed me a MacBook Pro which is using the same monitor via a USB bridge and HDMI. The monitor works as expected. So it really *is* a driver issue. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193947] AMDGPU crash again
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1193947 https://bugzilla.suse.com/show_bug.cgi?id=1193947#c3 --- Comment #3 from Frans de Boer <frans(a)fransdb.nl> --- (In reply to Takashi Iwai from comment #2) > The test kernel package is being built in OBS home:tiwai:bsc1193947 repo. > It'll be available later (after an hour or so) at > http://download.opensuse.org/repositories/home:/tiwai:/bsc1193947/standard/ > > Please give it a try later. I did try the patch kernel as asked. Negative result, see log listing: Jan 3 20:34:43 pws1 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=28943, emitted seq=28945 Jan 3 20:34:43 pws1 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process kscreenlocker_g pid 3770 thread kscreenloc:cs0 pid 3773 Jan 3 20:34:43 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin! Jan 3 20:34:47 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: Failed to disable gfxoff! Jan 3 20:34:47 pws1 kernel: [drm] REG_WAIT timeout 1us * 100000 tries - mpc2_assert_idle_mpcc line:479 Jan 3 20:34:52 pws1 kernel: [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3 Jan 3 20:35:00 pws1 kernel: amdgpu 0000:03:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) Jan 3 20:35:00 pws1 kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KGQ disable failed Jan 3 20:35:01 pws1 kernel: amdgpu 0000:03:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) Jan 3 20:35:01 pws1 kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed Jan 3 20:35:01 pws1 kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx Jan 3 20:35:04 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: SMU: I'm not done with your previous command! Jan 3 20:35:04 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: Failed to disable smu features. Jan 3 20:35:04 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: Fail to disable dpm features! Jan 3 20:35:04 pws1 kernel: [drm:amdgpu_device_ip_suspend_phase2 [amdgpu]] *ERROR* suspend of IP block <smu> failed -62 Jan 3 20:35:04 pws1 kernel: [drm] free PSP TMR buffer Jan 3 20:35:05 pws1 kernel: [drm] psp gfx command DESTROY_TMR(0x7) failed and response status is (0x80000306) Jan 3 20:35:05 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: MODE1 reset Jan 3 20:35:05 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset Jan 3 20:35:05 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset Jan 3 20:35:09 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: SMU: I'm not done with your previous command! Jan 3 20:35:09 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset failed Jan 3 20:35:09 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: ASIC reset failed with error, -62 for drm dev, 0000:03:00.0 Jan 3 20:35:19 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume Jan 3 20:35:19 pws1 kernel: [drm] PCIE GART of 512M enabled (table at 0x00000080005A4000). Jan 3 20:35:19 pws1 kernel: [drm] VRAM is lost due to GPU reset! Jan 3 20:35:19 pws1 kernel: [drm] PSP is resuming... Jan 3 20:35:20 pws1 kernel: [drm] failed to load ucode SMC(0x18) Jan 3 20:35:20 pws1 kernel: [drm] psp gfx command LOAD_IP_FW(0x6) failed and response status is (0x80000306) Jan 3 20:35:20 pws1 kernel: [drm] reserve 0xa00000 from 0x81fe000000 for PSP TMR Jan 3 20:35:22 pws1 kernel: [drm] psp gfx command AUTOLOAD_RLC(0x21) failed and response status is (0x0) Jan 3 20:35:22 pws1 kernel: [drm:psp_load_non_psp_fw [amdgpu]] *ERROR* Failed to start rlc autoload Jan 3 20:35:22 pws1 kernel: [drm:psp_resume [amdgpu]] *ERROR* PSP resume failed Jan 3 20:35:22 pws1 kernel: [drm:amdgpu_device_fw_loading [amdgpu]] *ERROR* resume of IP block <psp> failed -22 Jan 3 20:35:22 pws1 kernel: [drm] Skip scheduling IBs! Jan 3 20:35:23 pws1 kernel[1602]: Last message '[drm] Skip schedulin' repeated 1 times, suppressed by syslog-ng on pws1.fransdb.local Jan 3 20:35:22 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset(2) failed Jan 3 20:35:22 pws1 kernel: [drm] Skip scheduling IBs! Jan 3 20:35:23 pws1 kernel[1602]: Last message '[drm] Skip schedulin' repeated 5 times, suppressed by syslog-ng on pws1.fransdb.local Jan 3 20:35:22 pws1 kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Jan 3 20:35:23 pws1 kernel[1602]: Last message '[drm:amdgpu_cs_ioctl' repeated 3 times, suppressed by syslog-ng on pws1.fransdb.local Jan 3 20:35:22 pws1 kernel: snd_hda_intel 0000:03:00.1: refused to change power state from D3hot to D0 Jan 3 20:35:23 pws1 kernel: snd_hda_intel 0000:03:00.1: CORB reset timeout#2, CORBRP = 65535 Jan 3 20:35:23 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset end with ret = -22 Jan 3 20:35:33 pws1 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=1870, emitted seq=1872 Jan 3 20:35:33 pws1 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 Jan 3 20:35:33 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin! Jan 3 20:35:33 pws1 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=1369, emitted seq=1371 Jan 3 20:35:33 pws1 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 Jan 3 20:35:33 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin! Jan 3 20:35:33 pws1 kernel: amdgpu 0000:03:00.0: amdgpu: Bailing on TDR for s_job:524, as another already in progress ---------------------- So far with 5.16-rc8 no issues. Have not tried rc7, but rc6 failed also. rc4 and rc5 where fine. Continue testing with rc8. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193822] bluetooth disabled - unable to enable bluetooth after latest update
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1193822 https://bugzilla.suse.com/show_bug.cgi?id=1193822#c2 --- Comment #2 from Lars Marowsky-Bree <lmb(a)suse.com> --- Pieter, do you also see # systemctl status bluetooth.service ... > Jan 03 20:40:41 XXXXX bluetoothd[29605]: Failed to set mode: Failed (0x03) and # bluetoothctl show Controller 00:00:00:00:XX:XX (public) Name: XXXX Alias: XXXX Class: 0x00000000 Powered: no Discoverable: no DiscoverableTimeout: 0x000000b4 Pairable: yes that it's not powered on? I've also noticed that just now, but it's too late for me to try a kernel downgrade; I'll play experiment with that tomorrow. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193817] Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1193817 https://bugzilla.suse.com/show_bug.cgi?id=1193817#c5 --- Comment #5 from Ettore Atalan <atalanttore(a)googlemail.com> --- Created attachment 854919 --> https://bugzilla.suse.com/attachment.cgi?id=854919&action=edit Output from dmesg -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193817] Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1193817 https://bugzilla.suse.com/show_bug.cgi?id=1193817#c4 --- Comment #4 from Ettore Atalan <atalanttore(a)googlemail.com> --- Created attachment 854918 --> https://bugzilla.suse.com/attachment.cgi?id=854918&action=edit Output from hwinfo -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193817] Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1193817 https://bugzilla.suse.com/show_bug.cgi?id=1193817#c3 --- Comment #3 from Ettore Atalan <atalanttore(a)googlemail.com> --- If it helps, I'm glad to provide the output from hwinfo and the output from dmesg. -- You are receiving this mail because: You are the assignee for the bug.

1 0

2023

2022

2021

2020

openSUSE Kernel Bugs January 2022