linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [Bluez-devel] Dund connection problems
@ 2006-05-03 16:01 Dave Henriksen
  0 siblings, 0 replies; only message in thread
From: Dave Henriksen @ 2006-05-03 16:01 UTC (permalink / raw)
  To: bluez-devel

[-- Attachment #1: Type: text/plain, Size: 7117 bytes --]

All,

 

I was wondering is anyone might have an idea what would be causing devices
to be unable to connect to a Bluetooth hub I have built using BlueZ on a
small single board computer.   Generally, it works extremely well, but on
occasion this Bluetooth hub does the following when a client tries to
connect to it.   My kernel is 2.6.14.6-mh2, with bluez-libs-2.25 and the
latest bluez utils .

 

 

 

tail -30 /var/log/messages

 

May  3 09:47:56 OBBTHub hcid[4114]: link_key_notify (sba=00:02:72:C1:F1:07,
dba=00:0A:3A:55:05:D5)

May  3 09:48:53 OBBTHub hcid[4114]: link_key_request (sba=00:02:72:C1:F1:07,
dba=00:0A:3A:55:05:D5)

May  3 09:49:57 OBBTHub hcid[4114]: pin_code_request (sba=00:02:72:C1:F1:07,
dba=00:0A:3A:55:05:D5)

May  3 09:49:57 OBBTHub hcid[4114]: link_key_notify (sba=00:02:72:C1:F1:07,
dba=00:0A:3A:55:05:D5)

May  3 09:50:54 OBBTHub hcid[4114]: link_key_request (sba=00:02:72:C1:F1:07,
dba=00:0A:3A:55:05:D5)

May  3 09:51:58 OBBTHub hcid[4114]: pin_code_request (sba=00:02:72:C1:F1:07,
dba=00:0A:3A:55:05:D5)

May  3 09:51:58 OBBTHub hcid[4114]: link_key_notify (sba=00:02:72:C1:F1:07,
dba=00:0A:3A:55:05:D5)

May  3 09:52:55 OBBTHub hcid[4114]: link_key_request (sba=00:02:72:C1:F1:07,
dba=00:0A:3A:55:05:D5)

May  3 09:54:00 OBBTHub hcid[4114]: pin_code_request (sba=00:02:72:C1:F1:07,
dba=00:0A:3A:55:05:D5)

May  3 09:54:01 OBBTHub hcid[4114]: link_key_notify (sba=00:02:72:C1:F1:07,
dba=00:0A:3A:55:05:D5)

May  3 09:54:58 OBBTHub hcid[4114]: link_key_request (sba=00:02:72:C1:F1:07,
dba=00:0A:3A:55:05:D5)

May  3 09:56:02 OBBTHub hcid[4114]: pin_code_request (sba=00:02:72:C1:F1:07,
dba=00:0A:3A:55:05:D5)

May  3 09:56:03 OBBTHub hcid[4114]: link_key_notify (sba=00:02:72:C1:F1:07,
dba=00:0A:3A:55:05:D5)

May  3 09:57:00 OBBTHub hcid[4114]: link_key_request (sba=00:02:72:C1:F1:07,
dba=00:0A:3A:55:05:D5)

May  3 09:58:05 OBBTHub hcid[4114]: pin_code_request (sba=00:02:72:C1:F1:07,
dba=00:0A:3A:55:05:D5)

 

When I run hcidump on the hub that I have built, I get .   Please note the
"Connection refused - no resources available" that is about half way through
the file.

 

 

 

HCI sniffer - Bluetooth packet analyzer ver 1.29

device: hci0 snap_len: 1028 filter: 0xffffffff

> HCI Event: Connect Request (0x04) plen 10

< HCI Command: Accept Connection Request (0x01|0x0009) plen 7

> HCI Event: Command Status (0x0f) plen 4

> HCI Event: PIN Code Request (0x16) plen 6

< HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23

> HCI Event: Command Complete (0x0e) plen 10

> HCI Event: Link Key Notification (0x18) plen 23

> HCI Event: Connect Complete (0x03) plen 11

< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4

> HCI Event: Command Complete (0x0e) plen 6

< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4

> HCI Event: Command Status (0x0f) plen 4

> ACL data: handle 7 flags 0x02 dlen 12

    L2CAP(s): Connect req: psm 1 scid 0x0040

< ACL data: handle 7 flags 0x02 dlen 16

    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0

      Connection successful

> HCI Event: Max Slots Change (0x1b) plen 3

> HCI Event: Number of Completed Packets (0x13) plen 5

< ACL data: handle 7 flags 0x02 dlen 12

    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040

> HCI Event: Number of Completed Packets (0x13) plen 5

> HCI Event: Disconn Complete (0x05) plen 4

> HCI Event: Connect Request (0x04) plen 10

< HCI Command: Accept Connection Request (0x01|0x0009) plen 7

> HCI Event: Command Status (0x0f) plen 4

> HCI Event: Link Key Request (0x17) plen 6

< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22

> HCI Event: Command Complete (0x0e) plen 10

> HCI Event: Connect Complete (0x03) plen 11

< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4

> HCI Event: Command Complete (0x0e) plen 6

< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4

> HCI Event: Command Status (0x0f) plen 4

> ACL data: handle 6 flags 0x02 dlen 12

    L2CAP(s): Connect req: psm 1 scid 0x0040

< ACL data: handle 6 flags 0x02 dlen 16

    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0

      Connection successful

> HCI Event: Max Slots Change (0x1b) plen 3

> HCI Event: Number of Completed Packets (0x13) plen 5

> ACL data: handle 6 flags 0x02 dlen 12

    L2CAP(s): Connect req: psm 1 scid 0x0040

< ACL data: handle 6 flags 0x02 dlen 16

    L2CAP(s): Connect rsp: dcid 0x0000 scid 0x0040 result 4 status 0

      Connection refused - no resources available

> HCI Event: Number of Completed Packets (0x13) plen 5

< ACL data: handle 6 flags 0x02 dlen 12

    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040

> HCI Event: Number of Completed Packets (0x13) plen 5

> HCI Event: Disconn Complete (0x05) plen 4

> HCI Event: Connect Request (0x04) plen 10

< HCI Command: Accept Connection Request (0x01|0x0009) plen 7

> HCI Event: Command Status (0x0f) plen 4

> HCI Event: PIN Code Request (0x16) plen 6

< HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23

> HCI Event: Command Complete (0x0e) plen 10

> HCI Event: Link Key Notification (0x18) plen 23

> HCI Event: Connect Complete (0x03) plen 11

< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4

> HCI Event: Command Complete (0x0e) plen 6

< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4

> ACL data: handle 7 flags 0x02 dlen 12

    L2CAP(s): Connect req: psm 1 scid 0x0040

< ACL data: handle 7 flags 0x02 dlen 16

    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0

      Connection successful

> HCI Event: Command Status (0x0f) plen 4

> HCI Event: Max Slots Change (0x1b) plen 3

> HCI Event: Number of Completed Packets (0x13) plen 5

< ACL data: handle 7 flags 0x02 dlen 12

    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040

> HCI Event: Number of Completed Packets (0x13) plen 5

> HCI Event: Disconn Complete (0x05) plen 4

> HCI Event: Connect Request (0x04) plen 10

< HCI Command: Accept Connection Request (0x01|0x0009) plen 7

> HCI Event: Command Status (0x0f) plen 4

> HCI Event: Link Key Request (0x17) plen 6

< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22

> HCI Event: Command Complete (0x0e) plen 10

> HCI Event: Connect Complete (0x03) plen 11

< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4

> HCI Event: Command Complete (0x0e) plen 6

< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4

> HCI Event: Command Status (0x0f) plen 4

> ACL data: handle 6 flags 0x02 dlen 12

    L2CAP(s): Connect req: psm 1 scid 0x0040

< ACL data: handle 6 flags 0x02 dlen 16

    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0

      Connection successful

> HCI Event: Max Slots Change (0x1b) plen 3

> HCI Event: Number of Completed Packets (0x13) plen 5

 

Any ideas ?

 

Thanks,

 

Dave

 

 


[-- Attachment #2: Type: text/html, Size: 30419 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2006-05-03 16:01 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-03 16:01 [Bluez-devel] Dund connection problems Dave Henriksen

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).