...
>>59426737
Other urls found in this thread:
forums.anandtech.com
extremetech.com
pcgamer.com
techpowerup.com
arstechnica.com
anandtech.com
guru3d.com
twitter.com
SIR DELET DIS
Just lmao
AMD is so fucking incompetent, they fuck everything up.
I too spend my time benching specific instructions for a specific CPU benchmark.
>Look mom, I posted it again!
...
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?
>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.
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.
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
NOOOOO
WE WERE SUPPOSED TO WIN GUYS
>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
>noone in their right mind would even try to crash a server
????????????????????
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
>who would want/need to crash a server
Really makes you think
You could buy a VPS and crash the metal thus all other VPS, dipshit. This is fucking serious.
still no answer
thank you for the first proper answer, I understand the implications of this now, no need to be so hostile though
Sorry it's taking me a long time to think about who would want to crash a server
by your retarded amdtard logic we don't need ssl for banking because who would sniff packets
you're just projecting now
again, instead of giving a proper answer you're being unnecessarily witty and sarcastic
See
nice samefagging OP
1 more shekel has been deposited to your account
>forums.anandtech.com
>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
"just wait"
>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?
I'm not gonna buy some 3rd world poojeet shit that is riddled with bugs
>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.
>card
*chip
AMD is literally chink tier
All AMD threads should be moved to chink shit general
so I'm guessing you're not gonna buy intel either? because their cpus had issues too, and they weren't new architectures either
extremetech.com
pcgamer.com
I'm guessing you're not going to be buying nvidia either, because their GPUs also had issues, remember?
techpowerup.com
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
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
because it's same freaking cpu as last year
>4c/8t in 2017
fuck off to Sup Forums
what did you expect from a completely new architecture?
jesus, you guys are dense as fuck
>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
>this doesn't seem like a big deal at all
it doesn't matter to shills, they'll just ignore these links buddy
>same shit happened to HSW/SKL
>there's a microcode update fix incoming
Oh wow it's fucking nothing.
t. AMD shill
suck my cock, faggot
t. lampshade
intelcucks are on full force lately aren't they
Fuck everyone in this thread
guru3d.com
Microcode updates are normal.
when the fuck are mods gonna do their job?
this has been going on for weeks now
>DELET THIS
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.
you can always go back to your safe space /r/amd
nah just wait the cheaper chips will fuck AMD to pure s u c c sess
>New arcetecture
>New chipset
>New cpus
>Bugs happen
>Amd is incompetent
You are retarded
>amd isn't shit you guys, just wait, the next big thing is just around the corner
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?
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.
It's ok to have a CPU launch completely riddled with bugs and performance issues
Yes it's completely fine
Man intel never does Microcode updates, this is bull shit,
intel4lyfe
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
...
...
...
...
...
Yes, Nehalem was exactly that. But it's okay when the Jews do it.
...
...
...
...
Fuck off shill
...
...
Didn't Haswell, Broadwell and Skylake all have bugs in TSX where it had to be disabled completely?
Yes, but it's okay when the Jews do it.
...
I told you to FUCK OFF you retarded sill
Not as serious as unfixable as this
>one amd issue
>this one guy posting so many intel issues
>intel shills run away so fucking fast
...
Smelly kike, gas yourself.
>Intel has confirmed an in-the-wild erratum affecting its latest Skylake processor architecture and causing hangs during certain computationally-intensive operations
...
>Not as serious as unfixable as this
...
>"AMD has said"
lol
Yes?
...
Still, that's got the potential to be written into a dedicated exploit.
...
>. 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?
...
Is there a CVE for this yet?
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?
...
...
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.
...
...