On Fri, 2024-12-13 at 11:42 +0100, Thomas Gleixner wrote: > > That's the control thread on CPU0. The hotplug thread on CPU1 is stuck > here: > > task:cpuhp/1 state:D stack:0 pid:24 tgid:24 ppid:2 > flags:0x00004000 > Call Trace: > <TASK> > __schedule+0x51f/0x1a80 > schedule+0x3a/0x140 > schedule_timeout+0x90/0x110 > msleep+0x2b/0x40 > blk_mq_hctx_notify_offline+0x160/0x3a0 > cpuhp_invoke_callback+0x2a8/0x6c0 > cpuhp_thread_fun+0x1ed/0x270 > smpboot_thread_fn+0xda/0x1d0 > > So something with those blk_mq fixes went sideways.
$ git bisect bad
7678abee0867e6b7fb89aa40f6e9f575f755fb37 is the first bad commit
commit 7678abee0867e6b7fb89aa40f6e9f575f755fb37 (HEAD)
Author: Ming Lei <ming....@redhat.com>
Date: Tue Nov 12 20:58:21 2024 +0800
virtio-blk: don't keep queue frozen during system suspend
smime.p7s
Description: S/MIME cryptographic signature
