1 Kdump Test Description 2 ---------------------- 3 4 The test suite consists of two parts 5 6 * crasher: This is a basic kdump functionality testing. 7 * lkdtm : These tests use kprobes / jprobes to put probes in different 8 function for invoking a dump. 9 10 Only one of the above is used for testing at a time. While building the scripts, 11 select the one you want to run. It is suggested to use the lkdtm tests (which is 12 the default) for more elaborate testing. 13 14 The crasher module tests kdump in following senarios. 15 16 * ACS: invoke dump using sysrq C. 17 * ACP: invoke dump using panic [ panic test 0 ]. 18 * ACB: invoke dump using BUG [ panic test 1 ]. 19 * ACE: invoke dump using panic_on_oops [ panic test 2 ]. 20 * ACL: invoke dump in a hang situation. 21 22 On some type of hardware [ eg IBM System p and System i machines ] tests ACB 23 and ACE will require manual intervention. After running these tests machine 24 will drop into xmon. User will have to type X to get out of the xmon and 25 continue with the tests. As for the ACL test, user will have to invoke a dump 26 using the Hardware Management Console via soft reset. 27 28 The lkdtm module consists of following tests 29 30 * KPIDB: bug in do_irq 31 * KPIDE: exception in do_irq 32 * KPIDL: hang in do_irq 33 * KPIDP: panic in do_irq 34 * KPIEB: bug in handle_IRQ_event 35 * KPIEE: exception in handle_IRQ_event 36 * KPIEL: hang in handle_IRQ_event 37 * KPIEP: panic in handle_IRQ_event 38 * KPTEB: bug in tasklet_action 39 * KPTEE: exception in tasklet_action 40 * KPTEL: hang in tasklet_action 41 * KPTEP: panic in tasklet_action 42 * KPBB : bug in ll_rw_block 43 * KPBE : exception in ll_rw_block 44 * KPBL : hang in ll_rw_block 45 * KPBP : panic in ll_rw_block 46 * KPMSB: bug in shrink_inactive_list 47 * KPMSE: exception in shrink_inactive_list 48 * KPMSL: hang in shrink_inactive_list 49 * KPMSP: panic in shrink_inactive_list 50 * KPTB : bug in hr_timer_start 51 * KPTE : exception in hr_timer_start 52 * KPTL : hang in hr_timer_start 53 * KPTP : panic in hr_timer_start 54 55 On certain type of hardware [ eg IBM system p and system i machines] tests with 56 names ending in "B" and "E" might require manual intervention. After running 57 these tests machine will drop into debugger if one is configured. User will 58 have to type X to get out of the debugger and continue with the tests. For 59 tests with name ending in L [loop test] , user will have to invoke a dump using 60 the Hardware Management Console via soft reset. 61 62 While executing some loop testcases after invoking a dump via Hardware 63 Management Console you might get following message 64 65 Sending IPI to other cpus... 66 done waiting: 1 cpu(s) not responding 67 Activate soft-reset to stop other cpu(s) 68 69 In such case you will have to re-trigger dump via Hardware Management Console 70 one more time. This is a normal senario and not a bug. 71 72
