All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@kernel.org
Subject: [Bug 190831] Intel Bluetooth 8260 breaks with latest firmware
Date: Sat, 18 Feb 2017 20:43:16 +0000	[thread overview]
Message-ID: <bug-190831-62941-n5eVRsKuRu@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-190831-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=190831

Tony Houghton (h@realh.co.uk) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |h@realh.co.uk

--- Comment #47 from Tony Houghton (h@realh.co.uk) ---
I've got a similar problem with Debian kernel 4.9.6-3, except my mouse, a
Microsoft 3600, just seems to stop, without going into a low framerate first.
However, it did seem to go into a low framerate when I tried to see if my BT
speaker would work. The speaker would connect, but either not become available
in sound settings, or attempting to play to it caused the player (mpv) to just
pause at 00:00 indefinitely.

When trying to open GNOME's bluetooth settings when the mouse has stopped
working, there's a delay of several seconds before it appears, and I see this
in journalctl:

Feb 18 19:29:31 lenny bluetoothd[1140]: Failed to set mode: Failed (0x03)
Feb 18 19:29:31 lenny kernel: Bluetooth: hci0 command 0x0c1a tx timeout
Feb 18 19:29:33 lenny bluetoothd[1140]: Failed to set mode: Failed (0x03)
Feb 18 19:29:33 lenny gnome-control-c[1824]: Failed to set Discoverable to 1:
GDBus.Error:org.bluez.Error.Failed: Failed
Feb 18 19:29:33 lenny kernel: Bluetooth: hci0 command 0x0c1a tx timeout
Feb 18 19:29:35 lenny kernel: Bluetooth: hci0 command 0x200c tx timeout
Feb 18 19:29:37 lenny bluetoothd[1140]: Failed to set mode: Failed (0x03)
Feb 18 19:29:37 lenny kernel: Bluetooth: hci0 command 0x0c1a tx timeout
Feb 18 19:29:39 lenny bluetoothd[1140]: Failed to set mode: Failed (0x03)
Feb 18 19:29:39 lenny kernel: Bluetooth: hci0 command 0x0c1a tx timeout
Feb 18 19:29:47 lenny kernel: Bluetooth: hci0 command 0x200c tx timeout
Feb 18 19:29:59 lenny kernel: Bluetooth: hci0 command 0x200c tx timeout
Feb 18 19:30:11 lenny kernel: Bluetooth: hci0 command 0x200c tx timeout
F

When the settings dialog eventually opens, it says the mouse is still
Connected. Turning bluetooth off and on again makes the mouse reconnect, but
only for a few seconds.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2017-02-18 20:43 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21 17:54 [Bug 190831] New: Intel Bluetooth 8260 breaks with latest firmware bugzilla-daemon
2016-12-21 17:55 ` [Bug 190831] " bugzilla-daemon
2016-12-21 18:08 ` bugzilla-daemon
2016-12-21 19:56 ` bugzilla-daemon
2016-12-21 20:23 ` bugzilla-daemon
2016-12-21 20:24 ` bugzilla-daemon
2016-12-22  6:49 ` bugzilla-daemon
2016-12-22 20:35 ` bugzilla-daemon
2016-12-23  9:16 ` bugzilla-daemon
2017-01-05 10:09 ` bugzilla-daemon
2017-01-05 13:14 ` bugzilla-daemon
2017-01-05 13:59 ` bugzilla-daemon
2017-01-05 14:44 ` bugzilla-daemon
2017-01-05 14:53 ` bugzilla-daemon
2017-01-06  6:19 ` bugzilla-daemon
2017-01-06  6:27 ` bugzilla-daemon
2017-01-06  6:28 ` bugzilla-daemon
2017-01-06  6:46 ` bugzilla-daemon
2017-01-06  6:59 ` bugzilla-daemon
2017-01-06  7:06 ` bugzilla-daemon
2017-01-06  7:27 ` bugzilla-daemon
2017-01-06  7:28 ` bugzilla-daemon
2017-01-06  8:00 ` bugzilla-daemon
2017-01-06 12:25 ` bugzilla-daemon
2017-01-08 10:46 ` bugzilla-daemon
2017-01-13 16:45 ` bugzilla-daemon
2017-01-15 16:43 ` bugzilla-daemon
2017-01-17 17:07 ` bugzilla-daemon
2017-01-17 17:08 ` bugzilla-daemon
2017-01-17 17:09 ` bugzilla-daemon
2017-01-18 13:49 ` bugzilla-daemon
2017-01-19  6:54 ` bugzilla-daemon
2017-01-19  6:54 ` bugzilla-daemon
2017-01-19 10:22 ` bugzilla-daemon
2017-01-19 10:31 ` bugzilla-daemon
2017-01-19 11:16 ` bugzilla-daemon
2017-01-20 13:21 ` bugzilla-daemon
2017-01-29 13:35 ` bugzilla-daemon
2017-01-31  0:34 ` bugzilla-daemon
2017-01-31  7:14 ` bugzilla-daemon
2017-01-31 18:31 ` bugzilla-daemon
2017-02-01  6:41 ` bugzilla-daemon
2017-02-01 13:24 ` bugzilla-daemon
2017-02-04  3:11 ` bugzilla-daemon
2017-02-09  6:48 ` bugzilla-daemon
2017-02-09 20:57 ` bugzilla-daemon
2017-02-11 15:24 ` bugzilla-daemon
2017-02-11 22:59 ` bugzilla-daemon
2017-02-18 20:43 ` bugzilla-daemon [this message]
2017-02-23 16:28 ` bugzilla-daemon
2017-02-23 16:39 ` bugzilla-daemon
2017-02-24  8:47 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-190831-62941-n5eVRsKuRu@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-bluetooth@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.