- May 22, 2015
- 7,698 (4.11/day)
|Processor||Intel i5-6600k (AMD Ryzen5 3600 in a box, waiting for a mobo)|
|Motherboard||ASRock Z170 Extreme7+|
|Cooling||Arctic Cooling Freezer i11|
|Memory||2x16GB DDR4 3600 G.Skill Ripjaws V (@3200)|
|Video Card(s)||EVGA GTX 1060 SC|
|Storage||500GB Samsung 970 EVO, 500GB Samsung 850 EVO, 1TB Crucial MX300 and 3TB Seagate|
|Audio Device(s)||Audioquest Dragonfly Red :D|
|Power Supply||Seasonic 620W M12|
|Mouse||Logitech G502 Proteus Core|
|Software||Arch Linux + Win10|
Because any sane distribution is just uploading the fixed firmware into their repositories, thus they don't need to warn users because they're actually fixing the issue? Well, more like propagating the fix from Intel, but the end result is the same.Why are so many people offended by this warning from Debian? I think it's great that they warn their users (not everyone reads errata). If you do serious work on your PC you cannot afford for it to crash. So you disable HT until microcode update comes out: better be safe than sorry.
If you are not affected by this: good for you, move along now, nothing to see here. And please, show some respect for people putting their time into opensource projects. We all benefit from them ...
Plus, the bug is so "serious" it went undetected for an entire generation of CPUs.