Linux bluetooth development
 help / color / mirror / Atom feed
From: Sergey Lebedev <lsa.uz@pm.me>
To: Ferenc Lengyel <dev@lengyelf.eu>
Cc: "Vladimir V . Kondratyev" <vladimirkondratyev2@gmail.com>,
	Ravindra <ravindra@intel.com>, Kiran K <kiran.k@intel.com>,
	Paul Menzel <pmenzel@molgen.mpg.de>,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v4] Bluetooth: btintel_pcie: fix stale cache in set_dxstate fallback check
Date: Wed, 09 Sep 2026 17:49:24 +0000	[thread overview]
Message-ID: <20260909174918.80317-1-lsa.uz@pm.me> (raw)
In-Reply-To: <df180a89-b214-41b4-b8ce-c6ed6b12372f@lengyelf.eu>

Ferenc,

I owe you a plain acknowledgement: I told you my guess was that v4 alone would
fix your hibernation, and it did not. You checked instead of taking my word for
it, then instrumented the re-read and found the actual second fault - .thaw
running an FLR that leaves the controller in ROM when .poweroff asks it for D3
nine seconds later. That is the mechanism, and it is not one I would have got
to from this machine, where the failure is on s2idle and looks nothing like it.

The series went out yesterday with both patches:

  https://lore.kernel.org/linux-bluetooth/20260909123416.71919-1-lsa.uz@pm.me/

Your Tested-by is on 2/2 and deliberately not on 1/2, which is how you asked
for it: a tag on patch N means the tree with 1..N applied, so 2/2 is the one
that carries "the pair, tested". Your Assisted-by went with it, in your order.
Your own caveat about ten cycles against a one-in-three rate - Fisher p ~ 0.06 -
is quoted in the cover letter in your words rather than summarised away.

Nothing needed from you. If the maintainers ask for more cycles I will say so
here rather than assume you are available.

Sergey


  reply	other threads:[~2026-09-09 17:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-07 20:34 [PATCH] " Vladimir V. Kondratyev
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-09 12:36   ` 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=20260909174918.80317-1-lsa.uz@pm.me \
    --to=lsa.uz@pm.me \
    --cc=dev@lengyelf.eu \
    --cc=kiran.k@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=ravindra@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox