From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with Raspberry Pi 3B+and BT
Date: Tue, 16 Oct 2018 23:56:56 +0200 [thread overview]
Message-ID: <20181016235656.584581d2@gmx.net> (raw)
In-Reply-To: <CALtfCQaiCCCetMG8sHvTjnAZdfnBNUQvZSB0ynn3LT58NH9Omg@mail.gmail.com>
Hello Oscar,
On Tue, 16 Oct 2018 08:45:36 +0200, Oscar Gomez Fuente <oscargomezf@gmail.com> wrote:
> Hi Peter,
>
> I've tried the BT with the new rpi-bt-firmware [8c1e2bff1d],
> rpi-wifi-firmware [8c1e2bff1d] and linux-firmware [44d4fca992] and new
> linux [6d27aa156c] packages, but it fails with the same error:
>
> [30090.903743] Bluetooth: hci0: Frame reassembly failed (-84)
> [30092.980340] Bluetooth: Failed to disable LE scan: status 0x1f
> [30092.980346] Bluetooth: hci0 command 0x200c tx timeout
>
> After around 8 hours the BT didn't work again.
>
> Does anyone any suggestion?
Do the check with an original Raspbian Image, if the same error occurs
complain upstream about it, otherwise find out what makes the difference...
Try the search the web, your are not the only one with this problem [1], [2]...
Regards,
Peter
[1] https://github.com/raspberrypi/linux/issues/2264
[2] https://raspberrypi.stackexchange.com/questions/70217/tons-of-bluetooth-hci0-frame-reassembly-failed-84-messages
>
> Best regards.
>
> Oscar Gomez Fuente
> TST Sistemas
> www.tst-sistemas.es
next prev parent reply other threads:[~2018-10-16 21:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 8:45 [Buildroot] Problem with Raspberry Pi 3B+and BT Oscar Gomez Fuente
2018-10-11 12:48 ` Matthew Weber
2018-10-11 14:44 ` Oscar Gomez Fuente
2018-10-12 21:41 ` Peter Seiderer
2018-10-13 9:13 ` Oscar Gomez Fuente
2018-10-16 6:45 ` Oscar Gomez Fuente
2018-10-16 21:56 ` Peter Seiderer [this message]
2018-10-17 6:37 ` Oscar Gomez Fuente
2018-10-29 7:24 ` Oscar Gomez Fuente
2018-10-29 18:38 ` Peter Seiderer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181016235656.584581d2@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox