I would like to see a stack trace of the busy bluetoothd process, which
means killing it in a way that it will dump core and create a crash
report. But that won't work right now because of bug 1870060.

Intead, please attach 'gdb' (run it as root) to the busy bluetoothd
process and then run 'bt' in gdb to get a backtrace.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1871695

Title:
  Bluetoothd uses 100% of a CPU thread

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I have a bluetooth keyboard that I use for my laptop, which runs
  Kubuntu 19.04. I noticed though, that a short while after connecting
  the keyboard, the CPU fan goes on and one of the threads is at 100%.
  If I open a terminal and type "top", it shows that a process called
  bluetoothd is taking 12% of the CPU power which is a full thread
  (100/8=12.5). I'm not sure what it's doing, but it doesn't require
  that much CPU power to work. If I end the process and restart it, the
  keyboard works fine and the CPU is calm until it happens again (about
  20 minutes later). I reinstalled bluez and even tried recompiling from
  source, but the problem persists.

  My specs:

  Version of bluetoothd: 5.50
  Linux Kernel: 5.3.0-46-generic
  KDE Plasma Version 5.16.5


  Thank you,
  Isaac Cohen
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-12-15 (115 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:5301 HTMicroelectronics Goodix Fingerprint 
Device 
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3583
  Package: bluez 5.50-0ubuntu5.1 [modified: 
lib/systemd/system/bluetooth.service lib/udev/hid2hci 
lib/udev/rules.d/97-hid2hci.rules]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=dad855bd-aa2f-4675-a8a6-6fa960525f41 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0WHCP7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd05/30/2019:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0WHCP7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:        Type: Primary  Bus: USB
        BD Address: AC:D5:64:CC:54:D6  ACL MTU: 1024:8  SCO MTU: 50:8
        UP RUNNING PSCAN ISCAN 
        RX bytes:47194 acl:2390 sco:0 events:266 errors:0
        TX bytes:3046 acl:50 sco:0 commands:163 errors:0
  mtime.conffile..etc.dbus-1.system.d.bluetooth.conf: 2020-04-07T16:35:14.446062

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871695/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to