[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHaCkmekKtgdVhm7RFp0jo_mfjsJgAMY738wG0LPdgLZN6kq4A@mail.gmail.com>
Date: Thu, 12 Sep 2024 21:45:17 +0200
From: Jesper Juhl <jesperjuhl76@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
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!
> 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
> 22e0a697bfd5a86bd5c20d279bfffd
> 131de6bb32]
Of course. Just tell me what to do.
- Jesper
On Thu, 12 Sept 2024 at 17:37, Jakub Kicinski <kuba@...nel.org> wrote:
>
> 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]
Powered by blists - more mailing lists