diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2017-09-11 07:19:06 +0300 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2017-09-11 07:19:06 +0300 |
| commit | f007cad159e99fa2acd3b2e9364fbb32ad28b971 (patch) | |
| tree | 3347b090b27c27082414070a9cbf08a7bb75cbc6 /include/trace/events/block.h | |
| parent | 64414e5f9896805c2e80583345e9b1745be73aa9 (diff) | |
| download | linux-f007cad159e99fa2acd3b2e9364fbb32ad28b971.tar.xz | |
Revert "firmware: add sanity check on shutdown/suspend"
This reverts commit 81f95076281fdd3bc382e004ba1bce8e82fccbce.
It causes random failures of firmware loading at resume time (well,
random for me, it seems to be more reliable for others) because the
firmware disabling is not actually synchronous with any particular
resume event, and at least the btusb driver that uses a workqueue to
load the firmware at resume seems to occasionally hit the "firmware
loading is disabled" logic because the firmware loader hasn't gotten the
resume event yet.
Some kind of sanity check for not trying to load firmware when it's not
possible might be a good thing, but this commit was not it.
Greg seems to have silently suffered the same issue, and pointed to the
likely culprit, and Gabriel C verified the revert fixed it for him too.
Reported-by: Linus Torvalds <torvalds@linux-foundation.org>
Pointed-at-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Tested-by: Gabriel C <nix.or.die@gmail.com>
Cc: Luis R. Rodriguez <mcgrof@kernel.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/trace/events/block.h')
0 files changed, 0 insertions, 0 deletions