From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bert Karwatzki <spasswolf@web.de>
Cc: Stuart Hayes <stuart.w.hayes@gmail.com>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: hung tasks on shutdown in linux-next-202409{20,23,24,25}
Date: Wed, 25 Sep 2024 14:09:23 +0200 [thread overview]
Message-ID: <2024092503-banshee-reoccupy-93d1@gregkh> (raw)
In-Reply-To: <20240925114002.3380-1-spasswolf@web.de>
On Wed, Sep 25, 2024 at 01:40:01PM +0200, Bert Karwatzki wrote:
> Since linux-next-20240920 my Msi Alpha 15 Laptop has repeatedly suffered
> from hung tasks when shutting down (though not on every shutdown). After
> some time when shutting down does not work the following messages about
> hung tasks appear on screen:
> INFO: task systemd-shutdow:1 blocked for more than 61 seconds.
> and several of these
> INFO: task kworker/u64:*:* blocked for more than 61 seconds.
>
> The error can be provoked by repeatedly rebooting the system, and so
> I bisected the error between v6.11 and next-20240920. As the first bad
> commit I got the merge commit
>
> commit 32035d78548754935544d2ae23d39c6090ad0b50
> Merge: 9dfe3a6f3f77 6a36d828bdef
> Author: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Fri Sep 20 12:48:01 2024 +1000
>
> Merge branch 'driver-core-next' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
>
> Both parents of the commit tested as not affected by the bug. (I declared a commit as
> good when it survived ten reboot cycles without a hang, the bad commits usually
> hung after at most 3 reboots).
>
> The error is also still present in next-202409{23,24,25}. In next-20240925 I can
> fix the issue by the following reverting commit 1a0f3e00961c (commit 1a0f3e00961c
> is similar to commit 32035d785487, both merge branch 'driver-core-next'
> from gregkh/driver-core.git):
Thanks for the report, I _just_ reverted all of these in my branch due
to another report just like this. I'll be glad to take them back after
-rc1 if these issues can be worked out.
So the next linux-next release should be good, OR if you could pull my
driver-core.git driver-core-next branch to verify the revert worked for
you, that would be great.
thanks,
greg k-h
next prev parent reply other threads:[~2024-09-25 12:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 11:40 hung tasks on shutdown in linux-next-202409{20,23,24,25} Bert Karwatzki
2024-09-25 12:09 ` Greg Kroah-Hartman [this message]
2024-09-25 19:15 ` Bert Karwatzki
-- strict thread matches above, loose matches on Subject: below --
2024-09-25 21:37 Bert Karwatzki
2024-09-25 21:48 ` stuart hayes
2024-09-29 10:52 Bert Karwatzki
2024-09-29 10:53 Bert Karwatzki
2024-09-30 21:11 ` stuart hayes
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=2024092503-banshee-reoccupy-93d1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=spasswolf@web.de \
--cc=stuart.w.hayes@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.