linux-kernel - Re: AMD C1E issue? 2.6.38.4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110507162130.GA13307@liondog.tnic>
Date:	Sat, 7 May 2011 18:21:30 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Udo van den Heuvel <udovdh@...all.nl>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: AMD C1E issue?   2.6.38.4

Hi,

On Sat, May 07, 2011 at 03:45:09PM +0200, Udo van den Heuvel wrote:
> Hello,
> 
> Saw these in my messages after enabling C1E on my new Jetway Mini-ITX board:
> 
> # microcode_ctl -u
> microcode_ctl: writing microcode (length: 430080)
> microcode_ctl: error writing to '/dev/cpu/microcode' errno=22 (Invalid
> argument)
> microcode_ctl: there may be messages from the driver in your system log.
> 
> microcode: AMD microcode update via /dev/cpu/microcode not supported
> microcode: AMD microcode update via /dev/cpu/microcode not supported

no, the message is correct - the AMD ucode driver doesn't support
ucode loading method through the /dev node, only through the firmware
loader. I.e., you should simply put the microcode image into
/lib/firmware/amd-ucode/ and compile the kernel microcode driver as a
module - then it'll load automatically.

> This is on kernel.org 2.6.38.4 on AMD Athlon II X2 235e on JNC84E-LF
> board, Fedora 14 for most of the rest of the stuff.
> 
> Anybody can tell why the update cannot work?
> The previous board (JNC81) did not show these but also did not have C1E
> in BIOS as far as I recall.

This doesn't have anything to do with C1E.

HTH.

-- 
Regards/Gruss,
    Boris.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/