From: Guillaume Tucker <firstname.lastname@example.org>
To: Mike Rapoport <email@example.com>
Cc: Andrea Arcangeli <firstname.lastname@example.org>,
Andrew Morton <email@example.com>,
Stephen Rothwell <firstname.lastname@example.org>,
Mike Rapoport <email@example.com>, Baoquan He <firstname.lastname@example.org>
Subject: Re: kernelci/staging-next bisection: sleep.login on rk3288-rock2-square #2286-staging
Date: Fri, 18 Dec 2020 21:59:26 +0000 [thread overview]
Message-ID: <email@example.com> (raw)
On 13/12/2020 08:23, Mike Rapoport wrote:
> Hi Guillaume,
> On Fri, Dec 11, 2020 at 09:53:46PM +0000, Guillaume Tucker wrote:
>> Hi Mike,
>> Please see the bisection report below about a boot failure on
>> rk3288 with next-20201210.
>> Reports aren't automatically sent to the public while we're
>> trialing new bisection features on kernelci.org but this one
>> looks valid.
>> There's nothing in the serial console log, probably because it's
>> crashing too early during boot. This was confirmed on two rk3288
>> platforms on kernelci.org: rk3288-veyron-jaq and
>> rk3288-rock2-square. There's no clear sign about other platforms
>> being impacted.
>> If this looks like something you want to investigate but you
>> don't have a platform at hand to reproduce it, please let us know
>> if you would like the test to be re-run on kernelci.org with some
>> debug config turned on, or if you have a fix to try.
> I'd apprciate if you can build a working kernel with
> CONFIG_DEBUG_MEMORY_INIT=y and run it with
> memblock=debug mminit_loglevel=4
> in the command line.
> If I understand correctly, DEBUG_LL is not an option for these platforms
> so if earlyprintk didn't display the log there is not much to do about
OK, sorry for the delay. I've built a kernel and booted it as
you requested, and also found that the issue was due to this
memory area defined in arch/arm/boot/dts/rk3288.dtsi:
#address-cells = <2>;
#size-cells = <2>;
* The rk3288 cannot use the memory area above 0xfe000000
* for dma operations for some reason. While there is
* probably a better solution available somewhere, we
* haven't found it yet and while devices with 2GB of ram
* are not affected, this issue prevents 4GB from booting.
* So to make these devices at least bootable, block
* this area for the time being until the real solution
* is found.
reg = <0x0 0xfe000000 0x0 0x1000000>;
So I've put a hack on top of 950c37691925 to skip adding a
node in memblock_enforce_memory_reserved_overlap() if the base
address is 0xfe000000, which got the kernel booting. Here's the
and the full test job details, if this helps:
I haven't really looked much further than that, but I'll be
available on Monday to help run other tests if needed.
next prev parent reply other threads:[~2020-12-18 22:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <firstname.lastname@example.org>
2020-12-11 21:53 ` kernelci/staging-next bisection: sleep.login on rk3288-rock2-square #2286-staging Guillaume Tucker
2020-12-13 8:23 ` Mike Rapoport
2020-12-18 21:59 ` Guillaume Tucker [this message]
2021-01-03 13:47 ` Mike Rapoport
2021-01-03 20:09 ` Andrea Arcangeli
2021-01-05 9:13 ` Mike Rapoport
2021-01-12 10:53 ` Guillaume Tucker
2021-01-12 11:10 ` Guillaume Tucker
2021-01-12 12:06 ` Mike Rapoport
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).