retitle 716917 some old kernels may hang in D state when per-core update is triggered severity 716917 important affects 716917 amd64-microcode summary 716917 0 thanks
On Mon, 15 Jul 2013, nicolas.patr...@gmail.com wrote: > Le 15/07/2013 16:52:01, Henrique de Moraes Holschuh a écrit : > > So, does it work? Or does it hang? > > It hangs. Unfortunately, this means the issue is very likely caused by a kernel bug on the AMD microcode kernel support. I feared as much when I noticed you were using a 2.6.38 kernel, which was end-of-line'd two years ago. FYI, that's not a supported kernel for Debian Wheezy (stable) and later, it is too old. Anyway, please remove microcode update support from your 2.6.38 kernel: it is broken. Either recompile it without microcode update support, or get rid of the microcode.ko module (if the driver was not compiled in statically). There is a slim chance that the problem is on the interactions of that old kernel with firmware loader or udev, and not the microcode driver. It is not worth debugging it, but if you want to: trigger the microcode update, wait for several minutes to see if it recovers from the hang (firmware load timeout), and check the kernel log (/var/log/kern.log). Anyway I *think* it works fine on the latest 2.6.32 (or at least I didn't get any complains from the people using intel-microcode or amd64-microcode backports in Debian Squeeze), so I will blacklist anything that is older than 3.0 and not 2.6.32. -- "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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
