From: Russ Weight <russell.h.weight@intel.com>
To: "Zhou, Jie2X" <jie2x.zhou@intel.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "shuah@kernel.org" <shuah@kernel.org>,
"mcgrof@kernel.org" <mcgrof@kernel.org>,
"Zhang, Tianfei" <tianfei.zhang@intel.com>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Li, Philip" <philip.li@intel.com>
Subject: Re: fw_fallback.sh test failed in Debian 11
Date: Wed, 30 Nov 2022 09:32:54 -0800 [thread overview]
Message-ID: <0e688462-7f22-118e-6cb1-de8b582e3973@intel.com> (raw)
In-Reply-To: <CY4PR11MB132092589F9270FB559B01D8C5159@CY4PR11MB1320.namprd11.prod.outlook.com>
On 11/29/22 21:59, Zhou, Jie2X wrote:
> hi,
>
>> Are you sure you have the proper kernel code loaded with the test
>> firmware code that creates this sysfs file? Without that, this test
>> will not work.
> I checked following config options, and they all enabled.
>
> tools/testing/selftests/firmware/config
> CONFIG_TEST_FIRMWARE=y
> CONFIG_FW_LOADER=y
> CONFIG_FW_LOADER_USER_HELPER=y
> CONFIG_IKCONFIG=y
> CONFIG_IKCONFIG_PROC=y
> CONFIG_FW_UPLOAD=y
>
> best regards,
Nevertheless, the error message you reported in your first email indicates
that the test_firmware device may not be present. Did you verify that the running
system reports the expected configs? What does the following command show?
zgrep CONFIG_TEST_FIRMWARE /proc/config.gz
- Russ
next prev parent reply other threads:[~2022-11-30 17:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 2:35 fw_fallback.sh test failed in Debian 11 Zhou, Jie2X
2022-11-29 8:12 ` gregkh
2022-11-30 5:59 ` Zhou, Jie2X
2022-11-30 17:32 ` Russ Weight [this message]
2022-12-01 0:42 ` Zhou, Jie2X
2022-12-01 0:55 ` Russ Weight
2022-12-01 1:28 ` Zhou, Jie2X
2022-12-01 2:37 ` Russ Weight
2022-12-02 6:02 ` Zhou, Jie2X
2022-12-02 16:29 ` Russ Weight
2022-12-08 2:32 ` Luis Chamberlain
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=0e688462-7f22-118e-6cb1-de8b582e3973@intel.com \
--to=russell.h.weight@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jie2x.zhou@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=philip.li@intel.com \
--cc=shuah@kernel.org \
--cc=tianfei.zhang@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).