TLB bug still present in B3 rev Phenoms

[kl0012]

TLB...TLB...TLB....

I've had two Phenom 9500's since Nov.26
One crunching at stock speeds full load-> NO TLB CRASHES

The other one been overclocked
been running at 2772Mhz since Dec.27
TLB fix disabled
running games,benchies and crunching-> NO TLB CRASHES

If I had TLB crashing I don't my Phenom would have made it to 32nd spot on Riesel Sieve Boinc for daily RAC in less then a week
Computer ID 33998 owner Frank Encruncher
http://boinc.rieselsieve.com/orig/to...=expavg_credit

Does it matter if there is TLB bug on Phenom... Answer NO

The bug is very critical for servers.
Here is the problem:
http://www.x86-64.org/pipermail/disc...er/010281.html
Here is the answer:
http://www.x86-64.org/pipermail/disc...er/010282.html

[justapost]

The bug is very critical for servers.
Here is the problem:
http://www.x86-64.org/pipermail/disc...er/010281.html
Here is the answer:
http://www.x86-64.org/pipermail/disc...er/010282.html

Thank you for those links, this is the first time i see the bug in action.
The guy who answerd is working for AMD according to his sig, so it seems to be no BS this time.

I could not make the bug occure with xen and differen guest osses all running prime95 or other benchmarks.
It would be interesting what software he ran.

[Shintai]

Thank you for those links, this is the first time i see the bug in action.
The guy who answerd is working for AMD according to his sig, so it seems to be no BS this time.

I could not make the bug occure with xen and differen guest osses all running prime95 or other benchmarks.
It would be interesting what software he ran.

It is not as easy as such. The guess is its due to hot spots. Thats also one reason it could be safe at under 2.4Ghz. So Its abit like OC and chips. Random picks. Maybe only 5% of all chips have this bug at stock speed. And with an increased chance with higher frequency.

if it was a fixed bug so to say. I am pretty sure AMD would have caught it in their QA process.

We have a few people here with 0 bugs, and we have an example of a person in WCG forum where it crashes.

[justapost]

It is not as easy as such. The guess is its due to hot spots. Thats also one reason it could be safe at under 2.4Ghz. So Its abit like OC and chips. Random picks. Maybe only 5% of all chips have this bug at stock speed. And with an increased chance with higher frequency.

There is a detailed description of the TLB-thing at LostCircuit here.

if it was a fixed bug so to say. I am pretty sure AMD would have caught it in their QA process.

I dont want to say the bug does not exist, but i experienced it is pretty hard to trigger it.

We have a few people here with 0 bugs, and we have an example of a person in WCG forum where it crashes.

Thx, gona try to trigger the bug with WCG. Do you remeber when the crash was reported in the WCG forum.
According to LostCircuit the bug can only occure with hardware enabled virtualisation. What did the person at WCG use?

[Shintai]

There is a detailed description of the TLB-thing at LostCircuit here.

I dont want to say the bug does not exist, but i experienced it is pretty hard to trigger it.

Thx, gona try to trigger the bug with WCG. Do you remeber when the crash was reported in the WCG forum.
According to LostCircuit the bug can only occure with hardware enabled virtualisation. What did the person at WCG use?

He just ran WCG and it crashed a few times.

Also i think you misunderstood my post. Its not hard to trigger as such. It just depends on your luck of CPU. If there is a hot thermal spot or not and if so, at what frequencies. I do not believe it s a virtualization only bug. Its a pretty lame excuse. Also you would just have the BIOS setting where you disable or enable virtualization to enable or disable the fix aswell. I call it a smoke screen

[justapost]

He just ran WCG and it crashed a few times.

Also i think you misunderstood my post. Its not hard to trigger as such. It just depends on your luck of CPU. If there is a hot thermal spot or not and if so, at what frequencies. I do not believe it s a virtualization only bug. Its a pretty lame excuse. Also you would just have the BIOS setting where you disable or enable virtualization to enable or disable the fix aswell. I call it a smoke screen

NP I wrote a mail to x86-64 with a link to the description, waiting for feedback now. The reviewer seems to be an amd-fan so i do not trust that guy.

The hotspot thing is speculation atm. No phenom user in the AMD section could find a relation between stability and temps or between stability and the tlb-fix.

Maybe you are right and not all cpu's are affected. But that whould be something AMD-marketing whould have mentioned.

Here is an success report for the linux tlb-patch.

[Shintai]

Maybe you are right and not all cpu's are affected. But that whould be something AMD-marketing whould have mentioned.

You cant do that as a company. Just imagine it. "Only some of our CPUs are faulthy, we dont know which ones".

It would be a PR suicide.

Also patching agains 1 or a few possible bugs is not a fix really in what we usually see.