netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lifshits, Vitaly" <vitaly.lifshits@intel.com>
To: Preindl <preindl@protonmail.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "intel-wired-lan@lists.osuosl.org" <intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [BUG] igc: ASPM causes I226-V NIC to drop after idle
Date: Sun, 7 Sep 2025 17:04:28 +0300	[thread overview]
Message-ID: <2c8d205d-ccd5-43e7-a63f-e223a8e6a90d@intel.com> (raw)
In-Reply-To: <8zW6rn6ENKd_scHL34Qx4e0KGlekfpSuHxVId5nBR-S9-BYI0v-ozzGBv7LcR3KGlwTzDTEDhhhbkmwmM5GhmvVgEC3zf6YYoraQruWmfNU=@protonmail.com>

On 9/5/2025 1:03 AM, Preindl wrote:
> Hello,
> 
> I'd like to add the following information/correction.
> 
> The issue can be traced to the following error that appears typically 
> after a period of inactivity
> igc: Failed to read reg 0xc030!
> 
> The kernel parameter pcie_aspm=off does not solve the issue.
> I am testing now the parameters pcie_port_pm=off and 
> pcie_aspm.policy=performance that are often reported to mitigate the 
> above error.
> 
> This issue seems to be more common with Asus motherboards and may be 
> reproducible with Intel I225-V NICs, see also
> https://bbs.archlinux.org/viewtopic.php?id=288371 <https:// 
> bbs.archlinux.org/viewtopic.php?id=288371>
> https://forum.proxmox.com/threads/network-card-drop-igc-0000-09-00-0- 
> eno1-pcie-link-lost.121295/ <https://forum.proxmox.com/threads/network- 
> card-drop-igc-0000-09-00-0-eno1-pcie-link-lost.121295/>
> https://www.reddit.com/r/buildapc/comments/xypn1m/ 
> network_card_intel_ethernet_controller_i225v_igc/ <https:// 
> www.reddit.com/r/buildapc/comments/xypn1m/ 
> network_card_intel_ethernet_controller_i225v_igc/>
> 
> 
> 
> On Monday, September 1st, 2025 at 4:45 PM, Preindl 
> <preindl@protonmail.com> wrote:
>> Hello,
>>
>> I am seeing an issue with the Intel I226-V Ethernet controller on an 
>> ASUS ProArt X870E motherboard. When PCIe Active State Power Management 
>> (ASPM) is enabled, the NIC becomes unavailable after a period of 
>> inactivity. Disabling ASPM avoids the problem.
>>
>> This looks like a hardware/firmware issue, but since it is easily 
>> reproducible (there are several forum discussions), it may warrant a 
>> kernel quirk in the igc driver to disable ASPM for this firmware (or 
>> device?).
>>
>> ---
>>
>> Hardware:
>> - Motherboard: ASUS ProArt X870E
>> - NIC: Intel I226-V [8086:125c] (rev 06)
>> - Subsystem: [1043:8867]
>> - Firmware version (from ethtool -i): 2023:889d
>>
>> Software:
>> - OS: Debian GNU/Linux 13 (trixie)
>> - Kernel: Linux 6.12.41+deb13-amd64
>> - Driver: igc
>>
>> ---
>>
>> Steps to reproduce (logs attached)
>> 1. Boot system with default PCIe ASPM enabled.
>> 2. Leave the box/NIC idle for some time.
>> 3. NIC disappears (reappears after reboot)
>>
>> Workaround:
>> - Booting with pcie_aspm=off (or disabling ASPM in BIOS) keeps the NIC 
>> stable.
>>
>> Expected:
>> - NIC should remain functional with ASPM enabled.
>>
>> Actual:
>> - NIC crashes at/after idle when ASPM is enabled.
>>
>> ---
>>
>> Please let me know if additional information or testing would help.
>>
> 

Hello,

Thank you for the detailed report and for sharing your findings.
Unfortunately, there’s not much we can do within the driver to work 
around this issue. The behavior you're observing appears to stem from an 
unexpected PCIe link state change, which the OS interprets as a surprise 
removal of the device.

Given that, I recommend reaching out to ASUS support directly, as this 
may be related to motherboard firmware or hardware compatibility.

      parent reply	other threads:[~2025-09-07 14:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01 20:45 [BUG] igc: ASPM causes I226-V NIC to drop after idle Preindl
2025-09-05  2:20 ` Preindl
     [not found] ` <8zW6rn6ENKd_scHL34Qx4e0KGlekfpSuHxVId5nBR-S9-BYI0v-ozzGBv7LcR3KGlwTzDTEDhhhbkmwmM5GhmvVgEC3zf6YYoraQruWmfNU=@protonmail.com>
2025-09-07 14:04   ` Lifshits, Vitaly [this message]

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=2c8d205d-ccd5-43e7-a63f-e223a8e6a90d@intel.com \
    --to=vitaly.lifshits@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=netdev@vger.kernel.org \
    --cc=preindl@protonmail.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;
as well as URLs for NNTP newsgroup(s).