On Sat, 12 Dec 2009 14:17:35 +0200 Nikos Chantziaras <[email protected]> wrote:
> > Well, I don't load it manually but have /etc/init.d/microcode_ctl in my > boot runlevel, but I guess this doesn't make any difference. My logs > look the same except for the time (there's no delay) and the microcode > version (probably due to different CPU used.) > Thanks for looking. The closest report I could find to my problem (actually the only report) is at this link: http://lkml.indiana.edu/hypermail/linux/kernel/0703.3/2196.html My kernel has all that hotplug and ACPI stuff turned off. That should not make any difference but possibly there is a kernel bug somewhere that has been overlooked. It is doubtful that many people use microcode updating and so problems like this could easily slip past. I will search for a while longer and then file a bug report with the Linux kernel mailing list. Incidentally, the Gentoo boot script for microcode_ctl is not correct. It uses a "-d" option to specify the microcode device: microcode_ctl -d /dev/cpu/microcode But the "-d" option does not exist. The device is specified at compile time. Frank Peters
