Linux-Bluetooth Archive on lore.kernel.org
 help / Atom feed
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: Fri, 18 Jan 2019 07:22:11 +0000
Message-ID: <bug-198699-62941-xVLYoeNY57@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198699-62941@https.bugzilla.kernel.org/>

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

Johan Hedberg (johan.hedberg@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |johan.hedberg@gmail.com

--- Comment #24 from Johan Hedberg (johan.hedberg@gmail.com) ---
The "last event is not cmd complete" is in most/all cases a red herring, so
please don't focus on that. There's a patch in mainline that will remove it for
all valid situations (i.e. when the command completed with command status
instead of command complete):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1629db9c75342325868243d6bca5853017d91cf8

It seems like this issue has probably lots of different bugs mixed into it, all
incorrectly attributing themselves to this misleading warning message, when in
fact there's something unrelated going wrong. Those that are experiencing
issues even after applying the patch I referred to, please open new issues,
especially if the "last event is not cmd complete" message goes away for you
with the patch. This one can probably be closed since the misleading message
should now be gone.

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

  parent reply index

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 ` 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
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 [this message]
2019-02-01 21:28 ` bugzilla-daemon
2019-03-27  2:10 ` bugzilla-daemon

Reply instructions:

You may reply publically 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-xVLYoeNY57@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

Linux-Bluetooth Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-bluetooth/0 linux-bluetooth/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-bluetooth linux-bluetooth/ https://lore.kernel.org/linux-bluetooth \
		linux-bluetooth@vger.kernel.org linux-bluetooth@archiver.kernel.org
	public-inbox-index linux-bluetooth


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-bluetooth


AGPL code for this site: git clone https://public-inbox.org/ public-inbox