linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Batyiev <batyiev@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Bluetooth ECDH selftest failed (endianness issue?)
Date: Thu, 27 Dec 2018 05:21:10 +0200	[thread overview]
Message-ID: <CAEQQxWzdBy9JOC7+oQTBJ35Gov1CDk17fy+XH=jha8MuT9fy9Q@mail.gmail.com> (raw)

Hello everyone,

I'm trying to pair my MIPS based router with a phone (using bluez),
without success.
I have turned on debugging features of bluetooth kernel module and I
got this in dmesg:

[  234.481526] Bluetooth: Core ver 2.22
[  234.485231] Bluetooth: Starting self testing
[  234.525375] Bluetooth: ECDH sample 1 failed
[  234.529728] Bluetooth: Finished self testing

Also, I checked hcidump, and it seems that SMP "Pairing confirm"
command got rejected by the phone with an error ("Reason: Unspecified
Reason (0x08)").
As far as I understand, ECDH computation is involved in a pairing process.

However, my Linux desktop is able to successfully pair to the phone
(Ubuntu 18.04) via the same dongle, using same version of bluez.

The huge difference between my desktop and router is endianness:
router is big-endian, while desktop is little-endian. Maybe, that's
the case?

I'm not sure how to debug this, could you please advise?

Router specs:
CPU: QCA9531 (MIPS_24KC, big-endian)
Distro: OpenWRT git master
Linux: 4.14.88
BlueZ: 5.49
Bluetooth dongle: CSR8510 A10

Thanks,
  Andrey

             reply	other threads:[~2018-12-27  3:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-27  3:21 Andrey Batyiev [this message]
2018-12-29  7:35 ` Bluetooth ECDH selftest failed (endianness issue?) Marcel Holtmann
2019-01-03 20:19   ` Andrey Batyiev
2019-01-07 22:37     ` Andrey Batyiev
2019-01-18  9:43       ` Marcel Holtmann
2019-01-18 13:51         ` Emil Lenngren
2019-01-21 14:53           ` Marcel Holtmann
2019-01-21 16:56             ` Emil Lenngren

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='CAEQQxWzdBy9JOC7+oQTBJ35Gov1CDk17fy+XH=jha8MuT9fy9Q@mail.gmail.com' \
    --to=batyiev@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).