All of lore.kernel.org
 help / color / mirror / Atom feed
From: "thomas.schorpp" <t.schorpp@gmx.de>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, sco not the problem
Date: Tue, 06 Jan 2004 16:55:10 +0100	[thread overview]
Message-ID: <3FFADA5E.8050202@gmx.de> (raw)
In-Reply-To: <3FFACF71.70607@gmx.de>

thomas.schorpp wrote:
> Marcel Holtmann wrote:
> 
>> Hi Thomas,
>>
>>
>>>> This is HCI 16.4 firmware and it should work fine. Do you use the SCO
>>>> audio support for the HCI USB driver? If yes, disable it, because I
>>>> heard of problems with ISOC transfers on VIA chips if I remember
>>>> correctly.
>>>
>>>
>>> NO sco module loaded(?)
>>
>>
>>
>> I am not talking about the sco module. I am talking about the SCO audio
>> option of the HCI USB driver. Disable it to avoid ISOC transfers.
> 
> 
> yes, ill check, i think it is disabled, wanted only pan from the 
> beginning, thx a lot.

was enabled, now disabled, no change, stalled after 2 minutes transfer:

Jan  6 16:38:46 TOM1 pand[4118]: New connection from 00:10:60:A5:0F:DC bnep0

Jan  6 16:42:37 TOM1 kernel: hci_acl_tx_to: hci0 ACL tx timeout
Jan  6 16:42:37 TOM1 kernel: hci_acl_tx_to: hci0 killing stalled ACL 
connection DC:0F:A5:60:10:00

trying alternate usb driver...


> 
>>
>>
>>>> Use 2.4.23-mh1 or 2.4.24-mh1.
>>>
>>>
>>> roger that. what change do you think in the changelogs should target 
>>> the problem?
>>
>>
>>
>> In general nothing will help here, but I must be sure that we talk about
>> the same version of the Bluetooth subsystem.
> 
> 
> yes, ill try the patches IF theyre considered stable.
> will also try another usb driver -WARNING- do not use via vt6202 ehci 
> chipsets, they crashed my gatewaysystem reproducable on boot. :(
> 
> but i wonder why the window$ stacks do not trigger the fault... maybe 
> usb... have problems with sane scanner too :)
> 
>>
>> 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
>>
>>
> 
> y
> tom
> 
> 
> 
> -------------------------------------------------------
> 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
> 
> 

  reply	other threads:[~2004-01-06 15:55 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 ` [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, VIA USB HUBS Marcel Holtmann
2004-01-06 12:57   ` 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             ` thomas.schorpp [this message]
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=3FFADA5E.8050202@gmx.de \
    --to=t.schorpp@gmx.de \
    --cc="t.[NO_SPAM]schorpp"@gmx.de \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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.