Messages in this thread | | | Date | Thu, 19 Sep 2013 11:58:34 -0300 | From | Henrique de Moraes Holschuh <> | Subject | Issues with AMD microcode updates |
| |
Jacob, Andreas,
I take care of the amd64 microcode update support for Debian, and I'm receiving user reports of lockup issues with the AMD microcode driver in several kernels. This is about the runtime update interface, /sys/devices/system/cpu/*/microcode/reload and /sys/devices/system/cpu/microcode/reload.
Basically, the issue is that the process that tries to write "1" to the reload node gets stuck in "D" state on several kernel versions.
I started by blacklisting several older kernels (e.g. I got a report of 2.6.38 locking up), but recently I got a report of a lockup with kernel 3.5.1. Blacklisting everything before 3.10 is not exactly kosher, not when I would have to blindly trust 3.0, 3.2 and 3.4 to not have whatever issue is causing the lockups.
IMHO that's the point where it becomes interesting to actually track down the bug even if it apparently doesn't exist anymore on the more recent kernels, and ensure that the stable/long-term kernels have the fix. That would also help distros blacklist microcode update on the broken kernels.
Unfortunately, I don't own, or have access to, any boxes with an AMD processor (let alone one with an AMD processor in need of a microcode update) to bissect the problem.
I'd appreciate if AMD (or anyone with an AMD processor, really) could help me track this issue down.
Debian bug reports: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717185 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723081
-- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
| |