| 1 |
On Sat, 12 Dec 2009 14:17:35 +0200 |
| 2 |
Nikos Chantziaras <realnc@×××××.de> wrote: |
| 3 |
|
| 4 |
> |
| 5 |
> Well, I don't load it manually but have /etc/init.d/microcode_ctl in my |
| 6 |
> boot runlevel, but I guess this doesn't make any difference. My logs |
| 7 |
> look the same except for the time (there's no delay) and the microcode |
| 8 |
> version (probably due to different CPU used.) |
| 9 |
> |
| 10 |
|
| 11 |
Thanks for looking. |
| 12 |
|
| 13 |
The closest report I could find to my problem (actually the only |
| 14 |
report) is at this link: |
| 15 |
|
| 16 |
http://lkml.indiana.edu/hypermail/linux/kernel/0703.3/2196.html |
| 17 |
|
| 18 |
My kernel has all that hotplug and ACPI stuff turned off. That |
| 19 |
should not make any difference but possibly there is a kernel |
| 20 |
bug somewhere that has been overlooked. It is doubtful that |
| 21 |
many people use microcode updating and so problems like this |
| 22 |
could easily slip past. |
| 23 |
|
| 24 |
I will search for a while longer and then file a bug report with |
| 25 |
the Linux kernel mailing list. |
| 26 |
|
| 27 |
Incidentally, the Gentoo boot script for microcode_ctl is not correct. |
| 28 |
It uses a "-d" option to specify the microcode device: |
| 29 |
|
| 30 |
microcode_ctl -d /dev/cpu/microcode |
| 31 |
|
| 32 |
But the "-d" option does not exist. The device is specified at |
| 33 |
compile time. |
| 34 |
|
| 35 |
Frank Peters |
Archives