public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: AMD microcode updates - where are they?!
Date: Tue, 16 Jul 2019 10:47:38 +0100	[thread overview]
Message-ID: <1747010.DnOZzGAsZ9@localhost> (raw)
In-Reply-To: <20190715211812.62rhlceuxghzmwku@matica.foolinux.mooo.com>

[-- Attachment #1: Type: text/plain, Size: 2450 bytes --]

On Monday, 15 July 2019 22:18:12 BST Ian Zimmerman wrote:
> UH-OH, Self-followup:
> 
> On 2019-07-14 21:30, Ian Zimmerman wrote:
> > I find it odd that there is apparently no central way to track which
> > firmwares are being loaded without a debugging kernel.
> > 
> > The relevant messages in linux/drivers/base/firmware_loader/main.c are
> > all dev_dbg(), which as I understand does nothing on a non-debug kernel.
> > Even the message printed when the firmware file is missing is of that
> > type.
> > 
> > I guess I could turn on the userspace helper, set it to some script that
> > just logs every request and fails, and then remove the whole
> > /lib/firmware tree, but that is a _really_ round-about way.
> 
> Solved with a kernel patch:
> 
> --- a/drivers/base/firmware_loader/main.c	2019-07-13 23:01:15.000000000
> -0700 +++ b/drivers/base/firmware_loader/main.c	2019-07-14
> 23:33:22.348028910 -0700 @@ -336,7 +336,7 @@
>  					 path);
>  			continue;
>  		}
> -		dev_dbg(device, "direct-loading %s\n", fw_priv-
>fw_name);
> +		pr_notice("direct-loading firmware %s\n", fw_priv-
>fw_name);
>  		fw_priv->size = size;
>  		fw_state_done(fw_priv);
>  		break;


Thanks Ian, nothing different with the patch implemented.  I am becoming 
convinced there is no applicable microcode patch for my fam + model of AMD 
CPUs.

$ dmesg | egrep -i "firmware|microcode"
[    0.000000] [Firmware Info]: CPU: Re-enabling disabled Topology Extensions 
Support.
[    0.343586] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.351361] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 
00-3f] only partially covers this bridge
[    0.627638] [drm] Loading ARUBA Microcode
[    0.629254] [drm] Found VCE firmware/feedback version 50.0.1 / 17!
[    5.753421] [drm] Loading hainan Microcode
[    6.643785] microcode: CPU0: patch_level=0x06001119
[    6.647663] microcode: CPU1: patch_level=0x06001119
[    6.649170] microcode: CPU2: patch_level=0x06001119
[    6.650136] microcode: CPU3: patch_level=0x06001119
[    6.651110] microcode: Microcode Update Driver: v2.2.
[    8.125143] psmouse serio1: elantech: assuming hardware version 3 (with 
firmware version 0x450f03)
[    9.938954] psmouse serio1: elantech: assuming hardware version 3 (with 
firmware version 0x450f03)
[   30.738249] firmware_class: direct-loading firmware regulatory.db
[   30.738915] firmware_class: direct-loading firmware regulatory.db.p7s

-- 
Regards,

Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-07-16  9:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12 12:18 [gentoo-user] AMD microcode updates - where are they?! Mick
2019-07-12 16:07 ` [gentoo-user] " Ian Zimmerman
2019-07-13  0:56   ` Adam Carter
2019-07-13  1:13     ` Adam Carter
2019-07-13 10:04       ` Mick
2019-07-13 10:01     ` Mick
2019-07-13 16:21 ` [gentoo-user] " Jack
2019-07-13 17:18   ` Mick
2019-07-13 17:23     ` Mick
2019-07-13 17:42     ` Jack
2019-07-13 18:06       ` Mick
2019-07-13 18:16         ` Corbin
2019-07-13 19:23           ` Mick
2019-07-13 20:16             ` Wols Lists
2019-07-13 21:01               ` Rich Freeman
2019-07-13 22:03                 ` Mick
2019-07-14 13:26                   ` Mick
2019-07-15  0:42                     ` Adam Carter
2019-07-17  3:21                     ` Corbin
2019-07-17 10:58                       ` Mick
2019-07-17 12:46                         ` Corbin
2019-07-17 20:51                           ` [gentoo-user] " Ian Zimmerman
2019-07-18 12:33                             ` Corbin
2019-07-18 18:23                               ` Mick
2019-07-17 23:38                         ` [gentoo-user] " Adam Carter
2019-07-15  4:30         ` [gentoo-user] " Ian Zimmerman
2019-07-15 21:18           ` Ian Zimmerman
2019-07-16  9:47             ` Mick [this message]
2019-07-15  5:15         ` [gentoo-user] " Adam Carter
2019-07-16  8:10     ` Neil Bothwick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1747010.DnOZzGAsZ9@localhost \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox