https://www.techpowerup.com/231536/ amd-ryzen-machine-crashe

File: amdloo.png (316KB, 882x758px) Image search: [Google]

316KB, 882x758px

>>59426737

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

71KB, 552x661px

>>59426737
SIR DELET DIS

>>59426737
Just lmao

AMD is so fucking incompetent, they fuck everything up.

I too spend my time benching specific instructions for a specific CPU benchmark.

>>59426737
>Look mom, I posted it again!

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

66KB, 568x612px

>>59426817
>>59426818

>>59426829
but they're right, when was the last time you bought a CPU just to look at benchmark numbers?

I bought a r7 1700 and my prev cpu (i5 4670) doesn't even come close to it in video editing and multitasking

not to mention it didn't crash a single time during any workload while overclocked to 3.5ghz on a stock cooler (gonna oc it more when I get a better cooler), so what's your problem?

>>59426852
>What also makes this important is because a simple application, running at user privileges (i.e. lacking special super-user/admin privileges), has the ability to crash the machine. Such a code could even be executed through virtual machines, and poses a security issue, with implications for AMD's upcoming "Naples" enterprise processor launch.

This shit is pretty serious desu senpai

I really wanted to give AMD a chance but with this, it's over.

File: fanboy.png (11KB, 265x238px) Image search: [Google]

11KB, 265x238px

>>59426737
1 shekel has been deposited to your account

>Is this an issue with Windows? The crash does not seem to happen in Linux
>But for some reason, it only affects this particular benchmark. Other programs (like prime95 and y-cruncher) aren't affected despite using FMAs.
Oh wow, some obscure benchmark crashes Windows.

>>59426870
well,
1. noone in my apartment would even want to crash my computer, while I am on it, which means this is irrelevant to me and most people

2. I'm fairly sure that servers are securely protected both from internet attacks, and noone in their right mind would even try to crash a server for some reason, and most reasons I can think of relate to wars or are tinfoil-tier

people will over-react over this, as they always have

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

156KB, 633x758px

NOOOOO
WE WERE SUPPOSED TO WIN GUYS

File: tears.jpg (74KB, 522x545px) Image search: [Google]

74KB, 522x545px

>>59426870
>AWS server running "Naples"
>Buy time on a huge grid
>Run FMA3 instruction on every node
>Entire server room crashes
>Every machine is stuck in a spin-cycle
>House fire
>Amazon server room burns to the ground
>Everyone else starts doing it to every server room around the world
>Fires from adjacent server rooms coalesce
>Firestorm hits the entire planet
>Major cities begin to burn
>AMD HQ is on fire
>Trump orders JSOC to capture AMD's executive board
>AMD now truly bankrupt and finished

>>59426941
>noone in their right mind would even try to crash a server

????????????????????

>>59426956
context is "Such a code could even be executed through virtual machines, and poses a security issue, with implications for AMD's upcoming "Naples" enterprise processor launch."

so you tell me who would want/need to crash a server

>>59426972
>who would want/need to crash a server

Really makes you think

>>59426941
You could buy a VPS and crash the metal thus all other VPS, dipshit. This is fucking serious.

>>59426986
still no answer

>>59426990
thank you for the first proper answer, I understand the implications of this now, no need to be so hostile though

>>59426992
Sorry it's taking me a long time to think about who would want to crash a server

>>59426992
by your retarded amdtard logic we don't need ssl for banking because who would sniff packets

>>59427012
you're just projecting now

>>59427009
again, instead of giving a proper answer you're being unnecessarily witty and sarcastic

>>59426992
See >>59426952

File: intel rekt2.png (195KB, 882x751px) Image search: [Google]

195KB, 882x751px

nice samefagging OP

1 more shekel has been deposited to your account

>https://forums.anandtech.com/threads/ryzen-locking-on-certain-fma3-workloads.2501604/

>At posting AMD has confirmed this issue and that a fix will be provided via motherboard firmware update. More than likely this comes in the form of an updated AGESA protocol.

fix incoming

>>59427035
"just wait"

File: 1446126200314.jpg (30KB, 720x438px) Image search: [Google]

30KB, 720x438px

>>59427049
>there is issue with product X
>creator of product X gets issue fixed
>lol product X still sucks dude, because of this one issue that was fixed!

how many intel dicks do you have in your body right now, retard?

>>59427081
I'm not gonna buy some 3rd world poojeet shit that is riddled with bugs

>>59427094
>jim keller
>pajeet

you tried

>this little known benchmark has been tailored by its developer to be highly specific to the CPU micro-architecture, with separate binaries for each major x64 architecture (eg: Bulldozer, Sandy Bridge, Haswell, Skylake, etc.), and as such the GitHub repository does not have a "Zen" specific binary.
>does not have a "Zen" specific binary.

I mean my next card will probably be Intel, but this doesn't seem like a big deal at all. It's a brand new architecture.

>>59427113
>card
*chip

>>59427096
AMD is literally chink tier

All AMD threads should be moved to chink shit general

>>59427094
so I'm guessing you're not gonna buy intel either? because their cpus had issues too, and they weren't new architectures either

https://www.extremetech.com/computing/220953-skylake-bug-causes-intel-chips-to-freeze-in-complex-workloads

http://www.pcgamer.com/intel-skylake-cpus-are-bending-under-the-pressure-of-some-coolers/

I'm guessing you're not going to be buying nvidia either, because their GPUs also had issues, remember?

https://www.techpowerup.com/223669/geforce-gtx-pascal-faces-high-dvi-pixel-clock-booting-problems

>>59427136
Compare the Kaby Lake launch to Ryzen

Ryzen launch is a complete bug riddled disaster of a launch

My Kaby Lake CPU is on the way right now, I have no regrets

>>59426870
so, intel PR is retarded for trying to push on AMD through this
data center security guys aren't that stupid to fall for clickbait

>>59427151
because it's same freaking cpu as last year

>>59427151
>4c/8t in 2017

fuck off to /v/

File: 1488364490959.jpg (10KB, 250x250px) Image search: [Google]

10KB, 250x250px

>>59427151
what did you expect from a completely new architecture?

jesus, you guys are dense as fuck

>>59427113
>The Haswell-specific binary (along with, we imagine, Skylake), adds support for the FMA3 instruction-set, which Ryzen supports, and which lends some importance to the discovery of this bug.
it's supposed to work

>>59427113
>this doesn't seem like a big deal at all

>>59426952

https://arstechnica.com/gadgets/2016/01/intel-skylake-bug-causes-pcs-to-freeze-during-complex-workloads/
http://www.anandtech.com/show/8376/intel-disables-tsx-instructions-erratum-found-in-haswell-haswelleep-broadwelly


>durr

>>59427279
it doesn't matter to shills, they'll just ignore these links buddy

>>59426737
>same shit happened to HSW/SKL
>there's a microcode update fix incoming

Oh wow it's fucking nothing.

>>59427307
t. AMD shill

File: 1455889987310.jpg (39KB, 343x481px) Image search: [Google]

39KB, 343x481px

>>59427315
suck my cock, faggot

>>59427315
t. lampshade

intelcucks are on full force lately aren't they

>>59426737
Fuck everyone in this thread
https://www.guru3d.com/news-story/intel-skylake-processors-crash-at-specific-prime-number-calculations.html

Microcode updates are normal.

when the fuck are mods gonna do their job?
this has been going on for weeks now

>>59427395
>DELET THIS

File: amdinanutshell3.jpg (2MB, 700x5000px) Image search: [Google]

2MB, 700x5000px

>>59427395
They did nothing when AMDrones were shitting this place up with their typical overhyping bullshit for months.

I don't understand why they're supposed to do something now.

>>59427395
you can always go back to your safe space /r/amd

>>59426737
nah just wait the cheaper chips will fuck AMD to pure s u c c sess

>>59426783
>New arcetecture
>New chipset
>New cpus

>Bugs happen

>Amd is incompetent

You are retarded

>>59427489
>amd isn't shit you guys, just wait, the next big thing is just around the corner

>>59426737
Went through whole thread but no one actually said what the fuck an FMA3 instruction is or how it's relevant to typical computing workloads.
Is this another one of those threads where people attack each other over the performance of something like AVX2, despite the fact that nothing actually uses it?

>>59427594

It's just a floating point arithmetic instruction set.

Fused Multiply Add with 3 integers.

It's not important what it is, only that it can shut the entire server down with high level access.

Problem is being fixed, so it means nothing.

File: this-is-fine.png (310KB, 580x282px) Image search: [Google]

310KB, 580x282px

>>59427503
It's ok to have a CPU launch completely riddled with bugs and performance issues

Yes it's completely fine

>>59427081
Man intel never does Microcode updates, this is bull shit,

intel4lyfe

>>59427381
Spreading FUD is all they can do at the moment as Intel has nothing to offer against the Niples-lineup or against the upcoming APUs in the forseeable future, and the agressive pricing of R7 pulled the rug under the whole X99 lineup

>>59427740
Yes, Nehalem was exactly that. But it's okay when the Jews do it.

>>59427923
>>59427918
>>59427909
>>59427897
>>59427889
>>59427875
>>59427865
>>59427853
>>59427843
Fuck off shill

Didn't Haswell, Broadwell and Skylake all have bugs in TSX where it had to be disabled completely?

>>59427942
Yes, but it's okay when the Jews do it.

>>59427930
>>59427940
I told you to FUCK OFF you retarded sill

>>59427942
Not as serious as unfixable as this

File: 1487993694204.jpg (59KB, 763x757px) Image search: [Google]

59KB, 763x757px

>one amd issue
>this one guy posting so many intel issues
>intel shills run away so fucking fast

>>59427951
Smelly kike, gas yourself.

>>59427951
>Intel has confirmed an in-the-wild erratum affecting its latest Skylake processor architecture and causing hangs during certain computationally-intensive operations

>>59427035
>Not as serious as unfixable as this
>>59427951

>>59427972
>"AMD has said"

lol

>>59427983
Yes?

>>59426938
Still, that's got the potential to be written into a dedicated exploit.

>>59426737
>. But for some reason, it only affects this particular benchmark. Other programs (like prime95 and y-cruncher) aren't affected despite using FMAs.
>Members of the HWBot forums found that Ryzen powered machines crash on running the Haswell-specific binary, at "Single-Precision - 128-bit FMA3 - Fused Multiply Add." The Haswell-specific binary
>Haswell-specific binary
>Haswell-specific binary

Gee I wonder what's the problem.

Further in the thread:

>From the hwbot thread, a fix is coming with a new microcode. Also disabling SMT prevent the crash.


Oh wow it's fucking nothing, again?

>>59427996
Is there a CVE for this yet?

>>59426737
Is this the thread where we just read clickbait and don't bother with anything else, like what this affects, how is it fixed? Can it be fixed?

>>59428027
Yes it can and will be fixed with microcode update. Same happened with Haslel/Broadlel/Skymeme.

>FMA exploit(with still unknown hole, as other FMA benchmarks run fine) targeting 5% of total hardware and even less than 1% since this is currently Zen specific

Right, that's a much better idea than just some niggerscript that can target everyone phone, desktop and tablet browser on the planet.

AMD shills going nuts in this thread

>>59428056
this is a huge issue you fucking moron. the good part is that it's getting fixed, but it's sad that you're trying to argue that it's no big deal

>>59428099
You fuckstick, you don't even KNOW why it's crashing at the moment! How can you even begin to write an exploit!?

File: tumblr_inline_ni55qz10OK1qkdr2y.jpg (8KB, 100x100px) Image search: [Google]

8KB, 100x100px

>>59426737
microcode update (fed to the cpu via new bioses, or loaded by windows / linux) and done.

It amuses me so many people want AMD to fail.

>>59428106
the mere fact that a user-space application can crash the whole system means there's a problem. the code is on github so any fucktard could run it without even having to figure out which specific part is causing it, and it would be possible for the problematic sequence of instructions to appear in other programs by accident

File: 1487888155171.png (162KB, 633x900px) Image search: [Google]

162KB, 633x900px

>>59427843
>>59427853
>>59427865
>>59427875
>>59427889
>>59427897
>>59427909
>>59427918
>>59427923
>>59427930
>>59427940
>>59427949
>>59427961
>>59427971
>>59427982
>>59427994
>>59428005
>>59428017
>>59428030
>>59428042
>>59428057
>>59428064
>>59428075
STOP IT STOP IT STOP IT STOP IIITTTTTTTTTTTT

>>59426737
>no error dumps

What are these people even doing?

File: hgsHdP6.png (398KB, 1032x1412px) Image search: [Google]

398KB, 1032x1412px

>>59426737

Wew how can intel shills ever recover from this thread?

>>59428232
Selective memory is a very powerful thing.

File: 1409693710684.jpg (29KB, 300x300px) Image search: [Google]

29KB, 300x300px

>he hates tech even the new stuff.

>>59428693
>>59428700
>>59428708
>>59428714
>>59428723
IT JUST KEEPS GOING

>>59428752
Keep up the good work.

File: lol.gif (2MB, 200x150px) Image search: [Google]

2MB, 200x150px

>one MAD RedTeam+ shill is literally doing damage control

File: Screenshot_2017-03-16-10-56-48.png (186KB, 1440x2560px) Image search: [Google]

186KB, 1440x2560px

There we go.
All 141 Desktop Intel Skylake errata.
If you're interested, here are the spec sheets, including all of their known errata from Sandy Bridge to KabyLake.

http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/2nd-gen-core-desktop-specification-update.pdf

http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/3rd-gen-core-desktop-specification-update.pdf

http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/4th-gen-core-family-desktop-specification-update.pdf

http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/desktop-mobile-5th-gen-core-family-spec-update.pdf

http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/7th-gen-core-family-spec-update.pdf

Also, all 203 errata for the 2011 platform
http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/core-i7-lga-2011-specification-update.pdf

File: 1487513003722.jpg (51KB, 600x515px) Image search: [Google]

51KB, 600x515px

>>59428811
More like singlehandedly BTFO all Intel shills

>>59428869
>203

>it's okay when intel does it

>>59428175
/thread

File: 1488400157075.jpg (114KB, 960x874px) Image search: [Google]

114KB, 960x874px

>>59428811
These AMD shills are fucking hilarious desu senpai

Can't even imagine what is going through their sick little heads

>>59429663
Liking open standards and non shady business tactics. They must be absolutely insane!

>>59429977
absolute amdmen

File: 1488664232472.png (84KB, 653x726px) Image search: [Google]

84KB, 653x726px

>>59427843
>>59427853
>>59427865
>>59427875
>>59427889
>>59427897
>>59427909
>>59427918
>>59427923
>>59427930
>>59427940
>>59427949
>>59427961
>>59427971
>>59427972
>>59427982
>>59427994
>>59428005
>>59428017
>>59428030
>>59428042
>>59428057
>>59428064
>>59428075
>>59428075

NOOOOOOOOOOOOOOO PLZ STOP