From: Borislav Petkov <bp@alien8.de>
To: Linn Crosetto <linn@hp.com>
Cc: Matt Fleming <matt@console-pimps.org>,
Dave Young <dyoung@redhat.com>, WANG Chao <chaowang@redhat.com>,
kexec@lists.infradead.org, horms@verge.net.au,
ebiederm@xmission.com, hpa@zytor.com, trenn@suse.de,
vgoyal@redhat.com, toshi.kani@hp.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/4] x86: Pass memory range via E820 for kdump
Date: Sat, 15 Mar 2014 15:26:25 +0100 [thread overview]
Message-ID: <20140315142625.GA8735@nazgul.tnic> (raw)
In-Reply-To: <20140314202706.GX7672@oranje.fc.hp.com>
On Fri, Mar 14, 2014 at 02:27:06PM -0600, Linn Crosetto wrote:
> Since this testing was done on a prototype, I will send you the log in
> a separate email. I tried efi.git/next (with the addition of 4ce7a86),
> and hit the same panic.
Well, if the stack trace is the same:
> ? __unmap_pmd_range+0x77/0x190
> unmap_pmd_range+0xcf/0x1c0
> populate_pgd+0x16d/0x250
> __cpa_process_fault+0x15/0xb0
...
it looks like populate_pgd() fails and unmaps the whole range. You could
add some debug printks to find out exactly why populate_pgd() fails.
Also, please try to catch full dmesg and the whole oops.
Btw, Matt, your whole efi/next stuff is already in tip, right? Because
if so, Linn could simply test latest tip/master.
Thanks.
next prev parent reply other threads:[~2014-03-15 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1394464149-30384-1-git-send-email-chaowang@redhat.com>
[not found] ` <1394464149-30384-5-git-send-email-chaowang@redhat.com>
[not found] ` <20140313222428.GW7672@oranje.fc.hp.com>
2014-03-14 2:47 ` Dave Young
2014-03-14 8:26 ` Matt Fleming
2014-03-14 20:27 ` Linn Crosetto
2014-03-15 14:26 ` Borislav Petkov [this message]
2014-03-15 14:41 ` Borislav Petkov
2014-03-15 14:48 ` Matt Fleming
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=20140315142625.GA8735@nazgul.tnic \
--to=bp@alien8.de \
--cc=chaowang@redhat.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=linn@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=toshi.kani@hp.com \
--cc=trenn@suse.de \
--cc=vgoyal@redhat.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
all inboxes | Powered by JetHome®