Re: [gentoo-user] memtest86+ taking too long
On Nov 19, 2007 12:03 PM, de Almeida, Valmor F. [EMAIL PROTECTED] wrote: Hello, After looking at the /var/log/messages file, I saw an entry which seemed to indicate a memory address problem. I decided to run memtest86+. However it is taking too long. So far 17 hours and still going. The Pass field reads 25%; I hope this is an indication of how much of the total has been done. The Test field is frequently updated so it seems memtest is running. The total memory is 10GB, the chipset: Intel E7505 ECC. Is this execution time expected? Thanks for any comments, -- Valmor de Almeida -- [EMAIL PROTECTED] mailing list For 10 gigs? probably. -- - Mark Shields
RE: [gentoo-user] memtest86+ taking too long
From: Mark Shields [mailto:[EMAIL PROTECTED] On Nov 19, 2007 12:03 PM, de Almeida, Valmor F. [EMAIL PROTECTED] wrote: Is this execution time expected? Thanks for any comments, -- Valmor de Almeida For 10 gigs? probably. Wow. In fact I don't have a clue when it is going to end. There are 2 fields with varying percentage values; but they get cleared from time to time. Another field is called Test and it was #3 (I think), and now it is at #4. So far it has taken 20:35h. On the upside, no errors detected. -- Valmor de Almeida -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] memtest86+ taking too long
memtest86 will keep retesting your memory over and over. Look at the Pass and Errors column. If Errors is 0 and Pass is more than 1, your memory is fine. If Pass is 0 and Errors is 0, then it is still on the first run. It shouldn't take this long. In that case make sure you have the latest version. Example: http://www.memtest.org/pics/i875-big.gif On Nov 19, 2007 12:47 PM, de Almeida, Valmor F. [EMAIL PROTECTED] wrote: Wow. In fact I don't have a clue when it is going to end. There are 2 fields with varying percentage values; but they get cleared from time to time. Another field is called Test and it was #3 (I think), and now it is at #4. So far it has taken 20:35h. On the upside, no errors detected. -- [EMAIL PROTECTED] mailing list
RE: [gentoo-user] memtest86+ taking too long
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bryan memtest86 will keep retesting your memory over and over. Look at the Pass and Errors column. If Errors is 0 and Pass is more than 1, your memory is fine. If Pass is 0 and Errors is 0, then it is still on the first run. It shouldn't take this long. In that case make sure you have the latest version. Excellent. I have the latest version 1.70, and the Pass column is at 4 and no errors. Thanks, -- Valmor -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] memtest86+ taking too long
* de Almeida, Valmor F. [EMAIL PROTECTED] 19. Nov 07: From: Mark Shields [mailto:[EMAIL PROTECTED] On Nov 19, 2007 12:03 PM, de Almeida, Valmor F. [EMAIL PROTECTED] wrote: Is this execution time expected? Yes, I can confirm that. In addition you should run it more than one time... In fact I don't have a clue when it is going to end. It will never end. If it finished all tests it will start over again. There are 2 fields with varying percentage values; but they get cleared from time to time. Another field is called Test and it was #3 (I think), and now it is at #4. So far it has taken 20:35h. On the upside, no errors detected. In the table below you have a field Pass, probably 0 right now. This will increment after the first turn. In upper area you have another Pass and a progress bar right of it. That's the progress of the current pass. One pass involves several tests (configurable by pressing c). (Disclaimer: everything from my mind.) To be sure make at least a second run, because some memory faults will only manifest after hardware is heated. The more passes the better. Last words: if memtest86+ doesn't find any errors, even not after days, you still can't be totally sure that your memory is okay. But if it finds a damaged address there is for sure a problem with hardware. Second last words: if it finds a problem there can be other broken parts beside memory. Basically everything involved on the path from memory to CPU: memory, Northbridge, memory controller, CPU... HTH, kind regards, Frank. -- Sigmentation fault -- [EMAIL PROTECTED] mailing list
