archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <>
To: Guillaume Tucker <>
Cc: Andrea Arcangeli <>,
	Andrew Morton <>,
	Stephen Rothwell <>,,
	"" <>,,,
	Mike Rapoport <>, Baoquan He <>
Subject: Re: kernelci/staging-next bisection: sleep.login on rk3288-rock2-square #2286-staging
Date: Sun, 13 Dec 2020 10:23:14 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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 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 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 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

> Thanks,
> Guillaume

Sincerely yours,

  reply	other threads:[~2020-12-13  8:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
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 [this message]
2020-12-18 21:59     ` Guillaume Tucker
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

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:

* 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).