1. 04 10月, 2006 1 次提交
  2. 26 6月, 2006 1 次提交
  3. 11 1月, 2006 1 次提交
  4. 13 9月, 2005 1 次提交
  5. 10 9月, 2005 1 次提交
  6. 26 6月, 2005 2 次提交
    • V
      [PATCH] kdump documentation update to introduce use of irqpoll · d58831e4
      Vivek Goyal 提交于
      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: NVivek Goyal <vgoyal@in.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      d58831e4
    • V
      [PATCH] kdump: Documentation for Kdump · b089f4a6
      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 <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: NHariprasad Nellitheertha <hari@in.ibm.com>
      Signed-off-by: NEric Biederman <ebiederm@xmission.com>
      Signed-off-by: NVivek Goyal <vgoyal@in.ibm.com>
      Signed-off-by: Nrandy_dunlap <rdunlap@xenotime.net>
      Signed-off-by: NManeesh Soni <maneesh@in.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      b089f4a6