From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Giuseppe Sacco <giuseppe@sguazz.it>, linuxppc-dev@lists.ozlabs.org
Subject: Re: kernel since 5.6 do not boot anymore on Apple PowerBook
Date: Thu, 27 Aug 2020 20:28:11 +0200 [thread overview]
Message-ID: <3d171af2-90d5-aeb7-6a32-471daceaf5ed@csgroup.eu> (raw)
In-Reply-To: <37c4253abc08ef3e93d67cae5b92252af96fcf65.camel@sguazz.it>
Le 27/08/2020 à 16:37, Giuseppe Sacco a écrit :
> Il giorno gio, 27/08/2020 alle 12.39 +0200, Christophe Leroy ha
> scritto:
>> Hi,
>>
>> Le 27/08/2020 à 10:28, Giuseppe Sacco a écrit :
> [...]
>>> Sorry, I made a mistake. The real problem is down, on the same
>>> function, when it calls low_sleep_handler(). This is where the problem
>>> probably is.
>>
>> Great, you spotted the problem.
>>
>> I see what it is, it is in low_sleep_handler() in
>> arch/powerpc/platforms/powermac/sleep.S
>>
>> All critical registers are saved on the stack. At restore, they are
>> restore BEFORE re-enabling MMU (because they are needed for that). But
>> when we have VMAP_STACK, the stack can hardly be accessed without the
>> MMU enabled. tophys() doesn't work for virtual stack addresses.
>>
>> Therefore, the low_sleep_handler() has to be reworked for using an area
>> in the linear mem instead of the stack.
>
> I am sorry, but I don't know how to fix it. Should I open a bug for
> tracking this problem?
Yes please, at https://github.com/linuxppc/issues/issues
In the meantime, I have sent a patch to disable CONFIG_VMAP_STACK when
CONFIG_ADB_PMU is selected until this is fixed.
Have you tried without CONFIG_ADB_PMU ? Or does it make no sense ?
Christophe
next prev parent reply other threads:[~2020-08-27 18:30 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
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 [this message]
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=3d171af2-90d5-aeb7-6a32-471daceaf5ed@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).