On Wed, Apr 26, 2006 at 10:49:35AM -0700, David Wilder wrote: > > 2) On x86, enable high memory support under "Processor type and > features": > > CONFIG_HIGHMEM=y
I think it should be changed to CONFIG_HIGHMEM64G=y > > 3) On x86 and x86_64, disable symmetric multi-processing support > under "Processor type and features": > > CONFIG_SMP=n > I guess that we can get rid of this requirement. Users can continue to build SMP kernels and provide maxcpus=1 option in the command line while loading second kernel. > 4) On ppc64, disable NUMA support and enable EMBEDDED support: > > CONFIG_NUMA=n > CONFIG_EMBEDDED=y > CONFIG_EEH=N for the dump-capture kernel > > 5) Enable "kernel crash dumps" support under "Processor type and > features": > > CONFIG_CRASH_DUMP=y > > 6) Use a suitable value for "Physical address where the kernel is > loaded" (under "Processor type and features"). This only appears when > "kernel crash dumps" is enabled. By default this value is 0x1000000 > (16MB). It should be the same as X in the "[EMAIL PROTECTED]" boot > parameter discussed above. > > On x86 and x86_64, use "CONFIG_PHYSICAL_START=0x1000000". > > On ppc64 the value is automatically set at 32MB when > CONFIG_CRASH_DUMP is set. > > 6) Optionally enable "/proc/vmcore support" under "Filesystems" -> > "Pseudo filesystems". > > CONFIG_PROC_VMCORE=y > You can mention that now it is set by defaul if CONFIG_CRASH_DUMP is selected. > 7) Make and install the kernel and its modules. DO NOT add this kernel > to the boot loader configuration files. > > > Load the Dump-capture Kernel > ============================ > > After booting to the system kernel, load the dump-capture kernel using > the following command: > > kexec -p <dump-capture-kernel> \ > --initrd=<initrd-for-dump-capture-kernel> --args-linux \ > --append="root=<root-dev> init 1 irqpoll" > Add maxcpus=1 > > Notes on loading the dump-capture kernel: > > * <dump-capture-kernel> must be a vmlinux image (that is, an > uncompressed ELF image). bzImage does not work at this time. > > * 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). > > * The "irqpoll" boot parameter reduces driver initialization failures > due to shared interrupts in the dump-capture kernel. > > * You must specify <root-dev> in the format corresponding to the root > device name in the output of mount command. > > * "init 1" boots the dump-capture kernel into single-user mode without > networking. If you want networking, use "init 3." > > > Kernel Panic > ============ > > After successfully loading the dump-capture kernel as previously > described, the system will reboot into the dump-capture kernel if a > panic occurs. You can write a module to force the panic, or use > "ALT-SysRq-c" to initiate a crash dump for testing purposes. > There are more trigger points now. - die_nmi() - die() So if hardlockup is detected and NMI is configured, system will boot into capture kenrel. If die() is called and it happens to be a thread with pid 0 or 1 or die() is called inside interrupt context, then system will boot into capture kernel. if oops happens and panic_on_oops is set then system will boot into dump capture kernel. -vivek
_______________________________________________ fastboot mailing list [email protected] https://lists.osdl.org/mailman/listinfo/fastboot
