From: Udo van den Heuvel <udovdh@xs4all.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: AMD C1E issue? 2.6.38.4
Date: Sat, 07 May 2011 18:30:10 +0200 [thread overview]
Message-ID: <4DC57392.8010902@xs4all.nl> (raw)
In-Reply-To: <20110507162130.GA13307@liondog.tnic>
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
next prev parent reply other threads:[~2011-05-07 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 13:45 AMD C1E issue? 2.6.38.4 Udo van den Heuvel
2011-05-07 16:21 ` Borislav Petkov
2011-05-07 16:30 ` Udo van den Heuvel [this message]
2011-05-08 19:00 ` Borislav Petkov
2011-05-09 9:05 ` Heinz Diehl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DC57392.8010902@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox