linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@kernel.org
Subject: [Bug 198477] Intel 8260 bluetooth error with new kernel 4.15
Date: Mon, 16 Apr 2018 14:45:19 +0000	[thread overview]
Message-ID: <bug-198477-62941-aodY2SgQ1w@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198477-62941@https.bugzilla.kernel.org/>

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

hfel (tonis.rand@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tonis.rand@gmail.com

--- Comment #3 from hfel (tonis.rand@gmail.com) ---
Have the same problem on 4.15: a previously paired Bluetooth device keeps
looping between connected/disconnected. Only way to connect is to re-pair. 

Surprisingly, this issue seems to happen only with the first paired Bluetooth
device; any subsequently paired devices reconnect normally.

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

           reply	other threads:[~2018-04-16 14:45 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-198477-62941@https.bugzilla.kernel.org/>]

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-198477-62941-aodY2SgQ1w@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 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).