LinuxQuestions.org - Resume from suspend issue on ASUS MB with NVIDIA

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Resume from suspend issue on ASUS MB with NVIDIA (https://www.linuxquestions.org/questions/slackware-14/resume-from-suspend-issue-on-asus-mb-with-nvidia-4175694331/)

Resume from suspend issue on ASUS MB with NVIDIA

Hi,

I am using Slackware current on an ASUS motherboard that uses NVIDIA/Intel graphics cards. When I try to wake up the computer from suspend by pressing any key on the keyboard, it would wake up but my monitor fails to respond even when I use my mouse.

Here is some hardware info:

Code:

$ sudo lspci

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex

00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU

00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

00:08.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)

00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)

00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0

00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1

00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2

00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3

00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4

00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5

00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6

00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7

01:00.0 Non-Volatile memory controller: Sandisk Corp WD Blue SN550 NVMe SSD (rev 01)

02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream

03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge

03:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge

03:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge

03:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge

03:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge

04:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4352 802.11ac Wireless Network Adapter (rev 03)

05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

06:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP

06:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

06:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

07:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

08:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

09:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2060] (rev a1)

09:00.1 Audio device: NVIDIA Corporation TU104 HD Audio Controller (rev a1)

09:00.2 USB controller: NVIDIA Corporation TU104 USB 3.1 Host Controller (rev a1)

09:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU104 USB Type-C UCSI Controller (rev a1)

0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function

0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP

0b:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP

0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

0b:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller

0c:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

0d:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

Code:

 

$ head /proc/cpuinfo 

processor        : 0

vendor_id        : AuthenticAMD

cpu family        : 23

model                : 113

model name        : AMD Ryzen 5 3600 6-Core Processor

stepping        : 0

microcode        : 0x8701013

cpu MHz                : 2195.386

cache size        : 512 KB

physical id        : 0

I had to attach a text file containing the list of installed packages because it was to long to fit on here.

If there is any info that is needed or any other commands that you'd like me to run, let me know. There was a recent update to the kernel and I haven't rebooted yet but when I do, I'll see if rebooting fixes it and report back.

** EDIT **
Still no luck with the latest kernel.

There was an issue with this hardware (e.g. here and here) but it has been fixed.
From /usr/src/linux-5.10.32/drivers/pci/quirks.c

Code:

static void quirk_no_flr(struct pci_dev *dev)

{

        dev->dev_flags |= PCI_DEV_FLAGS_NO_FLR_RESET;

}

DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x1487, quirk_no_flr);

DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x148c, quirk_no_flr);

DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x149c, quirk_no_flr);

DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1502, quirk_no_flr);

DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1503, quirk_no_flr);

Is your BIOS up to date?

Quote:

Originally Posted by budrz89 (Post 6245316)

I've had this problem in the past (not at present) and always put it down to the monitor being particularly finicky. I used to power-cycle it to fix it. Your issue may be entirely different.

@allend,

My BIOS did need an update but even after updating it, the problem persists.

@Martinus2u,

How did you power cycle it in order to get it working?

** EDIT **

BTW, I forgot to mention that I also tried adding

Code:

amdgpu.dc=0 amdgpu.audio=0 amdgpu.dpm=0 amdgpu.aspm=0 amdgpu.runpm=0 amdgpu.bapm=0

to my kernel command line in /etc/default/grub as well as

Code:

acpi_osi=linux noapic

(as suggested here here but I'm not sure if the "--quirk-s3-bios" and "--quirk-s3-mode" apply here since pm-suspend got replaced by loginctl)

but neither of these worked.

You could be experiencing this issue: https://gitlab.freedesktop.org/drm/amd/-/issues/1230

@ctrlaltca, maybe... I may have to wait until the new release comes out if that is the case.

It doesn't make sense though because I could have sworn that the suspend/resume worked on other distros before (like CRUX for example).

For what it's worth, I've attached my dmesg log.

Strangely enough suspend/resume works on my LFS partition (May 3, sysv development version, using pkgutils as my package manager). I tried Artix (version runit-20210426-x86_64), CRUX (3.6), and Debian (version 9, I know it's old) and they all had that same problem. I had a hard time installing Slackware 14.2 on a USB for some reason but Alien Bob's Slackware 14.2+ installed just fine. Just the suspend/resume doesn't want to work.

One thing that I can think of is that maybe it has something to do with the auto generation of the grub.cfg file. Another are the init scripts or how fstab is setup. Not sure, but I followed the uefi hint along with the LFS book and parts of the BLFS book. Then I used prt-get for retrieving packages in contrib, opt, and xorg (with some modifications); some needed core packages I had to retrieve manually.

I wonder if pm-suspend will work on LFS if I tried Slackware 14.2 source repository using Slackware's package manager instead. I've installed and got it working on my Dell Vostro 15 laptop (Intel instead of AMD, but it might be worth trying out).

What connection are you using between graphics and monitor? There are some driver related issues recently solved with the 460.80 driver regarding Display Port. Those issues now fixed, were/are not entirely consistent, thus the sometime-y behaviour.

Using Moread HDMI to VGA like this one:

https://www.amazon.com/Moread-Gold-P.../dp/B00SW9JI9A

connected to a 24" monitor.

If it helps, I've attached dmesg before and after suspend on my LFS box using the diff command. The suspend/resume seems to work and is consistent on LFS with kernel 5.11.16.

Looking at the dmesg output in post #6

Quote:

[ 5.685605] nouveau 0000:09:00.0: NVIDIA TU104 (164000a1)
...
[ 6.634020] nvidia-gpu 0000:09:00.3: i2c timeout error e0000000
[ 6.634032] ucsi_ccg 2-0008: i2c_transfer failed -110
[ 6.634040] ucsi_ccg 2-0008: ucsi_ccg_init failed - -110
[ 6.634051] ucsi_ccg: probe of 2-0008 failed with error -110
[

took me to this bug report.

@allend, ah interesting. Thanks for finding that!

The error appears in the previous dmesg (from my Slackware distro) but not in the other dmesg (on my LFS partition). So that's where the problem lies.

I guess I would either need to wait for the developers to patch the kernel or somehow do it myself, but I never had to patch a kernel before. Is it something like

Code:

cd /usr/src/<kernel>/

patch -p0 .... (or whatever patch level)

make oldconfig

make modules_install

cp arch/x86/boot/bzImage /boot/vmlinuz-huge-<version>

cp System.map /boot/System.map-huge-<version>

cp .config /boot/config-huge-<version>

Or maybe I would be better off waiting for testing to go through? Advice?

I've applied the patch but the error seems to persist. I followed these steps:

Code:

cd /usr/src/<kernel>/

patch -p0 .... (or whatever patch level)

make

make modules_install

cp arch/x86/boot/bzImage /boot/vmlinuz-huge-<version>

cp System.map /boot/System.map-huge-<version>

cp .config /boot/config-huge-<version>

I've attached the new diff of before and after the "loginctl suspend" as well as the patch (remove the ".txt" at the end).