- Add serial=com1, serial=com2, serial=com3 or serial=com4 to the isolinux config file.
     KERNEL /pmagic/bzImage
     APPEND initrd=/ubcd/boot/cpustres.gz root=/dev/ram0 ramdisk_size=13000 serial=com1 ubcdcmd=stresscpu2
- Make a directory (mkdir ./cpustress-initrd).
- Mount the cpustress initrd image as root (sudo mount -o loop initrd ./cpustress-initrd).
- Uncomment the appropriate line in /etc/inittab.
- Unmount the initrd.

     APPEND initrd=/ubcd/boot/cpustres.gz root=/dev/ram0 ramdisk_size=13000 ubcdcmd=stresscpu2

LABEL -
MENU LABEL CPU Burn-in V1.00
TEXT HELP
Heats up any x86 CPU to the maximum possible operating temperature that is
achievable by using ordinary software. This allows the user to adjust the CPU
speed up to the practical maximum while still being sure that stability is
achieved even under the most stressful conditions.
ENDTEXT
KERNEL /pmagic/bzImage
APPEND initrd=/ubcd/boot/cpustres.gz root=/dev/ram0 ramdisk_size=13000 ubcdcmd=cpuburn

LABEL -
MENU LABEL CPUinfo
TEXT HELP
Gives info about your CPU: number of processors, vendor, CPU family, CPU model name,
CPU speed, cache size, possible construction bugs of your cpu, which extensions (flags)
your CPU supports.
ENDTEXT
KERNEL /pmagic/bzImage
APPEND initrd=/ubcd/boot/cpustres.gz root=/dev/ram0 ramdisk_size=13000 ubcdcmd=cpuinfo

LABEL -
MENU LABEL StressCPU 2 (requires CPU with SSE)
TEXT HELP
Torture-test your CPU in order to make sure that you don't have overheating
problems. Requires SSE-equipped x86 CPUs. Executes a special version of the
Gromacs innerloops that mixes SSE and normal assembly instructions to heat
your CPU as much as possible.
ENDTEXT
KERNEL /pmagic/bzImage
APPEND initrd=/ubcd/boot/cpustres.gz root=/dev/ram0 ramdisk_size=13000 ubcdcmd=stresscpu2

LABEL -
MENU LABEL Mersenne Prime Test V23.9/24.14
TEXT HELP
Mersenne Prime Search program that stresses the CPU.
ENDTEXT
KERNEL /pmagic/bzImage
APPEND initrd=/ubcd/boot/cpustres.gz root=/dev/ram0 ramdisk_size=13000 ubcdcmd=mprime

LABEL -
MENU LABEL Stress V1.00 - System Burn-In Test
TEXT HELP
Simple workload generator for POSIX systems. It imposes a configurable amount
of CPU, memory, I/O, and disk stress on the system. This menu item launches
stress with the "--help" parameter that displays all possible options. You
need to run it again with the stress test options that you prefer.
ENDTEXT
KERNEL /pmagic/bzImage
APPEND initrd=/ubcd/boot/cpustres.gz root=/dev/ram0 ramdisk_size=13000 ubcdcmd=stress

LABEL -
MENU LABEL Help for CPU stress image
TEXT HELP
Displays help for the programs inside the CPU stress image
ENDTEXT
KERNEL /pmagic/bzImage
APPEND initrd=/ubcd/boot/cpustres.gz root=/dev/ram0 ramdisk_size=13000 ubcdcmd=help

CPU Burn-in README
------------------

What is CPU Burn-in?
-------------------

CPU Burn-in v1.0 by Michal Mienik is the ultimate stability testing tool for overclockers. The program heats up any x86 CPU to the maximum possible operating temperature that is achievable by using ordinary software.  This allows the user to adjust the CPU speed up to the practical maximum while still being sure that stability is achieved even under the most stressful conditions. The program continuously monitors for erroneous calculations ensuring the CPU does not generate errors during calculations.

Note from Gert Hulselmans: 'cpuburn' is a wrapper that automaticly detects the number of CPUs so they can be stressed all at the same time. It will run an instance of 'cpuburn-in' for each CPU in order to heat all CPUs up at the same time.

Why use CPU Burn-in?
-------------------

In the past overclocking stability was tested by running intensive software such as Distributed.Net clients or SETI@home.  Running either piece of software for 24 hours would generally show up instability. A looping Quake3 timedemo was also a good choice.

However, there are inherent limitations in these tests:

Not every error caused by overclocking causes a program to crash or the system to hang. Some errors may be more subtle, such as a slight miscalculation. If such an event occurs and causes a pixel to render a slightly different colour in Quake3 for example, the user is unlikely to notice and overall this is no big deal. However such small errors can have a potentially devastating on distributed projects such as SETI@home, which rely on the reliable processing of data.

CPU Burn-in consistently delivers a higher CPU operating temperature than the above mentioned  applications.  This allows CPU Burn-in to be particularly effective at testing overclocking stability
and cooling effectiveness.

How does it work?
----------------

CPU Burn-in constantly cycles FPU intensive functions for a user specified period of time. The resultant calculations are constantly checked for data integrity.  If the program detects erroneous data the user is immediately informed.  Applications such as SETI@home and Distributed.Net perform no such data checking.  The user must rely on those programs to crash or the system to hang before a problem can be noticed.

Instructions:
------------

Please Note: Overclocking can potentially be harmful to your CPU.  It may fry or fail prematurely in the long term.  I cannot and will not be responsible for any damage you do to your hardware. By it's very nature, CPU Burn-in pushes the CPU to the max.  Increasing the voltage, Mhz, or PCI/AGP above the recommended levels can cause damage.

CPU Burn-in runs best as a high priority process on an otherwise idle system.



Run the program with one command line value to specify the length of time to run the test:

eg.
   "cpuburn 10"    will run the test for ten minutes.


If you want to run cpuburn-in for a certain time, you can also add a parameter to the isolinux config file:

eg. Run cpuburn-in for 10 days.

     KERNEL /pmagic/bzImage
     APPEND initrd=/ubcd/boot/cpustres.gz root=/dev/ram0 ramdisk_size=13000
            ubcdcmd=cpuburn days=10


eg. Run cpuburn-in for 10 hours.

     KERNEL /pmagic/bzImage
     APPEND initrd=/ubcd/boot/cpustres.gz root=/dev/ram0 ramdisk_size=13000
            ubcdcmd=cpuburn hours=10


eg. Run cpuburn-in for 10 minutes.

     KERNEL /pmagic/bzImage
     APPEND initrd=/ubcd/boot/cpustres.gz root=/dev/ram0 ramdisk_size=13000
            ubcdcmd=cpuburn minutes=10


If those parameters are all provided to the APPEND command of the isolinux config, the run time will be determined by the first value of the time duration which will be searched in the following order: days > hours > minutes.
So if 'minutes=100000000' and 'days=10' is found, the run time will be set to 14400 minutes (= 10 days).


If cpuburn is called without parameters, it will run cpuburn-in for 10080 minutes (= 7 days).


Contact:
-------
   
If your system experiences instability during the burn-in test or you receive error messages it's likely
the system has been overclocked too far.

If you believe a bug in the program has been found please email cluster2k@hotmail.com

                 ============
                 | CPU info |
                 ============

          Written by Gert Hulselmans
                on 25 July 2008

CPU info will give you some info about your CPU:
- number of processors
- Vendor
- CPU family
- CPU model name
- CPU speed
- cache size
- possible construction bugs of your CPU
- which flags your CPU supports
- ...

An example from my dual core PC:

processor   : 0
vendor_id   : AuthenticAMD
cpu family   : 15
model      : 107
model name   : AMD Athlon(tm) 64 X2 Dual Core Processor 5000+
stepping   : 1
cpu MHz      : 1000.000
cache size   : 512 KB
physical id   : 0
siblings   : 2
core id      : 0
cpu cores   : 2
fdiv_bug   : no
hlt_bug      : no
f00f_bug   : no
coma_bug   : no
fpu      : yes
fpu_exception   : yes
cpuid level   : 1
wp      : yes
flags      : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch ts fid vid ttp tm stc 100mhzsteps
bogomips   : 2062.54
clflush size   : 64

processor   : 1
vendor_id   : AuthenticAMD
cpu family   : 15
model      : 107
model name   : AMD Athlon(tm) 64 X2 Dual Core Processor 5000+
stepping   : 1
cpu MHz      : 1000.000
cache size   : 512 KB
physical id   : 0
siblings   : 2
core id      : 1
cpu cores   : 2
fdiv_bug   : no
hlt_bug      : no
f00f_bug   : no
coma_bug   : no
fpu      : yes
fpu_exception   : yes
cpuid level   : 1
wp      : yes
flags      : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch ts fid vid ttp tm stc 100mhzsteps
bogomips   : 2062.54
clflush size   : 64

Help: wrapper for the Mersenne Prime Torture test (mprime)
==========================================================

Written by Gert Hulselmans on 28 July 2008.
'mprime' is a wrapper that automaticly detects the number of CPUs so they can be
stressed all at the same time. It will run an instance of 'mprime' for each
CPU in order to heat all CPUs up at the same time. You can do this by running
the background option (-bn with n= number of processes). However, this option
does not display any output on the screen. This can be solved by running several
instances of mprime with the background (&) option of the shell. This method
displays the output of the multiple instances of mprime.

This wrapper avoids specifying the working directory part (-W) and the torure
(-t) option of the command 'mprime -t -W/tmp/torture-test/torture.XXXXXX',
so the user can run 'mprime' from a terminal without worrying which parameters
to add to use the torture test of Mersenne Prime Test.

Stress
******

* Menu:

* Overview::                    Overview of `stress'.
* Invoking stress::             How to run `stress'.
* Examples::                    Some example invocations.
* Copying This Manual::
* Index::

1 Overview of `stress'
**********************

`stress' is not a benchmark, but is rather a tool designed to put given
subsytems under a specified load.  Instances in which this is useful
include those in which a system administrator wishes to perform tuning
activities, a kernel or libc programmer wishes to evaluate denial of
service possibilities, etc.

2 Invoking stress
*****************

The format for running the `stress' program is:

     `stress' [OPTION [ARGS]] ...

   `stress' supports the following options:

`-?'
`--help'
     Show help information.

`--version'
     Show version information.

`-v'
`--verbose'
     Turn up verbosity.

`-q'
`--quiet'
     Turn down verbosity.

`-n'
`--dry-run'
     Show what would have been done.

`-t SECS'
`--timeout SECS'
     Time out after SECS seconds.

`--backoff USECS'
     Wait for factor of USECS microseconds before starting work.

`-c FORKS'
`--cpu FORKS'
     Spawn FORKS processes each spinning on `sqrt()'.

`-i FORKS'
`--io FORKS'
     Spawn FORKS processes each spinning on `sync()'.

`-m FORKS'
`--vm FORKS'
     Spawn FORKS processes each spinning on `malloc()'.

`-m FORKS'
`--vm FORKS'
     Spawn FORKS processes each spinning on `malloc()'.

`--vm-bytes BYTES'
     Allocate BYTES number of bytes.  The default is 1.

`--vm-hang'
     Instruct each vm hog process to go to sleep after allocating
     memory.  This contrasts with their normal behavior, which is to
     free the memory and reallocate _ad infinitum_.  This is useful for
     simulating low memory conditions on a machine.  For example, the
     following command allocates 256M of RAM and holds it until killed.

          % stress --vm 2 --vm-bytes 128M --vm-hang

NOTE: Don't use the following options!
      This cpustress image doesn't support writing to a disk.
      If you want to to stress the hard disk also, boot into windows and
      download Stress v1.01 or use a real linux distribution (e.g. Parted
      Magic) and run it from there.
`-d FORKS'
`--hdd FORKS'
     Spawn FORKS processes each spinning on `write()'.

`--hdd-bytes BYTES'
     Write BYTES number of bytes.  The default is 1GB.

`--hdd-noclean'
     Do not unlink file(s) to which random ASCII data is written.


   Note: Suffixes may be s,m,h,d,y (time) or k,m,g (size).

3 Example invocations
*********************

The simple case is that you just want to bring the system load average
up to an arbitrary value.  The following forks 13 processes, each of
which spins in a tight loop calculating the sqrt() of a random number
acquired with rand().

   % `stress -c 13'

   Long options are supported, as well as is making the output less
verbose.  The following forks 1024 processes, and only reports error
messages if any.

   % `stress --quiet --cpu 1k'

   To see how your system performs when it is I/O bound, use the -i
switch.  The following forks 4 processes, each of which spins in a
tight loop calling sync(), which is a system call that flushes memory
buffers to disk.

   % `stress -i 4'

   Multiple hogs may be combined on the same command line.  The
following does everything the preceding examples did in one command,
but also turns up the verbosity level as well as showing how to cause
the command to self-terminate after 1 minute.

   % `stress -c 13 -i 4 --verbose --timeout 1m'


NOTE: Don't use the following options!
      This cpustress image doesn't support writing to a disk.
      If you want to to stress the hard disk also, boot into windows and
      download Stress v1.01 or use a real linux distribution (e.g. Parted
      Magic) and run it from there.

   You can write a file of arbitrary length to disk.  The file is
created with mkstemp() in the current directory, the default is to
unlink it, but unlinking can be overridden with the -hdd-noclean flag.

   % `stress -d 1 --hdd-noclean --hdd-bytes 13'

   Large file support is enabled.

   % `stress -d 1 --hdd-noclean --hdd-bytes 3G'

Appendix A Copying This Manual
******************************

You may copy this manual under the terms of the GNU General Public
License.

     APPEND initrd=/ubcd/boot/cpustres/initrd.gz root=/dev/ram0
            ramdisk_size=12000 noapic ubcdcmd=

     APPEND initrd=/ubcd/boot/cpustres/initrd.gz root=/dev/ram0 ramdisk_size=12000 noapic ubcdcmd=

CPUstress image - version 2:
============================

Made by Gert Hulselmans.

Released under the GNU General Public License, version 2.

Last edited on 2 December 2008.

Content of this package:
_________________________

./build.tar      ==> tar archive that contains the files that you need to rebuild the image and the kernel

./bzImage      ==> kernel image

./gpl-2.0.txt      ==> GNU General Public License, version 2

./help/         ==> contains help texts for some programs (also available in the image itself)

./initrd.gz      ==> initrd

./README.txt      ==> this readme file


Content of the ./build.tar archive:
____________________________________

./busybox-config/
   .config      ==> configfile to configure busybox

./cpustress_build/   ==> contains all files which will be packed in the initrd

./kernel-config/
   .config      ==> configfile to configure the kernel

./mnt/         ==> directory where the initrd image gets mounted while building

./build         ==> build script to build the image


How to start?
_____________


Copy bzImage and initrd.gz to ./ubcd/boot/cpustres/ of your extracted UBCD iso.
(Don't use 'cpustress', isolinux only can handle 8 + 3  character filenames!)

Windows:
--------

e.g.: If you have extracted UBCD to c:\ubcd-extract\, this place is:
      c:\ubcd-extract\ubcd\boot\cpustres\

Linux:
------

e.g.: If you have extracted UBCD to ~/ubcd-extract/, this place is:
      ~/ubcd-extract/ubcd/boot/cpustres/


How to edit the CPUstress image?
________________________________

Unpack the cpustress-2.7z archive (you probably already did this, else you couln't read this README.
$ mkdir cpustress-v2
$ cd cpustress-v2
$ 7z x "./path/to/file/cpustress-v2.7z"

extract the ./build tar archive
$ tar xvf build.tar

Become root (use 'su root' to become root or prefix the following commands with 'sudo') and execute
the following commands as root to create the necessary device nodes.

$ mknod ./cpustress_build/dev/console c 4 0
$ mknod ./cpustress_build/dev/null c 1 3
$ mknod ./cpustress_build/dev/ram0 b 1 0

Now you can edit the files in ./cpustress_build/ and remaster the initrd.gz with the ./build script.
You have to run the ./build script as root user or with sudo.

./cpustress_build/usr/local/bin/ (/usr/local/bin/ directory in the image) contains the cpustress
specific programs, like cpuburn, cpuinfo, helpinfo, menu, mprime, stress and stresscpu2.

./cpustress_build/opt/ (/opt/ directory in the image) directory contains some help files and some
cpustress specific programs.


Contents of the isolinux config files:
______________________________________

  ############################################################
  # REMARK: All APPEND stuff should be on 1 line.            #
  #         For readability reasons it is placed on 2 lines. #
  ############################################################

CPU Burn-in v1.00: cpuburn
------------------

Run cpuburn without time parameter (it will run cpuburn-in for 10080
minutes (= 7 days)).

     KERNEL /ubcd/boot/cpustres/bzImage
     APPEND initrd=/ubcd/boot/cpustres/initrd.gz root=/dev/ram0
            ramdisk_size=12000 noapic ubcdcmd=cpuburn

Run cpuburn with a time parameter:

  eg. Run cpuburn for 10 days.

     KERNEL /ubcd/boot/cpustres/bzImage
     APPEND initrd=/ubcd/boot/cpustres/initrd.gz root=/dev/ram0
            ramdisk_size=12000 noapic ubcdcmd=cpuburn days=10

  eg. Run cpuburn for 10 hours.

     KERNEL /ubcd/boot/cpustres/bzImage
     APPEND initrd=/ubcd/boot/cpustres/initrd.gz root=/dev/ram0
            ramdisk_size=12000 noapic ubcdcmd=cpuburn hours=10

  eg. Run cpuburn for 10 minutes.

     KERNEL /ubcd/boot/cpustres/bzImage
     APPEND initrd=/ubcd/boot/cpustres/initrd.gz root=/dev/ram0
            ramdisk_size=12000 noapic ubcdcmd=cpuburn minutes=10


If those parameters are all provided to the APPEND command of the isolinux
config, the run time will be determined by the first value of the time duration
which will be searched in the following order: days > hours > minutes.
So if 'minutes=100000000' and 'days=10' is found, the run time will be set to
14400 minutes (= 10 days).


CPUinfo v1.00: cpuinfo
--------------

The following isolinux entry will run CPUinfo:

     KERNEL /ubcd/boot/cpustres/bzImage
     APPEND initrd=/ubcd/boot/cpustres/initrd.gz root=/dev/ram0
            ramdisk_size=12000 noapic ubcdcmd=cpuinfo


Helpinfo: helpinfo
---------

The following isolinux entry will run Helpinfo:

    KERNEL /ubcd/boot/cpustres/bzImage
    APPEND initrd=/ubcd/boot/cpustres/initrd.gz root=/dev/ram0
           ramdisk_size=12000 noapic ubcdcmd=helpinfo


The following isolinux entry will run Helpinfo for cpuburn:

    KERNEL /ubcd/boot/cpustres/bzImage
    APPEND initrd=/ubcd/boot/cpustres/initrd.gz root=/dev/ram0
           ramdisk_size=12000 noapic ubcdcmd=helpinfo cmdhelpinfo=cpuburn

You can change the cmdhelpinfo parameter to:
    - cpuburn
    - cpuinfo
    - helpinfo
    - mprime
    - stress
    - stresscpu2

Menu: menu
-----

The following isolinux entry will display the menu.

    KERNEL /ubcd/boot/cpustres/bzImage
    APPEND initrd=/ubcd/boot/cpustres/initrd.gz root=/dev/ram0
           ramdisk_size=12000 noapic ubcdcmd=menu

Mersenne Prime Torture test: mprime
----------------------------

The following isolinux entry will prompt to ask which version of mprime you want to run.

    KERNEL /ubcd/boot/cpustres/bzImage
    APPEND initrd=/ubcd/boot/cpustres/initrd.gz root=/dev/ram0
           ramdisk_size=12000 noapic ubcdcmd=mprime

If you want to run a specific version of mprime, when you boot the image, use:

    KERNEL /ubcd/boot/cpustres/bzImage
    APPEND initrd=/ubcd/boot/cpustres/initrd.gz root=/dev/ram0
           ramdisk_size=12000 noapic ubcdcmd=mprime23

      This will start 'Mersenne Prime 23.5.2'.

    KERNEL /ubcd/boot/cpustres/bzImage
    APPEND initrd=/ubcd/boot/cpustres/initrd.gz root=/dev/ram0
           ramdisk_size=12000 noapic ubcdcmd=mprime24

      This will start 'Mersenne Prime 24.14.2'.


Stress v1.0.0: stress
--------------

The following isolinux entry will run stress (will display the help text).

    KERNEL /ubcd/boot/cpustres/bzImage
    APPEND initrd=/ubcd/boot/cpustres/initrd.gz root=/dev/ram0
           ramdisk_size=12000 noapic ubcdcmd=stress

If you want to run a stress with specific parameters, when you boot the image,
use something similar to:

    KERNEL /ubcd/boot/cpustres/bzImage
    APPEND initrd=/ubcd/boot/cpustres/initrd.gz root=/dev/ram0
           ramdisk_size=12000 noapic ubcdcmd=stress cmdstress="--quiet -c 1k"

The cmdstress parameter contains the options that you want to pass to stress.


CPU stress tester 2.0: stresscpu2
----------------------

The following isolinux entry will run stresscpu2 (will display the help text).

    KERNEL /ubcd/boot/cpustres/bzImage
    APPEND initrd=/ubcd/boot/cpustres/initrd.gz root=/dev/ram0
           ramdisk_size=12000 noapic ubcdcmd=stresscpu2

Thanks:
_______

Thanks go to the following persons:

* deadite:        for testing my first cpustress image, for revealing the booting problem
                  on some machines, for revealing that USB and wireless keyboards didn't work
                  with the first version and for correcting the help files.
* StopSpazzing:   for testing the second version of my cpustress image with an USB keyboard.
* Patrick Verner: for compiling a minimal kernel that enables support for USB and wireless
                  keyboards and for solving some other problems that I had.
* alm:            for discovering the 'FATAL ERROR: Writing to temp file' bug with mprime.

Contact:
________

http://www.ultimatebootcd.com/forums/viewtopic.php?t=1476
Ask for Icecube ;-).

'helpinfo' displays the help text in such a way so that you can easily navigate
through it.

Use '<SPACE>', '<PageUp>', '<PageDown>', '<Up>' and '<Down>' to navigate
through the text. Press 'q' to quit 'helpinfo'.


Some general commands for all programs:
                            To reboot, press: '<Ctrl> + <Alt> + <Del>'
                    To quit a program, press: '<Ctrl> + C' or 'q'
To switch to another virtual terminal, press: '<Alt> + <Left/Right>'


'top' is usefull program to see the percentage of processing power used by a
specific program. When you run a CPU stress test, you will see that the
total persentage of the processing power is 100%.
    To quit 'top', you have to press 'q' or '<Ctrl> + C'.


By typing 'menu' at the terminal window, you will get a menu from which you can select the following programs:
   - CPU Burn-in v1.00       (cpuburn)
   - CPUinfo v1.00           (cpuinfo)
   - Helpinfo                (helpinfo)
   - Mersenne Prime v23.5.2  (mprime 23)
   - Mersenne Prime v24.14.2 (mprime 24)
   - Stress v1.0.0           (stress)
   - CPU stress tester 2.0   (stresscpu2)



Help is available for the following executables:
  * CPU stress and info tools:
   - CPU Burn-in v1.00       (cpuburn)
   - CPUinfo v1.00           (cpuinfo)
   - Helpinfo                (helpinfo)
   - Mersenne Prime          (mprime)
   - Stress v1.0.0           (stress)
   - CPU stress tester 2.0   (stresscpu2)


    If you want help for 'CPU Burn-in v1.00'.
    Run 'helpinfo cpuburn' in the terminal.

    KERNEL /ubcd/boot/cpustres/bzImage
    APPEND initrd=/ubcd/boot/cpustres/initrd.gz root=/dev/ram0
           ramdisk_size=12000 noapic ubcdcmd=mprime24