| robbiew | 2c26cc4 | 2001-09-25 17:34:51 +0000 | [diff] [blame] | 1 | crash01 |
| 2 | |
| 3 | A signal handler is set up so that in most cases the machine exception |
| 4 | generated by the illegal instructions, bad operands, etc in the procedure |
| 5 | made up of random data are caught; and another round of randomness may |
| 6 | be tried. Eventually a random instruction may corrupt the program or |
| 7 | the machine state in such a way that the program must halt. This is |
| 8 | a test of the robustness of the hardware/software for instruction |
| 9 | fault handling. |
| 10 | |
| 11 | Note: Running this program just a few times, using total CPU time of |
| 12 | less than a few seconds SHOULD NOT GIVE YOU ANY CONFIDENCE in system |
| 13 | robustness. Having it run for hours, with tens of thousands of cases |
| 14 | would be a different thing. It would also make sense to run this |
| 15 | stress test at the same time you run other tests, like a multi-user |
| 16 | benchmark. |
| 17 | |
| 18 | |
| 19 | crash02 |
| 20 | |
| 21 | A signal handler is set up so that in most cases the machine exception |
| 22 | generated by the illegal syscall, bad operands, etc in the procedure |
| 23 | made up of random data are caught; and another round of randomness may |
| 24 | be tried. Eventually a random syscall may corrupt the program or |
| 25 | the machine state in such a way that the program must halt. This is |
| 26 | a test of the robustness of the hardware/software for instruction |
| 27 | fault handling. |
| 28 | |
| 29 | Note: Running this program just a few times, using total CPU time of |
| 30 | less than a few seconds SHOULD NOT GIVE YOU ANY CONFIDENCE in system |
| 31 | robustness. Having it run for hours, with tens of thousands of cases |
| 32 | would be a different thing. It would also make sense to run this |
| 33 | stress test at the same time you run other tests, like a multi-user |
| 34 | benchmark. |
| 35 | |
| 36 | CAUTION: running this program may crash your system, your disk and all |
| 37 | your data along! DO NOT RUN IT ON PRODUCTION SYSTEMS! |
| 38 | CONSIDER YOUR DISK FRIED. |
| 39 | REMEMBER THE DISCLAIMER PART OF THE LICENSE. |
| 40 | |
| 41 | Running as user nobody and with all your filesystems |
| 42 | remounted to readonly may be wise.. |
| 43 | |
| robbiew | 95ed18e | 2002-02-19 21:40:14 +0000 | [diff] [blame^] | 44 | Disktest |
| 45 | |
| 46 | Does repeated accesses to a filespec and optionally writes to, reads from, |
| 47 | and verifies the data. By default, disktest makes assumptions about the running |
| 48 | environment which allows for a quick start of IO generation. However, Disktest has |
| 49 | a large number of command line options which can be used to adapt the test for a |
| 50 | variety of uses including data integraty, medium integraty, perforamance, and sim- |
| 51 | ple application simulation. |
| 52 | |
| robbiew | 2c26cc4 | 2001-09-25 17:34:51 +0000 | [diff] [blame] | 53 | f00f |
| 54 | |
| 55 | This is a simple test for handling of the pentium f00f bug. |
| 56 | It is an example of a catistrophic test case. If the system |
| 57 | doesn't correctly handle this test, it will likely lockup. |
| 58 | |