bluetooth hci interface "down" on every reboot

Bug #1388969 reported by Benjamin Staffin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

Each time I boot up, bluetooth doesn't work until I run "hciconfig hci0 up". Then it seems fine until the next reboot. This may be related to bug #1244764.

Before I run hciconfig hci0 up:
- rfkill indicates that the bluetooth device is *not* blocked.
    $ rfkill list
    0: phy0: Wireless LAN
            Soft blocked: no
            Hard blocked: no
    1: hci0: Bluetooth
            Soft blocked: no
            Hard blocked: no

- The gnome control center bluetooth module thinks that bluetooth is enabled, but scanning does not work. These messages appear in syslog when I click + to add a device:
    bluetoothd[605]: Discovery session 0x7f5fa71df5e0 with :1.93 activated
    bluetoothd[605]: hci0: Start Discovery (0x0023) failed: Not Powered (0x0f)

Then I run:
    $ sudo hciconfig hci0 up

At that point in syslog:
    bluetoothd[605]: Adapter /org/bluez/605/hci0 has been enabled

Then when I try to scan for bluetooth devices it works, with this in syslog:
    bluetoothd[605]: Discovery session 0x7f5fa71dada0 with :1.94 activated

I can just add an upstart service that runs hciconfig hci0 up at every boot, but that shouldn't be necessary if everything works correctly.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-24-generic 3.16.0-24.32
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ben2 3477 F.... pulseaudio
 /dev/snd/controlC0: ben2 3477 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory: 'iw'
CurrentDesktop: GNOME
Date: Mon Nov 3 12:04:15 2014
HibernationDevice: RESUME=UUID=94069f83-bfa0-43e6-a60c-b2531d0d5096
MachineType: SAMSUNG ELECTRONICS CO., LTD. 940X3G/930X3G
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=5b3be379-c68a-4eeb-92fe-db08e8e7eeda ro
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-24-generic N/A
 linux-backports-modules-3.16.0-24-generic N/A
 linux-firmware 1.138
SourcePackage: linux
UpgradeStatus: Upgraded to utopic on 2014-10-30 (4 days ago)
dmi.bios.date: 04/11/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P04ACJ.125.140411.dg
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP940X3G-K04US
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04ACJ.125.140411.dg:bd04/11/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn940X3G/930X3G:pvrP04ACJ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP940X3G-K04US:rvrSAMSUNG_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 940X3G/930X3G
dmi.product.version: P04ACJ
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Benjamin Staffin (benley) wrote :
description: updated
description: updated
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Benjamin Staffin, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.18-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
importance: Undecided → Low
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

Remote bug watches

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