Re: PROBLEM: Crash after mm: fix initialization of struct page for holes in memory layout

From: "Łukasz Majczak" <lma@semihalf.com>
To: Mike Rapoport <rppt@linux.ibm.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 13:15:14 +0100	[thread overview]
Message-ID: <CAFJ_xbo8Zv9VdJibC106sFOqoYsVhifm0eh=VWtMzeoUE4KVWA@mail.gmail.com> (raw)
In-Reply-To: <20210127111858.GA273567@linux.ibm.com>

Unfortunately nothing :( my current kernel command line contains:
console=ttyS0,115200n8 debug earlyprintk=serial loglevel=7

I was thinking about using earlycon, but it seems to be blocked.
(I think the lack of earlycon might be related to Chromebook HW
security design. There is an EC controller which is a part of AP ->
serial chain as kernel messages are considered sensitive from a
security standpoint.)

Best regards,
Lukasz

śr., 27 sty 2021 o 12:19 Mike Rapoport <rppt@linux.ibm.com> napisał(a):
>
> On Wed, Jan 27, 2021 at 11:08:17AM +0100, Łukasz Majczak wrote:
> > Hi Mike,
> >
> > Actually I have a serial console attached (via servo device), but
> > there is no output :( and also the reboot/crash is very fast/immediate
> > after power on.
>
> If you boot with earlyprintk=serial are there any messages?
>
> > Best regards
> > Lukasz
> >
> > śr., 27 sty 2021 o 11:05 Mike Rapoport <rppt@linux.ibm.com> napisał(a):
> > >
> > > 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.
>
> --
> Sincerely yours,
> Mike.