From: Lukas Middendorf <kernel@tuxforce.de>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: linux-btrfs@vger.kernel.org, Antti Palosaari <crope@iki.fi>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org,
Lukas Middendorf <kernel@tuxforce.de>
Subject: Re: Is request_firmware() really safe to call in resume callback when /usr/lib/firmware is on btrfs?
Date: Sat, 3 Apr 2021 18:07:09 +0200 [thread overview]
Message-ID: <63de0271-5222-efb0-b7ba-1ccf3d2401fa@tuxforce.de> (raw)
In-Reply-To: <679f1f74-1304-9e79-1d83-0810361b4503@tuxforce.de>
Hi Luis,
I now succeeded in reproducing this in VirtualBox running a F34 minimal
installation with / on btrfs (with default firmware files).
I can send you the virtual disk file if you want it. With the kernel
sourcecode and the compiled and installed kernel it currently is 21.8GiB.
On 03/04/2021 12:24, Lukas Middendorf wrote:
> On 03/04/2021 00:58, Luis Chamberlain wrote:
>> Can you provide kernel logs for where you are seeing things get stuck at?
I have dumped the output of the serial console with all outputs cranked
to the max.
In [1] is the output with test_firmware loaded and suspend test running.
This leads to a freeze. However it is not completely dead. While it does
not visually react, at least from time to time there still are some
messages from the kernel and the cursor is still blinking.
In [2] is a (successful) suspend and resume cycle with test_firmware not
loaded.
Lukas
[1] https://gist.github.com/midluk/05716f714f778d26dc02771245df0ac9
[2] https://gist.github.com/midluk/a03eb953b6cf097688b8be2e0cd387fd
next prev parent reply other threads:[~2021-04-03 16:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-09 18:51 Is request_firmware() really safe to call in resume callback when /usr/lib/firmware is on btrfs? Lukas Middendorf
2020-08-13 16:37 ` Luis Chamberlain
2020-08-13 21:53 ` Lukas Middendorf
2020-08-13 22:13 ` Luis Chamberlain
2020-08-14 11:38 ` Lukas Middendorf
2020-08-14 16:37 ` Luis Chamberlain
2020-08-14 21:59 ` Lukas Middendorf
2020-08-17 15:20 ` Luis Chamberlain
2020-08-17 22:04 ` Lukas Middendorf
2020-08-18 14:37 ` Luis Chamberlain
2021-04-01 14:59 ` Lukas Middendorf
2021-04-02 18:02 ` Luis Chamberlain
2021-04-02 22:19 ` Luis Chamberlain
2021-04-02 22:58 ` Luis Chamberlain
2021-04-03 10:24 ` Lukas Middendorf
2021-04-03 16:07 ` Lukas Middendorf [this message]
2021-04-03 20:25 ` Luis Chamberlain
2021-04-03 21:04 ` Luis Chamberlain
2021-04-05 9:52 ` Lukas Middendorf
2021-04-04 0:50 ` Lukas Middendorf
2021-04-08 18:02 ` Luis Chamberlain
2021-04-16 23:17 ` 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=63de0271-5222-efb0-b7ba-1ccf3d2401fa@tuxforce.de \
--to=kernel@tuxforce.de \
--cc=crope@iki.fi \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mchehab@kernel.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;
as well as URLs for NNTP newsgroup(s).