From: Mike Rapoport <rppt@linux.ibm.com>
To: "Łukasz Majczak" <lma@semihalf.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
"Radosław Biernacki" <rad@semihalf.com>,
"Marcin Wojtas" <mw@semihalf.com>,
"Alex Levin" <levinale@google.com>,
"Guenter Roeck" <groeck@google.com>,
"Jesse Barnes" <jsbarnes@google.com>,
"Chris Wilson" <chris@chris-wilson.co.uk>,
"Sarvela, Tomi P" <tomi.p.sarvela@intel.com>
Subject: Re: PROBLEM: Crash after mm: fix initialization of struct page for holes in memory layout
Date: Wed, 27 Jan 2021 12:04:54 +0200 [thread overview]
Message-ID: <20210127100454.GK196782@linux.ibm.com> (raw)
In-Reply-To: <CAFJ_xbqT8h2Exix3S6AGgB7W1N0u-=WKffAyb7Hk9-8K8FBwKA@mail.gmail.com>
Hi Lukasz,
On Wed, Jan 27, 2021 at 10:22:29AM +0100, Łukasz Majczak wrote:
> Crash after mm: fix initialization of struct page for holes in memory layout
>
> Hi,
> I was trying to run v5.11-rc5 on my Samsung Chromebook Pro (Caroline),
> but I've noticed it has crashed - unfortunately it seems to happen at
> a very early stage - No output to the console nor to the screen, so I
> have started a bisect (between 5.11-rc4 - which works just find - and
> 5.11-rc5),
> bisect results points to:
>
> d3921cb8be29 mm: fix initialization of struct page for holes in memory layout
>
> Reproduction is just to build and load the kernel.
>
> If it will help any how I am attaching:
> - /proc/cpuinfo (from healthy system):
> https://gist.github.com/semihalf-majczak-lukasz/3517867bf39f07377c1a785b64a97066
> - my .config file (for a broken system):
> https://gist.github.com/semihalf-majczak-lukasz/584b329f1bf3e43b53efe8e18b5da33c
>
> If there is anything I could add/do/test to help fix this please let me know.
Chris Wilson also reported boot failures on several Chromebooks:
https://lore.kernel.org/lkml/161160687463.28991.354987542182281928@build.alporthouse.com
I presume serial console is not an option, so if you could boot with
earlyprintk=vga and see if there is anything useful printed on the screen
it would be really helpful.
> Best regards
> Lukasz
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2021-01-27 10:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 9:22 PROBLEM: Crash after mm: fix initialization of struct page for holes in memory layout Łukasz Majczak
2021-01-27 10:04 ` Mike Rapoport [this message]
2021-01-27 10:08 ` Łukasz Majczak
2021-01-27 11:18 ` Mike Rapoport
2021-01-27 12:15 ` Łukasz Majczak
2021-01-27 13:15 ` Łukasz Majczak
2021-01-27 18:26 ` Mike Rapoport
2021-01-27 19:18 ` Łukasz Majczak
2021-01-28 2:45 ` Baoquan He
2021-01-28 9:31 ` 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:
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=20210127100454.GK196782@linux.ibm.com \
--to=rppt@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=groeck@google.com \
--cc=jsbarnes@google.com \
--cc=levinale@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lma@semihalf.com \
--cc=mw@semihalf.com \
--cc=rad@semihalf.com \
--cc=tomi.p.sarvela@intel.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 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.