From: Michael Ellerman <mpe@ellerman.id.au>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: crash in cpuidle_enter_state with 5.7-rc1
Date: Tue, 21 Apr 2020 22:21:52 +1000 [thread overview]
Message-ID: <87sggxghb3.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20200420194132.GM25468@kitsune.suse.cz>
Michal Suchánek <msuchanek@suse.de> writes:
> On Mon, Apr 20, 2020 at 08:50:30AM +0200, Michal Suchánek wrote:
>> On Mon, Apr 20, 2020 at 04:15:39PM +1000, Michael Ellerman wrote:
>> > Michal Suchánek <msuchanek@suse.de> writes:
> ...
>> >
>> >
>> > And I've just hit it with your config on a machine here, but the crash
>> > is different:
>> That does not look like it.
>> You don't have this part in the stack trace:
>> > [ 1.234899] [c000000007597420] [0000000000000000] 0x0
>> > [ 1.234908] [c000000007597720] [0000000000000a6d] 0xa6d
>> > [ 1.234919] [c000000007597a20] [0000000000000000] 0x0
>> > [ 1.234931] [c000000007597d20] [0000000000000004] 0x4
>> which is somewhat random but at least on such line is always present in
>> the traces I get. Also I always get crash in cpuidle_enter_state
> ..
>> > I'm going to guess it's STRICT_KERNEL_RWX that's at fault.
>> I can try without that as well.
>
> Can't reproduce without STRICT_KERNEL_RWX either.
I've reproduced something similar all the way back to v5.5, though it
seems harder to hit - sometimes 5 boots will succeed before one fails.
Are you testing on top of PowerVM or KVM?
cheers
next prev parent reply other threads:[~2020-04-21 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 16:03 crash in cpuidle_enter_state with 5.7-rc1 Michal Suchánek
2020-04-20 6:15 ` Michael Ellerman
2020-04-20 6:50 ` Michal Suchánek
2020-04-20 19:41 ` Michal Suchánek
2020-04-21 12:21 ` Michael Ellerman [this message]
2020-04-21 12:37 ` Michal Suchánek
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=87sggxghb3.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--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).