From: Giuseppe Sacco <giuseppe@sguazz.it>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: kernel since 5.6 do not boot anymore on Apple PowerBook
Date: Fri, 21 Aug 2020 17:44:18 +0200 [thread overview]
Message-ID: <ae2c93c55a785b5f450fe796619d2688f393fa30.camel@sguazz.it> (raw)
In-Reply-To: <5158eae8-6809-ae07-0d16-58f2a766f534@csgroup.eu>
Hello,
Il giorno ven, 21/08/2020 alle 16.03 +0200, Christophe Leroy ha
scritto:
[...]
> Thanks.
>
> The Oops in the video shows that the issue is at 0x1bcac and msr
> value
> shows that Instruction MMU is disabled. So this corresponds to
> address
> 0xc001bcac. In the vmlinux you sent me this address is in
> power_save_ppc32_restore()
>
> This issue is fixed by
> https://patchwork.ozlabs.org/project/linuxppc-dev/patch/7bce32ccbab3ba3e3e0f27da6961bf6313df97ed.1581663140.git.christophe.leroy@c-s.fr/
>
>
> 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 rebuilt the same kernel that I would otherwise have skipped because
of the other bug, and it worked, indeed.
I will continue my "bisect quest" unselecting VMAP_STACK in order to
speed up the bisecting.
Thank you very much,
Giuseppe
next prev parent reply other threads:[~2020-08-21 15:56 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 [this message]
2020-08-22 8:28 ` Giuseppe Sacco
2020-08-24 5:17 ` Christophe Leroy
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=ae2c93c55a785b5f450fe796619d2688f393fa30.camel@sguazz.it \
--to=giuseppe@sguazz.it \
--cc=christophe.leroy@csgroup.eu \
--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).