From: Mike Rapoport <email@example.com>
To: Chris Wilson <firstname.lastname@example.org>
Cc: Linus Torvalds <email@example.com>,
Andrew Morton <firstname.lastname@example.org>,
Linux Kernel Mailing List <email@example.com>
Subject: Re: Linux 5.11-rc5
Date: Tue, 26 Jan 2021 18:24:40 +0200 [thread overview]
Message-ID: <20210126162440.GC196782@linux.ibm.com> (raw)
On Mon, Jan 25, 2021 at 09:46:19PM +0000, Chris Wilson wrote:
> Quoting Mike Rapoport (2021-01-25 21:33:48)
> > On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> > > On Mon, Jan 25, 2021 at 12:35 PM Chris Wilson <firstname.lastname@example.org> wrote:
> > > >
> > > > Quoting Linus Torvalds (2021-01-25 01:06:40)
> > > > > Mike Rapoport (3):
> > > > ...
> > > > > mm: fix initialization of struct page for holes in memory layout
> > > >
> > > > We have half a dozen or so different machines in CI that are silently
> > > > failing to boot, that we believe is bisected to this patch.
> > >
> > > That commit reverts cleanly - so if you can verify that reverting it
> > > fixes your CI machines, I think that that's the right thing to do for
> > > now, unless Mike can figure out some obvious "Duh!" moment from your
> > > working dmesg.
> > Unfortunately not, at least at 11pm :(
> > Maybe tomorrow I'll have something smarter to say.
> CI does confirm that the revert of d3921cb8be29 brings the machines back
> to life.
I still cannot see what could possibly go wrong, so let's revert
d3921cb8be29 for now and I'll continue to work with Chris to debug this.
> > > Mike: should we perhaps revert the first patch too (commit
> > > bde9cfa3afe4: "x86/setup: don't remove E820_TYPE_RAM for pfn 0")?
This change should be quite innocuous, we anyway never allocate pfn 0 but
treat 0 as memory start in many places.
> > I wonder, maybe actually this one is causing troubles?
> > Chris, would it be possible to check what happens if you revert only
> > bde9cfa3afe4?
> Queued for CI, will be run in about an hour.
next prev parent reply other threads:[~2021-01-26 16:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 1:06 Linux 5.11-rc5 Linus Torvalds
2021-01-25 3:48 ` Guenter Roeck
2021-01-25 3:56 ` Bhaskar Chowdhury
2021-01-25 4:06 ` Guenter Roeck
2021-01-25 4:11 ` Bhaskar Chowdhury
2021-01-25 20:34 ` Chris Wilson
2021-01-25 20:49 ` Linus Torvalds
2021-01-25 21:33 ` Mike Rapoport
2021-01-25 21:46 ` Chris Wilson
2021-01-26 9:33 ` Chris Wilson
2021-01-26 16:24 ` Mike Rapoport [this message]
2021-01-26 18:45 ` Linus Torvalds
2021-01-27 9:38 ` Greg KH
2021-02-04 18:19 ` Mike Rapoport
2021-02-04 18:32 ` Linus Torvalds
2021-02-05 6:54 ` Greg KH
2021-01-25 21:04 ` Mike Rapoport
2021-01-25 21:13 ` Chris Wilson
2021-01-26 16:37 ` Mike Rapoport
2021-01-28 21:00 ` Pavel Machek
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 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.