Screen flashes and turns blank after resuming from blank state. Possibly a kernel bug. Fedora 35 with 5.14 kernel

noname01 · 11-13-2021, 01:57 PM

I'm using an r5 2500u laptop with a gtx 1050 gpu, an oem 256gb samsung 981a ssd, .

here is the dmesg:

Code:

[    0.000000] Linux version 5.14.10-300.fc35.x86_64 (mockbuild@bkernel01.iad2.fedoraproject.org) (gcc (GCC) 11.2.1 20210728 (Red Hat 11.2.1-1), GNU ld version 2.37-10.fc35) #1 SMP Thu Oct 7 20:48:44 UTC 2021

[    0.568538] Non-volatile memory driver v1.3
[    0.568560] Linux agpgart interface v0.103
[    0.573274] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0x7d44f000-0x7d44ffff flags 0x200] vs 7d44f000 4000
[    0.573280] tpm_crb MSFT0101:00: can't request region for resource [mem 0x7d44f000-0x7d44ffff]
[    0.573281] tpm_crb: probe of MSFT0101:00 failed with error -16



[    5.670755] Generic FE-GE Realtek PHY r8169-0-400:00: attached PHY driver (mii_bus:phy_addr=r8169-0-400:00, irq=MAC)
[    5.816873] r8169 0000:04:00.0 enp4s0: Link is Down
[    6.040270] ACPI: \: failed to evaluate _DSM (0x1001)
[    6.040278] ACPI: \: failed to evaluate _DSM (0x1001)
[    6.040280] ACPI: \: failed to evaluate _DSM (0x1001)
[    6.040283] ACPI: \: failed to evaluate _DSM (0x1001)
[    6.280232] ACPI: \: failed to evaluate _DSM (0x1001)
[    6.280240] ACPI: \: failed to evaluate _DSM (0x1001)
[    6.280243] ACPI: \: failed to evaluate _DSM (0x1001)
[    6.280246] ACPI: \: failed to evaluate _DSM (0x1001)
[   10.511160] wlp3s0: authenticate with 14:4d:67:7c:27:20
[   10.521000] wlp3s0: send auth to 14:4d:67:7c:27:20 (try 1/3)
[   10.531334] wlp3s0: authenticated
[   10.532786] wlp3s0: associate with 14:4d:67:7c:27:20 (try 1/3)
[   10.536737] wlp3s0: RX AssocResp from 14:4d:67:7c:27:20 (capab=0x411 status=0 aid=2)
[   10.544678] wlp3s0: associated
[   10.593060] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[   14.264472] rfkill: input handler disabled
[   14.406511] Bluetooth: RFCOMM TTY layer initialized
[   14.406519] Bluetooth: RFCOMM socket layer initialized
[   14.406615] Bluetooth: RFCOMM ver 1.11
[   19.384955] rfkill: input handler enabled
[   21.364754] rfkill: input handler disabled
[   61.741464] [drm] perform_link_training_with_retries: Link training attempt 1 of 4 failed
[   62.307271] [drm] perform_link_training_with_retries: Link training attempt 2 of 4 failed
[   62.872002] [drm] perform_link_training_with_retries: Link training attempt 3 of 4 failed
[   63.439548] [drm] enabling link 0 failed: 15
[   65.373934] wlp3s0: deauthenticating from 14:4d:67:7c:27:20 by local choice (Reason: 3=DEAUTH_LEAVING)
[   65.613436] PM: suspend entry (deep)
[   65.658148] Filesystems sync: 0.044 seconds
[   65.666984] rfkill: input handler enabled
[   65.724375] Freezing user space processes ... (elapsed 0.002 seconds) done.
[   65.726943] OOM killer disabled.
[   65.726945] Freezing remaining freezable tasks ... (elapsed 0.056 seconds) done.
[   65.799765] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[   65.800462] sd 1:0:0:0: [sda] Stopping disk
[   65.821952] [drm] free PSP TMR buffer
[   66.390828] PM: suspend devices took 0.608 seconds
[   66.392028] ACPI: EC: interrupt blocked
[   66.579308] ACPI: PM: Preparing to enter system sleep state S3
[   66.887185] ACPI: EC: event blocked
[   66.887190] ACPI: EC: EC stopped
[   66.887192] ACPI: PM: Saving platform NVS memory
[   66.887272] Disabling non-boot CPUs ...
[   66.890202] smpboot: CPU 1 is now offline
[   66.893607] smpboot: CPU 2 is now offline
[   66.896957] smpboot: CPU 3 is now offline
[   66.900289] smpboot: CPU 4 is now offline
[   66.904028] smpboot: CPU 5 is now offline
[   66.907400] smpboot: CPU 6 is now offline
[   66.910267] smpboot: CPU 7 is now offline
[   66.910721] ACPI: PM: Low-level resume complete
[   66.910721] ACPI: EC: EC started
[   66.910721] ACPI: PM: Restoring platform NVS memory
[   66.910721] Enabling non-boot CPUs ...
[   66.910721] x86: Booting SMP configuration:
[   66.910721] smpboot: Booting Node 0 Processor 1 APIC 0x1
[   66.890132] microcode: CPU1: patch_level=0x0810100b
[   66.912680] ACPI: \_PR_.P001: Found 2 idle states
[   66.913010] CPU1 is up
[   66.913113] smpboot: Booting Node 0 Processor 2 APIC 0x2
[   66.912438] microcode: CPU2: patch_level=0x0810100b
[   66.914018] ACPI: \_PR_.P002: Found 2 idle states
[   66.914525] CPU2 is up
[   66.914566] smpboot: Booting Node 0 Processor 3 APIC 0x3
[   66.913623] microcode: CPU3: patch_level=0x0810100b
[   66.915398] ACPI: \_PR_.P003: Found 2 idle states
[   66.916020] CPU3 is up
[   66.916064] smpboot: Booting Node 0 Processor 4 APIC 0x4
[   66.915171] microcode: CPU4: patch_level=0x0810100b
[   66.917819] ACPI: \_PR_.P004: Found 2 idle states
[   66.918598] CPU4 is up
[   66.918639] smpboot: Booting Node 0 Processor 5 APIC 0x5
[   66.917461] microcode: CPU5: patch_level=0x0810100b
[   66.919565] ACPI: \_PR_.P005: Found 2 idle states
[   66.920347] CPU5 is up
[   66.920384] smpboot: Booting Node 0 Processor 6 APIC 0x6
[   66.919214] microcode: CPU6: patch_level=0x0810100b
[   66.921290] ACPI: \_PR_.P006: Found 2 idle states
[   66.922245] CPU6 is up
[   66.922290] smpboot: Booting Node 0 Processor 7 APIC 0x7
[   66.920915] microcode: CPU7: patch_level=0x0810100b
[   66.923219] ACPI: \_PR_.P007: Found 2 idle states
[   66.924535] CPU7 is up
[   66.925773] ACPI: PM: Waking up from system sleep state S3
[   66.932410] ACPI: EC: interrupt unblocked
[   67.220366] ACPI: EC: event unblocked
[   67.227029] sd 1:0:0:0: [sda] Starting disk
[   67.227673] [drm] PCIE GART of 1024M enabled.
[   67.227675] [drm] PTB located at 0x000000F400900000
[   67.227700] [drm] PSP is resuming...
[   67.250421] [drm] reserve 0x400000 from 0xf43fc00000 for PSP TMR
[   67.289265] nvme nvme0: Shutdown timeout set to 8 seconds
[   67.312828] nvme nvme0: 16/0/0 default/read/poll queues
[   67.359960] amdgpu 0000:05:00.0: amdgpu: RAS: optional ras ta ucode is not available
[   67.379542] amdgpu 0000:05:00.0: amdgpu: RAP: optional rap ta ucode is not available
[   67.379544] amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[   67.381187] [drm] kiq ring mec 2 pipe 1 q 0
[   67.382811] amdgpu: restore the fine grain parameters
[   67.460328] ACPI: \: failed to evaluate _DSM (0x1001)
[   67.460334] ACPI: \: failed to evaluate _DSM (0x1001)
[   67.460337] ACPI: \: failed to evaluate _DSM (0x1001)
[   67.460340] ACPI: \: failed to evaluate _DSM (0x1001)
[   67.472281] [drm] VCN decode and encode initialized successfully(under SPG Mode).
[   67.472362] amdgpu 0000:05:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
[   67.472375] amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[   67.472375] amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[   67.472378] amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[   67.472391] amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[   67.472392] amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[   67.472395] amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[   67.472397] amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[   67.472399] amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[   67.472402] amdgpu 0000:05:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[   67.472404] amdgpu 0000:05:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
[   67.472407] amdgpu 0000:05:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
[   67.472409] amdgpu 0000:05:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
[   67.472411] amdgpu 0000:05:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
[   67.472414] amdgpu 0000:05:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
[   67.482484] usb 3-2: reset high-speed USB device number 2 using xhci_hcd
[   67.894790] Bluetooth: hci0: command 0x0c52 tx timeout
[   67.899359] usb 3-2.3: reset full-speed USB device number 5 using xhci_hcd
[   68.058833] usb 3-2.1: reset full-speed USB device number 3 using xhci_hcd
[   68.218738] usb 3-2.2: reset high-speed USB device number 4 using xhci_hcd
[   68.349655] PM: resume devices took 1.129 seconds
[   68.349665] OOM killer enabled.
[   68.349666] Restarting tasks ... 
[   68.352690] Bluetooth: hci0: Firmware revision 0.1 build 212 week 30 2021
[   68.357866] done.
[   68.368896] PM: suspend exit
[   68.378107] rfkill: input handler disabled
[   68.414412] Generic FE-GE Realtek PHY r8169-0-400:00: attached PHY driver (mii_bus:phy_addr=r8169-0-400:00, irq=MAC)
[   68.585246] r8169 0000:04:00.0 enp4s0: Link is Down
[   69.414757] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   69.597652] ata2.00: configured for UDMA/100
[   72.031737] wlp3s0: authenticate with 14:4d:67:7c:27:20
[   72.043194] wlp3s0: send auth to 14:4d:67:7c:27:20 (try 1/3)
[   72.049845] wlp3s0: authenticated
[   72.051823] wlp3s0: associate with 14:4d:67:7c:27:20 (try 1/3)
[   72.055809] wlp3s0: RX AssocResp from 14:4d:67:7c:27:20 (capab=0x411 status=0 aid=2)
[   72.059610] wlp3s0: associated
[   72.086288] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready

I'm suspecting an amd driver error. I have tried different driver versions on windows. v23 (6/2018) works. but starting from v25 till currenttly (v27) it just crashes in the same behavior. tried amdgpu.dc = 0, nomodeset,amdgpu.acpi = 0, amd.dpm = 0 ,no_console_suspend ,no avail.The above output ends after I ( push power button ) suspended the system and turn it back on ( it works, turn back on flawlessly ). Before that is when I tried to turn the screen blank (off , fn+f7 or by screen saver default timing) and can't turn it back on without forcing suspend with the power button first.

I use fwts aspm to check it out a bit here's a part of it

Code:

Test 1 of 2: PCIe ASPM ACPI test.
PCIe ASPM is not controlled by Linux kernel.

ADVICE: BIOS reports that Linux kernel should not modify ASPM settings that BIOS
configured. It can be intentional because hardware vendors identified some
capability bugs between the motherboard and the add-on cards.


Test 2 of 2: PCIe ASPM registers test.
PASSED: Test 2, PCIe ASPM setting matched was matched.
WARNING: Test 2, RP 0000h:00h:08h.01h L0s not enabled.
WARNING: Test 2, RP 0000h:00h:08h.01h L1 not enabled.
WARNING: Test 2, Device 0000h:05h:00h.03h L0s not enabled.
WARNING: Test 2, Device 0000h:05h:00h.03h L1 not enabled.

And something from automatic bug report:

Code:

crash_function resume_irqs

cmdline BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.14.16-301.fc35.x86_64 root=UUID=088be547-209f-4db1-9cdb-986dc33dbac0 ro rootflags=subvol=root rhgb quiet no_console_suspend

package kernel-core-5.14.16-301.fc35

type/analyzer Kerneloops/abrt-oops

Very stuck, help !

Update 1: updated to 5.14.17-301.fc35, still doesn't fix it.

smallpond · 11-15-2021, 08:06 AM

The "ACPI: \: failed to evaluate _DSM" messages do not indicate errors. They are here: https://patchwork.freedesktop.org/patch/159939/

The message "[drm] enabling link 0 failed: 15" is the serious one. It seems to be this unresolved kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=201139

What happens if you turn the monitor off and on? Are you connected via DisplayPort?

noname01 · 11-18-2021, 05:56 PM

Quote:

Originally Posted by smallpond

The "ACPI: \: failed to evaluate _DSM" messages do not indicate errors. They are here: https://patchwork.freedesktop.org/patch/159939/

The message "[drm] enabling link 0 failed: 15" is the serious one. It seems to be this unresolved kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=201139

What happens if you turn the monitor off and on? Are you connected via DisplayPort?

Sorry for late reply. If I turn the laptop display off and on it just output garbage ( flashes a few white lines, then total blank - back light still visable, until I hit suspend with the power button and turn it on again - this time it works somehow ), the same thing happen if I put the laptop on lock mode.

I don't really know which port is the laptop's monitor ( EDP ? ) connected to. Here's something:

Code:

[noname01@ispname ~]$ ls /sys/class/drm/card*

/sys/class/drm/card0:
dev  device  power  subsystem  uevent

/sys/class/drm/card1:
card1-eDP-1  card1-HDMI-A-1  dev  device  power  subsystem  uevent

/sys/class/drm/card1-eDP-1:
ddc     dpms         edid     i2c-17  power   subsystem
device  drm_dp_aux0  enabled  modes   status  uevent

/sys/class/drm/card1-HDMI-A-1:
ddc  device  dpms  edid  enabled  modes  power  status  subsystem  uevent

noname01 · 11-21-2021, 07:45 PM

New update: I suspect that this problem is with the ( now old ) amd driver. After a few day of utter frustration, I switch back to Windows, the same thing happened ( well, even worse, Windows didn't even let me resume from sleep ).

So, I checked out the AMD driver page of the version that the manufacturer had on their official support website ( 20.7.2 ) and tada: AMD is investigating isolated reports of intermittent system hangs while exiting system sleep on some AMD Ryzen™ 3000 Series Mobile Processors with Radeon™ Graphics.

Update my driver to Adrenalin 20.8.2. ( the one that they fix the issue ) -> Work faster than ever.

tldr: Driver error, perhaps they can fix this in the next linux kernel update ?