From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Giuseppe Sacco <giuseppe@sguazz.it>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: kernel since 5.6 do not boot anymore on Apple PowerBook
Date: Mon, 24 Aug 2020 07:17:13 +0200 [thread overview]
Message-ID: <f96d336d-fb81-fe9d-9890-db57c6560e85@csgroup.eu> (raw)
In-Reply-To: <c707f59d379a51b83ba52e796d137887219c32fc.camel@sguazz.it>
Hello Giuseppe,
Le 22/08/2020 à 10:28, Giuseppe Sacco a écrit :
> Hello Christophe,
>
> Il giorno ven, 21/08/2020 alle 16.03 +0200, Christophe Leroy ha
> scritto:
> [...]
>>
>> You also said in a previous mail that your original issue also
>> happens
>> when CONFIG_VMAP_STACK is not selected. The above bug being linked
>> to
>> CONFIG_VMAP_STACK, maybe it would be easier to bisect with
>> CONFIG_VMAP_STACK unselected.
>
> I was wrong. Disabling CONFIG_VMAP_STACK led me to all "good" compile
> and bisect ended without finding the culprit commit.
>
> So, I started from scratch: I rebuilt HEAD and found that it does show
> the original problem I am facing, then I rebuilt it without
> CONFIG_VMAP_STACK and found that it does pass (fix?) the problem, since
> kernel continue booting, but then it stops with three Oops related to
> command systemd-udevd.
>
> You may find a video that displays the complete boot, vmlinux, config,
> and system.map files here:
>
The Oopses in the video are fixed in 5.9-rc2, see my response to your
other mail.
So now we know that your kernel doesn't boot when CONFIG_VMAP_STACK is set.
Can you remind the exact problem ?
One common problem with CONFIG_VMAP_STACK is when some drivers are
invalidly using buffers in stack for DMA.
Couldn't try with CONFIG_DEBUG_VIRTUAL (without CONFIG_VMAP_STACK) and
see if it triggers some warnings ?
Thanks
Christophe
next prev parent reply other threads:[~2020-08-24 5:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 12:58 kernel since 5.6 do not boot anymore on Apple PowerBook Giuseppe Sacco
2020-07-07 13:35 ` Christophe Leroy
2020-07-07 14:03 ` Giuseppe Sacco
2020-07-07 14:52 ` Christophe Leroy
2020-07-07 15:34 ` Giuseppe Sacco
2020-07-08 7:59 ` Giuseppe Sacco
2020-07-08 8:38 ` Christophe Leroy
2020-07-08 8:56 ` Giuseppe Sacco
2020-07-08 17:00 ` Giuseppe Sacco
2020-07-08 17:09 ` Christophe Leroy
2020-07-08 17:36 ` Giuseppe Sacco
2020-07-08 18:44 ` Christophe Leroy
2020-08-21 6:55 ` Christophe Leroy
2020-08-21 8:22 ` Giuseppe Sacco
2020-08-21 13:29 ` Christophe Leroy
[not found] ` <8ce38d9bb162268f53a2292a916c44579421e552.camel@sguazz.it>
2020-08-21 14:03 ` Christophe Leroy
2020-08-21 15:44 ` Giuseppe Sacco
2020-08-22 8:28 ` Giuseppe Sacco
2020-08-24 5:17 ` Christophe Leroy [this message]
2020-08-24 20:48 ` Giuseppe Sacco
2020-08-26 10:10 ` Christophe Leroy
2020-08-26 13:53 ` Christophe Leroy
2020-08-26 22:28 ` Giuseppe Sacco
2020-08-27 7:46 ` Giuseppe Sacco
2020-08-27 8:28 ` Giuseppe Sacco
2020-08-27 10:39 ` Christophe Leroy
2020-08-27 14:37 ` Giuseppe Sacco
2020-08-27 18:28 ` Christophe Leroy
2020-08-28 17:07 ` Gabriel Paubert
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=f96d336d-fb81-fe9d-9890-db57c6560e85@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=giuseppe@sguazz.it \
--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).