hci_cmd_timer: hci0 command tx timeout

Bug #785783 reported by Tim Kornhammar
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I get several of the above errors during the boot process. It also seems like it is waiting for the hci0 during boot which is not a wanted feature.

$ lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

I know this is the 2.6.39 kernel but it is the same error on 2.6.38..
$ apt-cache policy linux-image-2.6.39-2-generic
linux-image-2.6.39-2-generic:
  Installerad: 2.6.39-2.7
  Kandidat: 2.6.39-2.7
  Versionstabell:
 *** 2.6.39-2.7 0
        500 http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu/ natty/main amd64 Packages
        100 /var/lib/dpkg/status
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: tim 1852 F.... pulseaudio
CRDA: Error: [Errno 2] Filen eller katalogen finns inte
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd9c00000 irq 49'
   Mixer name : 'Realtek ALC269VB'
   Components : 'HDA:10ec0269,104310b3,00100100'
   Controls : 19
   Simple ctrls : 11
DistroRelease: Ubuntu 11.10
HibernationDevice: RESUME=UUID=7f8129c5-1358-4d5a-bcb9-5024d51a6091
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: ASUSTeK Computer Inc. U36JC
Package: linux (not installed)
ProcEnviron:
 PATH=(custom, no user)
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-11-generic root=UUID=92b888c9-ab45-4083-a283-71d6bf693513 ro quiet splash enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=8M mtrr_chunk_size=32M vt.handoff=7
ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-11-generic N/A
 linux-backports-modules-3.0.0-11-generic N/A
 linux-firmware 1.60
StagingDrivers: mei
Tags: oneiric running-unity staging
Uname: Linux 3.0.0-11-generic x86_64
UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 02/25/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U36JC.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: U36JC
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU36JC.206:bd02/25/2011:svnASUSTeKComputerInc.:pnU36JC:pvr1.0:rvnASUSTeKComputerInc.:rnU36JC:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: U36JC
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote :
Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 785783

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: natty
Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : AcpiTables.txt

apport information

tags: added: apport-collected oneiric running-unity staging
description: updated
Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : AlsaDevices.txt

apport information

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : AplayDevices.txt

apport information

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : BootDmesg.txt

apport information

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : IwConfig.txt

apport information

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : Lspci.txt

apport information

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : Lsusb.txt

apport information

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : PciMultimedia.txt

apport information

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : ProcModules.txt

apport information

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : PulseSinks.txt

apport information

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : PulseSources.txt

apport information

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : RfKill.txt

apport information

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : UdevDb.txt

apport information

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : UdevLog.txt

apport information

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote : WifiSyslog.txt

apport information

Revision history for this message
Corbin (corbin) wrote :

I also have this problem. Me messages are always flooded with these. Here is the most recent output of dmesg:

[ 18.480023] hci_cmd_timer: hci0 command tx timeout
[ 19.480019] hci_cmd_timer: hci0 command tx timeout
[ 20.480021] hci_cmd_timer: hci0 command tx timeout
[ 21.480022] hci_cmd_timer: hci0 command tx timeout
[ 21.524686] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,commit=0
[ 21.630810] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0
[ 22.216733] init: plymouth-stop pre-start process (1490) terminated with status 1
[ 22.480034] hci_cmd_timer: hci0 command tx timeout
[ 23.480011] hci_cmd_timer: hci0 command tx timeout
[ 24.480021] hci_cmd_timer: hci0 command tx timeout
[ 25.480024] hci_cmd_timer: hci0 command tx timeout
[ 26.480022] hci_cmd_timer: hci0 command tx timeout
[ 27.480022] hci_cmd_timer: hci0 command tx timeout
[ 28.480022] hci_cmd_timer: hci0 command tx timeout
[ 29.056024] eth0: no IPv6 routers present
[ 29.480019] hci_cmd_timer: hci0 command tx timeout
[ 30.480064] hci_cmd_timer: hci0 command tx timeout
[ 31.480019] hci_cmd_timer: hci0 command tx timeout
[ 32.480023] hci_cmd_timer: hci0 command tx timeout
[ 33.480009] hci_cmd_timer: hci0 command tx timeout
[ 34.480009] hci_cmd_timer: hci0 command tx timeout
[ 35.480022] hci_cmd_timer: hci0 command tx timeout

Bálint Magyar (balintm)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
ozod (ozodyusupov) wrote :

I also have this problem. Me messages are always flooded with these. Here is the most recent output of dmesg:
[ 22.480034] hci_cmd_timer: hci0 command tx timeout
[ 23.480011] hci_cmd_timer: hci0 command tx timeout
[ 24.480021] hci_cmd_timer: hci0 command tx timeout
[ 25.480024] hci_cmd_timer: hci0 command tx timeout
[ 26.480022] hci_cmd_timer: hci0 command tx timeout
[ 27.480022] hci_cmd_timer: hci0 command tx timeout
[ 28.480022] hci_cmd_timer: hci0 command tx timeout
[ 29.056024] eth0: no IPv6 routers present
[ 29.480019] hci_cmd_timer: hci0 command tx timeout
[ 30.480064] hci_cmd_timer: hci0 command tx timeout
[ 31.480019] hci_cmd_timer: hci0 command tx timeout
[ 32.480023] hci_cmd_timer: hci0 command tx timeout
[ 33.480009] hci_cmd_timer: hci0 command tx timeout
[ 34.480009] hci_cmd_timer: hci0 command tx timeout
[ 35.480022] hci_cmd_timer: hci0 command tx timeout

Revision history for this message
penalvch (penalvch) wrote :

Tim Kornhammar, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.