* ppc32 panic on boot on linux-next
@ 2020-03-06 19:05 Nick Desaulniers
2020-03-07 8:42 ` Christophe Leroy
0 siblings, 1 reply; 5+ messages in thread
From: Nick Desaulniers @ 2020-03-06 19:05 UTC (permalink / raw)
To: Michael Ellerman; +Cc: clang-built-linux, linuxppc-dev
As a heads up, our CI went red last night, seems like a panic from
free_initmem? Is this a known issue?
https://travis-ci.com/ClangBuiltLinux/continuous-integration/jobs/295304058?utm_medium=notification&utm_source=email
--
Thanks,
~Nick Desaulniers
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: ppc32 panic on boot on linux-next
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
0 siblings, 1 reply; 5+ messages in thread
From: Christophe Leroy @ 2020-03-07 8:42 UTC (permalink / raw)
To: Nick Desaulniers, Michael Ellerman; +Cc: clang-built-linux, linuxppc-dev
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.
Christophe
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: ppc32 panic on boot on linux-next
2020-03-07 8:42 ` Christophe Leroy
@ 2020-03-07 9:00 ` Christophe Leroy
2020-03-10 4:44 ` Michael Ellerman
0 siblings, 1 reply; 5+ messages in thread
From: Christophe Leroy @ 2020-03-07 9:00 UTC (permalink / raw)
To: Nick Desaulniers, Michael Ellerman; +Cc: clang-built-linux, linuxppc-dev
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 ?
Christophe
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: ppc32 panic on boot on linux-next
2020-03-07 9:00 ` Christophe Leroy
@ 2020-03-10 4:44 ` Michael Ellerman
2020-03-10 11:06 ` Laurentiu Tudor
0 siblings, 1 reply; 5+ messages in thread
From: Michael Ellerman @ 2020-03-10 4:44 UTC (permalink / raw)
To: Christophe Leroy, Nick Desaulniers; +Cc: clang-built-linux, linuxppc-dev
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: ppc32 panic on boot on linux-next
2020-03-10 4:44 ` Michael Ellerman
@ 2020-03-10 11:06 ` Laurentiu Tudor
0 siblings, 0 replies; 5+ messages in thread
From: Laurentiu Tudor @ 2020-03-10 11:06 UTC (permalink / raw)
To: linuxppc-dev
Hello,
On 10.03.2020 06:44, Michael Ellerman wrote:
> 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
>
With latest linux-next, PPC32 Book-E boots to prompt:
https://paste.debian.net/1134272/
---
Best Regards, Laurentiu
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2020-03-10 11:12 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2020-03-10 11:06 ` Laurentiu Tudor
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.