From: Marcel Holtmann <marcel@holtmann.org>
To: Andreas Gaufer <andreas.gaufer@blue-cell-networks.com>
Cc: Bluez Devel <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] HCI Event: Connect Complete with Status 09
Date: Thu, 10 Jun 2004 16:32:20 +0200 [thread overview]
Message-ID: <1086877940.7930.32.camel@pegasus> (raw)
In-Reply-To: <20040610160148.1ca400c4.Andreas.Gaufer@blue-cell-networks.com>
Hi Andreas,
> Same behaviour w/o CONFIG_BT_HCIUSB_SCO. I disribe it again a bit more percise:
>
> hcitool -i hci1 cc 00:0A:D9:37:11:29
>
> < HCI Command: Create Connection(0x01|0x0005) plen 13
> 29 11 37 D9 0A 00 18 CC 02 00 00 00 00
> > HCI Event: Command Status(0x0f) plen 4
> 00 01 05 04
> > HCI Event: Connect Complete(0x03) plen 11
> 00 29 00 29 11 37 D9 0A 00 01 00
>
> hcitool con
> Connections:
> < ACL 00:0A:D9:37:11:29 handle 41 state 1 lm MASTER
>
> hcitool -i hci1 cc 00:0A:D9:37:11:29
> Can't create connection: Input/output error
>
> < HCI Command: Create Connection(0x01|0x0005) plen 13
> 29 11 37 D9 0A 00 18 CC 02 00 00 00 00
> > HCI Event: Command Status(0x0f) plen 4
> 0B 01 05 04
>
> hcitool con
> Connections:
>
> hcitool -i hci1 dc 00:0A:D9:37:11:29
> Get connection info failed: No such file or directory
>
> hcitool -i hci1 cmd 0x01 0x0006 0x29 0x00 0x13
> < HCI Command: ogf 0x01, ocf 0x0006, plen 3
> 29 00 13
> > HCI Event: 0x0f plen 4
> 00 01 06 04
>
>
> So the entry in the list that "hcitool con" prints gets lost when
> the secound cc is issued and fails. The chip still has the handle
> and it can be disconnected with hcitoom cmd.
>
> Im wondering witch part of the bluez Stack is maintaining the
> list and why the entry is dropped in case of a failed cc. I just
> can imagine that all acl handles are dropped that belong to that mac.
>
> IMHO it would be great if a handle could only be removed from the
> list if there is a successfull disconnect.
whoops, this looks really like a bug in the BlueZ stack. When the second
(in this case negative) command status arrives the stack must think of a
create connection failure and drop the connection from its internal list
without sending a disconnect. Check the hci_*.c kernel files.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-06-10 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 16:53 [Bluez-devel] HCI Event: Connect Complete with Status 09 Andreas Gaufer
2004-06-09 17:54 ` Steven Singer
2004-06-09 19:25 ` Andreas Gaufer
2004-06-10 10:18 ` [Bluez-devel] hcitool con list incomplete (was: Connect Complete with Status 09) Andreas Gaufer
2004-06-10 10:20 ` [Bluez-devel] HCI Event: Connect Complete with Status 09 Marcel Holtmann
2004-06-10 14:01 ` Andreas Gaufer
2004-06-10 14:32 ` Marcel Holtmann [this message]
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=1086877940.7930.32.camel@pegasus \
--to=marcel@holtmann.org \
--cc=andreas.gaufer@blue-cell-networks.com \
--cc=bluez-devel@lists.sourceforge.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