Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
03-11-2014, 10:37 AM
|
#1
|
Senior Member
Registered: Mar 2008
Location: Deutschland
Distribution: Slackware64-current
Posts: 1,084
|
AMD Microcode
Just noticed that the AMD64 site was back up after a long down time so I grabbed the latest microcode and installed it. I've got an AMD FX-6200 CPU and am running Slackware64-current. After rebooting I see that following in dmesg -
dmesg|grep microcode
[ 6.096501] microcode: CPU0: patch_level=0x06000623
[ 6.256374] microcode: CPU0: new patch_level=0x0600063d
[ 6.241885] microcode: CPU1: patch_level=0x06000623
[ 6.256554] microcode: CPU2: patch_level=0x06000623
[ 6.271080] microcode: CPU2: new patch_level=0x0600063d
[ 6.271164] microcode: CPU3: patch_level=0x06000623
[ 6.271246] microcode: CPU4: patch_level=0x06000623
[ 6.285775] microcode: CPU4: new patch_level=0x0600063d
[ 6.285855] microcode: CPU5: patch_level=0x06000623
[ 6.241885] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
It looks to me like CPU's 0, 2 and 4 are updating the new code but 1,3 and 5 are not. Am I misinterpreting this output or is something amiss? I'm not sure what it is supposed to look like. Thanks for any help.
|
|
|
03-26-2014, 12:31 AM
|
#3
|
Senior Member
Registered: Mar 2008
Location: Deutschland
Distribution: Slackware64-current
Posts: 1,084
Original Poster
|
Many thanks for your reply and the links. Good info to have.
|
|
|
03-26-2014, 12:35 AM
|
#4
|
LQ Guru
Registered: Dec 2011
Distribution: Slackware, Debian 12, Devuan & MX Linux
Posts: 9,528
|
Quote:
Originally Posted by 3rensho
Many thanks for your reply and the links. Good info to have.
|
Your very Welcome.
Glad to be a help- 
|
|
|
03-26-2014, 02:01 AM
|
#5
|
LQ Addict
Registered: Dec 2011
Location: UK
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
|
My CPU only seems to have the first 4 "cores" patched so you're not the only one:
Code:
dmesg |grep microcode
[ 2.144448] microcode: CPU0: patch_level=0x06000629
[ 2.144508] microcode: CPU1: patch_level=0x06000629
[ 2.144569] microcode: CPU2: patch_level=0x06000629
[ 2.144632] microcode: CPU3: patch_level=0x06000629
[ 2.144695] microcode: CPU4: patch_level=0x06000629
[ 2.144762] microcode: CPU5: patch_level=0x06000629
[ 2.144825] microcode: CPU6: patch_level=0x06000629
[ 2.144887] microcode: CPU7: patch_level=0x06000629
[ 2.146065] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[ 3.281820] platform microcode: firmware: direct-loading firmware amd-ucode/microcode_amd_fam15h.bin
[ 3.291644] microcode: CPU0: new patch_level=0x0600063d
[ 3.301433] microcode: CPU1: new patch_level=0x0600063d
[ 3.311241] microcode: CPU3: new patch_level=0x0600063d
[ 3.319662] microcode: CPU5: new patch_level=0x0600063d
|
|
|
03-26-2014, 03:28 PM
|
#6
|
LQ Guru
Registered: Dec 2011
Distribution: Slackware, Debian 12, Devuan & MX Linux
Posts: 9,528
|
Quote:
Originally Posted by 273
My CPU only seems to have the first 4 "cores" patched so you're not the only one:
Code:
dmesg |grep microcode
[ 2.144448] microcode: CPU0: patch_level=0x06000629
[ 2.144508] microcode: CPU1: patch_level=0x06000629
[ 2.144569] microcode: CPU2: patch_level=0x06000629
[ 2.144632] microcode: CPU3: patch_level=0x06000629
[ 2.144695] microcode: CPU4: patch_level=0x06000629
[ 2.144762] microcode: CPU5: patch_level=0x06000629
[ 2.144825] microcode: CPU6: patch_level=0x06000629
[ 2.144887] microcode: CPU7: patch_level=0x06000629
[ 2.146065] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[ 3.281820] platform microcode: firmware: direct-loading firmware amd-ucode/microcode_amd_fam15h.bin
[ 3.291644] microcode: CPU0: new patch_level=0x0600063d
[ 3.301433] microcode: CPU1: new patch_level=0x0600063d
[ 3.311241] microcode: CPU3: new patch_level=0x0600063d
[ 3.319662] microcode: CPU5: new patch_level=0x0600063d
|
I see--
Thanks for chiming in 273!-
I'm not sure if patching for microcode is a similar practice as patching the kernel.
IF I have time I'll study it.
|
|
|
03-26-2014, 08:59 PM
|
#7
|
Member
Registered: Apr 2010
Location: Cluj, Romania
Distribution: Debian Testing
Posts: 731
Rep: 
|
I noticed this too. I assumed that its like this because the patching is done at module, not core level.
|
|
|
03-27-2014, 01:57 AM
|
#8
|
LQ Addict
Registered: Dec 2011
Location: UK
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
|
Quote:
Originally Posted by gradinaruvasile
I noticed this too. I assumed that its like this because the patching is done at module, not core level.
|
That could well be it, however, the previous patches seem to be applied to all cores. Perhaps this one is per module.
|
|
|
03-27-2014, 09:39 PM
|
#9
|
LQ Guru
Registered: Dec 2011
Distribution: Slackware, Debian 12, Devuan & MX Linux
Posts: 9,528
|
Quote:
Originally Posted by 273
That could well be it, however, the previous patches seem to be applied to all cores. Perhaps this one is per module.
|
Neat!
How many moudules = the core? (or) equal one core?
|
|
|
03-28-2014, 02:02 AM
|
#10
|
LQ Addict
Registered: Dec 2011
Location: UK
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
|
Quote:
Originally Posted by Ztcoracat
Neat!
How many moudules = the core? (or) equal one core?
|
Each module contains 2 "cores" so in the FX-6200 there are three modules meaning 6 "cores" and in the FX-8120 there are 4 modules meaning 8 "cores".
|
|
|
03-28-2014, 06:14 PM
|
#11
|
LQ Guru
Registered: Dec 2011
Distribution: Slackware, Debian 12, Devuan & MX Linux
Posts: 9,528
|
Quote:
Originally Posted by 273
Each module contains 2 "cores" so in the FX-6200 there are three modules meaning 6 "cores" and in the FX-8120 there are 4 modules meaning 8 "cores".
|
So the number of modules determines the number of cores?
Or to better understand perhaps I should go look up the Fx-6200 (to find out how you knew it had 3 cores) and compare it to the Fx-8120 and read the spec's- This is intresting-- 
|
|
|
03-28-2014, 06:20 PM
|
#12
|
LQ Addict
Registered: Dec 2011
Location: UK
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
|
|
|
1 members found this post helpful.
|
03-28-2014, 06:46 PM
|
#13
|
LQ Guru
Registered: Dec 2011
Distribution: Slackware, Debian 12, Devuan & MX Linux
Posts: 9,528
|
Quote:
Originally Posted by 273
|
Thanks! 
|
|
|
All times are GMT -5. The time now is 03:50 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|