public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Liejun Tao <liejuntao001@gmail.com>
To: Ed Tsang <netdesign_98@yahoo.com>
Cc: Bluettooth Linux <linux-bluetooth@vger.kernel.org>
Subject: Re: double Connect req: psm 1 scid 0x0040 ?
Date: Tue, 2 Feb 2010 15:41:28 -0600	[thread overview]
Message-ID: <8a7a8d7b1002021341j2d9835f6m13e697aad2a41f59@mail.gmail.com> (raw)
In-Reply-To: <272603.59641.qm@web52603.mail.re2.yahoo.com>

Hi,

On Tue, Feb 2, 2010 at 2:33 PM, Ed Tsang <netdesign_98@yahoo.com> wrote:
>
> Hi all,
>  I was pulling my hair on opp a file to a Blackberry. Blackerry is set to "receive using bluetooth".
> 1. If the Blackberry was not paired before. It ran through ok: enter the pin, accept connection, accept the file.
> 2. If the Blackberry was paired and in it's device properties, I change the encryption off for my box. It ran through ok, accept connection, accept the file...
> 3. If the Blackberry was paired and I leave the device properties unchange (default is encryption on). It will fail, not seeing any prompt to accept the connection.
>
> In hcidump I seem to see a problem in #3. After the Encrypt Change there seem to be 2 >con. req. psm 1 scid 0x0040
>
> Any suggestion on how to trace it down/work around this?
> .............
>
> > HCI Event: Read Remote
> Supported Features (0x0b) plen 11
> < ACL data: handle 42 flags
> 0x02 dlen 10
>    L2CAP(s): Info req: type 2
> > HCI Event: Number of
> Completed Packets (0x13) plen 5
> > HCI Event: Encrypt Change
> (0x08) plen 4
> < ACL data: handle 42 flags
> 0x02 dlen 12
>    L2CAP(s): Connect req: psm 1 scid 0x0040
> > ACL data: handle 42 flags
> 0x02 dlen 12
>    L2CAP(s): Info rsp: type 2 result 1
>      Not supported
> < ACL data: handle 42 flags
> 0x02 dlen 12
>    L2CAP(s): Connect req: psm 1 scid 0x0040
> > HCI Event: Number of
> Completed Packets (0x13) plen 5
> > HCI Event: Number of
> Completed Packets (0x13) plen 5
> > ACL data: handle 42 flags
> 0x02 dlen 16
>    L2CAP(s): Connect rsp: dcid 0x0040 scid
> 0x0040 result 0 status 0
>      Connection successful
> < ACL data: handle 42 flags
> 0x02 dlen 12
>    L2CAP(s): Config req: dcid 0x0040 flags
> 0x00 clen 0
> > ACL data: handle 42 flags
> 0x02 dlen 16
>    L2CAP(s): Connect rsp: dcid 0x0041 scid
> 0x0040 result 4 status 0
>      Connection refused - no resources
> available
> .................
> Regards, Ed
>
>
>
>      __________________________________________________________________
> Get a sneak peak at messages with a handy reading pane with All new Yahoo! Mail: http://ca.promos.yahoo.com/newmail/overview2/
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

I'm trying to resolve this issue. Let me post the patch for review.

  reply	other threads:[~2010-02-02 21:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02 20:33 double Connect req: psm 1 scid 0x0040 ? Ed Tsang
2010-02-02 21:41 ` Liejun Tao [this message]
2010-02-03  0:28 ` Marcel Holtmann
2010-02-03 14:54   ` Ed Tsang
2010-02-03 15:07     ` Marcel Holtmann
2010-02-03 16:02       ` Ed Tsang
2010-06-16 10:21       ` Andrei Emeltchenko
2010-06-16 13:39         ` Ed Tsang
2010-06-16 14:14           ` Andrei Emeltchenko

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=8a7a8d7b1002021341j2d9835f6m13e697aad2a41f59@mail.gmail.com \
    --to=liejuntao001@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=netdesign_98@yahoo.com \
    /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