From: Marcel Holtmann <marcel@holtmann.org>
To: Frederic Danis <frederic.danis@access-company.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: BlueZ pairing failure and kernel 2.6.24 crash
Date: Wed, 04 Feb 2009 19:34:26 +0100 [thread overview]
Message-ID: <1233772466.12562.6.camel@californication> (raw)
In-Reply-To: <49886819.2030401@access-company.com>
Hi Frederic,
> I am working with BlueZ 3.22, kernel 2.6.24 on ARM and found 2 problems :
>
> - I am not able to pair with some phones (Nokia N70 and sony-ericsson
> P800). After some investigations, I found that a "L2CAP information
> request packet" is sent just after the ACL connection. Both phones reply
> with "command rejected" error, then disconnect the ACL link before BlueZ
> is able to finish the pairing (see attached traces).
>
> - with some other phones (LG 990 Viewty and sony-ericsson T610), the
> kernel crashes after pairing initiated by the phone is completed.
>
> For the first problem I removed the send of the "L2CAP information
> request packet" in the kernel (see attached patch). This fixes both
> problems.
>
> I did not found any usage of the remote L2CAP information in kernel.
> Is sending "L2CAP information request packet" mandatory for upper layer
> and/or qualification ?
> Is my fix OK ?
sending the L2CAP info is just fine. It should not cause any problems. I
think it is the pairing code that does some weird things at the wrong
time. Can you test with bluetooth-testing.git against bluez-4.28 to
verify that this issue still exists.
Regards
Marcel
next prev parent reply other threads:[~2009-02-04 18:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 15:51 BlueZ pairing failure and kernel 2.6.24 crash Frederic Danis
2009-02-04 18:34 ` Marcel Holtmann [this message]
2009-02-05 15:57 ` Frederic Danis
2009-02-26 9:48 ` Frederic Danis
2009-02-26 16:05 ` Marcel Holtmann
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=1233772466.12562.6.camel@californication \
--to=marcel@holtmann.org \
--cc=frederic.danis@access-company.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