linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: v4.7-rc2 kernel fails to boot when acpi=force
Date: Tue, 7 Jun 2016 11:23:17 +0100	[thread overview]
Message-ID: <20160607102317.GC2633@leverpostej> (raw)
In-Reply-To: <125b057c-647b-9db7-11b4-4b7123e4b80a@riken.jp>

On Tue, Jun 07, 2016 at 05:06:39PM +0900, Itaru Kitayama wrote:
> Upstream v4.7-rc2 kernel does not boot if parameter acpi is set to force
> on Overdrive. (acpi=off gets to the prompt)

Did acpi=force work on this board with an earlier kernel (e.g. v4.6)?

> When set to force it doesn't get to the Linux boot process and stalls.

What output do you get before it stalls?

I assume that you at least have output from the EFI stub?

Which command line options are you passing?

If you get nothing after the stub, try also passing:

earlycon=pl011,0xe1010000

Which may give an indication of what's going on.

> Here's the BIOS info:
> 
> Version 2.17.1249. Copyright (C) 2015 American Megatrends, Inc.
> BIOS Date: 09/03/2015 13:52:32 Ver: ROD0084E00

I don't know if the FW from a year ago provided everything necessary. It
may be something like the SPCR is simply missing, and there's no
console= passed to the kernel.

Thanks,
Mark.

  reply	other threads:[~2016-06-07 10:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07  8:06 v4.7-rc2 kernel fails to boot when acpi=force Itaru Kitayama
2016-06-07 10:23 ` Mark Rutland [this message]
2016-06-07 10:53   ` Itaru Kitayama
2016-06-07 11:05     ` Mark Rutland
2016-06-07 12:05       ` G Gregory
2016-06-08  9:28       ` Itaru Kitayama
2016-06-08  9:47         ` Mark Rutland
2016-06-08 10:07           ` Itaru Kitayama
2016-06-08 10:48             ` Mark Rutland
2016-06-09 13:11           ` Itaru Kitayama

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=20160607102317.GC2633@leverpostej \
    --to=mark.rutland@arm.com \
    --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).