How long should an athlon 1800 take to complete the memory test? Can I assume from this that my memory is bad? I've had to interrupt the test as I need to use the computer. Thanks, Steve.
On Tue, 2005-03-22 at 14:07 +0100, steve wrote:
How long should an athlon 1800 take to complete the memory test? Can I assume from this that my memory is bad?
I've had to interrupt the test as I need to use the computer.
Thanks, Steve.
I believe it runs in a loop so it will run until you stop it. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken Schneider wrote:
On Tue, 2005-03-22 at 14:07 +0100, steve wrote:
How long should an athlon 1800 take to complete the memory test? Can I assume from this that my memory is bad?
I believe it runs in a loop so it will run until you stop it.
Is "why?" a silly question? Rgds Martin
On Tuesday 22 March 2005 13:49, Martin Cleaver wrote:
Is "why?" a silly question? Not a silly question at all - basically there can be "problems" with memory that doesn't show up on the full suite of tests after the first run - could be due to heating/cooling problems on the chips, "dry" joints, that sort of thing. The initial run should detect any "logical" problems (leaky cells, that sort of thing) , whereas running it overnight should help detect random physical problems.
Well, that's my impression, anyway :grins: Jon
Martin Cleaver wrote:
Ken Schneider wrote:
On Tue, 2005-03-22 at 14:07 +0100, steve wrote:
How long should an athlon 1800 take to complete the memory test? Can I assume from this that my memory is bad?
I believe it runs in a loop so it will run until you stop it.
Is "why?" a silly question?
Memory problems might be intermittent or appear after a considerable time.
On Tuesday 22 March 2005 9:03 pm, James Knott wrote:
Martin Cleaver wrote:
Ken Schneider wrote:
On Tue, 2005-03-22 at 14:07 +0100, steve wrote:
How long should an athlon 1800 take to complete the memory test? Can I assume from this that my memory is bad?
I believe it runs in a loop so it will run until you stop it.
Is "why?" a silly question?
Memory problems might be intermittent or appear after a considerable time.
Indeed. About 4 years ago I had an old (k6-2) system that had one bad stick of ram. About a month after every cold boot the same memory location would fail. That location happened to be one that libqt was always using. All of a sudden I wouldn't be able to run anything linked to qt. When I finally bought a new system, I ran memtest86 to find out which stick was bad. It took a month for the bad address to show up. -- James Oakley Engineering - SolutionInc Ltd. joakley@solutioninc.com http://www.solutioninc.com
steve zei:
How long should an athlon 1800 take to complete the memory test? Can I assume from this that my memory is bad?
Depending how much mem you test. I suppose that in 4 hours you should have seen some complete passes. Use last version of memtest86 (3.2)
I've had to interrupt the test as I need to use the computer.
Thanks, Steve.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- L. de Braal BraHa Systems NL Terneuzen T +31 115 649333 F +31 115 649444
* Leen de Braal
steve zei:
How long should an athlon 1800 take to complete the memory test? Can I assume from this that my memory is bad?
Depending how much mem you test. I suppose that in 4 hours you should have seen some complete passes. Use last version of memtest86 (3.2)
For 1.5G on an athlon 1500 it takes something like 24 hours to run all tests upto and includign test #7. If you enable all tests (upto 10 or 12 or something) it will take much longer (days). Haven;t checked if memtest 3.2 has a serious performance improvement, but I doubt it. Kind regards, -- Gerhard den Hollander Phone :+31-10.280.1515 Global ICT manager Direct:+31-10.280.1539 Fugro-Jason Fax :+31-10.280.1511 gdenhollander@Fugro-Jason.com POBox 1573 visit us at http://www.Fugro-Jason.com 3000 BN Rotterdam JASON.......#1 in Reservoir Characterization The Netherlands This e-mail and any files transmitted with it are confidential and intended solely for the use of the addressee. This e-mail shall not be deemed binding unless confirmed in writing. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.
Gerhard, On Tuesday 22 March 2005 05:55, Gerhard den Hollander wrote:
...
For 1.5G on an athlon 1500 it takes something like 24 hours to run all tests upto and includign test #7. If you enable all tests (upto 10 or 12 or something) it will take much longer (days).
Wow! On my 3.0 GHz Pentium 4 with 2 GB of 400 MHz DRAM, the default set of tests (all but the last two) takes a little less than a half an hour.
Haven;t checked if memtest 3.2 has a serious performance improvement, but I doubt it.
Memtest86 (and any memory diagnostic software) is utterly memory-limited. The only way to speed it up would be to have it make less stringent tests.
Gerhard den Hollander
Randall Schulz
steve wrote:
How long should an athlon 1800 take to complete the memory test? Can I assume from this that my memory is bad?
It has a suite of tests it runs, then it starts all over. In 4 hours it probably started over a few times. It has a status line to say this. -- "In everything, do to others what you would have them do to you." Matthew 7:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
On Tuesday 22 March 2005 13:07, steve wrote:
How long should an athlon 1800 take to complete the memory test? Can I assume from this that my memory is bad?
Did it show any errors? If not, then no, it doesn't mean anything bad that it ran for hours. Usually if there are egregious problems with the memory they will show themselves relatively quickly, but memtest writes a whole bunch of patterns to the memory to test it. The whole thing could go on exhaustively for ages. But I must say if I had an error free 4 hour run I would give up and assume the memory is OK unless you have unexplained crashes or other reasons to believe it's bad. If you had errors, and you have more than one stick, remove one and run again, then remove the other and replace the first and run again. If you only find errors on one stick, then that's all you need to replace ... HTH Fergus
I've had to interrupt the test as I need to use the computer.
Thanks, Steve.
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
On Wed, 23 Mar 2005 01:17 am, Fergus Wilde wrote:
On Tuesday 22 March 2005 13:07, steve wrote:
How long should an athlon 1800 take to complete the memory test? Can I assume from this that my memory is bad?
Did it show any errors? If not, then no, it doesn't mean anything bad that it ran for hours. Usually if there are egregious problems with the memory they will show themselves relatively quickly, but memtest writes a whole bunch of patterns to the memory to test it. The whole thing could go on exhaustively for ages. But I must say if I had an error free 4 hour run I would give up and assume the memory is OK unless you have unexplained crashes or other reasons to believe it's bad.
Exactly. If you just want to see if a second hand stick of ram is any good, a run of a few hours should settle it. No errors listed below the bar = good. _IF_ you are having crashes, memtest is a good first test. If a run of a few days doesn't produce anything, then it's probably safe to rule out memory errors and look elsewhere for the problem. (Don't forget the power supply) I once had a memory error so subtle I could run memtest all weekend and only get 1 glitch. It was giving me a couple of crashes a week though and each crash left files that hung any process that read them. You can imagine how unusable my desktop got once there were a few of these pitfalls around. Replacement RAM and fsck.reiserfs --fix-fixable cured it. FWIW, michaelj -- Michael James michael.james@csiro.au System Administrator voice: 02 6246 5040 CSIRO Bioinformatics Facility fax: 02 6246 5166
On Tuesday 22 March 2005 23:59, Michael James wrote:
On Wed, 23 Mar 2005 01:17 am, Fergus Wilde wrote:
On Tuesday 22 March 2005 13:07, steve wrote:
How long should an athlon 1800 take to complete the memory test? Can I assume from this that my memory is bad?
Did it show any errors? If not, then no, it doesn't mean anything bad that it ran for hours. Usually if there are egregious problems with the memory they will show themselves relatively quickly, but memtest writes a whole bunch of patterns to the memory to test it. The whole thing could go on exhaustively for ages. But I must say if I had an error free 4 hour run I would give up and assume the memory is OK unless you have unexplained crashes or other reasons to believe it's bad.
Exactly. If you just want to see if a second hand stick of ram is any good, a run of a few hours should settle it. No errors listed below the bar = good.
_IF_ you are having crashes, memtest is a good first test. If a run of a few days doesn't produce anything, then it's probably safe to rule out memory errors and look elsewhere for the problem. (Don't forget the power supply)
I once had a memory error so subtle I could run memtest all weekend and only get 1 glitch. It was giving me a couple of crashes a week though and each crash left files that hung any process that read them. You can imagine how unusable my desktop got once there were a few of these pitfalls around. Replacement RAM and fsck.reiserfs --fix-fixable cured it.
FWIW, michaelj
Hi. No. It's in conjuction with the other thread on the list at the moment entitled, 'Re: [SLE] internal compiler error (second attempt)'. As I'm not allowed to ask multiple questions I had to break it into these two items. Sorry. THanks for your reply. Steve.
participants (12)
-
Felix Miata -
Fergus Wilde -
Gerhard den Hollander -
James Knott -
James Oakley -
Jon Jeffels -
Ken Schneider -
Leen de Braal -
Martin Cleaver -
Michael James -
Randall R Schulz -
steve