From: "Benjamin Fong" <benjamin.backup@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hcid defunct
Date: Sat, 7 Jul 2007 01:46:18 +0800 [thread overview]
Message-ID: <22b6c3510707061046m60093a6di9895824152220706@mail.gmail.com> (raw)
In-Reply-To: <1183042585.9499.19.camel@aeonflux.holtmann.net>
[-- Attachment #1.1: Type: text/plain, Size: 1963 bytes --]
Hi Marcel,
I'd upgraded to Bluez 3.12 as per advised, but the problem still persist. I
notice that the issue only occurs when I have more than 1 dongle attached
into the USB port. Thanks
Regards,
Ben
On 6/28/07, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Ben,
>
> > I've written a program which periodically invokes hcitool scan, and
> > following that propagate out content via obex to the acquired
> > bluetooth address. I've noticed something remarkably strange occuring
> > throughout the process. The program which I'd written is invoked
> > immediately after boot. I'd noticed when I "ps -e" my system, there
> > are a couple of defunct hcid processes. These defunct hcid jobs are
> > immediately visible right after boot and the amount of defunct hcid
> > process will to continue grow until the entire bluetooth service is
> > stuffed. Once the bluetooth srvice is stuffed, if I were to invoke
> > either hcitool or sdptool...I would get a "connection timeout" reply.
> > The only way to remedy the situation is to periodically restart the
> > bluetooth service, once the service is restarted - all of the defunct
> > hcid process will be cleared.
> >
> > Btw I'm running Bluez-utils and bluez-libs 3.10.1 on both Fedora 6 and
> > 7 (issue is replicatable on both system). I've multiple dongles, but
> > only 1 dongle dedicated to scanning. Any idea, guys?
>
> why don't you start trying bluez-utils-3.12 and see if the issue still
> exists.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
[-- Attachment #1.2: Type: text/html, Size: 2623 bytes --]
[-- Attachment #2: Type: text/plain, Size: 286 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-07-06 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 14:36 [Bluez-devel] hcid defunct Benjamin Fong
2007-06-28 14:56 ` Marcel Holtmann
2007-07-06 17:46 ` Benjamin Fong [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=22b6c3510707061046m60093a6di9895824152220706@mail.gmail.com \
--to=benjamin.backup@gmail.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