From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Mathieu Malaterre <malat@debian.org>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Failure to boot G4: dt_headr_start=0x01501000
Date: Thu, 23 May 2019 08:39:19 +0200 [thread overview]
Message-ID: <9b6e027e-0fa0-e088-d9a3-47b005cbc356@c-s.fr> (raw)
In-Reply-To: <CA+7wUsywReRnB1ASdbVrNRkWyPkSKhruBKo57kX--1qmU8hv7A@mail.gmail.com>
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 ?
Did you try latest powerpc/merge branch ?
Can you send your full .config ?
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,
>
next prev parent reply other threads:[~2019-05-23 6:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 12:15 Failure to boot G4: dt_headr_start=0x01501000 Mathieu Malaterre
2019-05-22 12:20 ` Christophe Leroy
2019-05-23 6:24 ` Mathieu Malaterre
2019-05-23 6:39 ` Christophe Leroy [this message]
2019-05-23 8:29 ` Mathieu Malaterre
2019-05-23 8:46 ` Mathieu Malaterre
2019-05-23 8:53 ` Mathieu Malaterre
2019-05-23 9:45 ` Christophe Leroy
2019-05-23 9:59 ` Christophe Leroy
2019-05-23 10:05 ` Christophe Leroy
2019-05-23 10:18 ` Christophe Leroy
2019-05-23 10:16 ` Mathieu Malaterre
2019-05-23 18:08 ` Christophe Leroy
2019-05-24 7:34 ` Mathieu Malaterre
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=9b6e027e-0fa0-e088-d9a3-47b005cbc356@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=malat@debian.org \
/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