From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
mripard@kernel.org, wens@csie.org, ebiederm@xmission.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: Trying to kexec on Allwinner A80
Date: Tue, 7 Apr 2020 11:01:00 +0100 [thread overview]
Message-ID: <20200407100100.GJ25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200407093253.GA4630@Red>
On Tue, Apr 07, 2020 at 11:32:53AM +0200, Corentin Labbe wrote:
> On Tue, Apr 07, 2020 at 09:12:57AM +0100, Russell King - ARM Linux admin wrote:
> > That was not reflected in the command lines given to kexec that you
> > quoted previously, so I'm now wondering if you're giving me the full
> > information.
> >
> > In any case, based on the information you've supplied thus far, I have
> > no further suggetsions to make.
> >
>
> Sorry I have added --debug after my initial mail.
> But I am surprised that no debug output like "MEMORY RANGES" is done (like I got in my first try).
> I have started to patch kexec-tools to check it, and debug is enabled.
> Furthermore, I got in locate_hole:237 memory_ranges=0.
> So the memory region in struct kexec_info is not initialized (and so cannot be printed)
The memory region information is initialised by get_memory_ranges()
in kexec/arch/arm/kexec-arm.c, which reads /proc/iomem.
That is called from my_load(), which checks that info.memory_ranges
is non-zero. If it's zero, it errors out with "Could not get memory
layout".
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 10.2Mbps down 587kbps up
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
mripard@kernel.org, wens@csie.org, ebiederm@xmission.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: Trying to kexec on Allwinner A80
Date: Tue, 7 Apr 2020 11:01:00 +0100 [thread overview]
Message-ID: <20200407100100.GJ25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200407093253.GA4630@Red>
On Tue, Apr 07, 2020 at 11:32:53AM +0200, Corentin Labbe wrote:
> On Tue, Apr 07, 2020 at 09:12:57AM +0100, Russell King - ARM Linux admin wrote:
> > That was not reflected in the command lines given to kexec that you
> > quoted previously, so I'm now wondering if you're giving me the full
> > information.
> >
> > In any case, based on the information you've supplied thus far, I have
> > no further suggetsions to make.
> >
>
> Sorry I have added --debug after my initial mail.
> But I am surprised that no debug output like "MEMORY RANGES" is done (like I got in my first try).
> I have started to patch kexec-tools to check it, and debug is enabled.
> Furthermore, I got in locate_hole:237 memory_ranges=0.
> So the memory region in struct kexec_info is not initialized (and so cannot be printed)
The memory region information is initialised by get_memory_ranges()
in kexec/arch/arm/kexec-arm.c, which reads /proc/iomem.
That is called from my_load(), which checks that info.memory_ranges
is non-zero. If it's zero, it errors out with "Could not get memory
layout".
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 10.2Mbps down 587kbps up
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
mripard@kernel.org, wens@csie.org, ebiederm@xmission.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: Trying to kexec on Allwinner A80
Date: Tue, 7 Apr 2020 11:01:00 +0100 [thread overview]
Message-ID: <20200407100100.GJ25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200407093253.GA4630@Red>
On Tue, Apr 07, 2020 at 11:32:53AM +0200, Corentin Labbe wrote:
> On Tue, Apr 07, 2020 at 09:12:57AM +0100, Russell King - ARM Linux admin wrote:
> > That was not reflected in the command lines given to kexec that you
> > quoted previously, so I'm now wondering if you're giving me the full
> > information.
> >
> > In any case, based on the information you've supplied thus far, I have
> > no further suggetsions to make.
> >
>
> Sorry I have added --debug after my initial mail.
> But I am surprised that no debug output like "MEMORY RANGES" is done (like I got in my first try).
> I have started to patch kexec-tools to check it, and debug is enabled.
> Furthermore, I got in locate_hole:237 memory_ranges=0.
> So the memory region in struct kexec_info is not initialized (and so cannot be printed)
The memory region information is initialised by get_memory_ranges()
in kexec/arch/arm/kexec-arm.c, which reads /proc/iomem.
That is called from my_load(), which checks that info.memory_ranges
is non-zero. If it's zero, it errors out with "Could not get memory
layout".
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 10.2Mbps down 587kbps up
next prev parent reply other threads:[~2020-04-07 10:01 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 8:27 Trying to kexec on Allwinner A80 Corentin Labbe
2020-04-06 8:27 ` Corentin Labbe
2020-04-06 8:27 ` Corentin Labbe
2020-04-06 9:16 ` Russell King - ARM Linux admin
2020-04-06 9:16 ` Russell King - ARM Linux admin
2020-04-06 9:16 ` Russell King - ARM Linux admin
2020-04-06 9:25 ` Corentin Labbe
2020-04-06 9:25 ` Corentin Labbe
2020-04-06 9:25 ` Corentin Labbe
2020-04-06 9:37 ` Russell King - ARM Linux admin
2020-04-06 9:37 ` Russell King - ARM Linux admin
2020-04-06 9:37 ` Russell King - ARM Linux admin
2020-04-06 20:10 ` Corentin Labbe
2020-04-06 20:10 ` Corentin Labbe
2020-04-06 20:10 ` Corentin Labbe
2020-04-07 7:31 ` Russell King - ARM Linux admin
2020-04-07 7:31 ` Russell King - ARM Linux admin
2020-04-07 7:31 ` Russell King - ARM Linux admin
2020-04-07 8:01 ` Corentin Labbe
2020-04-07 8:01 ` Corentin Labbe
2020-04-07 8:01 ` Corentin Labbe
2020-04-07 8:12 ` Russell King - ARM Linux admin
2020-04-07 8:12 ` Russell King - ARM Linux admin
2020-04-07 8:12 ` Russell King - ARM Linux admin
2020-04-07 9:32 ` Corentin Labbe
2020-04-07 9:32 ` Corentin Labbe
2020-04-07 9:32 ` Corentin Labbe
2020-04-07 10:01 ` Russell King - ARM Linux admin [this message]
2020-04-07 10:01 ` Russell King - ARM Linux admin
2020-04-07 10:01 ` Russell King - ARM Linux admin
2020-04-07 10:02 ` Russell King - ARM Linux admin
2020-04-07 10:02 ` Russell King - ARM Linux admin
2020-04-07 10:02 ` Russell King - ARM Linux admin
2020-04-07 10:19 ` Russell King - ARM Linux admin
2020-04-07 10:19 ` Russell King - ARM Linux admin
2020-04-07 10:19 ` Russell King - ARM Linux admin
2020-04-07 11:34 ` Corentin Labbe
2020-04-07 11:34 ` Corentin Labbe
2020-04-07 11:34 ` Corentin Labbe
2020-04-07 12:22 ` Russell King - ARM Linux admin
2020-04-07 12:22 ` Russell King - ARM Linux admin
2020-04-07 12:22 ` Russell King - ARM Linux admin
2020-04-07 13:05 ` Corentin Labbe
2020-04-07 13:05 ` Corentin Labbe
2020-04-07 13:05 ` Corentin Labbe
2020-04-07 13:26 ` Russell King - ARM Linux admin
2020-04-07 13:26 ` Russell King - ARM Linux admin
2020-04-07 13:26 ` Russell King - ARM Linux admin
2020-04-07 13:48 ` Corentin Labbe
2020-04-07 13:48 ` Corentin Labbe
2020-04-07 13:48 ` Corentin Labbe
2020-04-07 18:17 ` Russell King - ARM Linux admin
2020-04-07 18:17 ` Russell King - ARM Linux admin
2020-04-07 18:17 ` Russell King - ARM Linux admin
2020-04-08 8:40 ` Corentin Labbe
2020-04-08 8:40 ` Corentin Labbe
2020-04-08 8:40 ` Corentin Labbe
2020-04-08 9:33 ` Russell King - ARM Linux admin
2020-04-08 9:33 ` Russell King - ARM Linux admin
2020-04-08 9:33 ` Russell King - ARM Linux admin
2020-04-08 15:24 ` Corentin Labbe
2020-04-08 15:24 ` Corentin Labbe
2020-04-08 15:24 ` Corentin Labbe
2020-04-08 16:16 ` Russell King - ARM Linux admin
2020-04-08 16:16 ` Russell King - ARM Linux admin
2020-04-08 16:16 ` Russell King - ARM Linux admin
2025-04-13 8:52 ` Corentin Labbe
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=20200407100100.GJ25745@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=clabbe.montjoie@gmail.com \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=wens@csie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.