From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] nonblocking socket
Date: Fri, 04 Aug 2006 02:05:27 +0200 [thread overview]
Message-ID: <1154649927.3905.79.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <5f30e2610608031445qf67c5e8p12ea39b8be27077@mail.gmail.com>
Hi Jeff,
> Never mind on the example program, no need to create one, I can
> reproduce the problem with sdptool v2.25:
>
> `sdptool browse <remote-addr>`
>
> Failed to connect to SDP server on <remote-addr>: Operation already in progress
>
> local hcidump -X -V
>
> HCI sniffer - Bluetooth packet analyzer ver 1.30
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < HCI Command: Create Connection (0x01|0x0005) plen 13
> bdaddr remote-addr ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> > HCI Event: Command Status (0x0f) plen 4
> Create Connection (0x01|0x0005) status 0x0b ncmd 1
> Error: ACL Connection Already Exists
can you test it with latest 2.6.17-mh5 kernel?
This error indicates that an ACL already exists. Are you playing with
HCI connection creation from userspace? If you do so, then don't.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-08-04 0:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 22:26 [Bluez-users] nonblocking socket Jeff Wilson
2006-08-03 10:29 ` Marcel Holtmann
2006-08-03 17:17 ` Jeff Wilson
2006-08-03 21:45 ` Jeff Wilson
2006-08-04 0:05 ` Marcel Holtmann [this message]
2006-08-03 22:49 ` Jeff Wilson
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=1154649927.3905.79.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-users@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