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