public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff Wilson" <jazzbotley@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] nonblocking socket
Date: Thu, 3 Aug 2006 17:49:58 -0500	[thread overview]
Message-ID: <5f30e2610608031549x70d290edi33d9ae67a873ad03@mail.gmail.com> (raw)
In-Reply-To: <1154649927.3905.79.camel@aeonflux.holtmann.net>

No, I'm not directly creating HCI connections.  I use
socket(...,BTPROTO_RFCOMM) and then use that fd with read()/write()

On a hunch, I rebuilt my bluez-lib from the 2.25 tgz, re-installed,
then restarted hcid, sdpd, etc.  I can now use sdptool without error.

I guess libbluetooth got corrupted by a power-interruption reset?

Thanks for the feedback.  Sorry for the noise.

        Best regards,
          Jeff

On 8/3/06, Marcel Holtmann <marcel@holtmann.org> wrote:
> 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
>

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

      reply	other threads:[~2006-08-03 22:49 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
2006-08-03 22:49         ` Jeff Wilson [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=5f30e2610608031549x70d290edi33d9ae67a873ad03@mail.gmail.com \
    --to=jazzbotley@gmail.com \
    --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