+ linux-bluetooth
On Thu, Nov 8, 2018 at 4:08 PM João Paulo Rechi Vita <[email protected]> wrote: > > Hello Marcel, > > > On Oct 4, 2018, at 2:25 AM, Marcel Holtmann <[email protected]> wrote: > > > > Hi Kai-Heng, > > > >>> I think Canonical were facing some wifi fw load error from some 8260 > >>> earlier module during the BT still loading the fw. > >>> I believe we had later 8260 sku that fixed this issue. > >> > >> But there are already 8260 that is affected by this bug in the wild. > >> > >> Search "Bluetooth: hci0: Failed to send firmware data (-38)” and there are > >> lots of user are affected. > > > > which SKUs are these actually. What are the initial details about the boot > > loader. For the Bluetooth side, you should be able to grab them from dmesg > > or by running btmon. > > > > So I am not in favor of this kind of hack and creating dependencies between > > drivers. If you only have a hammer, then everything looks like a nail. And > > this is a massive hammer trying to squash everything. This problem needs to > > be debugged. And this starts by providing affected SKU information and > > firmware information. So get the details about the SKU and its Bluetooth > > and WiFi boot loaders. > > > > I have a Lenovo Yoga 900 which presents this problem and has the same > bootloader / firmware information as Kai-Heng already posted: > > [ 5.992426] Bluetooth: Core ver 2.22 > [ 5.992438] Bluetooth: HCI device and connection manager initialized > [ 5.992442] Bluetooth: HCI socket layer initialized > [ 5.992444] Bluetooth: L2CAP socket layer initialized > [ 5.992450] Bluetooth: SCO socket layer initialized > [ 6.004941] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 > [ 6.010922] Bluetooth: hci0: Device revision is 5 > [ 6.010923] Bluetooth: hci0: Secure boot is enabled > [ 6.010924] Bluetooth: hci0: OTP lock is enabled > [ 6.010925] Bluetooth: hci0: API lock is enabled > [ 6.010926] Bluetooth: hci0: Debug lock is disabled > [ 6.010927] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 > [ 6.014253] bluetooth hci0: firmware: direct-loading firmware > intel/ibt-11-5.sfi > [ 6.014256] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi > [ 6.613961] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 > [ 6.613966] Bluetooth: BNEP filters: protocol multicast > [ 6.613974] Bluetooth: BNEP socket layer initialized > [ 6.983804] Bluetooth: hci0: Failed to send firmware data (-38) > > And the following product id and revision, from usb-devices: > > T: Bus=01 Lev=01 Prnt=01 Port=06 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 > D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 > P: Vendor=8087 ProdID=0a2b Rev=00.01 > C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA > I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb > I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb > > I understand the drawbacks with the approach presented here and lack of clear > explanation of the problem, but I can confirm these patches work around the > problem on my machine. Is there any extra info or test result I can provide > to help debug this? I can also dedicate time to help write a different > solution if some guidance is provided. > > Kai-Heng, did you end up filling a Bugzilla entry for this? > > Please CC-me on the replies as I'm not receiving emails from linux-bluetooth > or linux-wireless anymore. > > Thanks, > > -- > João Paulo Rechi Vita > http://about.me/jprvita
