Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[solved] exclude ramadress (get physical dress on memtester
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
boerns
Apprentice
Apprentice


Joined: 18 Mar 2004
Posts: 164

PostPosted: Tue Mar 03, 2015 7:20 pm    Post subject: [solved] exclude ramadress (get physical dress on memtester Reply with quote

Hi,

if read all my stuff below what would be your answer?

Try to get new ram-modules or try to exclude faulty-ram-area from kernel and use modules?

Now lets get in detail?

please read, if not yet aware of it my other two posts first:

https://forums.gentoo.org/viewtopic-t-1010162-highlight-.html
https://forums.gentoo.org/viewtopic-t-1009620-highlight-.html

I have had a ram problem on my new hardware. Mainbaord was changed, same behaviour.

Now I have new Ram modules of 32 GB from G.Skill.

They have no issues with memtester, memtest86 and memtest86+, if cpu is not used.
Run at least 5 loops with each tool.

If cpu is used, for example compiling kernel in a loop on 3 cores while memtester is running on a 30g
ramarea on the 4th core, I get this:

holodeck ~ # memtester 30000M
memtester version 4.3.0 (64-bit)
Copyright (C) 2001-2012 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffffffffffff000
want 30000MB (31457280000 bytes)
got 30000MB (31457280000 bytes), trying mlock ...locked.
Loop 1:
Stuck Address : ok
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
Sequential Increment: ok
Solid Bits : ok
Block Sequential : ok
Checkerboard : ok
Bit Spread : ok
Bit Flip : ok
Walking Ones : ok
Walking Zeroes : ok

Loop 2:
Stuck Address : ok
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
Sequential Increment: ok
Solid Bits : testing 60FAILURE: 0x80000000 != 0x00000000 at offset 0x23cfec868.
Block Sequential : ok
Checkerboard : ok
Bit Spread : ok
Bit Flip : ok
Walking Ones : ok
Walking Zeroes : ok

Loop 3:
Stuck Address : ok
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
Sequential Increment: ok
Solid Bits : ok
Block Sequential : ok
Checkerboard : ok
Bit Spread : ok
Bit Flip : ok
Walking Ones : ok
Walking Zeroes : ok



When the failure occurs I get this in dmesg:

[Mär 3 17:00] kworker/dying (1024) used greatest stack depth: 11800 bytes left
[Mär 3 19:52] kworker/dying (2504) used greatest stack depth: 11624 bytes left


I read this :

http://log.or.cz/?p=89

and now my idea is to try to tell the kernel not tu use around 1 MB of ram around that physically broken adress.

But I do not understand how to calculate and get the physical adress. Because my own calculations do not
give the results given in that page. And memtester does not show the error. Just if cpu is used widely.

So what is your suggestion. Ram is bad and should be replaced? Or try to tell kernel to get rid of ramarea.

Alexander


Last edited by boerns on Sat Mar 14, 2015 5:15 pm; edited 1 time in total
Back to top
View user's profile Send private message
boerns
Apprentice
Apprentice


Joined: 18 Mar 2004
Posts: 164

PostPosted: Sat Mar 14, 2015 5:14 pm    Post subject: Reply with quote

There seems no way to calculate the adress correctly. But if you use memtest86 v4.3.7, activate all cpus in parallel you get it ;-)

Now for me its solved because I got 4 x "DDR3 8GB PC 1600 CL10 Kingston HyperX Fury White Series".

So with changed ram it now works.

Alexander
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum