linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: graeme.gregory@linaro.org (G Gregory)
To: linux-arm-kernel@lists.infradead.org
Subject: [Linaro-acpi] Touching the initrd before paging_init
Date: Tue, 15 Dec 2015 16:13:20 +0000	[thread overview]
Message-ID: <CAGCh1+=eyBstwL7aPTvmRDDEn0GDrf9gTkCKLDBwoNT916vUpg@mail.gmail.com> (raw)
In-Reply-To: <5670339A.7060307@redhat.com>

On 15 December 2015 at 15:36, Jon Masters <jcm@redhat.com> wrote:
> On 12/15/2015 06:19 AM, G Gregory wrote:
>
> <below refers to the GRUB-based approach not the initrd override>
>
>> Tried it, results were not great :-(
>>
>> set root='hd0,gpt2'
>> insmod acpi
>> acpi /DSDT.aml
>> linux /Image-leg earlycon=pl011,0xe1010000 console=ttyAMA0 acpi=force root
>> =/dev/sda2
>
> <snip>
>
>> [    0.000000] PC is at setup_arch+0xfc/0x564
>> [    0.000000] LR is at setup_arch+0xf8/0x564
>
> <snip>
>
> So we unmask SError in setup_arch, which happens now later enough that
> it'll come out of the UART where you can see it. However there are still
> occasions on some of these early platforms where an unhandled SError can
> exist as GRUB exits. I have seen that a number of times on Seattle if
> there's a pending error from one of the IO IP blocks on the SoC You
> might need a firmware update, but can you also confirm that this
> happened reproducibly?
>
It is Seattle RevB I am using and it is repeatable. I have pre-release
firmware on there!

Graeme

  reply	other threads:[~2015-12-15 16:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-13  8:47 Touching the initrd before paging_init Jon Masters
2015-12-07  6:05 ` Mark Rutland
2015-12-13 16:54   ` [Linaro-acpi] " G Gregory
2015-12-13 16:59 ` Leif Lindholm
2015-12-13 21:36   ` Jon Masters
2015-12-13 22:02     ` Jon Masters
2015-12-13 22:15       ` G Gregory
2015-12-13 22:19         ` Jon Masters
2015-12-15 11:19           ` G Gregory
2015-12-15 15:36             ` Jon Masters
2015-12-15 16:13               ` G Gregory [this message]
2015-12-15 16:28                 ` G Gregory
2015-12-15 16:31                   ` Jon Masters
2015-12-15 17:08                     ` G Gregory
2015-12-15 19:22                       ` G Gregory
2015-12-13 22:15       ` Jon Masters
2015-12-15  4:51         ` Jon Masters
2015-12-15 10:14           ` Leif Lindholm
2015-12-15 10:22           ` Mark Rutland
2015-12-15 11:43           ` Måns Rullgård
2015-12-15 15:29             ` Jon Masters
2015-12-15 15:42               ` Mark Rutland
2015-12-15 16:31               ` Måns Rullgård

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='CAGCh1+=eyBstwL7aPTvmRDDEn0GDrf9gTkCKLDBwoNT916vUpg@mail.gmail.com' \
    --to=graeme.gregory@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).