On Tuesday 28 July 2015 06:29:27 Gene Heskett wrote: > On Tuesday 28 July 2015 05:36:22 Darac Marjal wrote: > > On Mon, Jul 27, 2015 at 07:39:32PM -0400, Gene Heskett wrote: > > > Greetings all; > > > > > > Is there an autoloading routine I know not about that chooses to > > > see if either the intel-microdoe is loaded and applied, or the > > > amd64-microcode is applied? > > > > > > I cannot find a reference to the attempt to load it in the dmesg > > > report on this machine I am building.. Apt-get install says it is > > > already the latest version. Seems to me there ought to be some > > > treacks in the boot log. > > > > As I understand it, the microcode appropriate to the processor is > > PREpended to the inird image. The kernel will then read that very > > early on and apply it to each CPU as it starts it. > > > > https://www.kernel.org/doc/Documentation/x86/early-microcode.txt > > > > You should be able to see microcode being loaded by "dmesg | grep > > microcode". If that returns nothing, then it may simply be that your > > CPU(s) are running the latest available microcode. > > > > > Thanks folks. > > > > > > Cheers, Gene Heskett > > Since the cpu in question is an athlon64 X2, and therefore a bit > ancient, I'd doubt that. I just looked at the initrd with a hex > editor but see no identifying text that would help to identify what I > am looking at. > > I'll ask on the emc machine list if there is a way to regenerate the > initrd to include the AuthenticAMD bits. > > Thank you.
That list apparently does not harbor an answer, so I have now made 2 new initrd's following the instructions in the above link, and edited the grub boot to have it use the newly built initrd's on a reboot. One to test each of the two files in /lib/firmware/amd-ucode. The cpu ID's itself via dmesg as: [ 0.053621] CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping 02 Midway thru the dmesg after the reboot, dmesg reports: [ 2.893141] microcode: AMD CPU family 0xf not supported [ 4.039084] microcode: AMD CPU family 0xf not supported [ 6.627878] microcode: AMD CPU family 0xf not supported It appears to make 3 tries even. My google-fu has located where AMD says family 10h is the starter, the first cpu to support this, so am I to assume that the 0xf is too early? I had a lockup that exactly matched the description of a 10h & newer patch, yesterday. Only a 4 second hold on the power button killed the psu and got its attention. Is there no applicable microcode for the above CPU? The lockup I had yesterday would allow the machine to continue for an additional 1/2 second before the watchdog on the driver card bites and tristates all outputs, stopping the machine cold. This could be dangerous for obvious reasons. Thanks for any further insight on this. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201507281454.19942.ghesk...@wdtv.com
