From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: [Patch] Some btsco modifications
Date: Tue, 15 Mar 2005 17:17:03 -0700 [thread overview]
Message-ID: <42377AFF.8030405@xmission.com> (raw)
In-Reply-To: <1110930125.19889.13.camel@pc7.dolda2000.com>
Fredrik
> I just saw that sometimes the kernel apparently notices a broken RFCOMM
> channel and closes the socket. I don't know yet what might trigger it
> apart from an explicit disconnect.
wandering out of range, powering off the headset, suspending the laptop
are the ones I would run into.
> Either way, it made the btsco daemon chew up 100% CPU, so I added a case
> to detect it and exit for now. If it should be handled otherwise, that
> can be fixed when it is figured out what it should do instead.
ok
brad
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-03-16 0:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1110683934.5056.43.camel@pc7.dolda2000.com>
[not found] ` <4233C663.80109@xmission.com>
2005-03-14 1:11 ` [Bluez-devel] Re: [Patch] Some btsco modifications Fredrik Tolf
2005-03-14 11:52 ` Lars Grunewaldt
2005-03-14 13:51 ` Fredrik Tolf
2005-03-14 15:00 ` Fredrik Tolf
2005-03-14 12:55 ` Brad Midgley
2005-03-14 14:05 ` Fredrik Tolf
2005-03-14 17:26 ` Brad Midgley
2005-03-14 19:01 ` Florian Echtler
2005-03-14 20:34 ` Brad Midgley
2005-03-15 7:22 ` Brad Midgley
2005-03-15 23:42 ` Fredrik Tolf
2005-03-16 0:17 ` Brad Midgley [this message]
2005-03-16 1:56 ` Fredrik Tolf
2005-03-16 12:30 ` Lars Grunewaldt
2005-03-16 13:01 ` Fredrik Tolf
2005-03-16 15:18 ` Brad Midgley
2005-03-16 19:34 ` Lars Grunewaldt
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=42377AFF.8030405@xmission.com \
--to=bmidgley@xmission.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.