From: Mel Gorman <mgorman@techsingularity.net>
To: Will Deacon <will.deacon@arm.com>
Cc: Yury Norov <yury.norov@gmail.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, Michal Hocko <mhocko@kernel.org>,
linux-arm-kernel@lists.infradead.org,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Zi Yan <zi.yan@cs.rutgers.edu>, Vlastimil Babka <vbabka@suse.cz>
Subject: Re: 5.0-rc kernel hangs on early boot
Date: Wed, 13 Feb 2019 11:29:38 +0000 [thread overview]
Message-ID: <20190213112938.GP9565@techsingularity.net> (raw)
In-Reply-To: <20190213112520.GB1912@brain-police>
On Wed, Feb 13, 2019 at 11:25:21AM +0000, Will Deacon wrote:
> > Thanks Will.
> >
> > While I agree that going OOM early is a problem and would explain why
> > the boosting logic was hit at all, it's still the case that the boosting
> > should not divide by zero. Even if the booting is broken due to a lack
> > of memory, I'd still not prefer to crash due to 1c30844d2dfe272d58c.
>
> Yup, sorry, our previous mails crossed paths. Your patch looks sensible in
> its own right, I'm just left wondering why we're OOM so early during boot!
>
I completely agree that it's worth pinning down both issues.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2019-02-13 11:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 8:25 5.0-rc kernel hangs on early boot Yury Norov
2019-02-13 11:14 ` Mel Gorman
2019-02-13 11:51 ` Yury Norov
2019-02-13 13:19 ` Mel Gorman
2019-02-13 11:18 ` Will Deacon
2019-02-13 11:21 ` Mel Gorman
2019-02-13 11:25 ` Will Deacon
2019-02-13 11:29 ` Mel Gorman [this message]
2019-02-13 11:55 ` Yury Norov
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=20190213112938.GP9565@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=will.deacon@arm.com \
--cc=yury.norov@gmail.com \
--cc=zi.yan@cs.rutgers.edu \
/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