From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Erhard Furtner <erhard_f@mailbox.org>,
Michael Ellerman <mpe@ellerman.id.au>
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 15:47:38 +0000 [thread overview]
Message-ID: <fcdf2bf7-0834-b27f-4d24-28e05815ee6f@csgroup.eu> (raw)
In-Reply-To: <20230818111641.7f680ce7@yea>
Le 18/08/2023 à 11:16, Erhard Furtner a écrit :
> On Fri, 18 Aug 2023 09:13:21 +1000
> Michael Ellerman <mpe@ellerman.id.au> wrote:
>
>> Try just removing the call to btext_unmap() entirely and see how far it goes?
>>
>> cheers
>
> Ok, I commented out btext_unmap() in MMU_init() and the freeze just happens before the "Linux version 6.5.0-rc6-PMacG4-dirty [...]"-line:
>
> [ 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
>
> I also tried a kernel without KUAP/KUEP getting this:
>
> [ 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
>
> Here too the freeze just happens before the line "Linux version 6.5.0-rc6-PMacG4-dirty [...]" in dmesg.
>
> Attached is (warm boot) dmesg without KUAP/KUEP.
I'm wondering if the problem is just linked to the kernel being built
with CONFIG_SMP or if it is the actual startup of a secondary CPU that
cause the freeze.
Please leave the btext_unmap() in place because I think it is important
to keep it, and start the kernel with the following parameter:
nr_cpus=1
Thanks
Christophe
next prev parent reply other threads:[~2023-08-18 15:48 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
2023-08-18 9:16 ` Erhard Furtner
2023-08-18 15:47 ` Christophe Leroy [this message]
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=fcdf2bf7-0834-b27f-4d24-28e05815ee6f@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=erhard_f@mailbox.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).