linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: robert shteynfeld <robert.shteynfeld@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Mikhail Zaslonko <zaslonko@linux.ibm.com>,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	Gerald Schaefer <gerald.schaefer@de.ibm.com>,
	Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
	Dave Hansen <dave.hansen@intel.com>,
	Alexander Duyck <alexander.h.duyck@linux.intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Pavel Tatashin <pasha.tatashin@oracle.com>,
	Steven Sistare <steven.sistare@oracle.com>,
	Daniel Jordan <daniel.m.jordan@oracle.com>,
	Bob Picco <bob.picco@oracle.com>
Subject: Re: kernel panic due to https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2830bf6f05fb3e05bc4743274b806c821807a684
Date: Fri, 25 Jan 2019 16:58:10 +0100	[thread overview]
Message-ID: <20190125155810.GQ3560@dhcp22.suse.cz> (raw)
In-Reply-To: <CADfvbxqOOt_07hyeReEH_gCmTxxMYJr0-CSkqdX57wGTWisNTA@mail.gmail.com>

On Fri 25-01-19 10:52:06, robert shteynfeld wrote:
> The person who pointed to mm/page_alloc.c commits likely causing the
> issue did not have time to build a patched/reverted kernel to confirm
> his hypothesis.  When I tried backing out the two separate commits he
> suggested, the first commit (ie. the one in the subject) was the one
> that when backed out fixed the boot issue.  Reverting the second one
> had no effect.

OK, so can you provide the full dmesg (with revert) along wth
memblock=debug kernel parameter. Also would it be possible to configure
serial or net console to get the actual panic report please?
-- 
Michal Hocko
SUSE Labs

  reply	other threads:[~2019-01-25 15:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADfvbxqC1+XoSsn0sEDqFE16tN1Pq46-QDAaCu=AXJdZeY3rDQ@mail.gmail.com>
2019-01-24 15:48 ` Fwd: kernel panic due to https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2830bf6f05fb3e05bc4743274b806c821807a684 robert shteynfeld
2019-01-25  4:48 ` Linus Torvalds
2019-01-25  7:37   ` Michal Hocko
2019-01-25  8:19     ` Michal Hocko
2019-01-25  8:29       ` Michal Hocko
2019-01-25 15:52         ` robert shteynfeld
2019-01-25 15:58           ` Michal Hocko [this message]
2019-01-25 16:16             ` robert shteynfeld
2019-01-25 16:39               ` Michal Hocko
2019-01-25 16:51                 ` robert shteynfeld
2019-01-25 17:33                 ` Michal Hocko
2019-01-25 18:15                   ` Michal Hocko
2019-01-28  6:37                     ` Mikhail Gavrilov
2019-01-28  6:43                       ` Michal Hocko
2019-01-28 11:43                     ` Michal Hocko
2019-01-28 18:42                       ` Linus Torvalds
2019-01-28 19:02                         ` Michal Hocko

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=20190125155810.GQ3560@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.h.duyck@linux.intel.com \
    --cc=bob.picco@oracle.com \
    --cc=daniel.m.jordan@oracle.com \
    --cc=dave.hansen@intel.com \
    --cc=gerald.schaefer@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikhail.v.gavrilov@gmail.com \
    --cc=pasha.tatashin@oracle.com \
    --cc=robert.shteynfeld@gmail.com \
    --cc=steven.sistare@oracle.com \
    --cc=torvalds@linux-foundation.org \
    --cc=zaslonko@linux.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).