2018-09-03 07:43:19 |
Bas Zoetekouw |
bug |
|
|
added bug |
2018-09-03 07:43:38 |
Bas Zoetekouw |
attachment added |
|
lsusb-v.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5183918/+files/lsusb-v.log |
|
2018-09-03 07:43:53 |
Bas Zoetekouw |
attachment added |
|
lspci-vnvn.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5183919/+files/lspci-vnvn.log |
|
2018-09-03 07:44:11 |
Bas Zoetekouw |
attachment added |
|
version.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5183920/+files/version.log |
|
2018-09-03 08:00:07 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
2018-09-03 08:36:42 |
Bas Zoetekouw |
tags |
|
apport-collected cosmic |
|
2018-09-03 08:36:43 |
Bas Zoetekouw |
description |
I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b).
Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows:
hci0: Type: Primary Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0
and dmesg tells me (various combinations of):
[237660.728312] Bluetooth: hci0: command tx timeout
[237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout
[237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110)
Trying to reinitialize the device by reloading the driver has no effect:
╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb
shows in dmesg:
[237938.219190] usbcore: deregistering interface driver btusb
[237938.601731] usbcore: registered new interface driver btusb
[237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110)
[237940.626426] Bluetooth: hci0: command tx timeout
Strangely enough, reloading the module sometimes does work, upon which the kernel tells me :
aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb
aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb
aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5
aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled
aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled
aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled
aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled
aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete
aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs
aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot
aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs
aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Looking further back in the kernel log, the difference between failed and successful resumes seems to be this:
Resume with broken bt:
[236481.370814] Restarting tasks ...
[236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110)
Resume with working bt:
[16562.706263] Restarting tasks ...
[16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[16562.716050] Bluetooth: hci0: Device revision is 5
[16562.716052] Bluetooth: hci0: Secure boot is enabled
[16562.716053] Bluetooth: hci0: OTP lock is enabled
[16562.716054] Bluetooth: hci0: API lock is enabled
[16562.716055] Bluetooth: hci0: Debug lock is disabled
[16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[16564.202470] Bluetooth: hci0: Waiting for firmware download to complete
[16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs
[16564.203091] Bluetooth: hci0: Waiting for device to boot
[16564.215021] Bluetooth: hci0: Device booted in 11693 usecs
[16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
[16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed
and everything works fine after that.
The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. |
I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b).
Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows:
hci0: Type: Primary Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0
and dmesg tells me (various combinations of):
[237660.728312] Bluetooth: hci0: command tx timeout
[237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout
[237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110)
Trying to reinitialize the device by reloading the driver has no effect:
╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb
shows in dmesg:
[237938.219190] usbcore: deregistering interface driver btusb
[237938.601731] usbcore: registered new interface driver btusb
[237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110)
[237940.626426] Bluetooth: hci0: command tx timeout
Strangely enough, reloading the module sometimes does work, upon which the kernel tells me :
aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb
aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb
aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5
aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled
aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled
aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled
aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled
aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete
aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs
aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot
aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs
aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Looking further back in the kernel log, the difference between failed and successful resumes seems to be this:
Resume with broken bt:
[236481.370814] Restarting tasks ...
[236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110)
Resume with working bt:
[16562.706263] Restarting tasks ...
[16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[16562.716050] Bluetooth: hci0: Device revision is 5
[16562.716052] Bluetooth: hci0: Secure boot is enabled
[16562.716053] Bluetooth: hci0: OTP lock is enabled
[16562.716054] Bluetooth: hci0: API lock is enabled
[16562.716055] Bluetooth: hci0: Debug lock is disabled
[16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[16564.202470] Bluetooth: hci0: Waiting for firmware download to complete
[16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs
[16564.203091] Bluetooth: hci0: Waiting for device to boot
[16564.215021] Bluetooth: hci0: Device booted in 11693 usecs
[16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
[16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed
and everything works fine after that.
The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/pcmC0D0p: bas 4871 F...m pulseaudio
/dev/snd/controlC0: bas 4871 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.10
HibernationDevice:
RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93
#RESUME=/dev/dm-2
#RESUME=/dev/mapper/regan-swap
InstallationDate: Installed on 2016-12-22 (619 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Dell Inc. Latitude E7470
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.17.0-7-generic root=/dev/mapper/hostname-root ro resume=/dev/mapper/hostname-swap nosplash acpi_backlight=vendor
ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12
RelatedPackageVersions:
linux-restricted-modules-4.17.0-7-generic N/A
linux-backports-modules-4.17.0-7-generic N/A
linux-firmware 1.174
Tags: cosmic
Uname: Linux 4.17.0-7-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to cosmic on 2017-09-18 (349 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev sambashare scanner src sudo tss wireshark
_MarkForUpload: False
dmi.bios.date: 12/11/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.5
dmi.board.name: 0T6HHJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.18.5:bd12/11/2017:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude E7470
dmi.sys.vendor: Dell Inc. |
|
2018-09-03 08:36:44 |
Bas Zoetekouw |
attachment added |
|
AlsaInfo.txt https://bugs.launchpad.net/bugs/1790454/+attachment/5183922/+files/AlsaInfo.txt |
|
2018-09-03 08:36:45 |
Bas Zoetekouw |
attachment added |
|
CRDA.txt https://bugs.launchpad.net/bugs/1790454/+attachment/5183923/+files/CRDA.txt |
|
2018-09-03 08:36:49 |
Bas Zoetekouw |
attachment added |
|
CurrentDmesg.txt https://bugs.launchpad.net/bugs/1790454/+attachment/5183924/+files/CurrentDmesg.txt |
|
2018-09-03 08:36:50 |
Bas Zoetekouw |
attachment added |
|
IwConfig.txt https://bugs.launchpad.net/bugs/1790454/+attachment/5183925/+files/IwConfig.txt |
|
2018-09-03 08:36:51 |
Bas Zoetekouw |
attachment added |
|
Lspci.txt https://bugs.launchpad.net/bugs/1790454/+attachment/5183926/+files/Lspci.txt |
|
2018-09-03 08:36:53 |
Bas Zoetekouw |
attachment added |
|
Lsusb.txt https://bugs.launchpad.net/bugs/1790454/+attachment/5183927/+files/Lsusb.txt |
|
2018-09-03 08:36:54 |
Bas Zoetekouw |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1790454/+attachment/5183928/+files/ProcCpuinfoMinimal.txt |
|
2018-09-03 08:36:55 |
Bas Zoetekouw |
attachment added |
|
ProcEnviron.txt https://bugs.launchpad.net/bugs/1790454/+attachment/5183929/+files/ProcEnviron.txt |
|
2018-09-03 08:36:57 |
Bas Zoetekouw |
attachment added |
|
ProcInterrupts.txt https://bugs.launchpad.net/bugs/1790454/+attachment/5183930/+files/ProcInterrupts.txt |
|
2018-09-03 08:36:58 |
Bas Zoetekouw |
attachment added |
|
ProcModules.txt https://bugs.launchpad.net/bugs/1790454/+attachment/5183931/+files/ProcModules.txt |
|
2018-09-03 08:37:00 |
Bas Zoetekouw |
attachment added |
|
PulseList.txt https://bugs.launchpad.net/bugs/1790454/+attachment/5183932/+files/PulseList.txt |
|
2018-09-03 08:37:02 |
Bas Zoetekouw |
attachment added |
|
RfKill.txt https://bugs.launchpad.net/bugs/1790454/+attachment/5183933/+files/RfKill.txt |
|
2018-09-03 08:37:03 |
Bas Zoetekouw |
attachment added |
|
UdevDb.txt https://bugs.launchpad.net/bugs/1790454/+attachment/5183934/+files/UdevDb.txt |
|
2018-09-03 08:37:06 |
Bas Zoetekouw |
attachment added |
|
WifiSyslog.txt https://bugs.launchpad.net/bugs/1790454/+attachment/5183935/+files/WifiSyslog.txt |
|
2018-09-03 08:38:34 |
Bas Zoetekouw |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
2018-09-05 14:17:21 |
Joseph Salisbury |
linux (Ubuntu): importance |
Undecided |
Medium |
|
2018-09-05 14:17:24 |
Joseph Salisbury |
linux (Ubuntu): status |
Confirmed |
Incomplete |
|
2018-09-28 07:09:16 |
Bas Zoetekouw |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
2018-09-28 07:12:26 |
Bas Zoetekouw |
tags |
apport-collected cosmic |
apport-collected cosmic kernel-bug-exists-upstream |
|
2018-09-28 07:13:45 |
Bas Zoetekouw |
summary |
Bluetooth (btintel) stops working aster suspend/resume |
Bluetooth (btintel) stops working after suspend/resume |
|
2018-10-08 07:03:05 |
Bas Zoetekouw |
attachment added |
|
journal.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5198516/+files/journal.txt |
|
2018-10-08 10:11:56 |
Bas Zoetekouw |
attachment added |
|
dmesg.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5198582/+files/dmesg.log |
|
2018-10-08 12:25:47 |
Bas Zoetekouw |
attachment added |
|
dmesg-4.19rc7.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5198639/+files/dmesg-4.19rc7.log |
|
2018-10-09 06:58:40 |
Bas Zoetekouw |
attachment added |
|
dmesg.4.19.0-041900rc7-generic+usbcore.quirks.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5199005/+files/dmesg.4.19.0-041900rc7-generic+usbcore.quirks.txt |
|
2018-10-12 06:39:12 |
Bas Zoetekouw |
attachment added |
|
dmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5200246/+files/dmesg.txt |
|
2018-10-15 14:56:11 |
Bas Zoetekouw |
attachment added |
|
dmesg-200ms.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5201246/+files/dmesg-200ms.txt |
|
2018-10-18 07:00:21 |
Bas Zoetekouw |
attachment added |
|
dmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5202421/+files/dmesg.txt |
|
2019-01-08 15:24:03 |
Kai-Heng Feng |
attachment added |
|
0001-patch-for-LP-1790454.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5227688/+files/0001-patch-for-LP-1790454.patch |
|
2019-01-08 16:21:16 |
Ubuntu Foundations Team Bug Bot |
tags |
apport-collected cosmic kernel-bug-exists-upstream |
apport-collected cosmic kernel-bug-exists-upstream patch |
|
2019-01-08 16:21:17 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Joseph Salisbury |
2019-04-04 08:50:49 |
Emiliano |
bug |
|
|
added subscriber Emiliano |
2019-04-04 12:25:42 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Terry Rudd |
2019-06-17 07:15:58 |
Kai-Heng Feng |
attachment added |
|
btusb-no-autosuspend.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5271111/+files/btusb-no-autosuspend.patch |
|
2019-07-24 21:15:36 |
Brad Figg |
tags |
apport-collected cosmic kernel-bug-exists-upstream patch |
apport-collected cosmic cscc kernel-bug-exists-upstream patch |
|