From: Rong Chen <rong.a.chen@intel.com>
To: Catalin Marinas <catalin.marinas@arm.com>, Qian Cai <cai@lca.pw>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org
Subject: Re: [mm] c566586818: BUG:kernel_hang_in_early-boot_stage,last_printk:Probing_EDD(edd=off_to_disable)...ok
Date: Thu, 27 Aug 2020 17:16:47 +0800 [thread overview]
Message-ID: <120c99ce-6439-2945-e990-588c42a9e582@intel.com> (raw)
In-Reply-To: <20200826173010.GD24545@gaia>
On 8/27/20 1:30 AM, Catalin Marinas wrote:
> On Tue, Aug 25, 2020 at 11:02:40PM -0400, Qian Cai wrote:
>> On Aug 25, 2020, at 8:44 PM, Rong Chen <rong.a.chen@intel.com> wrote:
>>> I rebuilt the kernel on commit c566586818 but the error changed to
>>> "RIP: 0010:clear_page_orig+0x12/0x40", and the error can be
>>> reproduced on parent commit:
>> Catalin, any thought? Sounds like those early kmemleak allocations
>> cause some sort of memory corruption?
> I can't immediately see how but Rong implies that the error also happens
> on the parent commit. Does it mean the bisection isn't entirely right?
>
Hi Catalin,
The original bisection is for "BUG:kernel_hang_in_early-boot_stage"
which locate to commit c566586818,
and the boot will go on and meet the error "RIP:
0010:clear_page_orig+0x12/0x40" if we set
CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE=400, but the error shouldn't cause
by commit c566586818
because we can reproduce the error on parent commit.
Best Regards,
Rong Chen
prev parent reply other threads:[~2020-08-27 9:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 0:23 [mm] c566586818: BUG:kernel_hang_in_early-boot_stage,last_printk:Probing_EDD(edd=off_to_disable)...ok kernel test robot
2020-08-21 1:01 ` Qian Cai
2020-08-24 2:47 ` Rong Chen
2020-08-24 12:29 ` Qian Cai
2020-08-26 0:44 ` Rong Chen
2020-08-26 3:02 ` Qian Cai
2020-08-26 17:30 ` Catalin Marinas
2020-08-27 9:16 ` Rong Chen [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=120c99ce-6439-2945-e990-588c42a9e582@intel.com \
--to=rong.a.chen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=mhocko@kernel.org \
--cc=torvalds@linux-foundation.org \
--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