From: patchwork-bot+bluetooth@kernel.org
To: yCduIhFgkD <vladimirkondratyev2@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, pmenzel@molgen.mpg.de,
chandrashekar.devegowda@intel.com, arnd@arndb.de,
kiran.k@intel.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, lsa.uz@pm.me
Subject: Re: [PATCH v4] Bluetooth: btintel_pcie: fix stale cache in set_dxstate fallback check
Date: Tue, 29 Sep 2026 15:10:13 +0000 [thread overview]
Message-ID: <179069461352.983246.11748091968845078723.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260903192245.135310-2-vladimirkondratyev2@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 3 Sep 2026 21:22:38 +0200 you wrote:
> btintel_pcie returns -16 (EBUSY) during suspend, causing the entire
> suspend operation to abort on Intel Lunar Lake hardware. The system
> immediately resumes
> after every suspend attempt:
> Bluetooth: hci0: Timeout (200 ms) on alive interrupt for D2 entry,
> retry count 0
> Bluetooth: hci0: Timeout (200 ms) on alive interrupt for D2 entry,
> retry count 1
> Bluetooth: hci0: Timeout (200 ms) on alive interrupt for D2 entry,
> retry count 2
> btintel_pcie 0000:00:14.7: PM: pci_pm_suspend(): btintel_pcie_suspend
> [btintel_pcie] returns -16
> btintel_pcie 0000:00:14.7: PM: dpm_run_callback(): pci_pm_suspend
> returns -16
> btintel_pcie 0000:00:14.7: PM: failed to suspend async: error -16
> PM: Some devices failed to suspend, or early wake event detected
>
> [...]
Here is the summary with links:
- [v4] Bluetooth: btintel_pcie: fix stale cache in set_dxstate fallback check
https://git.kernel.org/bluetooth/bluetooth-next/c/20dfccf8d854
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-09-29 15:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 20:34 [PATCH] Bluetooth: btintel_pcie: fix stale cache in set_dxstate fallback check Vladimir V. Kondratyev
2026-05-07 21:06 ` bluez.test.bot
2026-09-01 20:37 ` [PATCH] " Vladimir V. Kondratyev
2026-09-01 22:36 ` bluez.test.bot
2026-09-02 5:35 ` [PATCH] " Paul Menzel
2026-09-02 7:24 ` Sergey Lebedev
2026-09-02 8:38 ` Paul Menzel
2026-09-02 9:30 ` Sergey Lebedev
2026-09-03 14:29 ` [PATCH v3] " Vladimir V. Kondratyev
2026-09-03 14:36 ` Paul Menzel
2026-09-03 14:47 ` [v3] " bluez.test.bot
2026-09-03 15:35 ` [PATCH v3] " Vladimir V. Kondratyev
2026-09-03 17:20 ` Sergey Lebedev
2026-09-03 18:40 ` [v3] " bluez.test.bot
2026-09-03 20:19 ` Paul Menzel
2026-09-03 19:22 ` [PATCH v4] " Vladimir V. Kondratyev
2026-09-03 19:53 ` Sergey Lebedev
2026-09-08 14:12 ` K, Kiran
2026-09-03 21:25 ` [v4] " bluez.test.bot
2026-09-09 12:36 ` [PATCH v4] " Sergey Lebedev
2026-09-29 15:10 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-08 17:43 btintel_pcie: hibernation intermittently aborted by -EBUSY from D3 entry timeout Sergey Lebedev
2026-09-09 0:45 ` [PATCH v4] Bluetooth: btintel_pcie: fix stale cache in set_dxstate fallback check Ferenc Lengyel
2026-09-09 17:49 ` Sergey Lebedev
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=179069461352.983246.11748091968845078723.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=arnd@arndb.de \
--cc=chandrashekar.devegowda@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsa.uz@pm.me \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=pmenzel@molgen.mpg.de \
--cc=vladimirkondratyev2@gmail.com \
/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.