linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219861] New: Bluetooth device in reset loop after suspend [regression]
Date: Thu, 13 Mar 2025 06:36:14 +0000	[thread overview]
Message-ID: <bug-219861-62941@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 219861
           Summary: Bluetooth device in reset loop after suspend
                    [regression]
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: pierre-bugzilla@ossman.eu
        Regression: No

Created attachment 307813
  --> https://bugzilla.kernel.org/attachment.cgi?id=307813&action=edit
kernel log

My bluetooth device has unfortunately stopped working after a suspend/resume
cycle with one of the recent kernel upgrades.

When this happens, I get a constant loop of this, spamming up my logs:

> Mar 09 18:16:44 mjolnir.ossman.eu kernel: Bluetooth: hci0: sending initial
> HCI reset failed (-19)
> Mar 09 18:16:45 mjolnir.ossman.eu kernel: usb 4-3: new full-speed USB device
> number 3 using ohci-pci
> Mar 09 18:16:45 mjolnir.ossman.eu kernel: usb 4-3: New USB device found,
> idVendor=8087, idProduct=07dc,>
> Mar 09 18:16:45 mjolnir.ossman.eu kernel: usb 4-3: New USB device strings:
> Mfr=0, Product=0, SerialNumb>
> Mar 09 18:16:47 mjolnir.ossman.eu kernel: usb 4-3: USB disconnect, device
> number 3

This is a regression. The issue was first seen with 6.12.11-200.fc41.x86_64.
That same version was used a whole month without issues, though, so I'm unsure
if the kernel itself is the culprit. But I don't know what else to examine.

A complete power cycle is required to return to normal. Power off/power on is
insufficient. You have to remove the power cable from the machine.

The device is also on the motherboard, which makes it impossible to just remove
and reinsert it.

-- 
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:[~2025-03-13  6:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13  6:36 bugzilla-daemon [this message]
2025-03-13 12:25 ` [Bug 219861] Bluetooth device in reset loop after suspend [regression] 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-219861-62941@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;
as well as URLs for NNTP newsgroup(s).