| Summary: | microcode_ctl - update-{intel,amd}-microcode not working - init file /etc/rc.d/init/microcode_ctl reported as missing | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Dick Gevers <dvgevers> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | doktor5000, fri, mackowiakp, mageia, marja11, tmb, unruh |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | MGA5TOO | ||
| Source RPM: | microccode_ctl-2.1-4 | CVE: | |
| Status comment: | |||
|
Description
Dick Gevers
2014-11-04 22:28:39 CET
Dick Gevers
2014-11-04 22:29:55 CET
Assignee:
bugsquad =>
thierry.vignaud
Samuel Verschelde
2015-06-06 01:35:28 CEST
Keywords:
(none) =>
NEEDINFO The only "file" in all packages in repos named microcode_ctl *folder* containing a readme, see files in *package* microcode_ctl
On what systems is this microcode updater supposed to run?
The description of that package is:
-------------8<--------------
microcode_ctl - Intel / AMD CPU Microcode Utilityâ
Since PentiumPro, Intel CPU are made of a RISC chip and of a microcode whose purpose is to decompose "old" ia32 instruction into new risc ones. P6 familly is concerned: PPro, PII, Celeron, PIII, Celeron2, Core 2, ... Recent kernels have the ability to update this microcode.
The microcode update is volatile and needs to be uploaded on each system boot. I.e. it doesn't reflash your cpu permanently. Reboot and it reverts back to the old microcode.
This package also support updating latest AMD CPU microcode.
----------->8--------------
I have the package microcode_ctl installed (by default presumably), but here is the result on both my Intel i7 and an old dualcore laptop:
systemctl status update-intel-microcode
â update-intel-microcode.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
Part of â/usr/share/doc/microcode_ctl/README :
>>> What it does
***************************************************************************
Deploy an Intel and AMD microcode. This tool is obsolete and the microcode
is the subject to be distributed via kernel-firmware, however Intel still
does not supply the microcode in a form consumable by the Linux's microcode
driver. So that this tool transform Intel's microcode as well as deploy it.
***************************************************************************
But according to change log in that package microcode is now autoloaded (by what?) and service dropped:
* mån 15 sep 2014 tv <tv> 2.1-3.mga5
+ Revision: 676039
- s/uggests:/Recommends:/
- drop the service as microcode is now autoloaded
* fre 20 dec 2013 tv <tv> 2.1-3.mga4
+ Revision: 559058
- fix loading microcode: just load kernel module + fix path (mga#11934)
Is this verified to sucessfully autoload microcode on all CPUs where microcode_ctl worked for?CC:
(none) =>
fri (In reply to Dick Gevers from comment #0) > /usr/sbin/update-intel-microcode: line 81: /etc/rc.d/init/microcode_ctl: No > such file or directory @Thomas: Would be nice if you could comment, people still get that error e.g. mailed via cron logs on mga5 final. The lines with the issue in /usr/sbin/update-intel-microcode are the last ones: $ nl /usr/sbin/update-intel-microcode [...] 66 if [ "-$1" != "---no-reload" -a "-$1" != "---download-only" ] ; then 67 /etc/rc.d/init.d/microcode_ctl reload 68 fi Is /usr/sbin/update-intel-microcode which is triggered by /etc/cron.monthly/update-microcode supposed to update the microcode? If that is the case, then it has to be fixed, right? CC:
(none) =>
doktor5000, mageia, tmb
Florian Hubold
2015-10-31 15:02:31 CET
Summary:
M5B1 update-intel-microcode not working - init file missing =>
microcode_ctl - update-{intel,amd}-microcode not working - init file /etc/rc.d/init/microcode_ctl reported as missing As workaround I changed lines:
if [ "-$1" != "---no-reload" -a "-$1" != "---download-only" ] ; then
/etc/rc.d/init.d/microcode_ctl reload
to:
if [ "-$1" != "---no-reload" -a "-$1" != "---download-only" ] ; then
echo "Reload after reboot"
#/etc/rc.d/init.d/microcode_ctl reloadCC:
(none) =>
mackowiakp This problem is still there. Does comment 5 really solve the problem? Ie, is installation of the microcode now automatic? And how can one check to see that the new microcode is actually loaded? (MGA5 updated, model name : Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz) CC:
(none) =>
unruh It looks more like the update is not used. Despite regular updates I see: journalctl -b |grep -n micro 11:Dec 06 09:52:18 ..... kernel: microcode: CPU0 microcode updated early to revision 0x19, date = 2013-06-21 206:Dec 06 09:52:19 ..... kernel: microcode: CPU1 microcode updated early to revision 0x19, date = 2013-06-21 208:Dec 06 09:52:20 ..... kernel: microcode: CPU2 microcode updated early to revision 0x19, date = 2013-06-21 210:Dec 06 09:52:20 ..... kernel: microcode: CPU3 microcode updated early to revision 0x19, date = 2013-06-21 585:Dec 06 09:52:21 ..... kernel: microcode: CPU0 sig=0x106a5, pf=0x2, revision=0x19 586:Dec 06 09:52:21 ..... kernel: microcode: CPU1 sig=0x106a5, pf=0x2, revision=0x19 587:Dec 06 09:52:21 ..... kernel: microcode: CPU2 sig=0x106a5, pf=0x2, revision=0x19 588:Dec 06 09:52:21 ..... kernel: microcode: CPU3 sig=0x106a5, pf=0x2, revision=0x19 589:Dec 06 09:52:21 ..... kernel: microcode: CPU4 sig=0x106a5, pf=0x2, revision=0x19 590:Dec 06 09:52:21 ..... kernel: microcode: CPU5 sig=0x106a5, pf=0x2, revision=0x19 591:Dec 06 09:52:21 ..... kernel: microcode: CPU6 sig=0x106a5, pf=0x2, revision=0x19 592:Dec 06 09:52:21 ..... kernel: microcode: CPU7 sig=0x106a5, pf=0x2, revision=0x19 593:Dec 06 09:52:21 ..... kernel: microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba AFAIC this bug can be closed Closing then. Status:
NEW =>
RESOLVED |