Suspend/Sleep Problem In Gigabyte B550 Aorus Pro AC Nvidia 470

[GaryD]

@SMD, will you please check on my updates above? Do you need the full logs?

[SMG]

While looking for a workaround to remedy the "no lockscreen" issue with the "pm-suspend" command, I found via autocomplete, the command "suspend-then-hibernate".

Do you have hibernation set up on your computer? Hibernation is turned off by default in LM20, but it can be enabled manually.

However, I'm seeing some error log on screen and in my dmesg below:

Code: Select all

[  100.906096] PM: dpm_run_callback(): usb_dev_resume+0x0/0x20 returns -5
[  100.906107] PM: Device 1-8 failed to resume async: error -5

[  931.094437] PM: dpm_run_callback(): usb_dev_resume+0x0/0x20 returns -5
[  931.094448] PM: Device 1-8 failed to resume async: error -5

[  939.317776] ata2: softreset failed (1st FIS failed)

The first two sets of lines look like the same message which was in your video. We would have to check to see which device that might be. You might be able to check in /var/log/syslog for 1-8 to see if you can find more information about it. Syslog is a text file so you can read it with any text editor.

I did a search on the last line and found this [solved] softreset failed (1st FIS failed), but that also has some other errors listed specific to the drive which turned out to be bad.

[GaryD]

Do you have hibernation set up on your computer? Hibernation is turned off by default in LM20, but it can be enabled manually.

> Nope, as this is a freshly installed LM20.2. No Hibernate Button either.

You might be able to check in /var/log/syslog for 1-8 to see if you can find more information about it. Syslog is a text file so you can read it with any text editor.

> Yep, will check on that this week and report back.

[SMG]

> Nope, as this is a freshly installed LM20.2. No Hibernate Button either.

There is no Hibernate button because hibernate is not enabled. It was removed multiple versions ago. (I think maybe Mint18 was the last version with it enabled? Not sure.)

Hibernate is save to disk while suspend is save to RAM. Usually one has to have the hibernation destination defined for it to be able to successfully resume and all your data re-appear. I am not sure how your system is handling suspend then hibernate if you do not have hibernate specifically enabled.

[GaryD]

I am not sure how your system is handling suspend then hibernate if you do not have hibernate specifically enabled.

> I don't even know myself, but it just works! I have a 32GB swap partition, the same as my RAM size. That's it!
I have no prior Hibernation setup.

[GaryD]

UPDATE: ON suspend-then-hibernate

I noticed when system is suspended for quite a while, like 8-hours or so, the system won't resume.

It needs to be powered on using the button - then upon boot up, you no longer have a saved state.

[SMG]

UPDATE: ON suspend-then-hibernate

I was on another thread yesterday where someone mentioned they were able to use hibernate on LM20.2 without doing anything special to enable it which seemed to be consistent with your statement until you said it didn't work for the 8-hour span.

If it might be related to the Nvidia driver, I noticed Nvidia released an updated driver on September 20th which mentions two different bug fixes that seem related to suspend and resume issues. It usually takes a little time for the package managers to prepare the Nvidia updates so they are available in Driver Manager, but I expect there will be a Nvidia 470.74 version available soon. Maybe the newer driver will clear the issue you are seeing.

[GaryD]

If it might be related to the Nvidia driver, I noticed Nvidia released an updated driver on September 20th which mentions two different bug fixes that seem related to suspend and resume issues. It usually takes a little time for the package managers to prepare the Nvidia updates so they are available in Driver Manager, but I expect there will be a Nvidia 470.74 version available soon. Maybe the newer driver will clear the issue you are seeing.

Today, I have finally installed the Nvidia driver 470.74 from the Driver Manager, however, I still see the same thing. Blank screen from suspend/wake state.

That's, when clicking on the suspend button.

I'm able to do suspend/wake however, when doing a pm-suspend or suspend-then-hibernate command.

Code: Select all

Graphics:  Device-1: NVIDIA GK208B [GeForce GT 710] driver: nvidia v: 470.74 bus ID: 04:00.0 
           Device-2: NVIDIA GK208B [GeForce GT 710] driver: nvidia v: 470.74 bus ID: 0a:00.0 
           Display: x11 server: X.Org 1.20.11 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: NVIDIA GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 470.74 direct render: Yes

[SMG]

Today, I have finally installed the Nvidia driver 470.74 from the Driver Manager, however, I still see the same thing. Blank screen from suspend/wake state.

I received similar feedback yesterday.

See this post for more information on which suspend command is preferred.

[GaryD]

so I would presume "sudo systemctl suspend" is the preferred command

You mentioned that in your linked thread, but that command is problematic on my end. I always ended up in black screen when resuming.

So I always use pm-suspend, or suspend-then-hibernate.

[SMG]

or suspend-then-hibernate.

You indicated earlier that was not always working properly if you suspended for an extended time.

I do not have any ideas at the present time.

[ici_chacal]

I have a very similar issue:
When I suspend, the machine immediately wakes back up, but gives me the login screen so I can log back in.

I have the Aorus Elite B550 AX V2, with Ryzen 9 5900X, RTX 2080 Super; the mobo shipped with the F11 BIOS.
Everything was working normally.

Then, in order to resolve an unrelated issue, I flashed the F14 BIOS, which subsequently caused the sleep problem.
The issue is the same with all Kernels, but the system suspends normally in Windows 10.

I guess either the BIOS needs to be fixed (doubt that'll happen), or the Linux kernel needs updating to accommodate whatever changed in the BIOS...

ic

[SMG]

I guess either the BIOS needs to be fixed (doubt that'll happen), or the Linux kernel needs updating to accommodate whatever changed in the BIOS...

Do you know what updates were in the BIOS? Maybe if enough people report this issue then the BIOS will get updated.

[ici_chacal]

Do you know what updates were in the BIOS? Maybe if enough people report this issue then the BIOS will get updated.

I'm afraid not. And the F11 BIOS is not listed on their support page either. The OP mentioned the issue was from F12 onwards.
I regret not saving F11 before flashing F14 now...

[GaryD]

I'm afraid not. And the F11 BIOS is not listed on their support page either. The OP mentioned the issue was from F12 onwards.
I regret not saving F11 before flashing F14 now...

Maybe you can try posting in their subReddit and ask for anyone who has the F11 copy of the BIOS.

Or, email Gigabyte direct.