cpuburn(1) [debian man page]

cpuburn(1)																cpuburn(1)

NAME

       cpuburn, burnBX, burnK6, burnK7, burnMMX, burnP5, burnP6 - a collection of programs to put heavy load on CPU

SYNOPSIS

       burnBX
       burnK6
       burnK7
       burnMMX
       burnP5
       burnP6

DESCRIPTION

       These  programs	are designed to load x86 CPUs as heavily as possible for the purposes of system testing ("burn in").  They have been opti-
       mized for different processors.	FPU and ALU instructions are coded in an assembler endless loop.  They do not test every instruction.  The
       goal  has  been to maximize heat production from the CPU, putting stress on the CPU itself, cooling system, motherboard (especially voltage
       regulators) and power supply (likely cause of burnBX/burnMMX errors).  The programs produce no output, but  signal  hardware  errors  by  a
       return code or (more likely) your machine locking up.

       burnP5	 is optimized for Intel Pentium with or without MMX CPUs
       burnP6	 is optimized for Intel PentiumPro, Pentium II & III CPUs
       burnK6	 is optimized for AMD K6 CPUs
       burnK7	 is optimized for AMD Athlon/Duron CPUs
       burnMMX	 tests cache/memory interfaces on all CPUs with MMX
       burnBX	 is an alternate cache/memory test for Intel CPUs

USAGE

       Burn  testing  is  designed to make your computer glitch if it has hardware problems, so make sure that nothing critical is running and all
       critical data is saved back to the hard-drives.	The best is to run it with filesystems mounted read-only.  Note that root  privileges  are
       not required.

       Run  the desired program in the background, checking the error result.  You'll may want to repeat this command for every processor you have
       in an SMP or HyperThreading system.  For example,

	   burnP6 || echo $? &

       Monitor progress of cpuburn by ps.  You can monitor CPU temperature and/or system voltages through ACPI or using the lm-sensors package	if
       you system supports it.	When finished, kill the burn* process(es).  For example,

	   killall burnP6

BUGS

       Report all bug to submit@bugs.debian.org, for more information visit http://bugs.debian.org

AUTHORS

       cpuburn was written by Robert Redelmeier <redelm@ev1.net>

								   June 04, 2011							cpuburn(1)

Check Out this Related Man Page

cpu_capabilities(3alleg4)					  Allegro manual					 cpu_capabilities(3alleg4)

NAME

       cpu_capabilities - Contains the capability flags of the CPU. Allegro game programming library.

SYNOPSIS

       #include <allegro.h>

       extern int cpu_capabilities;

DESCRIPTION

       Contains CPU flags indicating what features are available on the current CPU. The flags can be any combination of these:

	  CPU_ID       - Indicates that the "cpuid" instruction is
			 available. If this is set, then all Allegro CPU
			 variables are 100% reliable, otherwise there
			 may be some mistakes.
	  CPU_FPU      - An FPU is available.
	  CPU_IA64     - Running on Intel 64 bit CPU
	  CPU_AMD64    - Running on AMD 64 bit CPU
	  CPU_MMX      - Intel MMX  instruction set is available.
	  CPU_MMXPLUS  - Intel MMX+ instruction set is available.
	  CPU_SSE      - Intel SSE  instruction set is available.
	  CPU_SSE2     - Intel SSE2 instruction set is available.
	  CPU_SSE3     - Intel SSE3 instruction set is available.
	  CPU_3DNOW    - AMD 3DNow! instruction set is available.
	  CPU_ENH3DNOW - AMD Enhanced 3DNow! instruction set is
			 available.
	  CPU_CMOV     - Pentium Pro "cmov" instruction is available.

       You  can check for multiple features by OR-ing the flags together.  For example, to check if the CPU has an FPU and MMX instructions avail-
       able, you'd do:

	  if ((cpu_capabilities & (CPU_FPU | CPU_MMX)) ==
	      (CPU_FPU | CPU_MMX)) {
	     printf("CPU has both an FPU and MMX instructions!
");
	  }

       You can read this variable after you have called check_cpu() (which is automatically called by allegro_init()).

SEE ALSO

       check_cpu(3alleg4), cpu_vendor(3alleg4), cpu_family(3alleg4), cpu_model(3alleg4), cpu_capabilities(3alleg4), allegro_init(3alleg4)

Allegro 							   version 4.4.2					 cpu_capabilities(3alleg4)

Linux and UNIX Man Pages

cpuburn(1) [debian man page]

Check Out this Related Man Page