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:18:57 +0000 [thread overview]
Message-ID: <70ff4c17-11eb-66ad-a788-9abc8d329c29@c-s.fr> (raw)
In-Reply-To: <158e1855-62ef-baf6-4fff-f28131a7e095@c-s.fr>
On 05/23/2019 10:05 AM, Christophe Leroy wrote:
>
>
> 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 ?
>
I tried your config in Qemu, looks I'm getting a recursive Oops:
#50 0xc0066af0 in do_exit (code=0xb) at kernel/exit.c:787
#51 0xc0013984 in oops_end (flags=<optimized out>, regs=<optimized out>,
signr=0xb) at arch/powerpc/kernel/traps.c:253
#52 0xc001c30c in handle_page_fault () at arch/powerpc/kernel/entry_32.S:637
#53 0x20302e30 in ?? ()
#54 0xc001cb60 in btext_drawchar (c=0x0) at arch/powerpc/kernel/btext.c:522
#55 0xc00167cc in udbg_write (s=0xc113ae22 <text+2> " 0.000000] CPU: 0
PID: 0 Comm: swapper Not tainted 5.1.0+ #1647\n0\n", n=0x37) at
arch/powerpc/kernel/udbg.c:114
#56 0xc00d43f0 in call_console_drivers (ext_text=<optimized out>,
text=<optimized out>, len=<optimized out>, ext_len=<optimized out>) at
kernel/printk/printk.c:1780
#57 console_unlock () at kernel/printk/printk.c:2462
#58 0xc00d6630 in console_flush_on_panic () at kernel/printk/printk.c:2552
#59 0xc00618a0 in panic (fmt=0xc10f459f <buf+31> "!") at kernel/panic.c:280
#60 0xc0066af0 in do_exit (code=0xb) at kernel/exit.c:787
#61 0xc0013984 in oops_end (flags=<optimized out>, regs=<optimized out>,
signr=0xb) at arch/powerpc/kernel/traps.c:253
#62 0xc001c30c in handle_page_fault () at arch/powerpc/kernel/entry_32.S:637
#63 0x20302e30 in ?? ()
#64 0xc001cb60 in btext_drawchar (c=0x0) at arch/powerpc/kernel/btext.c:522
#65 0xc00167cc in udbg_write (s=0xc113ae22 <text+2> " 0.000000] CPU: 0
PID: 0 Comm: swapper Not tainted 5.1.0+ #1647\n0\n", n=0x45) at
arch/powerpc/kernel/udbg.c:114
#66 0xc00d43f0 in call_console_drivers (ext_text=<optimized out>,
text=<optimized out>, len=<optimized out>, ext_len=<optimized out>) at
kernel/printk/printk.c:1780
#67 console_unlock () at kernel/printk/printk.c:2462
#68 0xc00d6630 in console_flush_on_panic () at kernel/printk/printk.c:2552
#69 0xc00618a0 in panic (fmt=0xc10f459f <buf+31> "!") at kernel/panic.c:280
#70 0xc0066af0 in do_exit (code=0xb) at kernel/exit.c:787
#71 0xc0013984 in oops_end (flags=<optimized out>, regs=<optimized out>,
signr=0xb) at arch/powerpc/kernel/traps.c:253
#72 0xc001c30c in handle_page_fault () at arch/powerpc/kernel/entry_32.S:637
#73 0x20302e30 in ?? ()
#74 0xc001cb60 in btext_drawchar (c=0x0) at arch/powerpc/kernel/btext.c:522
#75 0xc00167cc in udbg_write (s=0xc113ae22 <text+2> " 0.000000] CPU: 0
PID: 0 Comm: swapper Not tainted 5.1.0+ #1647\n0\n", n=0x32) at
arch/powerpc/kernel/udbg.c:114
#76 0xc00d43f0 in call_console_drivers (ext_text=<optimized out>,
text=<optimized out>, len=<optimized out>, ext_len=<optimized out>) at
kernel/printk/printk.c:1780
#77 console_unlock () at kernel/printk/printk.c:2462
#78 0xc00d68d8 in vprintk_emit (facility=<optimized out>,
level=<optimized out>, dict=0x0, dictlen=0x0, fmt=0xc085e4c0
"\001\066printk: %sconsole [%s%d] enabled\n",
args=0xc10cff30) at kernel/printk/printk.c:1985
#79 0xc00d69d8 in vprintk_default (fmt=<optimized out>, args=<optimized
out>) at kernel/printk/printk.c:2012
#80 0xc00d7a40 in vprintk_func (fmt=<optimized out>, args=<optimized
out>) at kernel/printk/printk_safe.c:398
#81 0xc00d2638 in printk (fmt=<optimized out>) at
kernel/printk/printk.c:2045
#82 0xc00d4ef8 in register_console (newcon=0xc0cb9a20 <udbg_console>) at
kernel/printk/printk.c:2777
#83 0xc0b79ed0 in machine_init (dt_ptr=<optimized out>) at
arch/powerpc/kernel/setup_32.c:83
#84 0xc000347c in start_here () at arch/powerpc/kernel/head_32.S:901
Christophe
next prev parent reply other threads:[~2019-05-23 10:21 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
2019-05-23 10:18 ` Christophe Leroy [this message]
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=70ff4c17-11eb-66ad-a788-9abc8d329c29@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox