linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Erhard Furtner <erhard_f@mailbox.org>,
	Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: KASAN debug kernel fails to boot at early stage when CONFIG_SMP=y is set (kernel 6.5-rc5, PowerMac G4 3,6)
Date: Fri, 18 Aug 2023 09:13:21 +1000	[thread overview]
Message-ID: <87y1i9clf2.fsf@mail.lhotse> (raw)
In-Reply-To: <20230817203202.2b4c273c@yea>

Erhard Furtner <erhard_f@mailbox.org> writes:
> On Wed, 16 Aug 2023 15:56:26 +0000
> Christophe Leroy <christophe.leroy@csgroup.eu> wrote:
>
>> Not sure this is the reason of the crash. Just that it disables bootx 
>> console here and doesn't re-enable any console before the crash.
>> 
>> Could you move the call to btext_unmap() after the call to 
>> memblock_set_current_limit(lowmem_end_addr); at the end of function 
>> MMU_init()
>> 
>> And redo the test, still with my patch applied for the additional pr_infos.
>
> I moved btext_unmap() as you suggested and the order of functions displayed changed accordingly. Now the freeze happens later but still after the 1st call to btext_unmap():
>
> [    0.000000] printk: bootconsole [udbg0] enabled
> [    0.000000] Total memory = 2048MB; using 4096kB for hash table
> [    0.000000] mapin_ram:125
> [    0.000000] mmu_mapin_ram:169 0 30000000 1400000 2000000
> [    0.000000] __mmu_mapin_ram:146 0 1400000
> [    0.000000] __mmu_mapin_ram:155 1400000
> [    0.000000] __mmu_mapin_ram:146 1400000 30000000
> [    0.000000] __mmu_mapin_ram:155 20000000
> [    0.000000] __mapin_ram_chunk:107 20000000 30000000
> [    0.000000] __mapin_ram_chunk:117
> [    0.000000] mapin_ram:134
> [    0.000000] kasan_mmu_init:129
> [    0.000000] kasan_mmu_init:132 0
> [    0.000000] kasan_mmu_init:137
> [    0.000000] setup_kuap:23
> [    0.000000] setup_kuap:25
> [    0.000000] setup_kuap:30
> [    0.000000] setup_kuap:35
> [    0.000000] Activating Kernel Userspace Access Protection
> [    0.000000] setup_kuap:40
> [    0.000000] Activating Kernel Userspace Execution Prevention
> [    0.000000] btext_unmap:129

Try just removing the call to btext_unmap() entirely and see how far it goes?

cheers

  reply	other threads:[~2023-08-17 23:14 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 23:48 KASAN debug kernel fails to boot at early stage when CONFIG_SMP=y is set (kernel 6.5-rc5, PowerMac G4 3,6) Erhard Furtner
2023-08-11  6:45 ` Christophe Leroy
2023-08-13 19:38   ` Erhard Furtner
2023-08-14  9:40     ` Christophe Leroy
2023-08-14 17:27       ` Erhard Furtner
2023-08-15 17:21         ` [PATCH] Add pr_info() traces for investigation Christophe Leroy
2023-08-15 17:25         ` KASAN debug kernel fails to boot at early stage when CONFIG_SMP=y is set (kernel 6.5-rc5, PowerMac G4 3,6) Christophe Leroy
2023-08-15 20:01           ` Erhard Furtner
2023-08-16 15:56             ` Christophe Leroy
2023-08-17 18:32               ` Erhard Furtner
2023-08-17 23:13                 ` Michael Ellerman [this message]
2023-08-18  9:16                   ` Erhard Furtner
2023-08-18 15:47                     ` Christophe Leroy
2023-08-18 16:23                       ` Erhard Furtner
2023-08-22  7:31                         ` Christophe Leroy
2023-08-24  0:00                           ` Erhard Furtner
2023-08-24 11:36                             ` Michael Ellerman
2023-08-27 23:17                               ` Erhard Furtner
2023-08-31  5:32                                 ` Christophe Leroy
2023-08-31 22:44                                   ` Erhard Furtner
2023-09-01  7:43                                     ` Christophe Leroy
2023-09-03 21:06                                       ` Erhard Furtner
2023-09-04 14:48                                         ` Christophe Leroy
2023-09-04 14:55                                           ` Christophe Leroy
2023-09-04 21:32                                             ` Erhard Furtner
2023-09-12  0:11                                             ` Erhard Furtner
2023-09-12  7:47                                               ` Christophe Leroy
2023-09-12 15:59                                                 ` Erhard Furtner
2023-09-12 17:39                                                   ` Christophe Leroy
2023-09-12 20:09                                                     ` Erhard Furtner
2023-09-13  5:28                                                       ` Christophe Leroy
2023-09-14  4:54                                                     ` Christophe Leroy
2023-09-14 12:33                                                       ` Erhard Furtner
2024-02-28 23:55                                                       ` Erhard Furtner

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=87y1i9clf2.fsf@mail.lhotse \
    --to=mpe@ellerman.id.au \
    --cc=christophe.leroy@csgroup.eu \
    --cc=erhard_f@mailbox.org \
    --cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).