public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Yves Paulus <py@idlum.be>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] What does error 110 actually mean? What is it caused by?
Date: Mon, 06 Aug 2007 17:02:00 +0200	[thread overview]
Message-ID: <46B737E8.5060106@idlum.be> (raw)

Hello,

I keep getting this error in hcid output now and then, and for various 
calls:

(hcid stderr) hcid[32196]: connect(): Connection timed out (110)

 From my limited understanding, this error happens when a hci call to 
the dongle times out. Is it right?

I observed that on some computers, this error happens very often when 
kernel module ehci_hcd is loaded. It is generally coming up less often 
when it is not loaded.

Also, I failed to find any way to have any influence on those errors. I 
start getting them suddenly, and also suddenly, I stop getting them. I 
can have none for hours, and then suddenly lots of them for 5 minutes, 
and afterwards everything works properly again. I can also get one or 
two every few minutes. Really, I can't find a pattern for their appearence.

So what's happening there? Any feedback on this issue would be really 
appreciated.

Best Reagrds,
Pierre-Yves


-------------------------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2007-08-06 15:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06 15:02 Pierre-Yves Paulus [this message]
2007-08-11 18:18 ` [Bluez-devel] What does error 110 actually mean? What is it caused by? Marcel Holtmann

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=46B737E8.5060106@idlum.be \
    --to=py@idlum.be \
    --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