This article is going to take a look at a rather nasty low-level hardware bug which could bite people writing applications which are multi-threaded. The bug manifests itself in MySQL as we’ll see a bit later.
Part of the blame for the nastiness of this bug certainly lies with a third party who should have (and could have) publicly released a detailed errata, as we’ll see in a bit.
Consider this article a bit of a thought experiment; when you read this article ask yourself: “How would I have debugged this?”
http://timetobleed.com/mysql-doesnt-always-suck-this-time-its-amd/