From: Dick <dick@mrns.nl>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] input service leaking l2cap connections
Date: Fri, 7 Sep 2007 14:33:34 +0000 (UTC) [thread overview]
Message-ID: <loom.20070907T162203-609@post.gmane.org> (raw)
Hi,
I still have some trouble with the input service and I think I've found
something related which is reproduceable.
If a device is reconnecting a lot the l2cap table in /sys/class/bluetooth/l2cap
is growing with connections (which aren't closed).
Try the following with a HID input device:
1. Start and configure the input service for the device
2. Start hcidump
3. Power off the input device
4. Wait until "Disconn complete" appear in hcidump
5. Power on the input device
6. Repeat from step 3
If you look at:
sort /sys/class/bluetooth/l2cap |uniq -c
You will see a huge number of connections from the input device.
greetings,
Dick
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2007-09-07 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 14:33 Dick [this message]
2007-09-10 17:35 ` [Bluez-users] input service leaking l2cap connections Claudio Takahasi
-- strict thread matches above, loose matches on Subject: below --
2007-09-14 17:51 Dick
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=loom.20070907T162203-609@post.gmane.org \
--to=dick@mrns.nl \
--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