2007-06-28 14:36:40

by Benjamin Fong

[permalink] [raw]
Subject: [Bluez-devel] hcid defunct

Hi,

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?

Regards,
Ben


Attachments:
(No filename) (1.03 kB)
(No filename) (1.19 kB)
(No filename) (286.00 B)
(No filename) (164.00 B)
Download all attachments

2007-06-28 14:56:25

by Marcel Holtmann

[permalink] [raw]
Subject: Re: [Bluez-devel] hcid defunct

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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

2007-07-06 17:46:18

by Benjamin Fong

[permalink] [raw]
Subject: Re: [Bluez-devel] hcid defunct

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 <[email protected]> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>


Attachments:
(No filename) (1.92 kB)
(No filename) (2.56 kB)
(No filename) (286.00 B)
(No filename) (164.00 B)
Download all attachments