| View previous topic :: View next topic |
| Author |
Message |
Bones McCracker
Veteran
Joined: 14 Mar 2006
Posts: 1611
Location: U.S.A.
|
 Posted: Mon Jul 16, 2007 1:34 am Post subject: microcode-ctl question [Solved] |
 |
|
The documentation says: | Quote: | The utility will print something like:
microcode_ctl: writing microcode (length: 98304)
microcode_ctl: microcode successfuly written to /dev/cpu/microcode
The driver will send messages to the system log (/var/log/messages) like:
microcode: CPU1 updated from revision 7 to 14, date=09101999
microcode: CPU0 updated from revision 7 to 14, date=09101999 |
I'm not getting driver's log messages, and I'm wondering if anyone else running microcode-ctl can tell me whether they get the indicated "updated from revision foo to bar" log messages.
One of my logs is a catch-all, so I don't think the message is slipping through without being logged. Maybe the message is no longer generated? In case it's relevant, my kernel includes microcode as a module, and I've kept the default /etc/conf.d/microcode-ctl setting to unload it after use.
I'm not getting an error message from the initscript. When I run microcode_ctl manually (not using the initscript), I do see the utility's messages:
| Code: | # /usr/sbin/microcode_ctl -u -d /dev/cpu/microcode
/usr/sbin/microcode_ctl: writing microcode (length: 293888)
/usr/sbin/microcode_ctl: microcode successfuly written to /dev/cpu/microcode |
So I think it is functioning properly, but I still don't get the expected log message: "CPU1 updated from revision foo to bar, date=XXXXXXXX".
Thanks!
Last edited by Bones McCracker on Tue Jul 17, 2007 2:56 am; edited 1 time in total |
|
| Back to top |
|
 |
linuxreaktor
n00b
Joined: 03 Jan 2004
Posts: 41
Location: Frankfurt / Germany
|
| Posted: Mon Jul 16, 2007 9:21 am Post subject: |
|
|
hi, i also came across this, seeing that for a long time in the messages log, no microcode messages appeared, i think this is the reason why:
this is how microcode_ctl initscript looks like:
| Code: | ebegin "Updating microcode"
/usr/sbin/microcode_ctl -qu -d ${MICROCODE_DEV}
ret=$?
eend ${ret} "Failed to update microcode via '${MICROCODE_DEV}'"
[[ ${MICROCODE_UNLOAD} == "1" || ${MICROCODE_UNLOAD} == "yes" ]] \
&& rmmod microcode >& /dev/null
|
microcode_ctl is started using the "-q" option="run silently when successful"
greetings david |
|
| Back to top |
|
|
Bones McCracker
Veteran
Joined: 14 Mar 2006
Posts: 1611
Location: U.S.A.
|
| Posted: Mon Jul 16, 2007 6:22 pm Post subject: |
|
|
Thanks, but that's not it.
When I ran it manually, I did so without the -q option, and I only got the messages I showed.
I'm assuming it's working, but I'm curious about the versions. I wonder how to probe to see what version of the microcode is currently loaded. |
|
| Back to top |
|
|
shaumux
Veteran
Joined: 13 May 2005
Posts: 1013
Location: Hamburg
|
| Posted: Mon Jul 16, 2007 9:27 pm Post subject: |
|
|
I am also using it.
Its site says it will only put errror messages so if everything goes fine i don't think it will leave anything behind |
|
| Back to top |
|
|
Bones McCracker
Veteran
Joined: 14 Mar 2006
Posts: 1611
Location: U.S.A.
|
| Posted: Tue Jul 17, 2007 2:55 am Post subject: |
|
|
Ok. Good. I saw older references (apparently the documentation that comes with the source code is one of these) that indicate it messages to syslog as well. Thanks for clearing that up.  |
|
| Back to top |
|
|
|
Kernel & Hardware
