From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id C9905138334 for ; Mon, 15 Jul 2019 21:18:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1C232E0831; Mon, 15 Jul 2019 21:18:23 +0000 (UTC) Received: from very.loosely.org (very.loosely.org [173.255.215.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id AD5E0E0828 for ; Mon, 15 Jul 2019 21:18:22 +0000 (UTC) Received: from c-67-174-233-217.hsd1.ca.comcast.net ([67.174.233.217]:39798 helo=foolinux.mooo.com) by ahiker.mooo.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92-111-1a207ebe0) (envelope-from ) id 1hn8MX-0002p7-E8; Mon, 15 Jul 2019 14:18:21 -0700 Date: Mon, 15 Jul 2019 14:18:12 -0700 From: Ian Zimmerman To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] Re: AMD microcode updates - where are they?! Message-ID: <20190715211812.62rhlceuxghzmwku@matica.foolinux.mooo.com> References: <8454413.yhxcbTWUVq@localhost> <20190715043001.n3wxrw5jieuh6ton@matica.foolinux.mooo.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190715043001.n3wxrw5jieuh6ton@matica.foolinux.mooo.com> User-Agent: NeoMutt/20180716 X-Loosely-ASN: 7922 X-Archives-Salt: a618629b-0c78-4a93-832c-d9bf3b00eb87 X-Archives-Hash: e20b42cf8869adc02394c92c96e7c613 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.