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 18:37:54 -0800 [thread overview]
Message-ID: <57b8f45b-da8c-e9ae-6b3f-ba82f936c9b2@intel.com> (raw)
In-Reply-To: <CY4PR11MB13206A6918FFDEB5B3D3794BC5149@CY4PR11MB1320.namprd11.prod.outlook.com>
On 11/30/22 17:28, Zhou, Jie2X wrote:
>> How much of this path exists on your machine?
>> /sys/devices/virtual/misc/test_firmware/trigger_request
> This path exists.
>
>> And is there anything in the dmesg output that indicates a failure associated with
>> the test_firmware device?
> Yes.
>
> kern :info : [ 77.858068] test_firmware: loading 'test-firmware.bin'
> kern :info : [ 77.864705] test_firmware: loaded: 8
> kern :info : [ 77.874250] test_firmware: loading 'test-firmware.bin'
> kern :warn : [ 77.880672] misc test_firmware: Direct firmware load for test-firmware.bin failed with error -2
> kern :info : [ 77.890106] test_firmware: load of 'test-firmware.bin' failed: -2
> kern :info : [ 78.896662] test_firmware: loading ''
> kern :info : [ 78.901059] test_firmware: load of '' failed: -22
> kern :info : [ 78.907422] test_firmware: loading ''
> kern :err : [ 78.912278] test_firmware: failed to async load firmware
> kern :info : [ 78.918594] test_firmware: loading 'nope-test-firmware.bin'
> kern :warn : [ 78.925405] misc test_firmware: Direct firmware load for nope-test-firmware.bin failed with error -2
> kern :info : [ 78.935260] Ignoring firmware sysfs fallback due to sysctl knob
The above message looks like the problem. Firmware sysfs fallback has been turned off
on this system using sysctl. Can you try turning it on and rerunning the test?
Thanks,
- Russ
> kern :info : [ 78.941934] test_firmware: load of 'nope-test-firmware.bin' failed: -2
> kern :info : [ 78.962155] test_firmware: loading 'test-firmware.bin'
> kern :info : [ 78.968232] test_firmware: loaded: 9
> kern :info : [ 78.986063] test_firmware: loading 'test-firmware.bin'
> kern :info : [ 78.992269] test_firmware: loaded: 9
> kern :info : [ 79.023611] test_firmware: reset
> kern :info : [ 79.028466] test_firmware: batched sync firmware loading 'test-firmware.bin' 4 times
>
> best regards,
next prev parent reply other threads:[~2022-12-01 2:38 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
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 [this message]
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=57b8f45b-da8c-e9ae-6b3f-ba82f936c9b2@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