| Summary: | error in microcode_ctl's monthly cron job | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | eric gerbier <eric.gerbier> |
| Component: | RPM Packages | Assignee: | José Jorge <lists.jjorge> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | dvgevers, eatdirt, lists.jjorge, marja11 |
| Version: | 5 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | microcode_ctl-2.1-4.mga5.src.rpm | CVE: | |
| Status comment: | |||
|
Description
eric gerbier
2016-02-28 11:48:55 CET
Jani Välimaa
2016-02-28 16:20:04 CET
Summary:
error in cron monthly =>
error in microcode_ctl's monthly cron job assigning to all packagers collectively, since there is no maintainer for this package CC:
(none) =>
marja11 I'll take this one. Status:
NEW =>
ASSIGNED Fixed in cauldron, using modprobe microcode to replace the removed service. As this only gives a monthly warning in logs, I think it is useless to push an update for that. Do you agree? Status:
ASSIGNED =>
RESOLVED yes, of course, it is ok for me (I do not check cauldron before opening the ticket I may be wrong, but I still do not see that it works okay: With a completely uptodate cauldron, latest micrococe and microcode_ctl, kernel-server-4.4.3-1 I still get this: microcode-0.20160303-1.mga6.nonfree microcode_ctl-2.1-6.mga6 # journalctl -b |grep micr |grep kern >txt Mar 04 .. kernel: microcode: CPU0 microcode updated early to revision 0x19, date = 2013-06-21 Mar 04 .. kernel: microcode: CPU1 microcode updated early to revision 0x19, date = 2013-06-21 Mar 04 .. kernel: microcode: CPU2 microcode updated early to revision 0x19, date = 2013-06-21 Mar 04 .. kernel: microcode: CPU3 microcode updated early to revision 0x19, date = 2013-06-21 Mar 04 .. kernel: microcode: CPU0 sig=0x106a5, pf=0x2, revision=0x19 Mar 04 .. kernel: microcode: CPU1 sig=0x106a5, pf=0x2, revision=0x19 Mar 04 .. kernel: microcode: CPU2 sig=0x106a5, pf=0x2, revision=0x19 Mar 04 .. kernel: microcode: CPU3 sig=0x106a5, pf=0x2, revision=0x19 Mar 04 .. kernel: microcode: CPU4 sig=0x106a5, pf=0x2, revision=0x19 Mar 04 .. kernel: microcode: CPU5 sig=0x106a5, pf=0x2, revision=0x19 Mar 04 .. kernel: microcode: CPU6 sig=0x106a5, pf=0x2, revision=0x19 Mar 04 .. kernel: microcode: CPU7 sig=0x106a5, pf=0x2, revision=0x19 Mar 04 .. kernel: microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba So it seems to use the old version from 2013, not the updated one of 20151106 !?!? CC:
(none) =>
dvgevers (In reply to Dick Gevers from comment #5) > I may be wrong, but I still do not see that it works okay: Yes you are ;-) This bug is about an error in the script, not the firmware version. > So it seems to use the old version from 2013, not the updated one of > 20151106 !?!? The latest firmwares are often only for the latest hardware. If if have an old CPU, it loads the 2013 version for it , as it is the latest for it. On my 2007 Yonah Celeron, I get : microcode: CPU0 updated to revision 0x44, date = 2010-10-04 Thanks! Hi guys, just discover update_microcode in my /etc/cron.d, and tried. This is for current Cauldron: update-intel-microcode Error: could not find remote data in http://feeds.downloadcenter.intel.com/rss/?p=483&lang=eng ...exiting May someone rapidly check if this is a real bug or me not knowing how microcode work? cheers. CC:
(none) =>
eatdirt (In reply to Chris Denice from comment #8) > Hi guys, > just discover update_microcode in my /etc/cron.d, and tried. This is for > current Cauldron: > > update-intel-microcode > Error: could not find remote data in > http://feeds.downloadcenter.intel.com/rss/?p=483&lang=eng > ...exiting > > May someone rapidly check if this is a real bug or me not knowing how > microcode work? > > cheers. This is a real bug : intel has removed it's update RSS. We should remove the update script... Update cron removed in microcode_ctl-2.1-7 |