From 929ea95290cfbb6f7b9bbb3d41defe082fb1a927 Mon Sep 17 00:00:00 2001 From: Bernhard Walle Date: Tue, 16 Oct 2007 23:31:22 -0700 Subject: [PATCH] --- yaml --- r: 70787 b: refs/heads/master c: 4fd45090d6aed83e3978689d8dc98ce16b9689dd h: refs/heads/master i: 70785: cce7e46cdb738a5cfa91caaf8589ca0687663d99 70783: 8431834807060a0955a86b212e7c166dfc06b677 v: v3 --- [refs] | 2 +- trunk/Documentation/kdump/kdump.txt | 12 +++++++----- 2 files changed, 8 insertions(+), 6 deletions(-) diff --git a/[refs] b/[refs] index dc4999d1de97..28fccabe1aab 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: f00b51654ec919620aec911b4c3fa4ef3952bb6d +refs/heads/master: 4fd45090d6aed83e3978689d8dc98ce16b9689dd diff --git a/trunk/Documentation/kdump/kdump.txt b/trunk/Documentation/kdump/kdump.txt index 68aa1650973a..a9a411d8b978 100644 --- a/trunk/Documentation/kdump/kdump.txt +++ b/trunk/Documentation/kdump/kdump.txt @@ -301,11 +301,13 @@ For ppc64: Notes on loading the dump-capture kernel: * By default, the ELF headers are stored in ELF64 format to support - systems with more than 4GB memory. The --elf32-core-headers option can - be used to force the generation of ELF32 headers. This is necessary - because GDB currently cannot open vmcore files with ELF64 headers on - 32-bit systems. ELF32 headers can be used on non-PAE systems (that is, - less than 4GB of memory). + systems with more than 4GB memory. On i386, kexec automatically checks if + the physical RAM size exceeds the 4 GB limit and if not, uses ELF32. + So, on non-PAE systems, ELF32 is always used. + + The --elf32-core-headers option can be used to force the generation of ELF32 + headers. This is necessary because GDB currently cannot open vmcore files + with ELF64 headers on 32-bit systems. * The "irqpoll" boot parameter reduces driver initialization failures due to shared interrupts in the dump-capture kernel.