From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 199873] Bluetooth 3.0 mouses are automatically disconnected after connected
Date: Sun, 17 Feb 2019 22:20:22 +0000 [thread overview]
Message-ID: <bug-199873-62941-2WO3t5fhSu@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199873-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199873
antK (lkorg@manchestermonkey.co.uk) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lkorg@manchestermonkey.co.u
| |k
--- Comment #4 from antK (lkorg@manchestermonkey.co.uk) ---
I too have had the same issue...
Notebook: Dell XPS 13 9360
bios: tested with 2.9.1 and 2.10.0
OS: Debian stretch 9.8
Kernel: 4.9.0-8 debian 4.9.144-3
Wi-Fi/BT module: Intel Dual Band wirelss AC 8265, rev=0x230
Firmware: iwlwifi-8265-22.ucode
BlueZ: 5.43-2+deb9u1
BT Mouse: Logitech MX anywhere 2s
------
When attempting to pair one of 4 things will happen:
1. the bluetooth module locks up and stops responding - time out messages are
seen in dmesg
2. The wifi will reset but will return to a normal state with a failed
bluetooth as above
3. wifi and bluetooth will disappear and stop responding but wifi is
recoverable by invoking rfkill via the wifi hot key ( fn f12 )
4. The entire device stops responding and shortly after the machine will freeze
- there may be a panic but i can't see it due to lock up ( nothing written to
logs )
The pairing process will not complete as the device stops responding before
then.
Resetting the pci device via the /sys interface results in an instant hang
Other two xps devices i have contain ath10k cards and dont seem affected, mouse
can also be paired to an android device without issue.
tried bios upgrade to no avail. attempted using firmware direct from
linux-firmware repsitory instead of firmware-iwlwifi package ( 20161130-4 ) no
change
only fix i've found for this was to add the bt_coex_active=0 option when
loading the module ( modprobe: options iwlwifi bt_coex_active=0 )
this allows a connection to occur and for the device to pair however the mouse
movement on screen seems to be quite jittery at times.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-02-17 22:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-199873-62941@https.bugzilla.kernel.org/>
2018-12-11 23:24 ` [Bug 199873] Bluetooth 3.0 mouses are automatically disconnected after connected bugzilla-daemon
2019-02-17 22:20 ` bugzilla-daemon [this message]
2019-03-18 7:00 ` bugzilla-daemon
2019-03-18 7:23 ` bugzilla-daemon
2019-03-18 16:08 ` bugzilla-daemon
2019-03-18 21:41 ` bugzilla-daemon
2019-03-19 3:34 ` bugzilla-daemon
2019-03-25 8:42 ` bugzilla-daemon
2019-04-06 9:41 ` 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-199873-62941-2WO3t5fhSu@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-bluetooth@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).