kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #02491
[Bug 1197616] Re: Bluetooth sometimes does not work after resuming from suspend
I've tried to test again and it seems there are some problem with read error.
u@u-Inspiron-3137:~$ dmesg | grep error
[ 6.571775] usb 2-7: device descriptor read/8, error -110
[ 11.690873] usb 2-7: device descriptor read/8, error -110
[ 12.512528] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro
[ 16.922015] usb 2-7: device descriptor read/8, error -110
[ 22.041155] usb 2-7: device descriptor read/8, error -110
[ 27.272312] usb 2-7: device descriptor read/8, error -110
[ 32.391447] usb 2-7: device descriptor read/8, error -110
[ 37.622581] usb 2-7: device descriptor read/8, error -110
[ 42.741775] usb 2-7: device descriptor read/8, error -110
Bluetooth message shows no fw loading error.
u@u-Inspiron-3137:~$ dmesg | grep Blue
[ 13.192066] Bluetooth: Core ver 2.16
[ 13.192094] Bluetooth: HCI device and connection manager initialized
[ 13.192096] Bluetooth: HCI socket layer initialized
[ 13.192098] Bluetooth: L2CAP socket layer initialized
[ 13.192108] Bluetooth: SCO socket layer initialized
[ 13.229912] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 13.229916] Bluetooth: BNEP filters: protocol multicast
[ 13.241922] Bluetooth: RFCOMM TTY layer initialized
[ 13.241928] Bluetooth: RFCOMM socket layer initialized
[ 13.241930] Bluetooth: RFCOMM ver 1.11
lsusb can't see the broadcom bluetooth device.
u@u-Inspiron-3137:~$ lsusb
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 002: ID 0c45:6a00 Microdia
Bus 002 Device 007: ID 04f3:016c Elan Microelectronics Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1197616
Title:
Bluetooth sometimes does not work after resuming from suspend
Status in HWE Next Project:
Confirmed
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
Summary: Bluetooth sometimes does not work after resuming from suspend
Steps:
1. fwts s3 --s3-multiple=30 --s3-max-delay=5 --s3-min-delay=5
2. hcitool scan
Expected results: Can scan and connect to BT devices
Actual results: Can't scan and connect to BT devices
In kern.log:
Jul 3 00:33:48 1704 kernel: [ 2365.124561] PM: Finishing wakeup.
Jul 3 00:33:48 1704 kernel: [ 2365.156748] ------------[ cut here ]------------
Jul 3 00:33:48 1704 kernel: [ 2365.156764] WARNING: at /build/buildd/linux-lts-quantal-3.5.0/drivers/base/firmware_class.c:597 request_firmware+0xb5/0xf0()
Jul 3 00:33:48 1704 kernel: [ 2365.156767] Hardware name: Inspiron 3137
Jul 3 00:33:48 1704 kernel: [ 2365.124564] Restarting tasks ...
Jul 3 00:33:48 1704 kernel: [ 2365.156770] Modules linked in: hid_multitouch snd_hda_codec_realtek(O) snd_hda_codec_hdmi(O) snd_hda_intel(O) snd_hda_codec(O) snd_hwdep coretemp kvm_intel snd_pcm kvm ghash_clmulni_intel cryptd snd_seq_midi joydev snd_rawmidi dell_laptop dcdbas dell_wmi sparse_keymap dm_multipath scsi_dh lib80211_crypt_tkip snd_seq_midi_event microcode psmouse wl(PO) bnep snd_seq uvcvideo videobuf2_core videodev videobuf2_vmalloc snd_timer cfg80211 snd_seq_device btusb videobuf2_memops serio_raw parport_pc lib80211 rfcomm ppdev i915_hsw bluetooth snd soundcore snd_page_alloc wmi drm_kms_helper drm i2c_algo_bit intel_ips video mac_hid lp parport usbhid hid dm_raid45 xor dm_mirror dm_region_hash dm_log btrfs zlib_deflate libcrc32c r8168(O) [last unloaded: hid_multitouch]
Jul 3 00:33:48 1704 kernel: [ 2365.156867] Pid: 25680, comm: kworker/0:2 Tainted: P W IO 3.5.0-22-generic #34~precise1-Ubuntu
Jul 3 00:33:48 1704 kernel: [ 2365.156870] Call Trace:
Jul 3 00:33:48 1704 kernel: [ 2365.156881] [<ffffffff81052c9f>] warn_slowpath_common+0x7f/0xc0
Jul 3 00:33:48 1704 kernel: [ 2365.156887] [<ffffffff81052cfa>] warn_slowpath_null+0x1a/0x20
Jul 3 00:33:48 1704 kernel: [ 2365.156894] [<ffffffff81437575>] request_firmware+0xb5/0xf0
Jul 3 00:33:48 1704 kernel: [ 2365.156912] [<ffffffffa02ee470>] ? hci_dev_open+0x290/0x290 [bluetooth]
Jul 3 00:33:48 1704 kernel: [ 2365.156922] [<ffffffffa0337b0a>] btusb_load_firmware+0xba/0x240 [btusb]
Jul 3 00:33:48 1704 kernel: [ 2365.156936] [<ffffffffa02ee324>] hci_dev_open+0x144/0x290 [bluetooth]
Jul 3 00:33:48 1704 kernel: [ 2365.156949] [<ffffffffa02ee48d>] hci_power_on+0x1d/0x80 [bluetooth]
Jul 3 00:33:48 1704 kernel: [ 2365.156958] [<ffffffff81071bba>] process_one_work+0x11a/0x480
Jul 3 00:33:48 1704 kernel: [ 2365.156964] [<ffffffff81072bd5>] worker_thread+0x165/0x370
Jul 3 00:33:48 1704 kernel: [ 2365.156971] [<ffffffff81072a70>] ? manage_workers.isra.29+0x130/0x130
Jul 3 00:33:48 1704 kernel: [ 2365.156977] [<ffffffff81077b73>] kthread+0x93/0xa0
Jul 3 00:33:48 1704 kernel: [ 2365.156985] [<ffffffff816a8524>] kernel_thread_helper+0x4/0x10
Jul 3 00:33:48 1704 kernel: [ 2365.156990] [<ffffffff81077ae0>] ? flush_kthread_worker+0xb0/0xb0
Jul 3 00:33:48 1704 kernel: [ 2365.156996] [<ffffffff816a8520>] ? gs_change+0x13/0x13
Jul 3 00:33:48 1704 kernel: [ 2365.156999] ---[ end trace 4ef11670192df83d ]---
Jul 3 00:33:48 1704 kernel: [ 2365.157006] usb 1-1.7: firmware: fw-0a5c_21d7.hcd will not be loaded
Jul 3 00:33:48 1704 kernel: [ 2365.159451] Bluetooth: can't load firmware, may not work correctly
Jul 3 00:33:48 1704 kernel: [ 2365.164446] done.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1197616/+subscriptions
Follow ups