linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	linux-bluetooth@vger.kernel.org, linux-wireless@vger.kernel.org,
	regressions@lists.linux.dev
Subject: Re: [REGRESSION] hci0 hci_power_on [bluetooth] blocks for more than 2 min preventing suspend and shutdown
Date: Tue, 12 Jul 2022 08:45:39 +0200	[thread overview]
Message-ID: <a0de2973-4666-e8eb-019b-2ea6c9c98a0a@molgen.mpg.de> (raw)
In-Reply-To: <CABBYNZKibt14eHLFMUre9CZ+XNmUvsh_BNaDz+LzDtHB0NMBDQ@mail.gmail.com>

#regzbot introduced: ff7f2926114d3a50f5ffe461a9bce8d761748da5
#regzbot fixed-by: e36bea6e78ab2b6c9c7396972fee231eae551cfc


Dear Luiz,


Am 12.07.22 um 05:05 schrieb Luiz Augusto von Dentz:

> On Mon, Jul 11, 2022 at 12:14 PM Paul Menzel wrote:

>> On a Dell Latitude E7250 with
>>
>>        Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
>>
>> with Debian sid/unstable upgrading from Linux 5.18.5 to 5.19-rc4 results
>> in a regression, where the system does not suspend or does not power
>> off. Linux logs earlier:
>>
>> ```
>> [  242.677813] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
>> [  242.677818] task:kworker/u9:1    state:D stack:    0 pid:  379 ppid:      2 flags:0x00004000
>> [  242.677831] Workqueue: hci0 hci_power_on [bluetooth]

[…]

> https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=e36bea6e78ab2b6c9c7396972fee231eae551cfc

Ah, thank you. Sorry for the noise then.


Kind regards,

Paul

      reply	other threads:[~2022-07-12  6:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 19:14 [REGRESSION] hci0 hci_power_on [bluetooth] blocks for more than 2 min preventing suspend and shutdown Paul Menzel
2022-07-12  3:05 ` Luiz Augusto von Dentz
2022-07-12  6:45   ` Paul Menzel [this message]

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=a0de2973-4666-e8eb-019b-2ea6c9c98a0a@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=regressions@lists.linux.dev \
    /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).