netdev - Re: [Intel-wired-lan] igc: Network failure, reboot required: igc: Failed to read reg 0xc030!

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAHaCkmcZ6tqj8zJjLERO6Ze4SrKNHBpGL8aOLwt6CsX8b4TSFA@mail.gmail.com>
Date: Tue, 17 Sep 2024 13:39:23 +0200
From: Jesper Juhl <jesperjuhl76@...il.com>
To: "Lifshits, Vitaly" <vitaly.lifshits@...el.com>
Cc: Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Eric Dumazet <edumazet@...gle.com>, Tony Nguyen <anthony.l.nguyen@...el.com>, 
	Przemek Kitszel <przemyslaw.kitszel@...el.com>, intel-wired-lan@...ts.osuosl.org, 
	Paolo Abeni <pabeni@...hat.com>, "David S. Miller" <davem@...emloft.net>
Subject: Re: [Intel-wired-lan] igc: Network failure, reboot required: igc:
 Failed to read reg 0xc030!

On Sun, 15 Sept 2024 at 09:03, Lifshits, Vitaly
<vitaly.lifshits@...el.com> wrote:
>
> >
> >> 2. What is the NVM version that your NIC has? (ethtool -i eno1)
> > $ sudo ethtool -i eno1
> > driver: igc
> > version: 6.10.9-arch1-2
> > firmware-version: 1082:8770
> > expansion-rom-version:
> > bus-info: 0000:0c:00.0
> > supports-statistics: yes
> > supports-test: yes
> > supports-eeprom-access: yes
> > supports-register-dump: yes
> > supports-priv-flags: yes
>
> I see that you have an old NVM version, 1.82.
>
> In the recent versions, some power and stability bug fixes were
> introduced to the NVM.
>
> These fixes in the NVM might resolve completely your issue.
>
> Therefore, I'd like to ask you to contact your board vendor, Asus, to
> update the NVM to the latest version.
>
I'll get in touch with them and see if I can manage to get the
firmware updated. I'll reply back what happens and whether or not it
seems to fix the issue (after a while) - thank you for the
information.

- Jesper Juhl