lk/linux-kernel-test
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

[PATCH] kdump documentation update to introduce use of irqpoll

Browse Source 
o Specify "irqpoll" command line option which loading second kernel. This
  helps in reducing driver initialization failures in second kernel due
  to shared interrupts.
o Enabled LAPIC/IOAPIC support for UP kernels in second kernel. This reduces
  the chances of devices sharing the irq and hence reduces the chances of
  driver initialization failures in second kernel.
o Build a UP capture kernel and disabled SMP support.

Signed-off-by: Vivek Goyal <vgoyal@in.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
This commit is contained in:
Vivek Goyal
2005-06-25 14:58:17 -07:00
committed by Linus Torvalds
parent b089f4a68e
commit d58831e416
1 changed files with 16 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
Documentation/kdump/kdump.txt
View File

@@ -66,12 +66,18 @@ SETUP
CONFIG_PHYSICAL_START=0x1000000 CONFIG_PHYSICAL_START=0x1000000
c) Enable "/proc/vmcore support" (Optional, in Pseudo filesystems). c) Enable "/proc/vmcore support" (Optional, in Pseudo filesystems).
CONFIG_PROC_VMCORE=y CONFIG_PROC_VMCORE=y
d) Disable SMP support and build a UP kernel (Until it is fixed).
CONFIG_SMP=n
e) Enable "Local APIC support on uniprocessors".
CONFIG_X86_UP_APIC=y
f) Enable "IO-APIC support on uniprocessors"
CONFIG_X86_UP_IOAPIC=y
Note: Options a) and b) depend upon "Configure standard kernel features Note: i) Options a) and b) depend upon "Configure standard kernel features
(for small systems)" (under General setup). (for small systems)" (under General setup).
Option a) also depends on CONFIG_HIGHMEM (under Processor ii) Option a) also depends on CONFIG_HIGHMEM (under Processor
type and features). type and features).
Both option a) and b) are under "Processor type and features". iii) Both option a) and b) are under "Processor type and features".
3) Boot into the first kernel. You are now ready to try out kexec-based crash 3) Boot into the first kernel. You are now ready to try out kexec-based crash
dumps. dumps.
@@ -79,7 +85,7 @@ SETUP
4) Load the second kernel to be booted using: 4) Load the second kernel to be booted using:
kexec -p <second-kernel> --crash-dump --args-linux --append="root=<root-dev> kexec -p <second-kernel> --crash-dump --args-linux --append="root=<root-dev>
maxcpus=1 init 1" init 1 irqpoll"
Note: i) <second-kernel> has to be a vmlinux image. bzImage will not work, Note: i) <second-kernel> has to be a vmlinux image. bzImage will not work,
as of now. as of now.
@@ -87,12 +93,12 @@ SETUP
is sufficient to represent the physical memory up to 4GB. To store is sufficient to represent the physical memory up to 4GB. To store
headers in ELF64 format, specifiy "--elf64-core-headers" on the headers in ELF64 format, specifiy "--elf64-core-headers" on the
kexec command line additionally. kexec command line additionally.
iii) For now (or until it is fixed), it's best to build the iii) Specify "irqpoll" as command line parameter. This reduces driver
second-kernel without multi-processor support, i.e., make it initialization failures in second kernel due to shared interrupts.
a uniprocessor kernel.
5) System reboots into the second kernel when a panic occurs. A module can be 5) System reboots into the second kernel when a panic occurs. A module can be
written to force the panic, for testing purposes. written to force the panic or "ALT-SysRq-c" can be used initiate a crash
dump for testing purposes.
6) Write out the dump file using 6) Write out the dump file using
@@ -131,5 +137,5 @@ TODO
CONTACT CONTACT
======= =======
Hariprasad Nellitheertha - hari at in dot ibm dot com
Vivek Goyal (vgoyal@in.ibm.com) Vivek Goyal (vgoyal@in.ibm.com)
Maneesh Soni (maneesh@in.ibm.com)