From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <3FFADA5E.8050202@gmx.de> Date: Tue, 06 Jan 2004 16:55:10 +0100 From: "thomas.schorpp" Reply-To: "t.[NO_SPAM]schorpp"@gmx.de MIME-Version: 1.0 CC: Marcel Holtmann , BlueZ Mailing List Subject: Re: [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, sco not the problem References: <3FF9E3F2.4040506@gmx.de> <1073393043.2508.50.camel@pegasus> <3FFAB0C5.4050407@gmx.de> <1073396288.2508.72.camel@pegasus> <3FFABD90.1020903@gmx.de> <1073397402.2508.81.camel@pegasus> <3FFACF71.70607@gmx.de> In-Reply-To: <3FFACF71.70607@gmx.de> Content-Type: text/plain; charset=us-ascii; format=flowed List-ID: 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 > >