Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1730147
| From | Linus Torvalds <torvalds@linux-foundation.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: btusb "firmware request while host is not available" at resume |
| Date | 2017-09-11 06:30 +0200 |
| Message-ID | <uoowa-67j-3@gated-at.bofh.it> (permalink) |
| References | <uog5A-8ph-13@gated-at.bofh.it> <uolHX-3Uv-1@gated-at.bofh.it> <uonqp-5jQ-5@gated-at.bofh.it> <uonTr-5wo-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sun, Sep 10, 2017 at 8:49 PM, Gabriel C <nix.or.die@gmail.com> wrote:
>
> Yes 81f95076281f is to blame.. After reverting it all is fine again.
>
> 15 resume cycles on the one laptop , 10 on the other without to hit the
> trace.
Yeah, I think that disable/enable_firmware in the suspend/resume path
is basically just completely random code. There is nothing that
serializes with anything else, and it has no actual basis for saying
"I am now disabled/enabled" except for some entirely random time of
whenever the suspend/resume callbacks happen.
I'm going to revert it.
I wonder why 4.13 seemed to work for me. Or maybe it didn't, and I
just didn't notice, because I didn't use bluetooth and I wasn't
traveling. I test my laptop every release, but I don't necessarily
always _use_ it.
Linus
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
btusb "firmware request while host is not available" at resume Linus Torvalds <torvalds@linux-foundation.org> - 2017-09-10 21:30 +0200
Re: btusb "firmware request while host is not available" at resume Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-11 03:30 +0200
Re: btusb "firmware request while host is not available" at resume Gabriel C <nix.or.die@gmail.com> - 2017-09-11 05:20 +0200
Re: btusb "firmware request while host is not available" at resume Gabriel C <nix.or.die@gmail.com> - 2017-09-11 05:50 +0200
Re: btusb "firmware request while host is not available" at resume Linus Torvalds <torvalds@linux-foundation.org> - 2017-09-11 06:30 +0200
Re: btusb "firmware request while host is not available" at resume Marcel Holtmann <marcel@holtmann.org> - 2017-09-11 07:20 +0200
Re: btusb "firmware request while host is not available" at resume Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-11 15:50 +0200
Re: btusb "firmware request while host is not available" at resume "Luis R. Rodriguez" <mcgrof@kernel.org> - 2017-09-11 19:20 +0200
Re: btusb "firmware request while host is not available" at resume Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-11 21:40 +0200
Re: btusb "firmware request while host is not available" at resume "Luis R. Rodriguez" <mcgrof@kernel.org> - 2017-09-11 22:10 +0200
Re: btusb "firmware request while host is not available" at resume Gabriel C <nix.or.die@gmail.com> - 2017-09-12 02:20 +0200
Re: btusb "firmware request while host is not available" at resume "Luis R. Rodriguez" <mcgrof@kernel.org> - 2017-09-12 02:40 +0200
Re: btusb "firmware request while host is not available" at resume Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 02:50 +0200
Re: btusb "firmware request while host is not available" at resume "Luis R. Rodriguez" <mcgrof@kernel.org> - 2017-09-12 19:00 +0200
Re: btusb "firmware request while host is not available" at resume Marcel Holtmann <marcel@holtmann.org> - 2017-09-12 07:20 +0200
Re: btusb "firmware request while host is not available" at resume "Luis R. Rodriguez" <mcgrof@kernel.org> - 2017-09-12 18:30 +0200
Re: btusb "firmware request while host is not available" at resume Marcel Holtmann <marcel@holtmann.org> - 2017-09-13 09:00 +0200
Re: btusb "firmware request while host is not available" at resume "Luis R. Rodriguez" <mcgrof@kernel.org> - 2017-09-13 19:50 +0200
csiph-web