From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 206583] New: Aquantia NIC Suspend regression
Date: Mon, 17 Feb 2020 21:39:22 -0800 [thread overview]
Message-ID: <20200217213922.0ebd7b77@hermes.lan> (raw)
Begin forwarded message:
Date: Tue, 18 Feb 2020 05:13:38 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 206583] New: Aquantia NIC Suspend regression
https://bugzilla.kernel.org/show_bug.cgi?id=206583
Bug ID: 206583
Summary: Aquantia NIC Suspend regression
Product: Networking
Version: 2.5
Kernel Version: 5.5.4
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: silvaesilva@gmail.com
Regression: No
Created attachment 287451
--> https://bugzilla.kernel.org/attachment.cgi?id=287451&action=edit
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.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-02-18 5:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200217213922.0ebd7b77@hermes.lan \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.