So this piece of shit basically segfaults every time it tries

>>61753000
Why don't you post a source or article or anything?
You cheap shit posting fuck.

>>61753000
Install gentoo

>>61753000
The issue is far from that simple.

>>61753014
Lmao Ryzen is finished F A M
https://www.phoronix.com/scan.php?page=article&item=ryzen-segv-continues&num=1

Phenom TLB bug when amd shipped defective cpus and never did a recall. The "fix" hit performance greatly. Most AMDrones are too yound to remeber tho.

>>61753027
https://www.phoronix.com/forums/forum/phoronix/latest-phoronix-articles/967382-50-segmentation-faults-per-hour-continuing-to-stress-ryzen/page4

>>61753000

what does a software issue have to do with hardware?

>>61753069
>software issue

It was real in your mind?

>>61753000
When conftest runs it is looking for correct configuration to use and will cause segfaults on any system.
Once it is running it doesn't segfault.

File: 1489530100391.jpg (156KB, 633x758px) Image search: [Google]

156KB, 633x758px

>>61753000
NO THAT'S IMPOSSIBLE IT WAS AMD'S TURN!!!

>>61753028
>Phenom TLB bug when amd shipped defective cpus and never did a recall.

Not as bad as the Pentium F00F bug when Intel shipped Pentiums that could be locked up by a single opcode and never did a recall either.

File: 1457826012411.jpg (76KB, 450x320px) Image search: [Google]

76KB, 450x320px

>>61753000
I know Intel has had its problems with hardware bugs, but this seems like kind of a major one

>>61753079

explain how it only occurs under an extremely specific circumstance with a certain software?

File: 1483358128338.jpg (63KB, 633x758px) Image search: [Google]

63KB, 633x758px

>install gentoo
>segfault 6 hours into compiling
THANKS RAJA

>>61753136
You don't even understand what is going on.

>>61753149
Actually it can be replicated in gentoo, ubuntu and arch.

>>61753136
Not as major as dying Atoms.
>>61753154
>Raja
>CPUs
SOPA MACACO?

>>61753164

only ubuntu

>>61753164
>Doesn't happen on Manjaro
Shiiieeet

Ryzen had the same issue

>>61753159
what's going on?

>>61753027
>>61753000

>Update [5 August]: As a result of feedback, currently working on some updated results. As some have pointed out, the conftest segmentation faults aren't specific to Ryzen, so updating the tests to avoid confusion

>>61753202
AMD is out of the enterprise business

>>61753000
BLASFAMY!!
STOP DEFAMING AMD
INTEL POOJEET SHOO

>>61753202
Hey, ey! eyey.
I say Hey!

>>61753214
DELET

>>61753217
THIS.
SOPA

>>61753164
Don't mix up problems.

Phoronix test suite runs a conftest at the beginning of a stress run to look for the correct configuration to use for the hardware. In looking for the correct configuration it will segfault, it will discover bad configurations. It does this on every platform, not just on Ryzen CPUs.
The only problem here is that the stress test is looping so much that there are shitloads of segfaults in the hour, this is just a result of the tests finishing quickly and conftest being rerun.

If this is a software problem, some lunix nerds and open source evangelists are gonna have some egg on their faces.
If this is a hardware problem, microcode update can probably fix it.
If microcode can't fix it, there will have to be a workaround that either reduces performance or features. Which would be worst case scenario.

Likely it will be a microcode fix in a couple of months. Also, Intel certianly has these kind of issues as well (Hyperthreading bug was blowing up all over the internet and /g/ a few months ago)

>>61753217
U M A D E L I C I A

b-but m-muh year of AMD!!!!!111

File: 1469910365305.jpg (164KB, 442x400px) Image search: [Google]

164KB, 442x400px

>>61753214
Intel and libtard shills BTFO once again!

>>61753261
Here's the question. is it actually a fucking problem or not?
So far there is 0 evidence that segfaults are critical.

>>61753214
delete this you fucking antisemitic bastard

File: delicia.jpg (31KB, 395x558px) Image search: [Google]

31KB, 395x558px

>>61753273

>>61753282
The conftest segfault is a red herring. The real issue lies elsewhere.

>>61753282
segfaults are critical but is not ryzen's fault, is the libtards fault

Say it with me
>GLUED TOGETHER FAULTY DIES

>>61753282
segfaults are not hardware based by system based, if you're using windows you're safe.

>>61753321
See >>61753214
Stay retarded inteltard, are you ready to change motherboard again?

>>61753313
It's critical only if software hangs, it's not critical if OS in this case Linux, fixes it.

>UMA DELICIA
Update [5 August]: As a result of feedback, currently working on some updated results. As some have pointed out, the conftest segmentation faults aren't specific to Ryzen, so updating the tests to avoid confusion. Though one area being explored now as well is the Clang segmentation faults shown in the original article, not originating from conftest as well as Clang being able to yield the system hanging hard where the system is unresponsive and SSH is not working. Plus also incorporating more Ryzen-Kill tests as outlined in the aforelinked article

>>61753014
This.

>>61753202
https://svnweb.freebsd.org/base?view=revision&revision=321899

Nobody really knows exactly why, suspected to be weird interactions of SMT and microopcache. This "machine learning" part of Zen can do unexpected things at times it seems, this shit is probably really hard to debug on silicon level with simulators. x
>>61753330
windows codepaths doesn't seem to trigger unstable states. Linux can probably also change the code to circumvent the bug like freebsd, but it won't make enterprise people happy for sure

>>61753409
Are you blind? The segfault is not exclusive. Happens on intel processors too.

>>61753429
Does it happen LITERALLY EVERY MINUTE on Intel though? Thought so.

File: 1497894370789.jpg (112KB, 691x771px) Image search: [Google]

112KB, 691x771px

>>61753214
NOOOOO IT'S A LIE! INTEL HAS TO BE BETTER AT SOMETHING!!!!!!!

>>61753429
FreeBSD patch and their discussion is not related to that killryzen script.

>use inytel compiler
>shit dont work

good goy

>>61753457
it would be, if it was as fast as Ryzen

>>61753457
Does it happen every minute on ryzen? No. Fuck off favela monkey

>>61753472
It does. 50 segfaults in less than an hour.

>>61753482
>1 hour = 60 minutes
BRAZILIAN EDUCATION

U M A

>>61753491
>Less than an hour = an hour

Truly, reading comprehension of a literal brain damaged retard.

File: 1500088252115.jpg (137KB, 600x600px) Image search: [Google]

137KB, 600x600px

>>61753069
Software runs on hardware. I can't believe you're literally this stupid.

>>61753214
DUDE WTF DELETE THIS WE HAD A DEAL!!!! DIRTY GOY BASTIDS!!!

File: 1390508731534.png (539KB, 670x720px) Image search: [Google]

539KB, 670x720px

>>61753506
>>61753506
>Truly, reading comprehension of a literal brain damaged retard.

Less than an hour COULD BE 50 minutes or less, but it could also be 51-59 minutes, so you can't say 1 fault per minute on ryzen

Though at this point, you're literally splitting hairs about 1 vs 1 min, 10 sec, so... Both you and the other guy are fucking retarded.

>>61753491
>amdtard
>dyslexic
wew

>>61753601
>retard trying this hard to safe face

>>61753457
Conftest runs every time the stress test loops, so the only reason for it not to happen every minute on Intel is if the stress test takes longer.

File: SHITWREKER.png (418KB, 627x627px) Image search: [Google]

418KB, 627x627px

>>61753469

>try to run the stress tests myself
>install all the shit
>php out of memory errors
>all my php conf is set up for higher than required memory limits
>this thing fucking requires php to run
I hate it.

>>61753000
Windows doesn't have this problem

>>61753000
so basicly nothing has changed since ryzen 7

aka ryzen cant compile linux big fucking deal

>>61753000
SOPA

File: 1443364338656.png (59KB, 548x562px) Image search: [Google]

59KB, 548x562px

>>61753214

>>61753214
D E L I D

EPYC is a new stepping of the silicon (threadripper is not). They've probably fixed at least some of the bugs. Besides, seems like they can be fixed with microcode

It looks like FreeBSD wizards fixed it on their end? I'm not sure if this is just a workaround or not. Regardless it looks like AMD will have to fix this eventually with microcode.

https://svnweb.freebsd.org/base?view=revision&revision=321899

File: Ahmed-Mohamed-Twitter-Picture.jpg (67KB, 634x471px) Image search: [Google]

67KB, 634x471px

>>61753136
I love soldering CPUs

File: 1501906091187.jpg (39KB, 224x250px) Image search: [Google]

39KB, 224x250px

https://streamable.com/07vq6

>>61756208
DELET THIS BRO

>>61753214
Delete this post right now, or suffer the consequences

File: Untitled (5).png (46KB, 200x200px) Image search: [Google]

46KB, 200x200px

>>61756208

gAyMDfags BTFO

>>61756208
You really went through all the effort to make this stupid stock market trolling bullshit?

Jokes aside if your CPU is affected by this and needs an update, how do you get it? Is it just a downloadable flashing tool of some kind? I've never seen or done this before.

>>61756528
FreeBSD apparently has a fix or some sort of workaround https://svnweb.freebsd.org/base?view=revision&revision=321899

This may just be applied to other OS or compilers or whatever's causing the issue to crop up. It doesn't appear to happen on Windows.

Eventually AMD will have to issue a microcode update, though.

>>61756494
It's content creation.

File: inteldelidthis.png (241KB, 882x758px) Image search: [Google]

241KB, 882x758px

>>61753214

File: hurr.jpg (33KB, 962x720px) Image search: [Google]

33KB, 962x720px

>>61756208
>Using reaction image with old Radeon logo
>Makes video with green AMD arrow
If you're going to mock a company at least use the right logos

>>61756647
>shitposting is content creation

this is what kikes actually believe

I love how intlel has been on constant damage control since Ryzen

>just like libscum when Trump was elected
>inb4 pol

File: oldmemes2.jpg (30KB, 600x457px) Image search: [Google]

30KB, 600x457px

>>61756494
>>61756768

File: 1465709220715.jpg (120KB, 670x1000px) Image search: [Google]

120KB, 670x1000px

>>61753214
lmfaoooooooooooooooooooooo

>>61753000
nah, it segfaults mostly when a special program made to segfault with a shitty Linux scheduler is run on it. The same program segfaults xeons and older core i products.

Given that an oddly specific combination of instructions (addressable with microcode changes) issued to the same core on two threads (addressable via scheduler changes) this is obviously an unfixable hardware fault amyyyyyemdoomed etc.

>>61753154
>compiling ultra light weight OS on 32 core epyc
>more than 6 hours
okay.

File: 1500647453955.jpg (9KB, 250x250px) Image search: [Google]

9KB, 250x250px

>>61753214
NOOOO DELEEEEEEEEEEEEEET

>>61756208
This might be the most retarded video I've ever seen. Gratz, desu.

>>61753000
fake news

File: 877dc4cce1f19a0cd5c371a63af9fb040141f52e9670478975f97d352b573e57.png (125KB, 683x682px) Image search: [Google]

125KB, 683x682px

>>61753000
Guess i'll go with i9 then :^)

File: Liquidator.jpg (69KB, 433x640px) Image search: [Google]

69KB, 433x640px

>>61758552
Don't forget to grab on of these suits.

Reminds me of bulldozer launch, it segfaulted when anyone tried to run a steam game with valves drm. Got fixed in microcode later on.

File: 1502015079074.png (187KB, 568x612px) Image search: [Google]

187KB, 568x612px

>>61753214
FFFFFFFFFFFFFFFFFUUUUUUUUUUUUUU

>>61753214
LOONIX BTFO

File: 1491936963073.jpg (1MB, 1312x1730px) Image search: [Google]

1MB, 1312x1730px

>>61753000
>>61753214

>>61753321
SOPA DE MACACO