Available watchdog test cases
The test cases that I have been using for testing my watchdog work are available at
http://www.stinkycat.com/patches/watchdog_stuff/watchdog_test.tar.gz
The test are for both the legacy (well, current) /dev/watchdog interface and my proposed sysfs based interface.
--rustyl
Quoted 6 lines · Rusty Lynch
The test cases that I have been using for testing my watchdog work are available at
http://www.stinkycat.com/patches/watchdog_stuff/watchdog_test.tar.gzThe test are for both the legacy (well, current)
/dev/watchdoginterface and my proposed sysfs based interface.
Thanks a bunch Rusty, I'll take a look at them for LTP.
-Paul Larson
Just a quick question : is there an easy to force the kernel to Oops, to make sure that the watchdog will even be working under such conditions ?
I know people are all trying to avoid Oops... but I think the testplan should include that too...
Regards,
Paul
Quoted 9 lines · Rusty Lynch
Quoted 1 line
The test cases that I have been using for testing my
watchdog work are
Quoted 5 lines
available at
http://www.stinkycat.com/patches/watchdog_stuff/watchdog_test.tar.gzThe test are for both the legacy (well, current)
/dev/watchdoginterface and my proposed sysfs based interface.Thanks a bunch Rusty, I'll take a look at them for LTP.
Quoted 9 lines · Paul Rolland
Just a quick question : is there an easy to force the kernel to Oops, to make sure that the watchdog will even be working under such conditions ?
I know people are all trying to avoid Oops... but I think the testplan should include that too...
Regards,
Paul
You can write a kernel module that when loaded will disable all interrupts and sit and spin, or even easier just call panic().
--rustyl
Hello,
Quoted 7 lines
Quoted 1 line
I know people are all trying to avoid Oops... but I think
the testplan
Quoted 1 line
should include that too...
You can write a kernel module that when loaded will disable all interrupts and sit and spin, or even easier just call
panic().
Too easy I should have thought about it myself...
Thanks for the tip...
Regards,
Paul
Quoted 10 lines
Hello,
Quoted 7 lines
Quoted 1 line
I know people are all trying to avoid Oops... but I think
the testplan
Quoted 1 line
should include that too...
You can write a kernel module that when loaded will disable all interrupts and sit and spin, or even easier just call
panic().Too easy I should have thought about it myself...
Steve Hemminger of OSDL did one of these. You can get it at
www.osdl.org/archive/rddunlap/tools/dump_test.c
if you are interested. (I just put it there and there is a 15-minute rsync delay...)
~Randy