All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 221346] New: Bluetooth: btintel_pcie (8086:e476) may hang in shutdown path (synchronize_irq) during reboot stress test
Date: Sat, 11 Apr 2026 12:38:58 +0000	[thread overview]
Message-ID: <bug-221346-62941@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 221346
           Summary: Bluetooth: btintel_pcie (8086:e476) may hang in
                    shutdown path (synchronize_irq) during reboot stress
                    test
           Product: Drivers
           Version: 2.5
          Hardware: Intel
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: zhangzhigang1996@gmail.com
        Regression: No

On a system with Intel Bluetooth device [8086:e476] using the btintel_pcie
driver, the system intermittently hangs during reboot or shutdown, especially
under stress test conditions (continuous reboot cycles).

During shutdown, systemd-udevd is observed to be stuck in D state. Kernel
stack traces show the task blocked in the driver removal path, waiting in
synchronize_irq() after free_irq() is called.

The relevant call trace is:

  btintel_pcie_remove()
    → free_irq()
    → synchronize_irq()
      → __synchronize_irq()
      → wait for IRQ handler completion (never returns)

This indicates that the interrupt handler associated with the device may not
be properly quiesced before free_irq(), leading to a deadlock during teardown.

The issue is reproducible and disappears when the btintel_pcie module is
unloaded or blacklisted, suggesting the problem is specific to the btintel_pcie
driver.

No firmware loading errors are observed, and the device is otherwise functional
during normal operation.

This may indicate incomplete interrupt shutdown handling in the btintel_pcie
driver.

-- 
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:[~2026-04-11 12:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-11 12:38 bugzilla-daemon [this message]
2026-04-11 12:41 ` [Bug 221346] Bluetooth: btintel_pcie (8086:e476) may hang in shutdown path (synchronize_irq) during reboot stress test bugzilla-daemon
2026-04-11 12:45 ` bugzilla-daemon
2026-04-14  6:07 ` bugzilla-daemon
2026-04-14  6:45 ` bugzilla-daemon
2026-04-15  5:53 ` bugzilla-daemon
2026-04-15  5:59 ` bugzilla-daemon
2026-04-15  6:16 ` 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-221346-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.