netdev - Re: [Intel-wired-lan] I225-V (rev 03) LOM + Linux kernel 6.7.0 power save issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <8d3340c4-81f8-4617-849e-e1fba96d0a19@intel.com>
Date: Sun, 28 Jan 2024 09:32:54 +0200
From: Sasha Neftin <sasha.neftin@...el.com>
To: S. <strykar@...mail.com>, "netdev@...r.kernel.org"
	<netdev@...r.kernel.org>
CC: "intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
	"Ruinskiy, Dima" <dima.ruinskiy@...el.com>, "Lifshits, Vitaly"
	<vitaly.lifshits@...el.com>
Subject: Re: [Intel-wired-lan] I225-V (rev 03) LOM + Linux kernel 6.7.0 power
 save issues

On 26/01/2024 13:37, S. wrote:
> Hi,
> 
> This was tested on a recently assembled Asus X670E-E ROG Gaming Wifi 
> motherboard running a standard Arch linux install - "Linux r912 
> 6.7.0-arch3-1 #1 SMP PREEMPT_DYNAMIC Sat, 13 Jan 2024 14:37:14 +0000 
> x86_64 GNU/Linux."
> 
> The NIC will only connect at 100 Mbit, forcing 1000 logs "igc 
> 0000:0a:00.0 eno1: Force mode currently not supported".

1000M works only with auto-negotiation. (but it is not related)

> 
> When Gnome / kernel attempt to power save to standby, it logs "igc: 
> Failed to read reg 0xc030!" and proceeds to hang the machine for about 5 
> minutes, post which it resets back to GDM login.
> After discussing the symptoms on IRC, it was suggested to drop an email 
> to the igc driver maintainer.
> 
> Some notes and logs at - 
> https://gist.github.com/Strykar/c78c292ca0a8ef942af846a1272a044e
> The issue persists even on kernel 6.7.1

 From the log I can see that PCIe link loss - this maybe come from 
HW/platform or BIOS settings. As a first step, I suggest contacting the 
vendor (ASUS).

> 
> Is this a known issue?
> 
> Best,
> Avi