lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 22 Nov 2017 09:07:45 +0100
From:   Loic Poulain <>
To:     Peter Robinson <>
Cc:     Marcel Holtmann <>,
        Stefan Wahren <>,
        Matt Hart <>,
        Linux Kernel Mailing List <>,,,
        linux-arm-kernel <>,
        Eric Anholt <>
Subject: Re: [GIT PULL 1/2] bcm2835-dt-fixes-2017-10-06

Hi Peter,

> So it seems it's actually working fine albeit the strange mac addr, no
> idea what I was trying before, although there's an error about loading
> firmware:
> [   31.035291] Bluetooth: hci0: BCM: chip id 94
> [   31.035801] Bluetooth: hci0: BCM: features 0x2e
> [   31.037483] Bluetooth: hci0: BCM43430A1
> [   31.037498] Bluetooth: hci0: BCM43430A1 (001.002.009) build 0000
> [   31.037694] bluetooth hci0: Direct firmware load for
> brcm/BCM43430A1.hcd failed with error -2
> [   31.037704] Bluetooth: hci0: BCM: Patch brcm/BCM43430A1.hcd not found

Ok, think that's why you have this kind of 'default' address, you should be able
to provision a valid address with btmgmt tool. The chip can work
without applying
patch file, original firmware is then executed, which is potentially
more or less buggy.

> By adding a firmware [1] to the location it actually now stops
> working, although shows up with a hciconfig, and had the following
> errors.
> [   26.078038] Bluetooth: hci0: BCM: chip id 94
> [   26.096797] Bluetooth: hci0: BCM: features 0x2e
> [   28.130753] Bluetooth: hci0 command 0x0c14 tx timeout
> [   36.322725] Bluetooth: hci0: BCM: Reading local name failed (-110)

Really weird, because these steps are prior firmware loading, moreover on HCI
command timeout, the HCI core is supposed to retry sending of the command,
here nothing happened between [28.13] and [36.32]....

Could you please try to load hci_uart.ko manually after boot to see if it could
be related to some init timings/concurrency.


Powered by blists - more mailing lists