From: Chris Murphy <lists@colorremedies.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Chris Murphy <lists@colorremedies.com>,
Hugh Dickins <hughd@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
Linux Memory Management List <linux-mm@kvack.org>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: 5.7.0 page allocation failure: order:0, mode:0x400d0
Date: Wed, 10 Jun 2020 17:43:17 -0600 [thread overview]
Message-ID: <CAJCQCtTacMDq-T4tZFFMS394M_ccnRoHUFefO9Uh2Ov9vDfCug@mail.gmail.com> (raw)
In-Reply-To: <20200610233349.GL19604@bombadil.infradead.org>
On Wed, Jun 10, 2020 at 5:33 PM Matthew Wilcox <willy@infradead.org> wrote:
>
> On Wed, Jun 10, 2020 at 05:31:14PM -0600, Chris Murphy wrote:
> > On Mon, Jun 8, 2020 at 3:33 PM Hugh Dickins <hughd@google.com> wrote:
> > >
> > > ChrisM, could you try with the patch below, and see if it works
> > > for you - I hope it doesn't just give you a blank screen.
> >
> > Did this. Does compile, and boot, no blank screen, and webkitgtk
> > compiles without error (it ends in OOM, as expected).
>
> ... but the OOM doesn't point back to i915's shmem functions any more?
It doesn't, but...
I'm going to redo the test because Fedora Workstation 32 enables
earlyoom by default, and that's what triggered the OOM. Not the
kernel's oomkiller. But in the original report, earlyoom was also
enabled but not triggered, yet I got the reported splats.
--
Chris Murphy
next prev parent reply other threads:[~2020-06-10 23:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 7:38 Chris Murphy
2020-06-06 15:12 ` Matthew Wilcox
2020-06-07 0:50 ` Chris Murphy
2020-06-08 9:08 ` Vlastimil Babka
2020-06-08 11:44 ` Matthew Wilcox
2020-06-08 21:33 ` Hugh Dickins
2020-06-09 2:01 ` Matthew Wilcox
2020-06-10 15:21 ` Chris Murphy
2020-06-10 15:28 ` Chris Murphy
2020-06-10 23:31 ` Chris Murphy
2020-06-10 23:33 ` Matthew Wilcox
2020-06-10 23:43 ` Chris Murphy [this message]
2020-06-11 3:14 ` Chris Murphy
2020-06-15 20:29 ` Hugh Dickins
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=CAJCQCtTacMDq-T4tZFFMS394M_ccnRoHUFefO9Uh2Ov9vDfCug@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=chris@chris-wilson.co.uk \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox