All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Mathieu Malaterre <malat@debian.org>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Daniel Axtens <dja@axtens.net>
Subject: Re: Failure to boot G4: dt_headr_start=0x01501000
Date: Thu, 23 May 2019 10:05:57 +0000	[thread overview]
Message-ID: <158e1855-62ef-baf6-4fff-f28131a7e095@c-s.fr> (raw)
In-Reply-To: <ba3a1c25-72ce-cfb4-67ac-df07584f57f5@c-s.fr>



On 05/23/2019 09:59 AM, Christophe Leroy wrote:
> 
> 
> On 05/23/2019 09:45 AM, Christophe Leroy wrote:
>>
>>
>> Le 23/05/2019 à 10:53, Mathieu Malaterre a écrit :
>>>> 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 ?
> 
> While building with your config, I get a huge amount of:
> 
> ppc-linux-ld: warning: orphan section `.data..LASAN0' from 
> `lib/xarray.o' being placed in section `.data..LASAN0'.
>    SORTEX  vmlinux
> 
> 
> 
> I see you have also selected CONFIG_LD_DEAD_CODE_DATA_ELIMINATION=y
> 
> I guess nobody have never tried both this and CONFIG_KASAN together on 
> ppc32. I'll give it a try.


And you also have CONFIG_FTRACE.

In a recent patch implementing KASAN on PPC64, Daniel says that KASAN 
and FTRACE don't go together well 
(https://patchwork.ozlabs.org/patch/1103826/)

If you find out that it works without KASAN, can you then try with KASAN 
but without FTRACE ?

Christophe


  reply	other threads:[~2019-05-23 10:07 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
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 [this message]
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=158e1855-62ef-baf6-4fff-f28131a7e095@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=dja@axtens.net \
    --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 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.