public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215189] hci0: unexpected event for opcode 0xfc2f
Date: Sun, 27 Nov 2022 18:18:22 +0000	[thread overview]
Message-ID: <bug-215189-62941-TJlhIXW7TE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215189-62941@https.bugzilla.kernel.org/>

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

Rijnhard Hessel (wiredknight375@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wiredknight375@gmail.com

--- Comment #3 from Rijnhard Hessel (wiredknight375@gmail.com) ---
Forgive me if this isn't related but also seeing the same message with

Bus 001 Device 003: ID 8087:07dc Intel Corp. Bluetooth wireless interface

System:
  Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64
    Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
Machine:
  Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0
    serial: <superuser required>
  Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: <superuser required>
    UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015

Also the side track also seeing a lot of other issues around powering on the
adapter after a suspend resume cycle (quite a few over the web, on launchpad
etc)

so was wondering if it could be related.

-- 
You may reply to this email to add a comment.

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

      parent reply	other threads:[~2022-11-27 18:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 16:52 [Bug 215189] New: hci0: unexpected event for opcode 0xfc2f bugzilla-daemon
2022-05-08 19:15 ` [Bug 215189] " bugzilla-daemon
2022-11-27 18:18 ` bugzilla-daemon [this message]

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-215189-62941-TJlhIXW7TE@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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