From: Stephen Hemminger <stephen@networkplumber.org>
To: anthony.l.nguyen@intel.com, jesse.brandeburg@intel.com
Cc: intel-wired-lan@lists.osuosl.org
Subject: [Intel-wired-lan] suspend/resume broken of igc driver broken on 6.12
Date: Thu, 30 Jan 2025 09:11:11 -0800 [thread overview]
Message-ID: <20250130091111.46358882@hermes.local> (raw)
I am using:
5a:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-LM (rev 04)
Subsystem: Intel Corporation Device 0000
Flags: bus master, fast devsel, latency 0, IRQ 19, IOMMU group 20
Memory at 6c500000 (32-bit, non-prefetchable) [size=1M]
Memory at 6c600000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [70] MSI-X: Enable+ Count=5 Masked-
Capabilities: [a0] Express Endpoint, IntMsgNum 0
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 58-47-ca-ff-ff-7a-98-3d
Capabilities: [1c0] Latency Tolerance Reporting
Capabilities: [1f0] Precision Time Measurement
Capabilities: [1e0] L1 PM Substates
Kernel driver in use: igc
Kernel modules: igc
Using both Debian testing and my own kernel built from 6.12, the igc
driver appears broken after resume.
After resuming the device is down and no address present.
Attempts to set link up manually fail.
If I do rmmod/modprobe of igc it comes back.
Doing a bit of bisectting but it is slow going.
next reply other threads:[~2025-01-30 17:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 17:11 Stephen Hemminger [this message]
2025-01-30 19:17 ` [Intel-wired-lan] suspend/resume broken of igc driver broken on 6.12 Lifshits, Vitaly
2025-01-30 21:08 ` Stephen Hemminger
2025-01-31 1:21 ` Stephen Hemminger
2025-02-05 10:36 ` Lifshits, Vitaly
2025-02-06 4:13 ` Stephen Hemminger
2025-02-06 13:17 ` Lifshits, Vitaly
2025-02-06 20:09 ` Stephen Hemminger
2025-02-11 18:20 ` Lifshits, Vitaly
2025-02-11 19:05 ` Stephen Hemminger
2025-02-11 19:09 ` Stephen Hemminger
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=20250130091111.46358882@hermes.local \
--to=stephen@networkplumber.org \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox