From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] RFComm doesn't disconnect in server mode
Date: Wed, 13 Apr 2005 13:33:57 +0200 [thread overview]
Message-ID: <1113392037.9061.18.camel@pegasus> (raw)
In-Reply-To: <425BEB6E.4080500@palmsource.com>
Hi Frederic,
> I am working on headset profile implementation. In server mode, the
> headset (Jabra BT200) connects fine, but once my program close the
> RFComm socket, the ACL link is still up, until I stop the headset.
>
> I get in console :
> fdanis:> ./hstest server - 00:07:A4:05:B6:DA
> Server RFCOMM socket 3 listen on RFComm 2
> RFComm connected
> AT+CKPD=200
> RFComm disconnected
> fdanis:>
>
> Here are the last traces I got before stopping headset :
> > HCI Event: Mode Change (0x14) plen 6
> 0000: 00 29 00 02 00 08 .)....
> < ACL data: handle 0x0029 flags 0x02 dlen 8
> L2CAP(d): cid 0x0042 len 4 [psm 3]
> RFCOMM(s): DISC: cr 0 dlci 4 pf 1 ilen 0 fcs 0x16
> > HCI Event: Number of Completed Packets (0x13) plen 5
> 0000: 01 29 00 01 00 .)...
> > ACL data: handle 0x0029 flags 0x02 dlen 8
> L2CAP(d): cid 0x0041 len 4 [psm 3]
> RFCOMM(s): UA: cr 0 dlci 4 pf 1 ilen 0 fcs 0x3c
>
> Maybe a RFCOMM DISC frame on the DLCI 0 is missing.
the guys from TomTom discovered the same problem some time ago. This is
a reference counting problem on our side and a fix for that was posted
to the mailing list and is in the 2.6.12-rc2 kernel. However it seems
that this fix introduces an oops at some point. I haven't had the time
to investigate this any further.
The funny things with these kind of problems are that the specification
misses some words on who is responsible for terminating a signal channel
or the underlaying ACL link. Basically in your case the headset is the
initiator and it is too stupid too terminate its own RFCOMM signal
channel that it created previous. I have no idea why this is not caught
by the qualification tests.
I think the Jabra headsets are CSR based and maybe the CSR developers
are interested to hear about it. Please post the "hcitool info" output
for them.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-04-13 11:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 15:38 [Bluez-devel] RFComm doesn't disconnect in server mode Frederic Danis
2005-04-13 11:33 ` 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=1113392037.9061.18.camel@pegasus \
--to=marcel@holtmann.org \
--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