Can someone tell me why AMD makes such a fuss to send Michael CPU review samples? I mean you gave away 250 of those review kits to tech youtubers. Unless you were going to surprise him anyway :P
Announcement
Collapse
No announcement yet.
AMD Confirms Linux Performance Marginality Problem Affecting Some, Doesn't Affect Epyc / TR
Collapse
X
-
I thought its's honest
- Likes 1
Comment
-
Edit: To early for me detecting cleverly hidden sarcasm.....
Well they at least answered my question if they manage to reproduce the problem, and they do. For me Ryzen works for the intended purpose heavy parallel computing, so I don't mind the wait, but for those running compiling feasts it's a let-down, to run with one or a few cores.
Kind regards.
B.Last edited by Brutalix; 08 August 2017, 02:44 AM.
Comment
-
I'm still having really hard time to grasp how it could be hardware problem if it works well on another software (eg. Windows). However, as I'm sure AMD people know (much) more about their product than me, I will apologize for being wrong and saying it is a software bug, even tho I am still not convinced about it..., Michael should do the same on conftest segfaults once situation is resolved, and I think it was quite clear from comments on that article that is normal behaviour.
Comment
-
How long does the kill-ryzen script take to throw an error? have run it up to an hour without any problems
Currently set it going again about 15mins ago or so to see when/if it does anything
Antergos(updated)
running a 1700x @ 3.9
3200 mem via XMP
Gigabyte k7 board
well to update, hour now. it does show this though every 5 mins.
Code:[KERN] Aug 08 10:05:34 com1 kernel: mce: [Hardware Error]: Machine check events logged [KERN] Aug 08 10:05:34 com1 kernel: [Hardware Error]: Corrected error, no action required. [KERN] Aug 08 10:05:34 com1 kernel: [Hardware Error]: CPU:15 (17:1:1) MC3_STATUS[Over|CE|MiscV|-|-|-|-|SyndV|-]: 0xd820000000000150 [KERN] Aug 08 10:05:34 com1 kernel: [Hardware Error]: IPID: 0x000300b000000000, Syndrome: 0x000000002a000503 [KERN] Aug 08 10:05:34 com1 kernel: [Hardware Error]: Decode Unit Extended Error Code: 0 [KERN] Aug 08 10:05:34 com1 kernel: [Hardware Error]: Decode Unit Error: uop cache tag parity error. [KERN] Aug 08 10:05:34 com1 kernel: [Hardware Error]: cache level: RESV, tx: INSN, mem-tx: IRD
Comment
-
Originally posted by RussianNeuroMancer View PostRemember good old days? http://www.pcworld.com/article/112891/article.html No shame in using commodity hardware if you know what you are doing.
Comment
-
Comment