logo       

Re: ACL tx timeout?: msg#00166

Subject: Re: ACL tx timeout?
Hi,

 (1)
  I made some tests after I posted the following and
  in short, the problem still exists after I changed
  HCI_MAX_BULK_TX  from  4 to 1

   note : "uhci.o" could not be tried because "ohci.o"
            is the USB host driver in our case.


 (2)
  For me, the worst thing is that l2cap channel connection
  can not be connected once "ACL tx timeout" occurs.
  Infrequent occurrence  of "ACL tx timeout" could be
  acceptable.

 To make it recoverable, I am wodering upgrading firmware might
 be helpful or not.  (Below shows hciconfig result for the dongle.)
 BlueFW can't be used for CSR case, correct ? ( it is available only for BCM . 
?.)

  the posting by Carl (as of Mar.30 2003) regarding FW
   change lead me some confusion.  We bought BT-dongles from
   Mitsumi which actually use CSR chip, but did not directly
   from CSR.   Does anyone know how we can upgrade FW on
  such  commercial BT dongles ?

  hci1:   Type: USB
        BD Address: 00:A0:96:1F:D5:29 ACL MTU: 128:8  SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN
        RX bytes:338271 acl:2686 sco:0 events:5768 errors:0
        TX bytes:457198 acl:5294 sco:0 commands:223 errors:0
        Features: 0xff 0xff 0x05 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy:
        Link mode: ACCEPT MASTER
        Name: 'CSR - bc01b'
        Class: 0x000000
        Service Classes: Unspecified
        Device Class: Miscellaneous,
        HCI Ver: 1.1 (0x1) HCI Rev: 0x72 LMP Ver: 1.1 (0x1) LMP Subver: 0x72
        Manufacturer: Cambridge Silicon Radio (10)

 Any suggestion could be helpful for us.
 Thanks

Takayuki Kaiso
Thinktube Ltd.,
+81-78-857-8390



Takayuki Kaiso wrote:

> Hi, Max  and Ferenc
>
>  I have been troubled with the same problem which Ferenc reported.
>
>  In my case, an ACL link stalled after "a few hours" of normal connection ( 
> refer to (1) )
>  and never recovered from this status until the dongle is removed and
>  inserted again. ( refer to (2)).    ( Kernel  is 2.4.19 and 2.4.7 )
>
>  I was suspecting that the CSR firmware got into the problematic state..
>  The current firmware level is x72(11.2) and what do you think
>  whether upgrading the firmware might be helpful or not.
>
>  At first, I will follow what Max pointed in below, but if you have additional
>  suggestion based on my information, please let me know.
>
> (1).  Dongle-A reports "stalled ACL link" after a few hours connection
> Jun 25 11:52:52 turtle kernel: hci_acl_tx_to: hci1 ACL tx timeout
> Jun 25 11:52:52 turtle kernel: hci_acl_tx_to: hci1 killing stalled ACL 
> connection
> 5C:D4:1F:96:A0:00
> Jun 25 11:52:52 turtle kernel: l2cap_disconn_ind: hcon c92d48c0 reason 22
> Jun 25 11:52:52 turtle kernel: l2cap_conn_del: hcon c92d48c0 conn c349c760, 
> err 103
> Jun 25 11:52:52 turtle kernel: l2cap_sock_clear_timer: sock c7114700 state 1
> Jun 25 11:52:52 turtle kernel: l2cap_chan_del: sk c7114700, conn c349c760, 
> err 103
> Jun 25 11:52:52 turtle kernel: pan0: port 1(bnep0) entering disabled state
> Jun 25 11:52:52 turtle kernel: pan0: port 1(bnep0) entering disabled state
> Jun 25 11:52:52 turtle kernel: device bnep0 left promiscuous mode
> Jun 25 11:52:52 turtle kernel: l2cap_sock_release: sock c87ba980, sk c7114700
> Jun 25 11:52:52 turtle kernel: l2cap_sock_clear_timer: sock c7114700 state 9
>
> (2) Dongle-A rejected CONN_REQ from other node  (with Role-switch flag)
> Jun 25 12:19:25 turtle kernel: l2cap_connect_ind: hdev hci1, bdaddr 
> 5C:D4:1F:96:A0:00
> Jun 25 12:19:25 turtle kernel: l2cap_connect_cfm: hcon c901bea0 bdaddr 
> 5C:D4:1F:96:A0:00 status
> 0
> Jun 25 12:19:25 turtle kernel: l2cap_conn_add: hcon c901bea0 conn c349c320
> Jun 25 12:19:25 turtle kernel: l2cap_conn_ready: conn c349c320
> Jun 25 12:19:40 turtle kernel: l2cap_disconn_ind: hcon c901bea0 reason 22
> Jun 25 12:19:40 turtle kernel: l2cap_conn_del: hcon c901bea0 conn c349c320, 
> err 103
>
> thanks in advance
> Taka
>
> > At 04:25 AM 6/20/2003, Ferenc-Jan wrote:
> > >I flashed the latest firmware into the dongles, compiled kernel &
> > >bluez mods (2.4.21-rc2, tried 2.5.70 too.)
> > >Works like a charm. However, sooner rather than later, I get a
> > >        "hci0 ACL tx timeout, hci0 killing stalled ACL."
> > >
> > >After this, hciconfig -a ends halfway in a "can't read local name on hci0"
> > >until I unplug and reinsert the dongle.
> > Looks like USB problems to me. For some people it helps to switch from 
> > usb-uhci.o to uhci.o.
> > Try if first.
> >
> > You can also try to decrease number of outstanding bulk TX requests.
> > In the file drivers/bluetooth/hci_usb.h
> > Replace
> >         #define HCI_MAX_BULK_TX         4
> > with
> >         #define HCI_MAX_BULK_TX         1
> > Recompile and reload hci_usb module.
> >
> > Does that help ?
> >
> > Max
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: INetU
> > Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> > _______________________________________________
> > Bluez-users mailing list
> > Bluez-users@xxxxxxxxxxxxxxxxxxxxx
> > https://lists.sourceforge.net/lists/listinfo/bluez-users
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/bluez-users

--
*****************************************
\x97L\x8C\xC0\x89\xEFミ\x81@\x83V\x83\x93\x83N\x83`\x83\x85\x81[\x83u
\x8AC\x91\x94\x81@\x8Ch\x94V tkaiso@xxxxxxxxxxxxx
\x81\xA7658-0032 
\x90_\x8C\xCB\x8Es\x93\x8C\x93\xE5\x8B\xE6\x8C\xFC\x97m\x92\xAC\x92\x86\x82U\x81|\x82X\x81@KFM\x83r\x83\x8B\x81@8S-04
Phone: 078-857-8390
Fax: 078-857-8389
www.thinktube.com




-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php


<Prev in Thread] Current Thread [Next in Thread>