thank you for the help to gather more information.
I added "initcall_debug" in grub and tested the suspend / cpu-lockup problem after a rebooting into the new grub config.
I tried it different times, and can say, that the connected Thunderbolt dock was not the problem, as the cpu-lockup also happens, when the laptop was not connected to anything.
It is not happening on each suspend, but after some rounds of suspend+resume I can see the problem.
In the attachment is the kern.log with two incidents, the last one took quite a while (8000s).
If you have any other idea or have things I can test, I am happy to help!
Hi Thomas,
thank you for the help to gather more information.
I added "initcall_debug" in grub and tested the suspend / cpu-lockup problem after a rebooting into the new grub config.
I tried it different times, and can say, that the connected Thunderbolt dock was not the problem, as the cpu-lockup also happens, when the laptop was not connected to anything.
It is not happening on each suspend, but after some rounds of suspend+resume I can see the problem.
In the attachment is the kern.log with two incidents, the last one took quite a while (8000s).
If you have any other idea or have things I can test, I am happy to help!
Best regards,
Michael