From: Dave Young <dyoung@redhat.com>
To: Linn Crosetto <linn@hp.com>
Cc: matt@console-pimps.org, toshi.kani@hp.com,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
vgoyal@redhat.com, horms@verge.net.au, bp@alien8.de,
ebiederm@xmission.com, hpa@zytor.com, dyoung@redhat.com,
trenn@suse.de, WANG Chao <chaowang@redhat.com>
Subject: Re: [PATCH v3 4/4] x86: Pass memory range via E820 for kdump
Date: Fri, 14 Mar 2014 10:47:26 +0800 [thread overview]
Message-ID: <20140314024726.GA2245@dhcp-16-126.nay.redhat.com> (raw)
In-Reply-To: <20140313222428.GW7672@oranje.fc.hp.com>
> [..]
>
> I tested on a prototype system with 231 entries in the map with good results.
> Everything succeeds when using kexec to initiate a fast reboot. For crash, it
> works with and without --pass-memmap-cmdline when using noefi. I hit the
> following panic when initiating a crash leaving EFI enabled in the crash kernel:
>
> ? __unmap_pmd_range+0x77/0x190
> unmap_pmd_range+0xcf/0x1c0
> populate_pgd+0x16d/0x250
> __cpa_process_fault+0x15/0xb0
> __change_page_attr+0x15e/0x2a0
> __change_page_attr_set_clr+0x59/0xc0
> kernel_map_pages_in_pgd+0x7a/0xb0
> __map_region+0x46/0x64
> ? early_idt_handlers+0x117/0x120
> efi_map_region_fixed+0xd/0xf
> efi_enter_virtual_mode+0x4c/0x476
> ? early_idt_handlers+0x117/0x120
> ? early_idt_handlers+0x117/0x120
> start_kernel+0x2e5/0x376
> ? repair_env_string+0x5b/0x5b
> ? memblock_reserve+0x49/0x4e
> x86_64_start_reservations+0x2a/0x2c
> x86_64_start_kernel+0x19f/0x1ae
>
> However, I was able to reproduce this panic using an earlier version of
> kexec-tools, so I believe it is unrelated to this patch.
Can you test with matt's tree to see if it works?
If it still happens please post the full log.
Thanks
Dave
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2014-03-14 2:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 15:09 [PATCH v3 0/4] kexec-tools, x86: E820 memmap pass for kdump WANG Chao
2014-03-10 15:09 ` [PATCH v3 1/4] cleanup: add dbgprint_mem_range function WANG Chao
2014-03-10 15:09 ` [PATCH v3 2/4] x86: Store memory ranges globally used for crash kernel to boot into WANG Chao
2014-03-10 15:09 ` [PATCH v3 3/4] x86: add --pass-memmap-cmdline option WANG Chao
2014-03-10 15:09 ` [PATCH v3 4/4] x86: Pass memory range via E820 for kdump WANG Chao
2014-03-13 22:24 ` Linn Crosetto
2014-03-14 2:47 ` Dave Young [this message]
2014-03-14 8:26 ` Matt Fleming
2014-03-14 20:27 ` Linn Crosetto
2014-03-15 14:26 ` Borislav Petkov
2014-03-15 14:41 ` Borislav Petkov
2014-03-15 14:48 ` Matt Fleming
2014-03-14 3:49 ` WANG Chao
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=20140314024726.GA2245@dhcp-16-126.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=bp@alien8.de \
--cc=chaowang@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