Originally posted by Shevchen
View Post
Announcement
Collapse
No announcement yet.
Continuing To Stress Ryzen
Collapse
X
-
-
Originally posted by RyzenNewbie View Post
performance-wise, correct. Architectural-wise, wrong. If I calculate "1+1=2" on CPU A, then I expect that CPU B calculates "1+1=2", too; everytime. Given that CPU B claims having architectural compatibility with CPU A. And no, CPU A is not an Intel CPU.
//EDIT And btw: The failing amd64 instruction is documented, see page 290 at https://support.amd.com/TechDocs/24594.pdf - I fail to read "The CPU should corrupt the programs code while an interrupt arrives at the same core + the programs code is in the upper user memory area". So do you still think it's software related?Last edited by V10lator; 06 August 2017, 10:01 AM.
- Likes 1
Comment
-
Originally posted by scorpio810 View Post
Code:grep CONFIG_RCU_NOCB_CPU= /boot/config-4.11.12-vanilla CONFIG_RCU_NOCB_CPU=y grep CONFIG_RCU_NOCB_CPU_ALL= /boot/config-4.11.12-vanilla CONFIG_RCU_NOCB_CPU_ALL=y
Never see idle freezes since I added this options in my custom kernel.
Comment
-
Does anyone has run into these problems on RED HAT ENTERPRISE LINUX 7.3, SUSE LINUX ENTERPRISE SERVER 12.2 or UBUNTU LINUX 17.04 ?
I can't help thinking that "naples" linux support "officialy" should come with those Oses. As I understand, Ryzen is a "subset" of Epyc .
Those are the distros mentioned in the SOLUTION BRIEF June 2016 about EPYC pdf on http://www.amd.com/en/products/epyc-7000-series .
Comment
-
-
Originally posted by sdack View PostYou think everything inside a CPU is as simple as 1+1. It isn't.
CTRL + F and then entering "unpredicted" or "arbitrary" gives me only a red search mask in Firefox, unfortunately.
You're really awful, you know?
- Likes 1
Comment
-
Originally posted by RyzenNewbie View Post
interesting theory - but let me ask you this: if that software builds successfully on a Phenom - which, obviously, is not made by Intel - and suddenly does not successfully build anymore on a Ryzen; why should AMD have removed that wrong method? And especially, why not have told anyone about that change?
As of such, AMD might have gone from "old faulty tech copied from Intel" (due to compatibility concerns) to "we make it this way now".
Anyhow, we should try to watch how this develops.
Comment
-
Originally posted by Shevchen View PostAs of such, AMD might have gone from "old faulty tech copied from Intel" (due to compatibility concerns) to "we make it this way now".
That leads to a possible hidden workaround in Windows - that neither has been approved nor declined by anybody, yet.
Anyhow, we should try to watch how this develops.
Comment
-
-
Originally posted by RyzenNewbie View PostBut, a manufacturer has to communicate that then, either by provding an official statement or by packaging a little note on the package: "carefully, this CPU handles things differently than before".
- Likes 1
Comment
Comment