Skip to content
Snippets Groups Projects
  1. Dec 27, 2011
  2. Nov 25, 2010
  3. Jun 12, 2009
  4. Oct 22, 2008
    • Mohan Kumar M's avatar
      powerpc: Support for relocatable kdump kernel · 54622f10
      Mohan Kumar M authored
      
      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: default avatarPaul Mackerras <paulus@samba.org>
      Signed-off-by: default avatarMohan Kumar M <mohan@in.ibm.com>
      Signed-off-by: default avatarMichael Ellerman <michael@ellerman.id.au>
      Signed-off-by: default avatarBenjamin Herrenschmidt <benh@kernel.crashing.org>
      54622f10
  5. Jul 28, 2008
  6. Jul 08, 2008
  7. May 01, 2008
  8. Oct 19, 2007
  9. Oct 17, 2007
  10. Feb 21, 2007
  11. Feb 12, 2007
  12. Jan 23, 2007
  13. Jan 12, 2007
  14. Oct 03, 2006
  15. Jun 26, 2006
  16. Jun 25, 2006
  17. Jan 12, 2006
  18. Jan 10, 2006
  19. Sep 13, 2005
  20. Sep 09, 2005
  21. Jun 25, 2005
    • Vivek Goyal's avatar
      [PATCH] kdump documentation update to introduce use of irqpoll · d58831e4
      Vivek Goyal authored
      
      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: default avatarVivek Goyal <vgoyal@in.ibm.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      d58831e4
    • Vivek Goyal's avatar
      [PATCH] kdump: Documentation for Kdump · b089f4a6
      Vivek Goyal authored
      
      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 <second-kernel> --crash-dump --args-linux --append="root=<root-dev>
         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: default avatarHariprasad Nellitheertha <hari@in.ibm.com>
      Signed-off-by: default avatarEric Biederman <ebiederm@xmission.com>
      Signed-off-by: default avatarVivek Goyal <vgoyal@in.ibm.com>
      Signed-off-by: default avatarrandy_dunlap <rdunlap@xenotime.net>
      Signed-off-by: default avatarManeesh Soni <maneesh@in.ibm.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      b089f4a6
Loading