From: Vicente Bergas <vicencb@gmail.com>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Matthias Brugger <mbrugger@suse.com>,
Heiko Stuebner <heiko@sntech.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: kexec on rk3399
Date: Mon, 22 Jul 2019 19:05:37 +0200 [thread overview]
Message-ID: <d5959b93-40ce-455c-877e-c661a3f22351@gmail.com> (raw)
In-Reply-To: <91c53121-9041-e8a2-97a2-5b5626e24c6e@arm.com>
On Monday, July 22, 2019 4:54:41 PM CEST, Marc Zyngier wrote:
> On 22/07/2019 15:31, Vicente Bergas wrote:
>> Hi, i have been running linux on rk3399 booted with kexec fine until 5.2
>> From 5.2 onwards, there are memory corruption issues as reported here:
>> http://lkml.iu.edu/hypermail/linux/kernel/1906.2/07211.html
>> kexec has been identified as the principal reason for the issues.
>>
>> It turns out that kexec has never worked reliably on this platform, ...
>
> Not the most trusted version, but hey, why not...
>
>> 2.- Kexec into v5.2.2
>> 3.- The kernel reports nothing (earlycon not enabled) and does not boot.
>> The same kernel v5.2.2 works fine when booted without kexec.
>
> Can you please enable earlycon and let us know how far it goes? Your
> previous reports hinting at runtime memory corruption, but this seems to
> be much more radical...
Details on previous email, but basically, earlycon affects reproducibility.
If it is a runtime memory corruption, what are we hunting for? an issue in
the kernel before kexec or in the kernel after kexec?
> FWIW, I was able to kexec using 5.2-rcx (for values of x around 6) on a
> NanoPC-T4, using a mainline u-boot and firmware.
>
> Thanks,
>
> M.
Regards,
Vicenç.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-07-22 17:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 14:31 kexec on rk3399 Vicente Bergas
2019-07-22 14:46 ` Will Deacon
2019-07-22 16:08 ` Vicente Bergas
2019-07-22 14:47 ` Matthias Brugger
2019-07-22 16:56 ` Vicente Bergas
2019-07-22 14:54 ` Marc Zyngier
2019-07-22 17:05 ` Vicente Bergas [this message]
2019-07-22 17:35 ` Robin Murphy
2019-07-22 18:53 ` Vicente Bergas
2019-07-23 13:32 ` Robin Murphy
2019-08-14 12:53 ` Vicente Bergas
2019-08-14 13:06 ` Felipe Balbi
2019-08-14 13:15 ` Vicente Bergas
2019-08-15 6:00 ` Felipe Balbi
2019-08-14 13:12 ` Robin Murphy
2019-08-15 1:15 ` Vicente Bergas
2019-08-15 6:06 ` Felipe Balbi
2019-08-15 11:09 ` Robin Murphy
2019-08-17 17:41 ` [PATCH] usb: dwc3: Add shutdown to platform_driver Vicente Bergas
2019-08-27 11:45 ` Vicente Bergas
2019-08-27 11:53 ` Felipe Balbi
2019-08-27 12:16 ` Vicente Bergas
2019-09-09 15:07 ` Vicente Bergas
2019-10-23 6:31 ` Felipe Balbi
2019-10-24 12:15 ` Vicente Bergas
2019-10-25 10:25 ` Felipe Balbi
2019-10-25 10:42 ` Vicente Bergas
2019-09-19 11:36 ` Vicente Bergas
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=d5959b93-40ce-455c-877e-c661a3f22351@gmail.com \
--to=vicencb@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=mbrugger@suse.com \
--cc=will.deacon@arm.com \
/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).