linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: panand@redhat.com (Pratyush Anand)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM64 kexec/kdump timeline
Date: Mon, 01 Jun 2015 11:55:21 +0530	[thread overview]
Message-ID: <556BFAD1.7010907@redhat.com> (raw)
In-Reply-To: <55664FD9.1090808@codeaurora.org>



On Thursday 28 May 2015 04:44 AM, Timur Tabi wrote:
> On 05/27/2015 11:39 AM, Arnd Bergmann wrote:
>> ACPI support has just been merged and is still experimental. You
>> should be able to boot your system by passing a DT blob at the
>> initial boot that matches your hardware. Can you try if that
>> makes kexec work?
>
> If I had an initial DT blob that matched by hardware, I wouldn't need
> ACPI support!  This is an ARM64 Server system.  There is no device tree
> for the hardware.  Everything is in ACPI.

So what error do you see when you execute kexec.

We had seen a failure with check_cpu_nodes(), when booting with ACPI 
without any DTB.

If you see the similar failure, then can you pl try following:

diff --git a/kexec/arch/arm64/kexec-arm64.c b/kexec/arch/arm64/kexec-arm64.c
index 7b219097dfff..8e085212d8a5 100644
--- a/kexec/arch/arm64/kexec-arm64.c
+++ b/kexec/arch/arm64/kexec-arm64.c
@@ -640,7 +640,7 @@ int arm64_load_other_segments(struct kexec_info *info,
         result =  check_cpu_nodes(&dtb_1, &dtb_2);

         if (result)
-               return result;
+               fprintf(stderr, "kexec: Warning: No device tree 
available.\n");

         /*
          * Put the DTB after the kernel with an alignment of 128 KiB, 
giving

~Pratyush

  parent reply	other threads:[~2015-06-01  6:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <555E37FC.9020800@codeaurora.org>
     [not found] ` <1432239334.1922.7.camel@infradead.org>
2015-05-27  3:08   ` ARM64 kexec/kdump timeline Timur Tabi
2015-05-27  9:38     ` Ard Biesheuvel
2015-05-28  3:22       ` Hanjun Guo
2015-05-28 16:49         ` Geoff Levand
2015-05-27 16:32     ` Geoff Levand
2015-05-27 16:39     ` Arnd Bergmann
2015-05-27 23:14       ` Timur Tabi
2015-05-28  3:52         ` Hanjun Guo
2015-05-28  7:16           ` Ard Biesheuvel
2015-06-01  6:25         ` Pratyush Anand [this message]
2015-06-29 23:20           ` Timur Tabi
2015-07-08 23:03             ` Azriel Samson
     [not found]               ` <CAB5YjtCCO3vB6hrktL9wmpSP6mmtHGd-TQhYK3GnS1eQ7-XU-w@mail.gmail.com>
2015-12-04 21:53                 ` Azriel Samson

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=556BFAD1.7010907@redhat.com \
    --to=panand@redhat.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).