From: Vladimir Oltean <olteanv@gmail.com>
To: Asmaa Mnebhi <asmaa@nvidia.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"sridhar.samudrala@intel.com" <sridhar.samudrala@intel.com>,
"maciej.fijalkowski@intel.com" <maciej.fijalkowski@intel.com>,
David Thompson <davthompson@nvidia.com>
Subject: Re: [PATCH net v4 1/1] mlxbf_gige: Fix kernel panic at shutdown
Date: Sat, 22 Jul 2023 01:32:36 +0300 [thread overview]
Message-ID: <20230721223236.kgdjzl7unfbuenzm@skbuf> (raw)
In-Reply-To: <CH2PR12MB3895C55CC77385622898BCADD73FA@CH2PR12MB3895.namprd12.prod.outlook.com>
Hi Asmaa,
On Fri, Jul 21, 2023 at 07:06:03PM +0000, Asmaa Mnebhi wrote:
> > What is the race condition; what does the stack trace of the NPD look like?
>
> Hi Vladimir,
>
> [ OK ] Reached target Shutdown.
> [ OK ] Reached target Final Step.
> [ OK ] Started Reboot.
> [ OK ] Reached target Reboot.
> ...
> [ 285.126250] mlxbf_gige MLNXBF17:00: shutdown
> [ 285.130669] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000070
> [ 285.139447] Mem abort info:
> [ 285.142228] ESR = 0x0000000096000004
> [ 285.145964] EC = 0x25: DABT (current EL), IL = 32 bits
> [ 285.151261] SET = 0, FnV = 0
> [ 285.154303] EA = 0, S1PTW = 0
> [ 285.157430] FSC = 0x04: level 0 translation fault
> [ 285.162293] Data abort info:
> [ 285.165159] ISV = 0, ISS = 0x00000004
> [ 285.168980] CM = 0, WnR = 0
> [ 285.171932] user pgtable: 4k pages, 48-bit VAs, pgdp=000000011d373000
> [ 285.178358] [0000000000000070] pgd=0000000000000000, p4d=0000000000000000
> [ 285.185134] Internal error: Oops: 96000004 [#1] SMP
That is not a stack trace. The stack trace is what appears between the
lines "Call trace:" and "---[ end trace 0000000000000000 ]---", and it
is missing from what you've posted.
It would be nice if you could also post-process the stack trace you get
through the command below (run in a kernel tree):
cat stack_trace | scripts/decode_stacktrace.sh path/to/vmlinux .
so that we could see the actual C code line numbers, and not just the
offsets within your particular binary image.
next prev parent reply other threads:[~2023-07-21 22:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 14:19 [PATCH net v4 1/1] mlxbf_gige: Fix kernel panic at shutdown Asmaa Mnebhi
2023-07-21 15:02 ` Vladimir Oltean
2023-07-21 19:06 ` Asmaa Mnebhi
2023-07-21 22:32 ` Vladimir Oltean [this message]
2023-07-21 23:27 ` Asmaa Mnebhi
2023-07-21 23:29 ` Vladimir Oltean
2023-07-26 16:27 ` Jakub Kicinski
2023-08-08 17:45 ` Asmaa Mnebhi
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=20230721223236.kgdjzl7unfbuenzm@skbuf \
--to=olteanv@gmail.com \
--cc=asmaa@nvidia.com \
--cc=davem@davemloft.net \
--cc=davthompson@nvidia.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sridhar.samudrala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox