Hardware testing - Revision history

Sergey Bronnikov: Marked this version for translation

2015-12-26T08:40:00Z

Marked this version for translation

Sergey Bronnikov: add 'translate' tags

2015-12-25T22:44:20Z

add 'translate' tags

Sergey Bronnikov: Add category QA

2015-04-09T14:39:57Z

Add category QA

Kir: Protected "Hardware testing" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

2010-05-31T20:49:41Z

Protected "Hardware testing" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

Kir: Reverted edits by Lossy (Talk) to last revision by Dev

2010-05-31T20:48:46Z

Reverted edits by Lossy (Talk) to last revision by Dev

Lossy: misc corrections

2010-05-31T10:16:47Z

misc corrections

Dev at 14:38, 23 October 2006

2006-10-23T14:38:54Z

Kir: shhh...should be machine check exception

2006-07-11T05:23:15Z

shhh...should be machine check exception

Kir: Added a link to Memory check exception

2006-07-11T05:22:27Z

Added a link to Memory check exception

Kir: added to troubleshooting cat.

2006-06-06T10:05:40Z

added to troubleshooting cat.

@@ Line 1: / Line 1: @@
 <translate>
 Sometimes when you have a kernel panic, oops, [[machine check exception]], or other fatal crash, this is not programmers whom to blame, but your hardware (a classical example is {{Bug|174}}). This article describes how to properly test your hardware to check it is in a good shape.
 Note that most of the tests described below could do harm to your machine if something is wrong with it (e.g. it is overclocked, undercooled etc). In general, overclocking is not recommended for your production server boxes.
-== RAM tests ==
+== RAM tests == <!--T:3-->
 Random Access Memory (RAM) is sometimes faulty, which leads to some very strange system crashes. It is though highly recommended to test your system RAM. A several approaches and tools can be used.
-=== Memtest86 and Memtest86+ ===
+=== Memtest86 and Memtest86+ === <!--T:4-->
 [http://memtest86.com/ Memtest86] is a stand-alone RAM tester. It can either be booted from a CD, or from your normal Linux bootloader, such as GRUB or LILO.
 [http://memtest.org/ Memtest86+] is a forked version of Memtest86 with some features added.
-==== Installation ====
+==== Installation ==== <!--T:6-->
 You can either download and install one of this programs from the sites above, or they can be a part of your Linux distribution already.
 For Fedora Core, memtest86+ is available:
 <pre>yum install memtest86+</pre>
 For Gentoo, both programs are available:
 <pre>emerge memtest86
 emerge memtest86+</pre>
-==== Usage ====
+==== Usage ==== <!--T:9-->
 To test your system for faulty RAM, install either memtest and reboot into it. Run it for at least a few hours (at least 2-3 iterations). If there will be even a single error reported, you have to change your RAM chips (or, if your system is overclocked, downclock it to normal speed).
-=== Memtester ===
+=== Memtester === <!--T:10-->
 [http://pyropus.ca/software/memtester/ Memtester] is a userspace utility for testing the memory subsystem for faults. The good thing is you can test your memory without a need to reboot the server, and you can run other programs with it. The bad thing is not all the memory is tested.
-==== Installation ====
+==== Installation ==== <!--T:11-->
 For Fedora Core:
 <pre>yum install memtester</pre>
 For Gentoo:
 <pre>emerge memtester</pre>
 For other systems: download the sources from the [http://pyropus.ca/software/memtester/ Memtester homepage].
-==== Usage ====
+==== Usage ==== <!--T:14-->
 Invoke memtester as a root, giving an amount of memory it will test as an argument, e.g.:
 <pre># /usr/sbin/memtester 512M</pre>
 The more memory you will specify the better.
-== CPU cooling tests ==
+== CPU cooling tests == <!--T:17-->
 Such tests checks that your CPU can work fine under highest possible load and temperature.
-=== Cpuburn ===
+=== Cpuburn === <!--T:18-->
 [http://pages.sbcglobal.net/redelm/ Сpuburn] is an utility to burn your CPU as high as possible. It tests your system stability by checking how the CPU and the whole system is working under high temperatures.
-=== Installation ===
+=== Installation === <!--T:19-->
 For Fedora Core you can get the RPMS from [http://dag.wieers.com/packages/cpuburn/ DAG].
 For Gentoo:
 <pre>emerge cpuburn</pre>
 For other systems: download tarball from the [http://pages.sbcglobal.net/redelm/ home page], untar and run.
-=== Usage ===
+=== Usage === <!--T:23-->
 It is recommended to switch to single-user mode and remount all the partitions read-only, just in case of system hang.
 Run
 <pre>burnBX || echo $? &</pre>
@@ Line 67: / Line 80: @@
 <pre>killall -TERM burnBX</pre>
 You can also use burnMMX utility:
 <pre>burnMMX J || echo $? &</pre>
 Cpuburn author says burnMMX is not optimal for AMD processors; use burnBX if you have AMD.
-== Combined tests ==
+== Combined tests == <!--T:27-->
 It is also a good thing to run cpuburn and memtester in parallel. Chances are higher that some more errors are detected that way.
-== Cerberus Test Control System ==
+== Cerberus Test Control System == <!--T:29-->
 Another test for hardware publicly available is '''Cerberus Test Control System'''
 http://sourceforge.net/projects/va-ctcs/
-== External links ==
+== External links == <!--T:30-->
 * [http://memtest86.com/ Memtest86]
 * [http://memtest.org/ Memtest86+]

@@ Line 1: / Line 1: @@
 Sometimes when you have a kernel panic, oops, [[machine check exception]], or other fatal crash, this is not programmers whom to blame, but your hardware (a classical example is {{Bug|174}}). This article describes how to properly test your hardware to check it is in a good shape.
@@ Line 85: / Line 86: @@
 * [http://pages.sbcglobal.net/redelm/ Сpuburn]
 * [http://sourceforge.net/projects/va-ctcs/ Cerberus]
 [[Category: Troubleshooting]]
 [[Category: QA]]

← Older revision		Revision as of 14:39, 9 April 2015
Line 87:		Line 87:

	[[Category: Troubleshooting]]		[[Category: Troubleshooting]]
		+	[[Category: QA]]

@@ Line 85: / Line 85: @@
 * [http://pages.sbcglobal.net/redelm/ Сpuburn]
 * [http://sourceforge.net/projects/va-ctcs/ Cerberus]
-* [http://www.bestessays.com/doc_essay.php essay]
 [[Category: Troubleshooting]]

@@ Line 85: / Line 85: @@
 * [http://pages.sbcglobal.net/redelm/ Сpuburn]
 * [http://sourceforge.net/projects/va-ctcs/ Cerberus]
+* [http://www.bestessays.com/doc_essay.php essay]
 [[Category: Troubleshooting]]

← Older revision	Revision as of 20:49, 31 May 2010
(No difference)

← Older revision		Revision as of 05:23, 11 July 2006
Line 1:		Line 1:
−	Sometimes when you have a kernel panic, oops, [[~~memory~~ check exception]], or other fatal crash, this is not programmers whom to blame, but your hardware (a classical example is {{Bug\|174}}). This article describes how to properly test your hardware to check it is in a good shape.	+	Sometimes when you have a kernel panic, oops, [[machine check exception]], or other fatal crash, this is not programmers whom to blame, but your hardware (a classical example is {{Bug\|174}}). This article describes how to properly test your hardware to check it is in a good shape.

	Note that most of the tests described below could do harm to your machine if something is wrong with it (e.g. it is overclocked, undercooled etc). In general, overclocking is not recommended for your production server boxes.		Note that most of the tests described below could do harm to your machine if something is wrong with it (e.g. it is overclocked, undercooled etc). In general, overclocking is not recommended for your production server boxes.

← Older revision		Revision as of 05:22, 11 July 2006
Line 1:		Line 1:
−	Sometimes when you have a kernel panic, oops, or other fatal crash, this is not programmers whom to blame (a classical example is {{Bug\|174}}). This article describes how to properly test your hardware to check it's in a good shape.	+	Sometimes when you have a kernel panic, oops, [[memory check exception]], or other fatal crash, this is not programmers whom to blame, but your hardware (a classical example is {{Bug\|174}}). This article describes how to properly test your hardware to check it is in a good shape.

	Note that most of the tests described below could do harm to your machine if something is wrong with it (e.g. it is overclocked, undercooled etc). In general, overclocking is not recommended for your production server boxes.		Note that most of the tests described below could do harm to your machine if something is wrong with it (e.g. it is overclocked, undercooled etc). In general, overclocking is not recommended for your production server boxes.

← Older revision		Revision as of 10:05, 6 June 2006
Line 80:		Line 80:
	* [http://pyropus.ca/software/memtester/ Memtester]		* [http://pyropus.ca/software/memtester/ Memtester]
	* [http://pages.sbcglobal.net/redelm/ Сpuburn]		* [http://pages.sbcglobal.net/redelm/ Сpuburn]
		+
		+	[[Category: Troubleshooting]]