[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240912174606.3f008a47@kernel.org>
Date: Thu, 12 Sep 2024 17:46:06 -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 21:45:17 +0200 Jesper Juhl wrote:
> > 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.
TBH I don't work much with distro kernels so I don't know.
There is a script for decoding stack traces in the tree:
./scripts/decode_stacktrace.sh
but it needs vmlinux (uncompressed) with full(ish) debug info.
I think that distros split the debug symbols out?
Powered by blists - more mailing lists