From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org, mahesh@lists.ozlabs.org,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Michal Suchánek" <msuchanek@suse.de>
Subject: Re: Injecting SLB miltihit crashes kernel 5.9.0-rc5
Date: Wed, 16 Sep 2020 10:51:46 +1000 [thread overview]
Message-ID: <1600217251.rwlk7zedhj.astroid@bobo.none> (raw)
In-Reply-To: <87bli7p5dx.fsf@mpe.ellerman.id.au>
Excerpts from Michael Ellerman's message of September 15, 2020 10:54 pm:
> Michal Suchánek <msuchanek@suse.de> writes:
>> Hello,
>>
>> Using the SLB mutihit injection test module (which I did not write so I
>> do not want to post it here) to verify updates on my 5.3 frankernekernel
>> I found that the kernel crashes with Oops: kernel bad access.
>>
>> I tested on latest upstream kernel build that I have at hand and the
>> result is te same (minus the message - nothing was logged and the kernel
>> simply rebooted).
>
> That's disappointing.
It seems to work okay with qemu and mambo injection on upstream
(powernv_defconfig). I wonder why that nmi_enter is crashing.
Can you post the output of a successful test with the patch
reverted?
qemu injection test output -
[ 195.279885][ C0] Disabling lock debugging due to kernel taint
[ 195.280891][ C0] MCE: CPU0: machine check (Warning) Host SLB Multihit DAR: 00000000deadbeef [Recovered]
[ 195.282117][ C0] MCE: CPU0: NIP: [c00000000003c2b4] isa300_idle_stop_mayloss+0x68/0x6c
[ 195.283631][ C0] MCE: CPU0: Initiator CPU
[ 195.284432][ C0] MCE: CPU0: Probable Software error (some chance of hardware cause)
[ 220.711577][ T90] MCE: CPU0: machine check (Warning) Host SLB Multihit DAR: 00000000deadbeef [Recovered]
[ 220.712805][ T90] MCE: CPU0: PID: 90 Comm: yes NIP: [00007fff7fdac2e0]
[ 220.713553][ T90] MCE: CPU0: Initiator CPU
[ 220.714021][ T90] MCE: CPU0: Probable Software error (some chance of hardware cause)
Thanks,
Nick
next prev parent reply other threads:[~2020-09-16 0:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 8:43 Injecting SLB miltihit crashes kernel 5.9.0-rc5 Michal Suchánek
2020-09-15 12:54 ` Michael Ellerman
2020-09-16 0:51 ` Nicholas Piggin [this message]
2020-09-15 18:06 ` [PATCH] Revert "powerpc/64s: machine check interrupt update NMI accounting" Michal Suchanek
2020-09-15 18:16 ` peterz
2020-09-16 9:00 ` Michal Suchánek
2020-09-16 7:12 ` Injecting SLB miltihit crashes kernel 5.9.0-rc5 Mahesh Jagannath Salgaonkar
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=1600217251.rwlk7zedhj.astroid@bobo.none \
--to=npiggin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=msuchanek@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).