Intel 8265 Bluetooth ([8087:0A2B]) fails to init properly on wakeup from hibernation

[Leonard Lausen]

I am experiencing issues with hibernation on a xiaomi mibook air with the Intel 8265 Bluetooth chip ([8087:0A2B]). When waking up from hibernation, the chip fails to properly initialize (?).

More specifically, when trying to hibernate a second time the notebook will fail to enter hibernation mode due to:
"Freezing of tasks failed after 20.00r seconds (1 tasks refusing to freeze, wq_busy=0)"
where the task failing to freeze is hciconfig.

This seems to be due to a kernel bug initializing the bluetooth device on wakeup from hibernation. The kernel message reads "kernel: Bluetooth: hci0: Setting Intel event mask failed (-16)".

I have attached
1) /proc/version_signature
2) sudo lspci -vnvn
3) journalctrl

I can confirm that the issue with hibernation is resolved by blacklisting the bluetooth chip in
/etc/udev/rules.d/81-bluetooth-hci.rules

I have tried the most recent mainline kernel from the ubuntu kernel ppa and can confirm that the problem also occurs there (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc8/).

Please let me know if I can provide any other information to help fixing this bug.

I am running Maui Linux, which is basically Ubuntu 16.04 but includes more up-to-date KDE packages.
---
ApportVersion: 2.20.1-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: leonard 1336 F.... pulseaudio
CurrentDesktop: KDE
DistroRelease: Maui 2.1
InstallationDate: Installed on 2016-12-02 (5 days ago)
InstallationMedia: Maui - Release amd64 (20160811)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp.
 Bus 001 Device 002: ID 04f2:b5a3 Chicony Electronics Co., Ltd
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Timi TM1613
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic root=/dev/mapper/lvm-btrfs ro rootflags=subvol=@ quiet splash resume=/dev/mapper/lvm-swap vt.handoff=7
ProcVersionSignature: Ubuntu 4.8.0-25.27~16.04.1-generic 4.8.1
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-25-generic N/A
 linux-backports-modules-4.8.0-25-generic N/A
 linux-firmware 1.157.5
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: xenial xenial
Uname: Linux 4.8.0-25-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: False
dmi.bios.date: 08/11/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: A05
dmi.board.asset.tag: No Asset Tag
dmi.board.name: TM1613
dmi.board.vendor: Timi
dmi.board.version: A05
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Timi
dmi.chassis.version: A05
dmi.modalias: dmi:bvnInsydeCorp.:bvrA05:bd08/11/2016:svnTimi:pnTM1613:pvrA05:rvnTimi:rnTM1613:rvrA05:cvnTimi:ct10:cvrA05:
dmi.product.name: TM1613
dmi.product.version: A05
dmi.sys.vendor: Timi

[Brad Figg (brad-figg)]

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

apport-collect 1648526

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.

[Leonard Lausen (leezu)]

apport information

[Leonard Lausen (leezu)]

apport information

[Leonard Lausen (leezu)]

apport information

[Leonard Lausen (leezu)]

apport information

[Leonard Lausen (leezu)]

apport information

[Leonard Lausen (leezu)]

apport information

[Leonard Lausen (leezu)]

apport information

[Leonard Lausen (leezu)]

apport information

[Leonard Lausen (leezu)]

apport information

[Leonard Lausen (leezu)]

apport information

[Leonard Lausen (leezu)]

apport information

[Leonard Lausen (leezu)]

apport information

[Leonard Lausen (leezu)]

apport information

[Leonard Lausen (leezu)]

Please note that I have manually installed the yakkety kernel from the kernel ppa in an attempt to fix the problem. The above logfiles where generated on the yakkety kernel. The problem also occurs with the 16.04 "default" kernel version.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Leonard Lausen (leezu)]

Does the kernel from the ubuntu kernel ppa http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc8/ qualify as latest upstream kernel? As far as I see it still contains ubuntu specific patches. Or shall I first confirm this problem also occurs on the vanilla upstream kernel directly built from the kernel.org?

[Leonard Lausen (leezu)]

I have confirmed that the issue is also present in a self-compiled upstream version of v4.9-rc8 and reported it at http://www.spinics.net/lists/linux-bluetooth/msg69063.html