FS#69149 - [linux] Desktop won't boot with 5.10.3

Attached to Project: Arch Linux
Opened by José Miguel Sarasola (alosarjos) - Thursday, 31 December 2020, 07:26 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 14 October 2021, 21:49 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: After updating to 5.10.3 and rebooting, during the boot process the screen looses the signal (After the BIOS screen) and I have to use the SysRq keys to be able to boot into the system. Happening with both linux and linux-zen, booting with linux-lts I do not have this problem (And haven't seen anything like this before today)


Additional info:
* Package versions:

- linux 5.10.3.arch1-1
- linux-lts 5.4.85-1
- linux-zen 5.10.3.zen1-1

Steps to reproduce:

Boot the system (In my case I use Gnome with GDM enabled on systemd)
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Thursday, 14 October 2021, 21:49 GMT
Reason for closing:  Fixed
Additional comments about closing:  2021-10-12: A task closure has been requested. Reason for request: Now it's working as expected
Comment by José Miguel Sarasola (alosarjos) - Thursday, 31 December 2020, 07:57 GMT
Looks like using a workaround for previous kernel versions (Adding amdgpu to the modules list on the mkinitcpio.conf) solves the problem. But I didn't need it until today.
Comment by Olav Seyfarth (nursoda) - Thursday, 31 December 2020, 15:22 GMT
Similar here, but NOT upon booting but JUST when resuming from standby. When hibernating, it hangs and doesn't switch off, state is not saved, so on next boot it doesn't resume but boots normally. Both happens in 5.10.3 (release) and 5.10.4 (testing). Did not happen until (and including) 5.10.2. Hardware: Lenovo T480s, Intel CPU and integrated Intel GPU. Symptoms: After resuming (from standby), screen remans black, external monitor doesn't get signal. I installed ssh deamon to test whether "just" video or the whole system isn't responsive: After resuming (from standby) I can neither ping nor connect via SSH from another PC on the local network.
Comment by Pawel Pilarczyk (papavlos) - Thursday, 31 December 2020, 17:34 GMT
@nursoda It's "just" the video. You can switch Ctrl+Alt+F2 to tty and see the system is up and working.
Downgrading back to 5.9.14 solves the problem.
I'm running KDE 5.77.0 / Plasma 5.20.4, CPU: Intel Core i3 M 370 @ 4x 2.4GHz, GPU: GeForce GT 425M, with nvidia-390xx-dkms 390.138-8 driver.
Comment by Olav Seyfarth (nursoda) - Thursday, 31 December 2020, 17:39 GMT
@papavlos: No, at least on my system and on 5.10.4 I can no longer switch to console after resuming from standby.
Comment by Pawel Pilarczyk (papavlos) - Friday, 01 January 2021, 21:23 GMT
My system is back on rails already with 5.10.3 kernel.
Today the nvidia-390xx-dkms driver was updated to 290.138-10 version, to fix the kernel 5.10.x problem with nvidia.
No additional adjustments were needed to my system.
I am removing my vote here.
Comment by Olav Seyfarth (nursoda) - Saturday, 02 January 2021, 01:43 GMT
@papavlos: So it seems you suffered a different issue. Thanks for the feedback and keep well.

I have tested on another Laptop: Lenovo T14s (AMD CPU+internal GPU): No standby/display issues there with 5.10.3 and default (OS) drivers.

Since my T480s needs to get a new screen I created an account for the IT department, removed my account and wiped its data. Logged in with that new account and after updating to kernel 5.10.5 (and now 6.10.6), I no longer can reproduce the issue. So either it was on my side (user setting, unlikely IMHO since I did not set anything special) or it was the kernel (or any other arch) update – works for me now, so I pull back.

@alosarjos: What about your issue with recent kernel? Still present? Please re-try and update this bug, or close it.
Comment by José Miguel Sarasola (alosarjos) - Saturday, 16 January 2021, 16:42 GMT
Hey there. I was a bit off, since 5.10 added a regression on power consumption on Navi and I'm still holding back. Just tried though, and nothing, system is on "Reached target Graphical Interface" and cursor keeps there blinking.

This is on linux 5.10.7 generated without the amdgpu module

Rebooted into linux-zen with the module, and working fine, checked the boot logs and found this:

[drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:70:crtc-0] flip_done timed out

Which is not showing up on the zen boot (But it's 5.9)
Comment by José Miguel Sarasola (alosarjos) - Tuesday, 12 October 2021, 15:49 GMT
I'm closing this issue. I just tested today and the amdgpu module on the mkinitcpio is no longer required, the module loads automatically.

Loading...