From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: avoid Cortex-A9 livelock on tight dmb loops
Date: Fri, 1 Jun 2018 09:12:06 -0700 [thread overview]
Message-ID: <20180601161206.GW5705@atomide.com> (raw)
In-Reply-To: <20180601155502.GB6920@n2100.armlinux.org.uk>
* Russell King - ARM Linux <linux@armlinux.org.uk> [180601 15:57]:
> On Fri, Jun 01, 2018 at 08:35:12AM -0700, Tony Lindgren wrote:
> > CONFIG_KERNEL_LZMA fails:
> >
> > Try gzip decompression.
> > Try LZMA decompression.
> > lzma_decompress_file: read on /boot/zImage of 65536 bytes failed
> > kernel: 0xb6abb010 kernel_size: 0x43d0f0
> > MEMORY RANGES
> > 0000000080000000-00000000bfdfffff (0)
> > zImage header: 0x016f2818 0x00000000 0x0043d0f0
> > zImage size 0x43d0f0, file size 0x43d0f0
> > Reserved memory ranges
>
> This looks like an old kexec binary as it's missing the output from:
>
> dbgprintf("zImage requires 0x%08llx bytes\n", (unsigned long long)len);
>
> Please can you test with the current version - the official
> repository should now be up to date with my version. Thanks.
OK great. After updating kexec-tools to latest git veresion LZMA
crashkernel now also boots for me :)
Regards,
Tony
next prev parent reply other threads:[~2018-06-01 16:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 11:00 [PATCH v2] ARM: avoid Cortex-A9 livelock on tight dmb loops Russell King
2018-06-01 15:35 ` Tony Lindgren
2018-06-01 15:55 ` Russell King - ARM Linux
2018-06-01 16:12 ` Tony Lindgren [this message]
2018-06-04 9:42 ` Will Deacon
2018-06-04 18:08 ` Russell King - ARM Linux
-- strict thread matches above, loose matches on Subject: below --
2019-01-25 21:03 Russell King
2019-01-25 23:20 ` Tony Lindgren
2019-01-26 21:00 ` Paul Walmsley
2019-01-26 23:51 ` Russell King - ARM Linux admin
2019-01-27 1:15 ` Paul Walmsley
2019-01-27 15:28 ` Russell King - ARM Linux admin
2019-01-31 13:58 ` Will Deacon
2019-01-31 22:58 ` Russell King - ARM Linux admin
2019-02-01 10:19 ` Will Deacon
2019-02-01 21:20 ` Russell King - ARM Linux admin
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=20180601161206.GW5705@atomide.com \
--to=tony@atomide.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).