Bug 206583 - Aquantia NIC Suspend regression
Summary: Aquantia NIC Suspend regression
Status: RESOLVED PATCH_ALREADY_AVAILABLE
Alias: None
Product: Networking
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Stephen Hemminger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-18 05:13 UTC by Carlos Augusto
Modified: 2020-03-15 04:54 UTC (History)
3 users (show)

See Also:
Kernel Version: 5.5.4
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
Kernel Config (28.69 KB, application/gzip)
2020-02-18 05:13 UTC, Carlos Augusto
Details

Description Carlos Augusto 2020-02-18 05:13:38 UTC
Created attachment 287451 [details]
Kernel Config

When using 5.5 branch kernel my computer wouldn't go into the sleep state any longer.

Trying to sleep would almost work but the computer never really "turned off", keeping fans running. Trying to resume from that state was also absolutely impossible, as it seems the computer didn't get to sleep, hence it was not possible to wake it.

Bisecting identified 8aaa112a57c1d725c92dfad32c0694bd21b374d0 as the offending commit, which makes sense as this is "net: atlantic: refactoring pm logic". This was done directly on vanilla kernel tree.

Not sure how to exactly debug where the issue is in the code, but I can run other tests as needed.

CPU: ThreadRipper 2950x
MB: Asrock X399 Fatal1ty

possibly relevant boot params
amd_iommu=on iommu=pt nohpet tsc=reliable

config attached if needed.
Comment 1 Igor Russkikh 2020-02-18 09:57:28 UTC
Hi Carlos,

This is expected to be fixed in current "net" tree. Is it possible for you to test this tree? The fixing commit is 52a22f4d6ff95e8bdca557765c04893eb5dd83fd.

Or you may wait until 5.6-rc3 - it should contain the related fixes.

Thanks!
Comment 2 Carlos Augusto 2020-02-18 20:48:33 UTC
Igor,

I have just applied 52a22f4d6ff95e8bdca557765c04893eb5dd83fd against the 5.5.4 kernel and sleep is working again.

Not sure if we will want to just have it on 5.6 or fix on 5.5 tree too.

Also, because I don't know how the issue tracker work here in the kernel, I will leave it to your to change the ticket Status.

Thanks for the fast reply!

Note You need to log in before you can comment on or make changes to this bug.