This is a multi-part MIME message sent by reportbug.

Package: cpuburn
Version: 1.4-37
Severity: minor


The man page for the cpuburn collection of programs is missing essential 
information necessary for using them.  For example, it does not mention 
that the programs print no error messages, or any messages at all, but 
instead return an exit code to the shell.

I've rewritten the man page using information from the author's 
README and the source code and attached it to this bug report.

-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages cpuburn depends on:
ii  debconf [debconf-2.0]         1.5.24     Debian configuration management sy

cpuburn recommends no packages.

Versions of packages cpuburn suggests:
pn  hwtools                       <none>     (no description available)
pn  kernel-patch-badram           <none>     (no description available)
ii  memtest86                     3.4-2      thorough real-mode memory tester
ii  memtester                     4.0.8-1    A utility for testing the memory s

-- debconf information:
* cpuburn/dangerous:
.TH cpuburn 1 "August 30, 2002" "" ""
.SH NAME
\fBcpuburn, burnBX, burnK6, burnK7, burnMMX, burnP5, burnP6 \fP- a collection 
of programs to put heavy load on CPU
.SH SYNOPSIS
.nf
.fam C
\fBburnP6\fP || echo $?
\fBburnP5\fP || echo $?
\fBburnK7\fP || echo $?
\fBburnK6\fP || echo $?
\fBburnBX\fP [\fIA-P\fP] || echo $?
\fBburnMMX\fP [\fIA-P\fP] || echo $?
.fam T
.fi
.SH DESCRIPTION
.PP
These programs are designed to load x86 CPUs as heavily as possible
for the purposes of system testing ("burn in").  They have been
optimized 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
\fBburnBX\fP/\fBburnMMX\fP errors).  The programs produce no output,
but signal hardware errors by a return code or (more likely) your
machine locking up.

.TS
rB lR.
burnP5  is optimized for Intel Pentium with or without MMX processors
P6      is for Intel PentiumPro, Pentium II & III and Celeron CPUs
K6      is for AMD K6 processors
K7      is for AMD Athlon/Duron processors
MMX     is to test cache/memory interfaces on all CPUs with MMX
BX      is an alternate cache/memory test for Intel CPUs
.TE
.P

.SH USAGE
Burn testing is designed to make your computer glitch if it has
hardware problems, so it is best done from a ramdisk distribution
(tomsrtbt) or with filesystems unmounted or mounted read-only.  Note
that \fIroot\fP privileges are not required.

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

.fam C
        burnP6 || echo $? &
.fam T

Monitor progress of cpuburn by \fBps\fP.  When finished, \fBkill\fP
the \fBburn*\fP process(es).  For example, \fCpkill burnP6\fP.  If you
have temperature probes (fingers), ACPI, or the lm-sensors package,
you can check your CPU temperature and/or system voltages.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to