linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 214863] New: Intel AX200 "Bluetooth: hci0: failed to restart LE scan: status 31"
Date: Fri, 29 Oct 2021 02:02:51 +0000	[thread overview]
Message-ID: <bug-214863-62941@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 214863
           Summary: Intel AX200 "Bluetooth: hci0: failed to restart LE
                    scan: status 31"
           Product: Drivers
           Version: 2.5
    Kernel Version: mainline, bluetooh-next
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: kai.heng.feng@canonical.com
        Regression: No

Device: AX200
Bus 001 Device 002: ID 8087:0029 Intel Corp. 

Kernel: bluetooth-next
HEAD 2128939fe2e771645dd88e1938c27fdf96bd1cd0 ("Bluetooth: Fix removing adv
when processing cmd complete")

Reproduce step:
1) Open GNOME Settings' Bluetooh panel and let it continuously scan
2) Keep `rkfill block` and `rfkill unblock` loop.

Result:
Bluetooth stops working:
[   29.706981] Bluetooth: hci0: failed to restart LE scan: status 31

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

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

             reply	other threads:[~2021-10-29  2:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29  2:02 bugzilla-daemon [this message]
2022-04-14  2:12 ` [Bug 214863] Intel AX200 "Bluetooth: hci0: failed to restart LE scan: status 31" 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-214863-62941@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).