Messages in this thread | | | Date | Sat, 15 Mar 2014 15:26:25 +0100 | From | Borislav Petkov <> | Subject | Re: [PATCH v3 4/4] x86: Pass memory range via E820 for kdump |
| |
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.
| |