From: Michael Ellerman <mpe@ellerman.id.au>
To: Christophe Leroy <christophe.leroy@c-s.fr>,
Nick Desaulniers <ndesaulniers@google.com>
Cc: clang-built-linux <clang-built-linux@googlegroups.com>,
linuxppc-dev@ozlabs.org
Subject: Re: ppc32 panic on boot on linux-next
Date: Tue, 10 Mar 2020 15:44:54 +1100 [thread overview]
Message-ID: <875zfcked5.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <c084a429-9ea1-7126-f057-8647a2e0dfac@c-s.fr>
Christophe Leroy <christophe.leroy@c-s.fr> writes:
> Le 07/03/2020 à 09:42, Christophe Leroy a écrit :
>> Le 06/03/2020 à 20:05, Nick Desaulniers a écrit :
>>> As a heads up, our CI went red last night, seems like a panic from
>>> free_initmem? Is this a known issue?
>>
>> Thanks for the heads up.
>>
>> No such issue with either 8xx or book3s/32.
>>
>> I've now been able to reproduce it with bamboo QEMU.
>>
>> Reverting 2efc7c085f05 makes it disappear. I'll investigate.
>>
>
> Ok, I found the problem. virt_to_kpte() lacks a NULL pmd check. I'll
> send a patch for that.
>
> However, if there is no PMD I guess this area is mapped through some
> kind of block mapping. Therefore it should bail out of the function through:
>
> if (v_block_mapped(address))
> return 0;
>
>
> Can someone who knows BOOKE investigate that ?
Not sure we have anyone left?
cheers
next prev parent reply other threads:[~2020-03-10 4:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 19:05 ppc32 panic on boot on linux-next Nick Desaulniers
2020-03-07 8:42 ` Christophe Leroy
2020-03-07 9:00 ` Christophe Leroy
2020-03-10 4:44 ` Michael Ellerman [this message]
2020-03-10 11:06 ` Laurentiu Tudor
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=875zfcked5.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=christophe.leroy@c-s.fr \
--cc=clang-built-linux@googlegroups.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=ndesaulniers@google.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