[Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, VIA USB HUBS

[Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, VIA USB HUBS

[thomas.schorpp]

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?

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

[Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, stalling next accept

[thomas.schorpp]

thomas.schorpp wrote:
> 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?
> 
> 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
> 


pand/main.c/154/nsk = accept(sk, (struct sockaddr *) &l2a, &alen);

synchronous execution stalls next connect... adding a time out and recovery?

wheres the this "accept"() , cant find it in any bt header, need source 
browser for linux ;)

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

Re: [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, stalling next accept

[thomas.schorpp]

thomas.schorpp wrote:
> thomas.schorpp wrote:
> 
>> 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?
>>
>> 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
>>
> 
> 
> pand/main.c/154/nsk = accept(sk, (struct sockaddr *) &l2a, &alen);
> 
> synchronous execution stalls next connect... adding a time out and 
> recovery?
> 
> wheres the this "accept"() , cant find it in any bt header, need source 
> browser for linux ;)
> 
> 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
> 
> 

aah found it..
  /* Await a connection on socket FD.
     When a connection arrives, open a new socket to communicate with it,
     set *ADDR (which is *ADDR_LEN bytes long) to the address of the 
connecting
     peer and *ADDR_LEN to the address's actual length, and return the
     new socket's descriptor, or -1 for errors.  */
  extern int accept (int __fd, __SOCKADDR_ARG __addr,
  		   socklen_t *__restrict __addr_len)
       __THROW;

is invoked regardless driver state?

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

Re: [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, VIA USB HUBS

[Marcel Holtmann]

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

Re: [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, VIA USB HUBS

[thomas.schorpp]

Marcel Holtmann wrote:
> 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
> 
> 

hi marcel, thx for your fast acknowledge, heres some extended 
information, i could provide a hcidump -tsw in afew hours too:

root@TOM1:~# hcid
root@TOM1:~# hciconfig -a
hci0:   Type: USB
         BD Address: 00:10:60:A5:0F:EA ACL MTU: 192:8  SCO MTU: 64:8
         UP RUNNING PSCAN ISCAN
         RX bytes:99 acl:0 sco:0 events:13 errors:0
         TX bytes:296 acl:0 sco:0 commands:12 errors:0
         Features: 0xff 0xff 0x0f 0x00
         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
         Link policy: HOLD SNIFF PARK
         Link mode: ACCEPT MASTER
         Name: 'TOM1'
         Class: 0x000100
         Service Classes: Unspecified
         Device Class: Computer, Uncategorized
         HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP 
Subver: 0x20d
         Manufacturer: Cambridge Silicon Radio (10)

root@TOM1:~# uname -r
2.4.23
root@TOM1:~#
root@TOM1:~# lspci -v
00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333]
         Flags: bus master, medium devsel, latency 0
         Memory at e0000000 (32-bit, prefetchable) [size=64M]
         Capabilities: [a0] AGP version 2.0
         Capabilities: [c0] Power Management version 2

00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo 
KT266/A/333 AGP] (prog-if 00 [Normal decode])
         Flags: bus master, 66Mhz, medium devsel, latency 0
         Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
         I/O behind bridge: 0000c000-0000cfff
         Memory behind bridge: ec000000-edffffff
         Prefetchable memory behind bridge: e4000000-ebffffff
         Capabilities: [80] Power Management version 2

00:09.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
         Subsystem: Technotrend Systemtechnik GmbH: Unknown device 0000
         Flags: bus master, medium devsel, latency 32, IRQ 7
         Memory at ee000000 (32-bit, non-prefetchable) [size=512]

00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL-8139/8139C/8139C+ (rev 10)
         Subsystem: Realtek Semiconductor Co., Ltd. RT8139
         Flags: bus master, medium devsel, latency 32, IRQ 10
         I/O ports at d000 [size=256]
         Memory at ee001000 (32-bit, non-prefetchable) [size=256]
         Capabilities: [50] Power Management version 2

00:0b.0 Multimedia video controller: Brooktree Corporation Bt878 Video 
Capture (rev 02)
         Subsystem: Hauppauge computer works Inc. WinTV Series
         Flags: bus master, medium devsel, latency 32, IRQ 5
         Memory at ee002000 (32-bit, prefetchable) [size=4K]

00:0b.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture 
(rev 02)
         Subsystem: Hauppauge computer works Inc. WinTV Series
         Flags: bus master, medium devsel, latency 32, IRQ 5
         Memory at ee003000 (32-bit, prefetchable) [size=4K]

00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge
         Subsystem: VIA Technologies, Inc. VT8233 PCI to ISA Bridge
         Flags: bus master, stepping, medium devsel, latency 0
         Capabilities: [c0] Power Management version 2

00:11.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus 
Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
         Subsystem: VIA Technologies, Inc. VT8235 Bus Master 
ATA133/100/66/33 IDE
         Flags: bus master, medium devsel, latency 32, IRQ 11
         I/O ports at d400 [size=16]
         Capabilities: [c0] Power Management version 2

00:11.2 USB Controller: VIA Technologies, Inc. USB (rev 1b) (prog-if 00 
[UHCI])
         Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
         Flags: bus master, medium devsel, latency 32, IRQ 5
         I/O ports at d800 [size=32]
         Capabilities: [80] Power Management version 2

00:11.3 USB Controller: VIA Technologies, Inc. USB (rev 1b) (prog-if 00 
[UHCI])
         Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
         Flags: bus master, medium devsel, latency 32, IRQ 5
         I/O ports at dc00 [size=32]
         Capabilities: [80] Power Management version 2

00:11.4 USB Controller: VIA Technologies, Inc. USB (rev 1b) (prog-if 00 
[UHCI])
         Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
         Flags: bus master, medium devsel, latency 32, IRQ 5
         I/O ports at e000 [size=32]
         Capabilities: [80] Power Management version 2

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233 AC97 
Audio Controller (rev 30)
         Subsystem: Unknown device 1695:3004
         Flags: medium devsel, IRQ 10
         I/O ports at e400 [size=256]
         Capabilities: [c0] Power Management version 2

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 If 
[Radeon 9000] (rev 01) (prog-if 00 [VGA])
         Subsystem: Unknown device 17c0:000f
         Flags: bus master, stepping, 66Mhz, medium devsel, latency 32, 
IRQ 11
         Memory at e4000000 (32-bit, prefetchable) [size=64M]
         I/O ports at c000 [size=256]
         Memory at ed000000 (32-bit, non-prefetchable) [size=64K]
         Expansion ROM at <unassigned> [disabled] [size=128K]
         Capabilities: [58] AGP version 2.0
         Capabilities: [50] Power Management version 2

01:00.1 Display controller: ATI Technologies Inc Radeon R250 [Radeon 
9000] (Secondary) (rev 01)
         Subsystem: Unknown device 17c0:000e
         Flags: bus master, stepping, 66Mhz, medium devsel, latency 32
         Memory at e8000000 (32-bit, prefetchable) [disabled] [size=64M]
         Memory at ed010000 (32-bit, non-prefetchable) [disabled] [size=64K]
         Capabilities: [50] Power Management version 2

root@TOM1:~#


y
tom

P.S. what linux devenv and kernel debugging env do you use? i wasted 
years with visual c++ ;)

Re: [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, VIA USB HUBS

[Marcel Holtmann]

Hi Thomas,

> hi marcel, thx for your fast acknowledge, heres some extended 
> information, i could provide a hcidump -tsw in afew hours too:

the hcidump won't help here, because I am pretty sure that this is a
problem on the USB bus.

> root@TOM1:~# hciconfig -a
> hci0:   Type: USB
>          BD Address: 00:10:60:A5:0F:EA ACL MTU: 192:8  SCO MTU: 64:8
>          UP RUNNING PSCAN ISCAN
>          RX bytes:99 acl:0 sco:0 events:13 errors:0
>          TX bytes:296 acl:0 sco:0 commands:12 errors:0
>          Features: 0xff 0xff 0x0f 0x00
>          Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>          Link policy: HOLD SNIFF PARK
>          Link mode: ACCEPT MASTER
>          Name: 'TOM1'
>          Class: 0x000100
>          Service Classes: Unspecified
>          Device Class: Computer, Uncategorized
>          HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP 
> Subver: 0x20d
>          Manufacturer: Cambridge Silicon Radio (10)

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.

> root@TOM1:~# uname -r
> 2.4.23

Use 2.4.23-mh1 or 2.4.24-mh1.

> P.S. what linux devenv and kernel debugging env do you use? i wasted 
> years with visual c++ ;)

I use anjuta and vi as editor and for debugging it is simply printk ;)

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

Re: [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, VIA USB HUBS

[thomas.schorpp]

thx marcel,

Marcel Holtmann wrote:
> Hi Thomas,
> 
> 
>>hi marcel, thx for your fast acknowledge, heres some extended 
>>information, i could provide a hcidump -tsw in afew hours too:
> 
> 
> the hcidump won't help here, because I am pretty sure that this is a
> problem on the USB bus.

agree, will go to their mailing list later...

> 
> 
>>root@TOM1:~# hciconfig -a
>>hci0:   Type: USB
>>         BD Address: 00:10:60:A5:0F:EA ACL MTU: 192:8  SCO MTU: 64:8
>>         UP RUNNING PSCAN ISCAN
>>         RX bytes:99 acl:0 sco:0 events:13 errors:0
>>         TX bytes:296 acl:0 sco:0 commands:12 errors:0
>>         Features: 0xff 0xff 0x0f 0x00
>>         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>>         Link policy: HOLD SNIFF PARK
>>         Link mode: ACCEPT MASTER
>>         Name: 'TOM1'
>>         Class: 0x000100
>>         Service Classes: Unspecified
>>         Device Class: Computer, Uncategorized
>>         HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP 
>>Subver: 0x20d
>>         Manufacturer: Cambridge Silicon Radio (10)
> 
> 
> 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(?)

schorpp@TOM1:~$ lsmod
Module                  Size  Used by    Not tainted
bnep                    9716   1 (autoclean)
l2cap                  15884   2 (autoclean) [bnep]
sr_mod                 14936   0 (autoclean)
snd-mixer-oss          12080   3 (autoclean)
joydev                  5888   0 (unused)
keybdev                 1952   0 (unused)
mousedev                4244   0 (unused)
scanner                10936   0
hid                    21156   0 (unused)
printer                 7040   0
w9968cf-vpp            12864   6 (autoclean)
w9968cf                60568   0
hci_usb                 7832   1
bluez                  30436   2 [bnep l2cap hci_usb]
dvb-ttpci             304596   5
alps_bsrv2              3992   1
input                   3200   0 [joydev keybdev mousedev hid dvb-ttpci]
dvb-core               41220  16 [dvb-ttpci alps_bsrv2]
8139too                13384   1
mii                     2304   0 [8139too]
crc32                   2880   0 [bnep 8139too]
tuner                  10240   1 (autoclean)
tvaudio                13628   0 (autoclean) (unused)
msp3400                16396   1 (autoclean)
bttv                   94688   0
i2c-algo-bit            6984   1 [bttv]
videodev                5984   6 [w9968cf dvb-ttpci bttv]
snd-bt87x               5036   1
uhci                   24528   0 (unused)
usbcore                58752   1 [scanner hid printer w9968cf hci_usb uhci]
snd-via82xx            12032   3
snd-pcm                56288   0 [snd-bt87x snd-via82xx]
snd-timer              13412   0 [snd-pcm]
snd-ac97-codec         43436   0 [snd-via82xx]
snd-page-alloc          6004   0 [snd-bt87x snd-via82xx snd-pcm]
snd-mpu401-uart         3136   0 [snd-via82xx]
snd-rawmidi            12640   0 [snd-mpu401-uart]
snd-seq-device          3904   0 [snd-rawmidi]
snd                    29924   1 [snd-mixer-oss snd-bt87x snd-via82xx 
snd-pcm snd-timer snd-ac97-codec snd-mpu401-uart snd-rawmidi snd-seq-device]
soundcore               3332   2 [bttv snd]
ovcamchip              16872   1
i2c-core               12740   0 [w9968cf tuner tvaudio msp3400 bttv 
i2c-algo-bit ovcamchip]
ide-scsi                9424   0
schorpp@TOM1:~$

> 
> 
>>root@TOM1:~# uname -r
>>2.4.23
> 
> 
> Use 2.4.23-mh1 or 2.4.24-mh1.

roger that. what change do you think in the changelogs should target the 
problem?

> 
> 
>>P.S. what linux devenv and kernel debugging env do you use? i wasted 
>>years with visual c++ ;)
> 
> 
> I use anjuta and vi as editor and for debugging it is simply printk ;)
> 
> 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
> 
> 

thx
y
tom

Re: [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, VIA USB HUBS

[Marcel Holtmann]

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.

> > 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.

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

Re: [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, VIA USB HUBS

[thomas.schorpp]

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.

> 
> 
>>>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

Re: [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, sco not the problem

[thomas.schorpp]

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
> 
> 

Re: [Bluez-devel] hci_acl_tx_to: hci0 ACL tx timeout, solved, kmod loaded wrong ALTERNATE uhci driver by default

[thomas.schorpp]

hi,

thomas.schorpp wrote:
> 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...

SOLVED! compile only the usb-uhci (via...) driver, ok with at least :


00:11.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus 
Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
         Subsystem: VIA Technologies, Inc. VT8235 Bus Master 
ATA133/100/66/33 IDE
         Flags: bus master, medium devsel, latency 32, IRQ 11
         I/O ports at d400 [size=16]
         Capabilities: [c0] Power Management version 2

00:11.2 USB Controller: VIA Technologies, Inc. USB (rev 1b) (prog-if 00 
[UHCI])
         Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
         Flags: bus master, medium devsel, latency 32, IRQ 5
         I/O ports at d800 [size=32]
         Capabilities: [80] Power Management version 2

00:11.3 USB Controller: VIA Technologies, Inc. USB (rev 1b) (prog-if 00 
[UHCI])
         Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
         Flags: bus master, medium devsel, latency 32, IRQ 5
         I/O ports at dc00 [size=32]
         Capabilities: [80] Power Management version 2

00:11.4 USB Controller: VIA Technologies, Inc. USB (rev 1b) (prog-if 00 
[UHCI])
         Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
         Flags: bus master, medium devsel, latency 32, IRQ 5
         I/O ports at e000 [size=32]
         Capabilities: [80] Power Management version 2

thx a lot,
sorry for bothering you ;)

now testing the vt6202 on the gateway, should work, via says, its 
downwardscompatible to usb 1.1 drivers, well see.

> 
> 
>>
>>>
>>>
>>>>> 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
>>
>>
> 
> 
> 
> 
> -------------------------------------------------------
> 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