Gentoo Archives: gentoo-amd64

From: Frank Peters <frank.peters@×××××××.net>
To: gentoo-amd64@l.g.o
Subject: Re: [gentoo-amd64] Re: Microcode-ctl Problems
Date: Sat, 12 Dec 2009 06:03:17
Message-Id: 20091211234329.98b27d4d.frank.peters@comcast.net
In Reply to: [gentoo-amd64] Re: Microcode-ctl Problems by Nikos Chantziaras
1 On Sat, 12 Dec 2009 02:30:18 +0200
2 Nikos Chantziaras <realnc@×××××.de> wrote:
3
4 >
5 > I can't offer much help other than the assurance that it works on
6 > 64-bit. I've been using it to keep my CPU's microcode updated for quite
7 > a while. It's a Core 2 Duo though, not Quad, running Gentoo ~amd64.
8 >
9 >
10
11 Could you possibly check your kernel log?
12
13 Here is the log from my machine after loading the microcode module:
14
15 Dec 11 23:24:25 (none) kernel: microcode: CPU0 sig=0x6fb, pf=0x10, revision=0xb6
16 Dec 11 23:24:25 (none) kernel: platform microcode: firmware: requesting intel-ucode/06-0f-0b
17 Dec 11 23:25:25 (none) kernel: microcode: CPU1 sig=0x6fb, pf=0x10, revision=0xb6
18 Dec 11 23:25:25 (none) kernel: platform microcode: firmware: requesting intel-ucode/06-0f-0b
19 Dec 11 23:26:25 (none) kernel: microcode: CPU2 sig=0x6fb, pf=0x10, revision=0xb6
20 Dec 11 23:26:25 (none) kernel: platform microcode: firmware: requesting intel-ucode/06-0f-0b
21 Dec 11 23:27:25 (none) kernel: microcode: CPU3 sig=0x6fb, pf=0x10, revision=0xb6
22 Dec 11 23:27:25 (none) kernel: platform microcode: firmware: requesting intel-ucode/06-0f-0b
23 Dec 11 23:28:25 (none) kernel: Microcode Update Driver: v2.00 <tigran@×××××××××××××××××.uk>, Peter Oruba
24
25 The loading process occurs over four minutes as each cpu seems
26 to make some sort of request for intel microcode. There seems
27 to be a request and then a long wait.
28
29 I don't fully understand what is happening but the firmware drivers
30 seem to play some role. Maybe my kernel is not configured
31 correctly for handling firmware.
32
33 Frank Peters

Replies

Subject Author
[gentoo-amd64] Re: Microcode-ctl Problems Nikos Chantziaras <realnc@×××××.de>