linux-kernel - Re: 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240912083746.34a7cd3b@kernel.org>
Date: Thu, 12 Sep 2024 08:37:46 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jesper Juhl <jesperjuhl76@...il.com>
Cc: netdev@...r.kernel.org, intel-wired-lan@...ts.osuosl.org, "David S.
 Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo
 Abeni <pabeni@...hat.com>, Tony Nguyen <anthony.l.nguyen@...el.com>,
 Przemek Kitszel <przemyslaw.kitszel@...el.com>,
 linux-kernel@...r.kernel.org
Subject: Re: igc: Network failure, reboot required: igc: Failed to read reg
 0xc030!

On Thu, 12 Sep 2024 15:03:14 +0200 Jesper Juhl wrote:
> It just happened again.
> Same error message, but different stacktrace:

Hm, I wonder if it's power management related or the device just goes
sideways for other reasons. The crashes are in accessing statistics
and the relevant function doesn't resume the device. But then again,
it could just be that stats reading is the most common control path
operation.

Hopefully the Intel team can help.

Would you be able to decode the stack trace? It may be helpful
to figure out which line of code this is:

  igc_update_stats+0x8a/0x6d0 [igc
22e0a697bfd5a86bd5c20d279bfffd131de6bb32]