From: Jakub Kicinski <kuba@kernel.org>
To: Jesper Juhl <jesperjuhl76@gmail.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Eric Dumazet <edumazet@google.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
intel-wired-lan@lists.osuosl.org, Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] igc: Network failure, reboot required: igc: Failed to read reg 0xc030!
Date: Thu, 12 Sep 2024 17:46:06 -0700 [thread overview]
Message-ID: <20240912174606.3f008a47@kernel.org> (raw)
In-Reply-To: <CAHaCkmekKtgdVhm7RFp0jo_mfjsJgAMY738wG0LPdgLZN6kq4A@mail.gmail.com>
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?
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Jesper Juhl <jesperjuhl76@gmail.com>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: igc: Network failure, reboot required: igc: Failed to read reg 0xc030!
Date: Thu, 12 Sep 2024 17:46:06 -0700 [thread overview]
Message-ID: <20240912174606.3f008a47@kernel.org> (raw)
In-Reply-To: <CAHaCkmekKtgdVhm7RFp0jo_mfjsJgAMY738wG0LPdgLZN6kq4A@mail.gmail.com>
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?
next prev parent reply other threads:[~2024-09-13 0:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 15:10 [Intel-wired-lan] igc: Network failure, reboot required: igc: Failed to read reg 0xc030! Jesper Juhl
2024-09-11 15:10 ` Jesper Juhl
2024-09-12 13:03 ` [Intel-wired-lan] " Jesper Juhl
2024-09-12 13:03 ` Jesper Juhl
2024-09-12 15:37 ` [Intel-wired-lan] " Jakub Kicinski
2024-09-12 15:37 ` Jakub Kicinski
2024-09-12 19:45 ` [Intel-wired-lan] " Jesper Juhl
2024-09-12 19:45 ` Jesper Juhl
2024-09-13 0:46 ` Jakub Kicinski [this message]
2024-09-13 0:46 ` Jakub Kicinski
2024-09-13 7:02 ` [Intel-wired-lan] " Lifshits, Vitaly
2024-09-13 7:02 ` Lifshits, Vitaly
2024-09-13 21:52 ` Jesper Juhl
2024-09-13 21:52 ` Jesper Juhl
2024-09-15 7:03 ` Lifshits, Vitaly
2024-09-15 7:03 ` Lifshits, Vitaly
2024-09-17 11:39 ` Jesper Juhl
2024-09-17 11:39 ` Jesper Juhl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240912174606.3f008a47@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesperjuhl76@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.