SIMPLY EPYC!

>>61746516
wtf did u do anon?

>>61746516
>>>reddit

>>61746516
>text based logs
>2017.595890410958
top kek

>>61746574
???

They still haven't fixed it? Lmao

>>61746516
are those the ryzen segfaults under load everyone is talking about ?

>>61746574
what do you want? binary logs by systemd?

>>61746516
http://www.phoronix.com/scan.php?page=article&item=ryzen-segv-continues&num=1

here's context since OP is autistic

>>61746685
I want sound based logs voiced by Brian Blessed.

Gentooman btfo.

File: Chkdsk_results_Event_Viewer-3.png (99KB, 1054x1029px) Image search: [Google]

99KB, 1054x1029px

>>61746624
>>61746685

>>61746834
In both screenshots I see 0s and 1s representing tex. Where is the difference?
Protipp: There is none.

>>61746834
>complains about text logs
>offers text logs as an alternative
BUT ITS OKAY IF THE TEXT LOGS ARE IN A GRAPHICAL WINDOW HURRR DUDRRRRRRRR

Every time I see a post by a Windows user I am more and more convinced that Windows users are the niggers of the tech world. Even the mac users on /g/ are smarter than them, because they at least do some programming.

File: big_hook.png (11KB, 926x873px) Image search: [Google]

11KB, 926x873px

>>61746574
well memed

>>61746905
>>61747008
Have you ever used event viewer before? It's obviously more than just text logs

>>61747008
Linux users cant make a graphical chart or output fuck they dont even have a proper image editor ahahahahaha

is dat the ryzen bug?

File: kek.jpg (445KB, 499x499px) Image search: [Google]

445KB, 499x499px

>>61746516
Soon anons.. Soon

File: 1479551127287.jpg (95KB, 624x708px) Image search: [Google]

95KB, 624x708px

>>61746516
AMD finished&bankroupt

File: amd3.jpg (66KB, 568x612px) Image search: [Google]

66KB, 568x612px

>>61746516
FAKE NEWS

You bought a big stinky turd of a cup. How do you feel about it?

>EPYC confirmed to suffer from the segfault issue. AMD, we *need* an official statement
https://www.reddit.com/r/Amd/comments/6rrbsp/epyc_confirmed_to_suffer_from_the_segfault_issue/

>server chip touted as the best for VPS
>can't compile shit
wew

>>61747356
So it turns out to be a RAM issue, as lowering frequency solves this.
This thread can be now closed.

>>61747386
[citation needed]

>>61746834
Get out of here, it never contains any useful information at all
>Muh service crashed
why?
>No info

That's why you always have to make your own logger on top of reporting events

Fucking retard

>>61747386
Not it doesn't, it just gets less frequent.

Fucking fix this shit already, AMD. Epyc can't survive with this crap going on.

>>61747628
>lee better drivers meme
aymd making decent drivers muahahah, NEVER!!!

File: 1501951790958.jpg (3MB, 3456x2304px) Image search: [Google]

3MB, 3456x2304px

>>61747628
Working as intended. You're just being entitled.

>>61747386
So there goes the performance..lel
OH JUST BUY 3.6GHZ RAM TO EQUAL INTELS PERFORMANCE

>>61746516
AHHAHHAHAHAHHAHAHAHAHAHAHAHAHAHAHAHHAHAHAHAHAHAHAHAHAHA

File: logviewer.png (28KB, 842x609px) Image search: [Google]

28KB, 842x609px

>>61746834
wasn't it originally an idea by Sun that Microsoft later copied into Windows NT?

it is a good idea though

Glad I waited for Coffee Lake.

>>61746516
EPYC fail

>>61747735
It would be fixed with a microcode update, retard.

>>61747628
It's Sunday you mongrel

>>61747069
>Linux users cant make a graphical chart or output
Graphical analysis of data output is easy to script with gnuplot. This program has a GUI, because GUIs are for graphical tasks, not text tasks.

>>61747931
go to bed then, ching chong.

>>61747872
who cares?
it's better than text based logs that is for sure.

>>61746516

fucking kill yourself botnet delidshit

>>61748230
[autistic screeching]

Welp I guess it's AMD's turn to have a bunch of autistic chimps screeching about CPU bugs that will eventually be fixed by microcode updates anyway. https://lists.debian.org/debian-devel/2017/06/msg00308.html

>>61748310
>will eventually be fixed by microcode
AMD didn't even acknowledge it officialy. That's the problem.

>>61748502
Yes they did, and AMD Support ticket is open and active at this very moment.

>>61747919
BUHAHAHA

the game dev culture reached extremly sensitive hardware that can brick your computer.

thats why i will never switch from PowerPC

I was thinking of building a new computer with Ryzen this year, glad I've waited. I'll maybe wait another couple of years or two and hopefully it'll get fixed within that time

>>61746905
of course a FOSSfag would know literally nothing about UI.

>>61747850
To equal intel performance in games you idiot . In other tasks ryzen was already superior without high speed ram

>>61748849
not him, but Intel gains just as much from higher speed DDR retard faggot.
Ryzen is great for the 5% of people who regularly use more than 8 threads. Mediocre for everyone else

EPYC FAULT

>>61748524
So what's the solution? Where is the microcode update?

>>61750909
>So what's the solution?
No one knows yet.

>>61750909
The bug is so elusive that they're having trouble just pinning down what kind of conditions to replicate it under. Some people never have the problem happen to them at all, ever.

>>61750909
Wait for it. AMDfags already have plenty of experience.

>>61750943
It's also yet to happen on anything wangblows.
At all.

File: lolpng.png (149KB, 1120x977px) Image search: [Google]

149KB, 1120x977px

>occurs both in Linux and BSD
AYYYMD is literally finished in the enterprise market before enetering it

http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/xeon-5200-series-spec-update.pdf
http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/xeon-5300-spec-update.pdf
http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/xeon-5400-spec-update.pdf
http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/xeon-5500-specification-update.pdf
http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/xeon-5600-specification-update.pdf

>>61751355
>damage control the post

>>61746516
It's sad that Intel employees feel that it's their duty to spam this kind of FUD right before AMD rapes them for a few years. These segfaults are caused by the software and most people can't reproduce the issue.

AYYMD HOUSEFIRES 180W

>>61751422
It happens in both gcc and LLVM/Clang but nice try amdrone.

>>61751444
Yes, in very specific old versions that were released before Ryzen/EPYC support was added. Sad stuff.

>>61751460
>There were also claims of a "fix" in GCC 7. Well, back on the 1800X box I then built GCC 8.0.0 using the 20170730 snapshot for the bleeding-edge GCC compiler code. Nope, when using GCC 8 for the stress-run process, our open-source benchmarking software was still able to trigger 55 segmentation faults per hour.

KYS

>>61751521
Nobody else has been able to reproduce this dude's issue.

>>61751569
Literally a fag with dual socket epyc on plebbit cofirmed it.
KYS

>>61751569
Maybe just fucked up QC on the ryzen processors. Time will tell if Ryzen has any major fuck ups like bulldozer. I wouldn't doubt it.

>>61751589
not true dumb shithead

Jesus Fucking Christ, that damage control on amd subreddit. You didn't see shit like that when the P67 bug occured, now didn't you?

1700x, 1700, C6H and Taichi, only Samsung b-die modules, agesa 1.0.0.6 and all preceding versions, smt on or off, gcc-4.8.5, 6.*.*, 7.*, segfaults occur. Identical system on fx8350: no segfaults.

It's a turd and there most probably won't be fix before b2 stepping or even zenver2. And you-know-who left the AMD before zenver1 release: he won't be doing any bugfixing.

>>61751589
yeah, i'm sure a real person and not some intel-sponsored pajeet shitposter totally confirmed it

>>61747769
This plus you hate change and don't understand Linux at all.

File: amd1.jpg (71KB, 552x661px) Image search: [Google]

71KB, 552x661px

>>61751609
[autistic screeching]

AYYMD IS FINISHED & BANKRUPT

AYYMDPOORFAGS CONFIRMED ON SUICIDE WATCH

>>61751612
>And you-know-who left the AMD before zenver1 release: he won't be doing any bugfixing

Jim Keller wasn't the lead architect on Zen, dumb dumb, Mike Clark was.

>>61751612
Street shitters have done it again. I wouldn't trust those monkeys to make me a decent CPU there literally just shitting out a crappy version of a reverse engineered Intel cpu into the streets of the world

>>61751612
> Identical system on fx8350
Strange, because shit happens on FM2 platform just as much.

It's Barcelona TLB bug all over again and AMD didn't even bother to recall those faulty chips and their "fix" cause large hits in performance

>>61751612
Not disputing any of your points but you can't expect the shit wrecker to hang around to fix bugs

>>61751642
prove it pile of dung

>>61751679
Am3+*

>>61751636
>you hate change
Lennart loves change.
>doesn't understand Linux at all
Lennart doesn't understand Linux at all.

>>61751693
no I was talking about FM2.

>>61751708
8350 isn't socket FM2

>>61751722
wasn't talking about 8350, was I?

>>61751679
>>61751693
No it doesn't. Sabertooth R2.0, FX-8350, zero segfaults in four years. The very same system segfaults on both 1700 and 1700x, on Crosshair and Taichi, but not on FX-8350 (or 1090t for that matter.. or 2500k, 2600k, 3930k).

Recall soon and that will be the end of AYYMD street shitters

AMD can't afford any recall, unlike Intel (see the P67 bug, which is cost billions upon billions for Sintel). Epyc sale might be halted, but that's it.

https://www.reddit.com/r/Amd/

The damage control by these AYYMD street shitters is hilarious, trying to save their dying, bankrupt company

File: sweetie.jpg (188KB, 1528x1530px) Image search: [Google]

188KB, 1528x1530px

>>61751807
>tfw you're still using a B2 stepping P67 board and it still works perfectly

File: 1261329755822.png (234KB, 432x480px) Image search: [Google]

234KB, 432x480px

>buy amd server to save a few bucks
>your business goes bankrupt

Why did it suddenly pop up again?

I've known this issue for 1 month now (my original reason for not buying Ryzen and waiting for TR) and been following the AMD support thread closely but no solution yet emerged.
I remain positive that it can be fixed w/ a microcode update but as long as it's uncertain I won't buy either TR nor Ryzen

>>61751422
nah, it's a hardware bug. no point in whitewashing
%rip ends up ~64 bytes off for whatever reason

I am looking forward to reading the errata on this one..

>>61752308
disable opcache, shit works.
Really looks like Linux isn't as fast to react to new hardware as FOSS mentality would let freetads believe

>>61752308
Because people didn't know if it would appear on epyc cpus which are different stepping. AMD remining silent didn't help either.

>>61752352
kys retard
read the thread

>>61752341
>Hardware bug
>**Not actually present on all hardware only some**

>>61752381
I did, nobody here knows or understands what segfault is and why it appears, everyone just shouting "AMD CAN'T INTO HARDWARE" while not realising what and why can present a segfault.

>>61748589
s-stop, you're gonna make milk shoot out my nose!

>all that damage control
holy shit
why do americans take it upon themselves to defend corporations' honor (for free) like that all the time? honestly bizarre

wow okay

Looks like I'll buy a cheap Intel box instead. P4560, here I come

>>61750190
I mean, I just compiled with make -j8, I'd love to be able to use 16 threads and compile with make -j16

I'm sure streaming on Twitch would benefit as well

Verifying the blockchain would be faster with more threads as well

I use many separate things that max my 8 thread CPU

https://community.amd.com/thread/215773?start=645&tstart=0

>>61752503
because most of them lack strong father figure in their lives and cling to whatever comes close to it

>>61746834
retard, those are still text based logs being served by the mmc

>>61746752
>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.
Hmmmmm.

>>61752566
Those are all great examples of things 95% of people DON'T do often enough to make it worth sacrificing performance in everything else

>>61752755
Conftest segfaults constantly when it crops up in our Yocto-based embedded distro build at work.

>>61746516
lol keep raising awareness intel shills; the more you post this, the quicker the issue will be solved.

>>61752874
ryzen still wins on the singlecore-performance-per-dollar metric so what you're saying is stupid.

Yeah the conftest segfault is happening on literally anything. https://www.phoronix.com/forums/forum/phoronix/latest-phoronix-articles/967382-50-segmentation-faults-per-hour-continuing-to-stress-ryzen?p=967432#post967432

>>61752894
said nerviously the sweating indian because the lay off are coming after this disaster

>>61752950
So the problem is just that Epyc loops the test too frequently.

Which isn't a problem. It means it is ripping through the tests.

what is conftest? googling shows something python related, but that's interpreted right? as opposed to compiled

>>61746574
>text based logs

as a opposed to what?

some weird ass nextgen binary representation that generates some beautiful 5d image of the problem?

even binary logs are just some kind of high performance indexing with text data pointed to.

>>61753036
>what is conftest?
Conftest is just a part of phoronix that runs at the beginning of the test.

This is the extent of IDF?

File: 1498937081067_.png (149KB, 633x900px) Image search: [Google]

149KB, 633x900px

AMD is fuckin done for man!

>>61753023
the same problem ryzen 7 had some months ago
literally nothing has change
only that shills with no knowledge of compilers thinks its such a big deal that will destroy amd

File: keep-calm-then-segfault.png (23KB, 600x700px) Image search: [Google]

23KB, 600x700px

>>61746516
SEGFAULT

>>61753884
>>61755280
Lazy, can't even read the damn thread. >>61752950

>Linux is a broken POS

Wow, it's fucking nothing.

>>61755327
>Linux is a shit

Linux and Ryzen: A match made in Bangalore

got a 1800x, not gonna lie i was pretty pissed off when all the compilations were either segfault-ing or PC straight up crashing(this happens very often if you under-voltage the CPU, which apparently is now a "thing" since some faggots on youtube told everyone that bumping voltage is a bad thing - which it is - but it highly depends on the architecture of the CPU)

For people wanting a quick alternative: AMD's version of gcc (i believe it's called AOCC) fixes the issue, though i haven't tried it yet

Gonna try tomorrow FreeBSD which """apparently""" has some fixes

Also i'm pretty sure this can be fixed, multi-core compiling on windows werks just fine

Don't be ridiculous, are you anons implying that Shit Wrecker failed us?

>>61751612
>And you-know-who left the AMD before zenver1 release: he won't be doing any bugfixing.

>he thinks those guys do this kind of bugfixing

File: 8dbca80acf6a4c24eceab58e2ae5716f.png (315KB, 796x563px) Image search: [Google]

315KB, 796x563px

>>61755419
>this happens very often if you under-voltage the CPU
>AMD's version of gcc (i believe it's called AOCC) fixes the issue
>multi-core compiling on windows werks just fine

Undervolting/overvolting CPU/RAM fucks shit up. Check.
Lunix truly superior operating system. Check.
Windows and FreeBSD just werks. Check.

Pic related is Amada recompiling her kernel with AOCC. Obviously.

>>61755419
>Gonna try tomorrow FreeBSD which """apparently""" has some fixes
https://svnweb.freebsd.org/base?view=revision&revision=321899

You mean this?