27 Dec, 2011

1 commit


25 Nov, 2010

1 commit


13 Jun, 2009

1 commit


22 Oct, 2008

1 commit

  • This adds relocatable kernel support for kdump. With this one can
    use the same regular kernel to capture the kdump. A signature (0xfeed1234)
    is passed in r6 from panic code to the next kernel through kexec_sequence
    and purgatory code. The signature is used to differentiate between
    kdump kernel and non-kdump kernels.

    The purgatory code compares the signature and sets the __kdump_flag in
    head_64.S. During the boot up, kernel code checks __kdump_flag and if it
    is set, the kernel will behave as relocatable kdump kernel. This kernel
    will boot at the address where it was loaded by kexec-tools ie. at the
    address reserved through crashkernel boot parameter.

    CONFIG_CRASH_DUMP depends on CONFIG_RELOCATABLE option to build kdump
    kernel as relocatable. So the same kernel can be used as production and
    kdump kernel.

    This patch incorporates the changes suggested by Paul Mackerras to avoid
    GOT use and to avoid two copies of the code.

    Signed-off-by: Paul Mackerras
    Signed-off-by: Mohan Kumar M
    Signed-off-by: Michael Ellerman
    Signed-off-by: Benjamin Herrenschmidt

    Mohan Kumar M
     

29 Jul, 2008

1 commit


08 Jul, 2008

1 commit


01 May, 2008

1 commit

  • The extended crashkernel syntax is a little confusing in the way it handles
    ranges. eg:

    crashkernel=512M-2G:64M,2G-:128M

    Means if the machine has between 512M and 2G of memory the crash region should
    be 64M, and if the machine has 2G of memory the region should be 64M. Only if
    the machine has more than 2G memory will 128M be allocated.

    Although that semantic is correct, it is somewhat baffling. Instead I propose
    that the end of the range means the first address past the end of the range,
    ie: 512M up to but not including 2G.

    [bwalle@suse.de: clarify inclusive/exclusive in crashkernel commandline in documentation]
    Signed-off-by: Michael Ellerman
    Acked-by: Bernhard Walle
    Cc: "Eric W. Biederman"
    Cc: Simon Horman
    Signed-off-by: Bernhard Walle
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Michael Ellerman
     

20 Oct, 2007

1 commit

  • This adds the documentation for the extended crashkernel syntax into
    Documentation/kdump/kdump.txt.

    Signed-off-by: Bernhard Walle
    Cc: Andi Kleen
    Cc: "Luck, Tony"
    Cc: Paul Mackerras
    Cc: Benjamin Herrenschmidt
    Cc: Paul Mundt
    Cc: Vivek Goyal
    Cc: "Eric W. Biederman"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Bernhard Walle
     

17 Oct, 2007

4 commits

  • This cleans up kdump documentation a bit. Plus I do not think we want
    to mention Linux trademark in _every_ file in documentation....

    Signed-off-by: Pavel Machek
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Pavel Machek
     
  • This patch adds the "reset_devices" option (that's used only by one device
    driver for now) to the recommended list of command line parameters for kdump.

    Meaning (Documentation/kernel-parameters.txt):
    reset_devices [KNL] Force drivers to reset the underlying device
    during initialization.

    Signed-off-by: Bernhard Walle
    Cc: "Randy.Dunlap"
    Cc: Vivek Goyal
    Cc: "Eric W. Biederman"
    Cc: Haren Myneni
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Bernhard Walle
     
  • This patch reflects the
    http://git.kernel.org/?p=linux/kernel/git/horms/kexec-tools-testing.git;a=commit;h=b9c3648e690ad0dad12389659673206213a09760
    change in kexec-tools-testing also now in the kernel documentation.

    Signed-off-by: Bernhard Walle
    Cc: "Randy.Dunlap"
    Cc: Vivek Goyal
    Cc: "Eric W. Biederman"
    Cc: Haren Myneni
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Bernhard Walle
     
  • This patch adapts the Documentation/kdump/kdump.txt file to express the fact
    that the x86_64 kernel is now also relocatable. This makes i386 and x86_64
    now behave the same, simplifying the documentation.

    Signed-off-by: Bernhard Walle
    Cc: "Randy.Dunlap"
    Cc: Vivek Goyal
    Cc: "Eric W. Biederman"
    Cc: Haren Myneni
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Bernhard Walle
     

21 Feb, 2007

1 commit

  • Patch from Mohan Kumar M to add the ppc64 portions of the kdump
    documentation.

    http://thread.gmane.org/gmane.linux.kernel/481689/focus=3375

    Cc: Mohan Kumar M
    Cc: Vivek Goyal
    Signed-off-by: Simon Horman
    Cc: Paul Mackerras
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Simon Horman
     

13 Feb, 2007

1 commit

  • I've noticed that the boot options are not correct for in the documentation
    for kdump. The "init" keyword is not necessary, and causes a kernel panic
    when booting with an initrd on Fedora 5.

    [horms@verge.net.au: put original comment with the latest version of the patch]
    Signed-off-by: Judith Lebzeelter
    Acked-by: Vivek Goyal
    Signed-off-by: Simon Horman
    Cc: "Eric W. Biederman"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Horms
     

23 Jan, 2007

2 commits


12 Jan, 2007

1 commit

  • o Kdump documentation update.
    - Update details for using relocatable kernel.
    - Start using kexec-tools-testing release as it is latest and old
    kexec-tools can't load relocatable bzImage file.
    - Also add kdump on ia64 specific details.

    Signed-off-by: Vivek Goyal
    Cc: Horms
    Cc: Mohan Kumar M
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Vivek Goyal
     

04 Oct, 2006

1 commit


27 Jun, 2006

1 commit

  • In a testament to the utter simplicity and logic of the English
    language ;-), I found a single correct use - in kernel/panic.c - and
    10-15 incorrect ones.

    Signed-Off-By: Lee Revell
    Signed-off-by: Adrian Bunk

    Lee Revell
     

26 Jun, 2006

1 commit


12 Jan, 2006

1 commit


11 Jan, 2006

1 commit


13 Sep, 2005

1 commit


10 Sep, 2005

1 commit

  • There are minor changes in command line options in kexec-tools for kdump.
    This patch updates the documentation to reflect those changes.

    Signed-off-by: Vivek Goyal
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Vivek Goyal
     

26 Jun, 2005

2 commits

  • 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
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Vivek Goyal
     
  • This patch contains the documentation for the kexec based crash dump tool.

    Quick kdump-howto
    ================================================================

    1) Download and build kexec-tools.

    2) Download and build the latest kexec/kdump (-mm) kernel patchset.
    Two kernels need to be built in order to get this feature working.

    A) First kernel:
    a) Enable "kexec system call" feature:
    CONFIG_KEXEC=y
    b) Physical load address (use default):
    CONFIG_PHYSICAL_START=0x100000
    c) Enable "sysfs file system support":
    CONFIG_SYSFS=y
    d) Boot into first kernel with the command line parameter "crashkernel=Y@X":
    For example: "crashkernel=64M@16M".

    B) Second kernel:
    a) Enable "kernel crash dumps" feature:
    CONFIG_CRASH_DUMP=y
    b) Physical load addreess, use same load address as X in "crashkernel"
    kernel parameter in d) above, e.g., 16 MB or 0x1000000.
    CONFIG_PHYSICAL_START=0x1000000
    c) Enable "/proc/vmcore support" (Optional, in Pseudo filesystems).
    CONFIG_PROC_VMCORE=y

    3) Boot into the first kernel.

    4) Load the second kernel to be booted using:

    kexec -p --crash-dump --args-linux --append="root=
    maxcpus=1 init 1"

    5) System reboots into the second kernel when a panic occurs. A module can be
    written to force the panic, for testing purposes.

    6) See Documentation/kdump.txt for how to read the first kernel's
    memory image and how to analyze it.

    Signed-off-by: Hariprasad Nellitheertha
    Signed-off-by: Eric Biederman
    Signed-off-by: Vivek Goyal
    Signed-off-by: randy_dunlap
    Signed-off-by: Maneesh Soni
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Vivek Goyal