FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 07-15-2010, 11:45 PM
Mark Hobley
 
Default Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

Moritz Muehlenhoff wrote:
> The next release of Debian (6.0, code name Squeeze) will be based
> on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell
> us whether the problem persists.

Hello Moritz. I am testing with kernel 2.6.32-5-486

I am getting the timeout here, so I reckon this is still broken in Squeeze.

# hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1
UP RUNNING
RX bytes:330 acl:0 sco:0 events:8 errors:0
TX bytes:24 acl:0 sco:0 commands:16 errors:8
Features: 0xff 0x3e 0x09 0x76 0x80 0x01 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT
Can't read local name on hci0: Connection timed out (110)

# dmesg
[127422.591465] hci_cmd_task: hci0 command tx timeout

# lsusb
Bus 003 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

I tried updating to bluez-4.69, which I downloaded from an upstream source and compiled myself, but the problem still persists.

Mark.









--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 638868.87901.qm@web26504.mail.ukl.yahoo.com">http://lists.debian.org/638868.87901.qm@web26504.mail.ukl.yahoo.com
 
Old 09-29-2010, 09:49 PM
Mark Hobley
 
Default Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

I have just tested this with the experimental kernel version 2.6.36-rc5-486.
I am still getting the timeout error:

hciconfig -a hci0
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1
UP RUNNING
RX bytes:59 acl:0 sco:0 events:5 errors:0
TX bytes:15 acl:0 sco:0 commands:7 errors:2
Features: 0xff 0x3e 0x09 0x76 0x80 0x01 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT
Can't read local name on hci0: Connection timed out (110)






--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 995094.29733.qm@web26507.mail.ukl.yahoo.com">http://lists.debian.org/995094.29733.qm@web26507.mail.ukl.yahoo.com
 
Old 12-11-2010, 08:17 PM
Mark Hobley
 
Default Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

I have retested this again. This time with experimental kernel version 2.6.37-rc5 (Debian 2.6.37~rc5-1~experimental.1).

The timeout error is still occuring, so the latest attempts at fixing this have not worked. THE KERNEL IS STILL BROKEN:

hciconfig -a

hci0: Type: BR/EDR Bus: USB
BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1
UP RUNNING
RX bytes:413 acl:0 sco:0 events:18 errors:0
TX bytes:67 acl:0 sco:0 commands:21 errors:4
Features: 0xff 0x3e 0x09 0x76 0x80 0x01 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Can't read local name on hci0: Connection timed out (110)







--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 548440.6431.qm@web26503.mail.ukl.yahoo.com">http://lists.debian.org/548440.6431.qm@web26503.mail.ukl.yahoo.com
 
Old 12-11-2010, 08:33 PM
Ben Hutchings
 
Default Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

On Sat, 2010-12-11 at 21:17 +0000, Mark Hobley wrote:
> I have retested this again. This time with experimental kernel version
> 2.6.37-rc5 (Debian 2.6.37~rc5-1~experimental.1).
>
> The timeout error is still occuring, so the latest attempts at fixing
> this have not worked. THE KERNEL IS STILL BROKEN:

Please report this bug upstream at <https://bugzilla.kernel.org> under
product 'Drivers', component 'Bluetooth'. Let us know the bug number or
URL so we can track it.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
 
Old 02-26-2011, 08:13 PM
Mark Hobley
 
Default Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

I have just tested this again with kernel version 2.6.38-rc6-486.

This time, no timeout occurs with hciconfig:

hciconfig -a hci0

hci0: Type: BR/EDR Bus: USB
BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1
DOWN
RX bytes:342 acl:0 sco:0 events:10 errors:0
TX bytes:33 acl:0 sco:0 commands:11 errors:1
Features: 0xff 0x3e 0x09 0x76 0x80 0x01 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT

However, the device does not appear in the hcitool list at this time:

hcitool dev
Devices:

(There is nothing here)

I am still investigating this issue.

Mark.









--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 119223.54072.qm@web26501.mail.ukl.yahoo.com">http://lists.debian.org/119223.54072.qm@web26501.mail.ukl.yahoo.com
 
Old 02-26-2011, 10:22 PM
Mark Hobley
 
Default Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

Ahhhh! When I try to bring the device into operational mode, the timeout error occurs, so I guess this is still not fixed in 2.6.38-rc6-486:

hciconfig hci0 up
Can't init device hci0: Connection timed out (110)

Mark.






--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 653221.13235.qm@web26507.mail.ukl.yahoo.com">http://lists.debian.org/653221.13235.qm@web26507.mail.ukl.yahoo.com
 
Old 05-02-2011, 02:41 PM
Mark Hobley
 
Default Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

I have just tested this again with experimental kernel 2.6.39-rc4-486 (Debian 2.6.39~rc4-1~experimental.1). The problem is still occuring with that kernel build:

# hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1
DOWN
RX bytes:68 acl:0 sco:0 events:6 errors:0
TX bytes:18 acl:0 sco:0 commands:36 errors:30
Features: 0xff 0x3e 0x09 0x76 0x80 0x01 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT

# hciconfig hci0 up
Can't init device hci0: Connection timed out (110)

Mark.




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 323722.1514.qm@web26508.mail.ukl.yahoo.com">http://lists.debian.org/323722.1514.qm@web26508.mail.ukl.yahoo.com
 
Old 05-28-2011, 03:45 PM
Mark Hobley
 
Default Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

I upgraded the kernel to 2.6.39-1 from experimental and rebooted the system. Initially, After typing hcitool inq, the system showed that my mobile phone was present, so it appeared as though bluetooth was at least momentarily partially working. However, from the mobile phone, the computer was not listed, as if the computer was somehow hidden.

I upgraded bluez to version 4.93-1 from Debian experimental, in the hope that this might fix the visibility problem.

However, bluetooth now appears to be broken again. Following a reboot of the computer:

hciconfig -a

hci0: Type: BR/EDR Bus: USB
BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1
DOWN
RX bytes:59 acl:0 sco:0 events:5 errors:0
TX bytes:15 acl:0 sco:0 commands:36 errors:31
Features: 0xff 0x3e 0x09 0x76 0x80 0x01 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT

I now try to bring the interface into operational mode, and the timeout
error reoccurs:

hciconfig hci0 up
Can't init device hci0: Connection timed out (110)

dmesg shows squillions of errors as follows:

[nnnn.nnnnnn] hci_cmd_timer: hci0 command tx timeout

So it appears that there might also be bugs in bluez which are aggrevating this problem. BLUETOOTH IS NOT OPERATIONAL.

Mark.






--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 17011.91974.qm@web26507.mail.ukl.yahoo.com">http://lists.debian.org/17011.91974.qm@web26507.mail.ukl.yahoo.com
 
Old 06-21-2011, 06:53 PM
Mark Hobley
 
Default Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

I attached a system trace against #628454, so hopefully, someone can interpret this and tell us what is going wrong.





--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1308682410.4644.YahooMailClassic@web26502.mail.ukl .yahoo.com">http://lists.debian.org/1308682410.4644.YahooMailClassic@web26502.mail.ukl .yahoo.com
 
Old 06-22-2011, 10:13 PM
Mark Hobley
 
Default Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

A strange thing has just happened. I plugged the dongle in to get some information from it, and when I ran hciconfig, it showed as "up running":

hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1
UP RUNNING PSCAN
RX bytes:754 acl:0 sco:0 events:26 errors:0
TX bytes:368 acl:0 sco:0 commands:25 errors:0
Features: 0xff 0x3e 0x09 0x76 0x80 0x01 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF
Link mode: SLAVE ACCEPT
Name: 'Accel-OB2'
Class: 0x4a0100
Service Classes: Networking, Capturing, Telephony
Device Class: Computer, Uncategorized
HCI Version: 2.0 (0x3) Revision: 0x44
LMP Version: 2.0 (0x3) Subversion: 0x3
Manufacturer: Cambridge Silicon Radio (10)

I don't know why that has happened. I normally just get a timeout error, so it looks like this problem is not always consistent. I have not updated my system, since I last reported HCI Timeout.

My mobile phone is now temporarily visible to my computer, but I cannot see the computer from the mobile phone, so I am unable to initiate a transfer from the mobile phone. I don't know how to take the device out of invisibility mode, and when I try, it will probably revert back to giving HCI timeout, but hey ... this is the first time I have seen this half working since I upgraded bluez.

Mark.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1308780800.31280.YahooMailClassic@web26508.mail.uk l.yahoo.com">http://lists.debian.org/1308780800.31280.YahooMailClassic@web26508.mail.uk l.yahoo.com
 

Thread Tools




All times are GMT. The time now is 02:15 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org