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. Ben. -- Ben Hutchings The program is absolutely right; therefore, the computer must be wrong.
Attachment:
signature.asc
Description: This is a digitally signed message part