From: Ian Zimmerman <itz@very.loosely.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: AMD microcode updates - where are they?!
Date: Mon, 15 Jul 2019 14:18:12 -0700 [thread overview]
Message-ID: <20190715211812.62rhlceuxghzmwku@matica.foolinux.mooo.com> (raw)
In-Reply-To: <20190715043001.n3wxrw5jieuh6ton@matica.foolinux.mooo.com>
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;
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.
next prev parent reply other threads:[~2019-07-15 21:18 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 [this message]
2019-07-16 9:47 ` Mick
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=20190715211812.62rhlceuxghzmwku@matica.foolinux.mooo.com \
--to=itz@very.loosely.org \
--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