On Tue, Apr 26, 2022 at 05:38:58PM -0400, Zi Yan wrote: > Thanks. Do you mind attaching your config file? I cannot reproduce > the deadlock locally using my own config. I also see kmemleak_scan > in the dumped stack, so it must be something else in addition to > memory online/offline causing the issue. Of course it also need to enable those. The kmemleak_scan is just a symptom of one of the online operations is blocking forever, as the locks were never released. CONFIG_MEMORY_HOTPLUG=y CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=y CONFIG_MEMORY_HOTREMOVE=y