From: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
To: Pavel Tatashin <pasha.tatashin@oracle.com>
Cc: sachinp@linux.vnet.ibm.com,
Stephen Rothwell <sfr@canb.auug.org.au>,
Michal Hocko <mhocko@suse.com>,
sim@linux.vnet.ibm.com, venkatb3@in.ibm.com,
LKML <linux-kernel@vger.kernel.org>,
manvanth@linux.vnet.ibm.com,
Linux Memory Management List <linux-mm@kvack.org>,
linux-next@vger.kernel.org, aneesh.kumar@linux.vnet.ibm.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [next-20180711][Oops] linux-next kernel boot is broken on powerpc
Date: Fri, 13 Jul 2018 14:43:11 +0530 [thread overview]
Message-ID: <1531473191.6480.26.camel@abdul.in.ibm.com> (raw)
In-Reply-To: <CAGM2rebtisZda0kqhg0u92fTDxC+=zMNNgKFBLH38osphk0fdA@mail.gmail.com>
On Thu, 2018-07-12 at 13:44 -0400, Pavel Tatashin wrote:
> > Related commit could be one of below ? I see lots of patches related to mm and could not bisect
> >
> > 5479976fda7d3ab23ba0a4eb4d60b296eb88b866 mm: page_alloc: restore memblock_next_valid_pfn() on arm/arm64
> > 41619b27b5696e7e5ef76d9c692dd7342c1ad7eb mm-drop-vm_bug_on-from-__get_free_pages-fix
> > 531bbe6bd2721f4b66cdb0f5cf5ac14612fa1419 mm: drop VM_BUG_ON from __get_free_pages
> > 479350dd1a35f8bfb2534697e5ca68ee8a6e8dea mm, page_alloc: actually ignore mempolicies for high priority allocations
> > 088018f6fe571444caaeb16e84c9f24f22dfc8b0 mm: skip invalid pages block at a time in zero_resv_unresv()
>
> Looks like:
> 0ba29a108979 mm/sparse: Remove CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER
>
> This patch is going to be reverted from linux-next. Abdul, please
> verify that issue is gone once you revert this patch.
kernel booted fine when the above patch is reverted.
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
next prev parent reply other threads:[~2018-07-13 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 17:25 [next-20180711][Oops] linux-next kernel boot is broken on powerpc Abdul Haleem
2018-07-12 17:44 ` Pavel Tatashin
2018-07-13 9:13 ` Abdul Haleem [this message]
2018-07-14 0:55 ` Stephen Rothwell
2018-07-17 10:48 ` Abdul Haleem
2018-07-18 2:00 ` Pavel Tatashin
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=1531473191.6480.26.camel@abdul.in.ibm.com \
--to=abdhalee@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=manvanth@linux.vnet.ibm.com \
--cc=mhocko@suse.com \
--cc=pasha.tatashin@oracle.com \
--cc=sachinp@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=sim@linux.vnet.ibm.com \
--cc=venkatb3@in.ibm.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).