From: Minchan Kim <minchan@kernel.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Lukasz Odzioba <lukasz.odzioba@intel.com>,
Sasha Levin <sasha.levin@oracle.com>,
Michal Hocko <mhocko@suse.com>,
Kirill Shutemov <kirill.shutemov@linux.intel.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Vladimir Davydov <vdavydov@parallels.com>,
Ming Li <mingli199x@qq.com>,
Andrew Morton <akpm@linux-foundation.org>,
stable@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: 4.1.28 is broken due to "mm/swap.c: flush lru pvecs on compound page arrival"
Date: Sat, 16 Jul 2016 23:51:42 +0900 [thread overview]
Message-ID: <20160716145142.GA29738@bbox> (raw)
In-Reply-To: <alpine.LRH.2.02.1607161037180.18821@file01.intranet.prod.int.rdu2.redhat.com>
On Sat, Jul 16, 2016 at 10:46:17AM -0400, Mikulas Patocka wrote:
> Hi
>
> The patch c5ad33184354260be6d05de57e46a5498692f6d6 on the kernel v4.1.28
> breaks the kernel. The kernel crashes when executing the boot scripts with
> "kernel panic: Out of memory and no killable processes...". The machine
> has 512MB ram and 1 core.
>
> Note that the upstream kernel 4.7-rc4 with this patch works, but when the
> patch is backported to the 4.1 branch, it makes the system unbootable.
It seems a bug was introduced at backport time, I think.
Please, look at http://marc.info/?l=linux-mm&m=146868046305014&w=2
>
> Mikulas
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-07-16 14:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-16 14:46 4.1.28 is broken due to "mm/swap.c: flush lru pvecs on compound page arrival" Mikulas Patocka
2016-07-16 14:51 ` Minchan Kim [this message]
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=20160716145142.GA29738@bbox \
--to=minchan@kernel.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lukasz.odzioba@intel.com \
--cc=mhocko@suse.com \
--cc=mingli199x@qq.com \
--cc=mpatocka@redhat.com \
--cc=sasha.levin@oracle.com \
--cc=stable@vger.kernel.org \
--cc=vdavydov@parallels.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).