public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 214187] New: Intel 7260 Chip Failures
Date: Thu, 26 Aug 2021 15:22:41 +0000	[thread overview]
Message-ID: <bug-214187-62941@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 214187
           Summary: Intel 7260 Chip Failures
           Product: Drivers
           Version: 2.5
    Kernel Version: Linux 5.13.12-193.current x86_64
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: igorm@posteo.net
        Regression: No

Created attachment 298489
  --> https://bugzilla.kernel.org/attachment.cgi?id=298489&action=edit
Intel 7260 chip often fails

Hi,

At times, as I try to connect a Bluetooth device, the process fails and
Bluetooth functionality temporarily disappears from the system. It comes back
after a reboot. I can see no consistency in these failures. Sometimes they just
happen, sometimes they don't.

These commands also bring Bluetooth functionality back. However, failures may
happen again.

```
sudo systemctl enable bluetooth
sudo systemctl start Bluetooth
```

Another Bluetooth-related problem is the system may stall during a reboot. This
happens rarely and the following message is displayed after a long pause:

[See the attached image.]

I am not entirely sure but the Bluetooth card is most likely: Intel AC 8260
IEEE 802.11ac Bluetooth 4.2 - Wi-Fi/Bluetooth Combo Adapter

It has been like this for the last several months. Earlier I had other similar
Bluetooth problems on and off. I keep my system updated. Right now I am using:

* Solus OS 4.3 Fortitude
* Budgie DE 10.5.3-238 based on GNOME 40.3.0

Relevant terminal output:

```
user@pc ~ $ lspci | egrep -i --color 'network|ethernet'
[...]
01:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b)
user@pc ~ $ 
```

```
user@pc ~ $ dmesg | grep -i blue
[   19.751133] Bluetooth: Core ver 2.22
[   19.751153] Bluetooth: HCI device and connection manager initialized
[   19.751164] Bluetooth: HCI socket layer initialized
[   19.751166] Bluetooth: L2CAP socket layer initialized
[   19.751169] Bluetooth: SCO socket layer initialized
[   20.068652] Bluetooth: hci0: read Intel version: 370710018002030d57
[   20.068657] Bluetooth: hci0: Intel device is already patched. patch num: 57
[   20.084589] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   20.084595] Bluetooth: BNEP socket layer initialized
[   35.947535] Bluetooth: RFCOMM TTY layer initialized
[   35.947545] Bluetooth: RFCOMM socket layer initialized
[   35.947552] Bluetooth: RFCOMM ver 1.11
[16800.174315] bluetoothd[785]: segfault at 70 ip 000000000041ce1f sp
00007ffe30709d30 error 4 in bluetoothd[40b000+ae000]
user@pc ~ $
```

Could this be fixed?

Thanks.

-- 
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-08-26 15:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-214187-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