Re: Is request_firmware() really safe to call in resume callback when /usr/lib/firmware is on btrfs?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Aug 18, 2020 at 12:04:51AM +0200, Lukas Middendorf wrote:
> On 17/08/2020 17:20, Luis Chamberlain wrote:
> A freeze can happen on resume with and without the si2168 firmware files
> installed. It however is easier to hit the freeze with the firmware files
> installed. Without the firmware files present the freeze happens only if no
> other driver uses the firmware loader.
> 
> > 
> > This helps, thanks so much, now we'll have to write a reproducer, thanks
> > for the report!!
> 
> Will you do it yourself or do you expect me to do anything for this?

I meant to imply that we'd do this, now that we understand the problem. Thanks
for your report!

> > > The nouveau driver in use seems to be equivalent to running "ls -R
> > > /usr/lib/firmware" before suspend.
> > > 
> > > All the cases seem to boil down to:
> > > It freezes if the file system has to be accessed to list the content of
> > > /usr/lib/firmware or to read the si2168 firmware file
> > 
> > Let's confirm first whether or not your system is using other firmware
> > files too or not.
> 
> I confirmed that above. Why is this so important, anyway?

A reproducer is easier to write if the actual file neeed is not needed.
That's all.

  Luis



[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux