linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: Problem booting a PowerBook G4 Aluminum after commit cd08f109 with CONFIG_VMAP_STACK=y
Date: Tue, 11 Feb 2020 07:55:25 +0100	[thread overview]
Message-ID: <f35ea4e6-7c54-6acc-7d91-3a6eea56133c@c-s.fr> (raw)
In-Reply-To: <6a1802b8-c6a7-d091-1036-689e089b786f@lwfinger.net>



Le 10/02/2020 à 13:55, Larry Finger a écrit :
> On 2/9/20 12:19 PM, Christophe Leroy wrote:
>> Do you have CONFIG_TRACE_IRQFLAGS in your config ?
>> If so, can you try the patch below ?
>>
>> https://patchwork.ozlabs.org/patch/1235081/
>>
>> Otherwise, can you send me your .config and tell me exactly where it 
>> stops during the boot.
> 
> Christophe,
> 
> That patch did not work. My .config is attached.
> 
> It does boot if CONFIG_VMAP_STACK is not set.
> 
> The console display ends with the "DMA ranges" output. A screen shot is 
> also appended.
> 
> Larry
> 

Hi,

I tried your config under QEMU, it works.

In fact your console display is looping on itself, it ends at "printk: 
bootconsole [udbg0] disabled".

Looks like you get stuck at the time of switching to graphic mode. Need 
to understand why.

Christophe

       reply	other threads:[~2020-02-11  6:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f7565b89-c8b2-d2e7-929e-4b1abf72fc63@lwfinger.net>
     [not found] ` <159ed5d8-376b-1642-fb4b-01406d671cf1@c-s.fr>
     [not found]   ` <6a1802b8-c6a7-d091-1036-689e089b786f@lwfinger.net>
2020-02-11  6:55     ` Christophe Leroy [this message]
2020-02-11 16:06       ` Problem booting a PowerBook G4 Aluminum after commit cd08f109 with CONFIG_VMAP_STACK=y Larry Finger
2020-02-11 19:23         ` Christophe Leroy
     [not found]           ` <1787b507-dfbf-7801-f7d4-a1547e9bd588@lwfinger.net>
2020-02-13 11:23             ` Christophe Leroy
     [not found]           ` <7f63e8a8-95c5-eeca-dc79-3c13f4d98d39@lwfinger.net>
2020-02-13 14:43             ` RESEND: " Christophe Leroy
2020-02-13 23:09               ` Larry Finger
2020-02-14  6:24                 ` Christophe Leroy
2020-02-14 11:02                   ` Christophe Leroy
2020-02-14 18:20                   ` Larry Finger
2020-02-14 18:24                   ` Larry Finger
2020-02-14 19:35                     ` Christophe Leroy
2020-02-15  2:42                       ` Larry Finger
2020-02-15  7:55                         ` Christophe Leroy

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=f35ea4e6-7c54-6acc-7d91-3a6eea56133c@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linuxppc-dev@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).