Re: Failure to boot G4: dt_headr_start=0x01501000

[Christophe Leroy <christophe.leroy@c-s.fr>]

Le 23/05/2019 à 10:53, Mathieu Malaterre a écrit :
> On Thu, May 23, 2019 at 10:29 AM Mathieu Malaterre <malat@debian.org> wrote:
>>
>> On Thu, May 23, 2019 at 8:39 AM Christophe Leroy
>> <christophe.leroy@c-s.fr> wrote:
>>>
>>> Salut Mathieu,
>>>
>>> Le 23/05/2019 à 08:24, Mathieu Malaterre a écrit :
>>>> Salut Christophe,
>>>>
>>>> On Wed, May 22, 2019 at 2:20 PM Christophe Leroy
>>>> <christophe.leroy@c-s.fr> wrote:
>>>>>
>>>>>
>>>>>
>>>>> Le 22/05/2019 à 14:15, Mathieu Malaterre a écrit :
>>>>>> Hi all,
>>>>>>
>>>>>> I have not boot my G4 in a while, today using master here is what I see:
>>>>>>
>>>>>> done
>>>>>> Setting btext !
>>>>>> W=640 H=488 LB=768 addr=0x9c008000
>>>>>> copying OF device tree...
>>>>>> starting device tree allocs at 01401000
>>>>>> otloc_up(00100000, 0013d948)
>>>>>>      trying: 0x01401000
>>>>>>      trying: 0x01501000
>>>>>>     -› 01501000
>>>>>>      alloc_bottom : 01601000
>>>>>>      alloc_top    : 20000000
>>>>>>      alloc_top_hi : 20000000
>>>>>>      nmo_top      : 20000000
>>>>>>      ram_top      : 20000000
>>>>>> Building dt strings...
>>>>>> Building dt structure...
>>>>>> reserved memory map:
>>>>>>      00d40000 - 006c1000
>>>>>> Device tree strings 0x01502000 -> 0x00000007
>>>>>> Device tree struct 0x01503000 -> 0x00000007
>>>>>> Quiescing Open Firmware ...
>>>>>> Booting Linux via __start() @ 0x001400000
>>>>>> ->dt_headr_start=0x01501000
>>>>>>
>>>>>> Any suggestions before I start a bisect ?
>>>>>>
>>>>>
>>>>> Have you tried without CONFIG_PPC_KUEP and CONFIG_PPC_KUAP ?
>>>>
>>>> Using locally:
>>>>
>>>> diff --git a/arch/powerpc/configs/g4_defconfig
>>>> b/arch/powerpc/configs/g4_defconfig
>>>> index 14d0376f637d..916bce8ce9c3 100644
>>>> --- a/arch/powerpc/configs/g4_defconfig
>>>> +++ b/arch/powerpc/configs/g4_defconfig
>>>> @@ -32,6 +32,8 @@ CONFIG_USERFAULTFD=y
>>>>    # CONFIG_COMPAT_BRK is not set
>>>>    CONFIG_PROFILING=y
>>>>    CONFIG_G4_CPU=y
>>>> +# CONFIG_PPC_KUEP is not set
>>>> +# CONFIG_PPC_KUAP is not set
>>>>    CONFIG_PANIC_TIMEOUT=0
>>>>    # CONFIG_PPC_CHRP is not set
>>>>    CONFIG_CPU_FREQ=y
>>>>
>>>>
>>>> Leads to almost the same error (some values have changed):
>>>
>>> Ok.
>>>
>>> When you say you are using 'master', what do you mean ? Can you give the
>>> commit Id ?
>>>
>>> Does it boots with Kernel 5.1.4 ?
>>
>> I was able to boot v5.1:
>>
>> $ dmesg | head
>> [    0.000000] printk: bootconsole [udbg0] enabled
>> [    0.000000] Total memory = 512MB; using 1024kB for hash table (at (ptrval))
>> [    0.000000] Linux version 5.1.0+ (malat@debian.org) (gcc version
>> 8.3.0 (Debian 8.3.0-7)) #8 Thu May 23 06:26:38 UTC 2019
>>
>> Commit id is:
>>
>> e93c9c99a629 (tag: v5.1) Linux 5.1
>>
>>> Did you try latest powerpc/merge branch ?
>>
>> Will try that next.
> 
> I confirm powerpc/merge does not boot for me (same config). Commit id:
> 
> a27eaa62326d (powerpc/merge) Automatic merge of branches 'master',
> 'next' and 'fixes' into merge

I see in the config you sent me that you have selected CONFIG_KASAN, 
which is a big new stuff.

Can you try without it ?

Christophe

> 
> 
>>> Can you send your full .config ?
>>
>> Config is attached.
>>
>> Thanks,
>>
>>> Christophe
>>>
>>>>
>>>> done
>>>> Setting btext !
>>>> W=640 H=488 LB=768 addr=0x9c008000
>>>> copying OF device tree...
>>>> starting device tree allocs at 01300000
>>>> alloc_up(00100000, 0013d948)
>>>>     trying: 0x01300000
>>>>     trying: 0x01400000
>>>>    -› 01400000
>>>>     alloc_bottom : 01500000
>>>>     alloc_top    : 20000000
>>>>     alloc_top_hi : 20000000
>>>>     nmo_top      : 20000000
>>>>     ram_top      : 20000000
>>>> Building dt strings...
>>>> Building dt structure...
>>>> reserved memory map:
>>>>     00c40000 - 006c0000
>>>> Device tree strings 0x01401000 -> 0x00000007
>>>> Device tree struct 0x01402000 -> 0x00000007
>>>> Quiescing Open Firmware ...
>>>> Booting Linux via __start() @ 0x001400000
>>>> ->dt_headr_start=0x01400000
>>>>
>>>> Thanks anyway,
>>>>