Bug 122040

Summary: microcode_ctl shouldn't be executed on AMD systems
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Andreas Kleen <ak>
Component: BasesystemAssignee: Kurt Garloff <garloff>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Enhancement    
Priority: P5 - None    
Version: RC 4   
Target Milestone: ---   
Hardware: Other   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Andreas Kleen 2005-10-10 17:06:48 UTC 
The microcode updater generates ugly messages on an AMD system.
Microcode updates by the OS are only supported on Intel systems
so the package should check first for an Intel CPU and if not
do nothing.
Comment 1 Kurt Garloff 2005-11-14 22:14:16 UTC 
Hmmm, would a check in the init script do the job? you'd just get a "skipped"
then.
Comment 2 Andreas Kleen 2005-11-14 22:28:41 UTC 
Either that or remove the printk in the kernel. The later might be easier.
Comment 3 Kurt Garloff 2005-11-28 18:47:33 UTC 
I grep -i intel in the init script now.
Submitted to STABLE.
Comment 4 Ulrich Windl 2006-03-09 08:05:47 UTC 
I'd prefer one of the following solutions, with a preference on 2):
1) Not install the usility for AMD system at all
2) Provide a microcode update utility for AMD CPUs

syslog quote:
Mar  8 20:28:33 aax264 kernel: IA-32 Microcode Update Driver: v1.14 <tigran@veritas.com>
Mar  8 20:28:33 aax264 kernel: microcode: CPU1 not a capable Intel processor
Mar  8 20:28:33 aax264 kernel: microcode: CPU0 not a capable Intel processor
Mar  8 20:28:33 aax264 kernel: microcode: No new microcode data for CPU1
Mar  8 20:28:33 aax264 kernel: microcode: No new microcode data for CPU0
Mar  8 20:28:33 aax264 kernel: IA-32 Microcode Update Driver v1.14 unregistered
Comment 5 Andreas Kleen 2006-03-09 11:44:12 UTC 
(2) doesn't make sense because AMD doesn't provide microcode updates outside BIOS.
Comment 6 Kurt Garloff 2006-03-10 13:39:25 UTC 
In 10.1, we don't try to update the microcode on non-intel CPUs, you'll
just see an "unused".
You request intelligence in the package installer to only install the
package on intel machines. We won't do that for CODE10. More important
problems to be solved than such cosmetic issues.