Re: kdump test update

[Alexander Nyberg <alexn@telia.com>]

tis 2005-05-24 klockan 14:38 +0530 skrev Nagesh Sharyathi:
> These I have tested on the kernel 2.6.12-rc4-mm1 with the following test
> suites , with kdump enabled 
> 
> Once test suites PASS/SUCCESS, force the machine to hang(lock up) by 
> disabling irqs with the attached SPINLOCK test module from Badari 
> Pulavarthy, 
> try to take dump either with sysrq key or nmi_watchdog=2 kernel parameter.
> 
> Test Suite: 
> -----------
> LTP Runall, FSracer(race condition in file system) with LVM partitions 
> (over ext2, ext3, JFS, XFS), FS stress, Mem Test/Bash Memory, Cerberus, 
> KernBench, NetPerf.
> 
> System Info:
> ------------
> Distro: SLES 9 SP1
> 
> Software/kernel variables:
> --------------------------
> 1. kernel - linux-2.6.12-rc4-mm1 
> 2. kexec-tools-1.101 + kdump patches
> 3. kernel.sysrq=1
>  
> Command line parameters for first kernel:
> -----------------------------------------
>   root = <> vga=0x31a selinux=0 splash=silent resume=<> elevator=cfq 
> showpts
>   crashkernel=48M@16M console=tty0 console=ttyS0,38400n1
>  
> Hardwares on which is test cases are run:
> -----------------------------------------
> 
> A) 1way, Pentium IV 2.8GHz, 2G RAM
>    - Network Interface (e1000)
>    - Disk I/O: SCSI storage controller: Adaptec Ultra320
> 
>    o Ran test suite KERNBENCH and CERBERUS test ran successfully. Forced 
>      system hang by inserting spinlock test module and tried to invoke 
>      panic with sysrq+c, but it failed to force Panic. I failed to take 
> the 
>      dump as sysrq keys failed to respond during hang.

This is expected, your spinlock module disables interrupts so
sysrq-crashdump has not a chance to get through. NMI watchdog is highly
necessary. (this is even more reason to have NMI watchdog on by default
on at least newer cpus even on x86 if kdump enters mainline and wants to
be useful).


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/