All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: "t.[NO_SPAM]" <schorpp@gmx.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, VIA USB HUBS
Date: Tue, 06 Jan 2004 13:44:03 +0100	[thread overview]
Message-ID: <1073393043.2508.50.camel@pegasus> (raw)
In-Reply-To: <3FF9E3F2.4040506@gmx.de>

Hi Thomas,

> hi, yes i read the previous threads, this could be the well known 
> problems with the via usb chips ;), it does not occur with my older p2 
> machine. linux, pda and window$ clients kill my server after minutes:
> 
> 
> ^[[AJan  5 21:09:46 TOM1 kernel: hci_acl_tx_to: hci0 ACL tx timeout
> Jan  5 21:09:46 TOM1 kernel: hci_acl_tx_to: hci0 killing stalled ACL 
> connection DC:0F:A5:60:10:00
> Jan  5 21:22:47 TOM1 pand[5823]: Accept failed. Interrupted system call(4)
> Jan  5 21:53:36 TOM1 kernel: hci_acl_tx_to: hci0 ACL tx timeout
> Jan  5 21:53:36 TOM1 kernel: hci_acl_tx_to: hci0 killing stalled ACL 
> connection DC:0F:A5:60:10:00
> 
> same with the nokia affix stack.
> 
> cuurently i run a script detecting this error, resetting the bluetooth 
> and restarting the daemons automatically.
> 
> no nice way.
> 
> there should be a way to recover that fault better, but where to start?

why do you think that this is a BlueZ problem? What kernel do you use?
What do "hciconfig -a" say about your dongle?

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2004-01-06 12:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-05 22:23 [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, VIA USB HUBS thomas.schorpp
2004-01-06  0:30 ` [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, stalling next accept thomas.schorpp
2004-01-06  0:45   ` thomas.schorpp
2004-01-06 12:44 ` Marcel Holtmann [this message]
2004-01-06 12:57   ` [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, VIA USB HUBS thomas.schorpp
2004-01-06 13:38     ` Marcel Holtmann
2004-01-06 13:52       ` thomas.schorpp
2004-01-06 13:56         ` Marcel Holtmann
2004-01-06 15:08           ` thomas.schorpp
2004-01-06 15:55             ` [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, sco not the problem thomas.schorpp
2004-01-06 20:03               ` [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, solved, kmod loaded wrong ALTERNATE uhci driver by default thomas.schorpp

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=1073393043.2508.50.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=schorpp@gmx.de \
    /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.