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]
Date:	Sat, 07 May 2011 18:30:10 +0200
From:	Udo van den Heuvel <udovdh@...all.nl>
To:	linux-kernel@...r.kernel.org
Subject: Re: AMD C1E issue?   2.6.38.4

On 2011-05-07 18:21, Borislav Petkov wrote:
>> 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.

Wel, yes/no.
It works that way on my other boxes.
On this specific box microcode_ctl is not activated automagically during
startup of the machine.

> This doesn't have anything to do with C1E.

OK, that helps. Thanks.

What else could be the cause of microcode_ctl not updating?
Situation is:
microcode: CPU0: patch_level=0x10000b7
microcode: CPU1: patch_level=0x10000b7
Is that new enough so that there is just no newer code to be uploaded
for AMD Athlon(tm) II X2 235e Processor ?

Udo
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ