From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 198699] Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)
Date: Sun, 04 Nov 2018 12:00:36 +0000 [thread overview]
Message-ID: <bug-198699-62941-a7DuN41xa6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198699-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198699
Oleksandr Pylypenko (lex.pilipenko@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lex.pilipenko@gmail.com
--- Comment #20 from Oleksandr Pylypenko (lex.pilipenko@gmail.com) ---
Confirming the issue on Dell Vostro 5468 with Intel Bluetooth adapter
(8087:0a2a), OS Ubuntu 18.04.1, kernel version. 4.15.0-36-generic. Audio output
appears to clog and tear second after log line shows in dmesg. This goes for
4-5 seconds, after which playback continues normally for another ~10 seconds.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2018-11-04 12:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-198699-62941@https.bugzilla.kernel.org/>
2018-10-22 12:43 ` [Bug 198699] Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f) bugzilla-daemon
2018-10-27 4:08 ` bugzilla-daemon
2018-10-27 4:13 ` bugzilla-daemon
2018-10-27 4:17 ` bugzilla-daemon
2018-10-30 19:15 ` bugzilla-daemon
2018-11-04 12:00 ` bugzilla-daemon [this message]
2018-11-12 14:22 ` bugzilla-daemon
2018-11-12 17:34 ` bugzilla-daemon
2019-01-18 6:31 ` bugzilla-daemon
2019-01-18 7:22 ` bugzilla-daemon
2019-02-01 21:28 ` bugzilla-daemon
2019-03-27 2:10 ` 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-198699-62941-a7DuN41xa6@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 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.