December 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1193397] amdgpu: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 05 Dec '21

05 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c22 --- Comment #22 from Kourosh P. <kourosh(a)pourdanandeh.com> --- Created attachment 854330 --> http://bugzilla.opensuse.org/attachment.cgi?id=854330&action=edit dmesg After switching to console 1 and startx -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193397] amdgpu: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 05 Dec '21

05 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c21 --- Comment #21 from Kourosh P. <kourosh(a)pourdanandeh.com> --- Created attachment 854329 --> http://bugzilla.opensuse.org/attachment.cgi?id=854329&action=edit dmesg After No Signal at console 7 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193397] amdgpu: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 05 Dec '21

05 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c20 --- Comment #20 from Kourosh P. <kourosh(a)pourdanandeh.com> --- (In reply to Takashi Iwai from comment #16) > Try to boot with monitor off, run X. Then before turning on the monitor, > enable the debug option of drm, run the following as root: > echo 0x1e > /sys/module/drm/parameters/debug > > Then turn on the monitor, confirm the problem ('no signal'). Save the dmesg > output at this stage. dmesg | susepaste https://susepaste.org/49240459 > Then move to VT1, restore the monitor out, and save the dmesg output again. > After that, clear the drm debug option > echo 0 > /sys/module/drm/parameters/debug I hope with "move to VT1" you mean CTRL+ALT+F1 and run the command, and not rebooting the system with monitor ON this time. I did go to TTY1, login, startx (X took a lot longer time to load but only the mouse cursor is visible with screen showing black) waited few minutes and the ddesktop came on for a split second and everything went black except the mouse cursor being visible. I did dmesg: dmesg | susepaste https://susepaste.org/12185740 I had to move to TTY2 to be able to reboot the system safely (took a LONG time). Don't know if I should have done another dmesg output after a successful reboot with monitor ON?! > Upload the saved two dmesg outputs to Bugzilla. > > BTW, when you boot with another desktop environment (such as icewm), does > the problem persist? I mean not to log out and switch from KDE, but login > directly to icewm session (which should be available as fallback) at boot. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193397] amdgpu: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 05 Dec '21

05 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c19 --- Comment #19 from Kourosh P. <kourosh(a)pourdanandeh.com> --- To @Nikolai In the BIOS Advanced > System Agent (SA) Configuration > Graphics Configuration > Primary Display > 'Auto' was selected. The other options were 'CPU Graphics', 'PEG', 'PCIE' and I changed it to 'PEG'. Advanced > System Agent (SA) Configuration > Graphics Configuration > iGPU Multi-Monitor is already set to 'Disabled'. I rebooted the system with monitor OFF and got the same result with DP NO Signal when monitor was turned on. sudo inxi -aSCGImz System: Kernel: 5.3.18-59.34-default x86_64 bits: 64 compiler: gcc v: 7.5.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.3.18-59.34-default root=UUID=843c52a9-20ba-4694-abc3-a3988c2c354a splash=silent resume=/dev/disk/by-uuid/295c1286-73fd-42fa-9f7a-21fa1103e118 mitigations=auto quiet Console: tty 1 dm: SDDM Distro: openSUSE Leap 15.3 Memory: RAM: total: 15.53 GiB used: 733.7 MiB (4.6%) Array-1: capacity: 64 GiB slots: 4 EC: None max module size: 16 GiB note: est. Device-1: ChannelA-DIMM1 size: No Module Installed Device-2: ChannelA-DIMM2 size: 8 GiB speed: 2133 MT/s type: DDR4 detail: synchronous bus width: 64 bits total: 64 bits manufacturer: G-Skill part-no: F4-3000C16-8GISB serial: N/A Device-3: ChannelB-DIMM1 size: No Module Installed Device-4: ChannelB-DIMM2 size: 8 GiB speed: 2133 MT/s type: DDR4 detail: synchronous bus width: 64 bits total: 64 bits manufacturer: G-Skill part-no: F4-3000C16-8GISB serial: N/A CPU: Topology: 8-Core model: Intel Core i7-10700K bits: 64 type: MT MCP arch: N/A family: 6 model-id: A5 (165) stepping: 5 microcode: EC L1 cache: 512 KiB L2 cache: 16.0 MiB L3 cache: 16.0 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 121596 Speed: 800 MHz min/max: 800/5100 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 801 6: 800 7: 800 8: 800 9: 801 10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800 Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown status: Not affected Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: Tul driver: amdgpu v: kernel bus ID: 04:00.0 chip ID: 1002:73bf Display: server: X.org 1.20.3 compositor: kwin_x11 driver: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa tty: 208x57 Message: Advanced graphics data unavailable in console for root. Info: Processes: 338 Uptime: N/A Init: systemd v: 246 runlevel: 5 target: graphical.target Compilers: gcc: N/A Shell: bash (sudo) v: 4.4.23 running in: tty 1 (SSH) inxi: 3.1.00 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193397] amdgpu: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 05 Dec '21

05 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c18 --- Comment #18 from Stefan Dirsch <sndirsch(a)suse.com> --- Well, according to the logs the reporter provided the internal GPU has been disabled. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193397] amdgpu: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 05 Dec '21

05 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c17 Nikolai Nikolaevskii <kaykaykay123(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kaykaykay123(a)gmail.com --- Comment #17 from Nikolai Nikolaevskii <kaykaykay123(a)gmail.com> --- According to inxi output OP uses Intel Core i7-10700K + ASUSTeK PRIME Z490-A + AMD Navi 21 video card. With Intel Core i7-10700K he has 2 video cards: built-in Intel UHD 630 and discrete AMD (previously Nvidia). But inxi shows only AMD Navi 21. There are some settings in BIOS about video cards: disable/enable iGFX (i.e. built-in), and which video card BIOS will initialize first - built-in or discrete. So, if built-in video card is disabled, but is set to be initialized first, he may get observed behaviour. To OP: please provide full output for command: sudo inxi -aSCGImz -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193397] amdgpu: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 05 Dec '21

05 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c16 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(kourosh@pourdanan | |deh.com) --- Comment #16 from Takashi Iwai <tiwai(a)suse.com> --- Try to boot with monitor off, run X. Then before turning on the monitor, enable the debug option of drm, run the following as root: echo 0x1e > /sys/module/drm/parameters/debug Then turn on the monitor, confirm the problem ('no signal'). Save the dmesg output at this stage. Then move to VT1, restore the monitor out, and save the dmesg output again. After that, clear the drm debug option echo 0 > /sys/module/drm/parameters/debug Upload the saved two dmesg outputs to Bugzilla. BTW, when you boot with another desktop environment (such as icewm), does the problem persist? I mean not to log out and switch from KDE, but login directly to icewm session (which should be available as fallback) at boot. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193091] Keyboard no longer working at console
by bugzilla_noreply＠suse.com 05 Dec '21

05 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193091 https://bugzilla.suse.com/show_bug.cgi?id=1193091#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- OK, if it's a USB, it might be due to the recent XHCI regression. Could you test the kernel in OBS home:tiwai:bsc1192569 repo? If this still doesn't work, please give more logs (dmesg output and hwinfo output). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193397] amdgpu: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 04 Dec '21

04 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c15 --- Comment #15 from Stefan Dirsch <sndirsch(a)suse.com> --- Thanks. But in that case it's more confusing than helpful. ;-) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193397] amdgpu: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 04 Dec '21

04 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c14 --- Comment #14 from Kourosh P. <kourosh(a)pourdanandeh.com> --- This issue was not only experienced with AMD GPU but with NVIDIA as well. You know better. I thought it would be helpful. -- You are receiving this mail because: You are the assignee for the bug.

1 0