Hi, I know, this is a very old bug report but as I am still running Debian/jessie (and others might too), I thought my findings would still be helpful and/or lead to closing this bug. On 10/07/2014 09:18 AM, Bjørn Mork wrote: > Ben Hutchings <ben@decadent.org.uk> writes: >> On Mon, 2014-10-06 at 20:15 +0200, Julien Cristau wrote: >>> Package: src:linux >>> Version: 3.16.3-2 >>> Severity: normal >>> >>> Hi, >>> >>> I get the following trace in my kernel log, which I don't think I've >>> seen in pre-3.16 versions: >>> >>> Sep 29 19:12:49 betterave kernel: [ 7696.920600] PM: resume of devices complete after 508.149 msecs >>> Sep 29 19:12:49 betterave kernel: [ 7696.921181] ------------[ cut here ]------------ >>> Sep 29 19:12:49 betterave kernel: [ 7696.921188] WARNING: CPU: 2 PID: 3533 at /build/linux-P15SNz/linux-3.16.3/drivers/base/firmware_class.c:1109 _request_firmware+0x521/0xaf0() >> [...] >>> Sep 29 19:12:49 betterave kernel: [ 7696.921405] [<ffffffff813af8ac>] ? request_firmware+0x2c/0x40 >>> Sep 29 19:12:49 betterave kernel: [ 7696.921412] [<ffffffffa065f895>] ? btusb_setup_bcm_patchram+0x85/0x430 [btusb] >>> Sep 29 19:12:49 betterave kernel: [ 7696.921419] [<ffffffff813a663a>] ? rpm_check_suspend_allowed+0x6a/0xc0 >> [...] >>> Sep 29 19:12:49 betterave kernel: [ 7696.921528] bluetooth hci0: firmware: brcm/BCM20702A0-0a5c-21e6.hcd will not be loaded >> [...] >> >> This means: btusb tries to load firmware during its resume operation, >> when userland is not yet available. This doesn't work if firmware >> loading depends on the userland firmware agent. >> >> The warning won't appear if the firmware is installed in the usual >> place, as direct loading will work. And the firmware agent is npw >> deprecated and not even enabled in Debian kernels. We could remove this >> warning, but it would be papering over a driver bug. > > Are you sure about this? FWIW I've occasionally seen similar warnings > from another btusb device with firmware (using kernels I've built > myself, so not reported here of course). And I haven't really bothered to > look at the root cause before, so I haven't reported it upstream either. > [...] I also got this kernel backtrace log, especially after resume from suspend. So I tested the following configurations: * Kernel: 3.16.43-2+deb8u2 / without firmware * Kernel: 3.16.43-2+deb8u2 / with firmware * Kernel: 4.9.30-2+deb9u2~bpo8+1 / without firmware * Kernel: 4.9.30-2+deb9u2~bpo8+1 / with firmware Finding the correct firmware is a complete different story (see my comments in #801084 for details) but I only got the kernel backtrace log with the first configuration (Kernel: 3.16.43-2+deb8u2 / without firmware). So I think this issue is fixed in the jessie-backports kernel. If you need more information on this, please let me know. If Julien can confirm that the kernel log is not shown with the new kernel version, this bug can be closed. Regards, - Darsha
Attachment:
signature.asc
Description: OpenPGP digital signature