Your message dated Sat, 17 Feb 2018 19:43:49 +0100
with message-id <[email protected]>
and subject line Re: Bug#888577: [tlp] tlp makes bluetooth disfunctional
has caused the Debian Bug report #888577,
regarding [tlp] tlp makes bluetooth disfunctional
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
888577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888577
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tlp
Version: 1.0-1~bpo9+1
Severity: important

After install TLP i can not use bluetooth anymore (when trying to activate it from the kde system tray). The interesting thing is, if I install TLP, when bluetooth is activated and shutdown the computer, it seems to save the state of bluetooth on startup and activates it, and it works perfectly, even disabling/enabling the adapter. The problem only seems to appear, if the adapter isn't activated by TLP on boot.

syslog tells me:

Jan 27 12:30:56 RMMbook kernel: [ 41.988563] Bluetooth: hci0 urb ffff971614031600 failed to resubmit (113)
Jan 27 12:31:04 RMMbook bluetoothd[709]: Failed to set mode: Failed (0x03)
Jan 27 12:31:06 RMMbook kernel: [ 51.792216] Bluetooth: hci0 urb ffff9716797e53c0 failed to resubmit (113)
Jan 27 12:31:14 RMMbook bluetoothd[709]: Failed to set mode: Failed (0x03)
Jan 27 12:31:16 RMMbook kernel: [ 62.028298] Bluetooth: hci0 urb ffff97163e790900 failed to resubmit (113)
Jan 27 12:31:24 RMMbook bluetoothd[709]: Failed to set mode: Failed (0x03)

The same error exists indepentendly of if t he package tlp-rdw is installed or not.

kernel version is:
4.14.0-2-amd64

laptop model is:
dell xps 13 9360, intel 8th gen

hwinfo about bluetooth tells:

  [Created at usb.122]
  Unique ID: 2UT6.UCUpDou4XhB
  Parent ID: k4bc.2DFUsyrieMD
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0
  SysFS BusID: 1-3:1.0
  Hardware Class: bluetooth
  Model: "Qualcomm Atheros Bluetooth Device"
  Hotplug: USB
  Vendor: usb 0x0cf3 "Qualcomm Atheros Communications"
  Device: usb 0xe300
  Revision: "0.01"
  Driver: "btusb"
  Driver Modules: "btusb"
  Speed: 12 Mbps
  Module Alias: "usb:v0CF3pE300d0001dcE0dsc01dp01icE0isc01ip01in00"
  Driver Info #0:
    Driver Status: btusb is active
    Driver Activation Cmd: "modprobe btusb"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #43 (Hub)

I can't find any setting in /etc/default/tlp to deactivate bluetooth support...


--- System information. ---
Architecture: Kernel:       Linux 4.14.0-2-amd64

Debian Release: 9.3
900 stretch packagecloud.io 900 stable security.debian.org 900 stable ftp.ch.debian.org 800 stretch-backports ftp.ch.debian.org 700 testing ftp.ch.debian.org 600 unstable ftp.ch.debian.org 500 zesty ppa.launchpad.net 500 stable-updates ftp.ch.debian.org 500 stable repo.skype.com
--- Package information. ---
Depends                  (Version) | Installed
==================================-+-===========
init-system-helpers     (>= 1.18~) | 1.48
lsb-base                           | 9.20161125
hdparm                             | 9.51+ds-1
iw                                 | 4.9-0.1
 OR wireless-tools                 | 30~pre9-12+b1
pciutils                           | 1:3.5.2-1
rfkill                             | 0.5-1+b1
usbutils                           | 1:007-4+b1


Recommends          (Version) | Installed
=============================-+-===========
tlp-rdw                       | ethtool                       | 1:4.8-1+b1
smartmontools                 | 6.5+svn4324-1
linux-cpupower                |

Suggests            (Version) | Installed
=============================-+-===========
tp-smapi-dkms                 | acpi-call-dkms                |

--- End Message ---
--- Begin Message ---
As Thomas mentioned, this is actually a known problem mentioned in the
FAQ (please read the link he provided), and not a bug.

Regards,

-- 
Raphaƫl Halimi

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to