Recent searches
Search options
I've been filing bugs to improve Mozilla's crash reporting infrastructure so it's easier to see at a glance if a particular crash affects only a specific CPU but also if only some microcode versions are affected.
I said it before but I'll say it again. I would have never thought that CPU bugs would have become an everyday occurrence, but here we are.
But by all means, keep pouring capitals into "artificial intelligence" while the very foundation of computing is falling apart and we can't trust a machine to execute instructions reliably.
@gabrielesvelto Are you saying these defects are becoming more frequent in newer CPUs? Or is this a problem that has already existed, and we're just getting better at detecting them? This would make a great hacks post (if that site still exists?)
@wlach it wasn't a thing which is why we have "famous" CPU bugs such as the Pentium FDIV issue. In the last few years it has become more and more common, with certain CPU families being particulary affected such as AMD's Jaguar and first Zen generation, as well as Intel's early Atom processors and lately Raptor Lake and its derivatives.
@gabrielesvelto @wlach Had an old Ryzen 1800x laying around some time ago and figured we might as well use it as a CI server, so I installed Ubuntu on the box and threw some Yocto builds at it.
The compiler kept segfaulting. Turned out, yeah, the early 1800x models just didn't execute instructions correctly.
So that was fun