3 ms·
Not the first bug reported for Ryzen. Wasn't there a couple of others too, one with linux locking up and another triggered by the ocaml compiler emitting opcode
by 0x0 9y ago
Not the first bug reported for Ryzen. Wasn't there a couple of others too, one with linux locking up and another triggered by the ocaml compiler emitting opcodes refering AH/BH/CH/DH registers in a tight loop?
Edit: Sorry, the ocaml bug was Intel Skylake. It's interesting how so many new CPUs have breaking bugs. Feels like it's been quiet since the original pentium F00F bug and then all of a sudden everyone's new CPUs break.
- moogly 9y agoThe OCaml thing was Skylake. But at least that one was fixed back in May.
- bloaf 9y agoThe ocaml compiler found a bug in Intel's Skylake/Kaby Lake. If they found one for Ryzen too, I haven't heard about it. https://lists.debian.org/debian-devel/2017/06/msg00308.html https://lists.debian.org/debian-devel/2017/06/msg00308.html
- 0x0 9y agoYou are right, of course.
- loeg 9y ago> It's interesting how so many new CPUs have breaking bugs. Dan Luu observed the same thing, and thinks it will continue to be very likely: https://danluu.com/cpu-bugs/ https://danluu.com/cpu-bugs/
- dis-sys 9y agocool article, thanks a lot for sharing. it mentions something that I really worried about - Intel knowingly requested its own validation efforts to be reduced so they can place half baked products onto the market faster. pretty sad that both Intel/AMD are seem to be cutting corners to just be a little bit faster in the competition.