I am experiencing this issue on a new xeon scalable machine.
I can confirm that it is present with xenial linux-image-generic, and linux-image-generic-hwe, kernels 4.4.0-116, and 4.13.0-38, and I can reproduce it at will.
It no longer seems to occur on kernel 4.15.0-13.
In all cases, clocksource was already set to TSC automatically on install.
The soft lockup and hard lockup were triggered each time by a waf build of the ns3 project.
In each case, a failure occurred while running the commands as a regular user, but the system was stable if run as root, or with sudo.
I am experiencing this issue on a new xeon scalable machine. generic, and linux-image- generic- hwe, kernels 4.4.0-116, and 4.13.0-38, and I can reproduce it at will.
I can confirm that it is present with xenial linux-image-
It no longer seems to occur on kernel 4.15.0-13.
In all cases, clocksource was already set to TSC automatically on install.
The soft lockup and hard lockup were triggered each time by a waf build of the ns3 project.
In each case, a failure occurred while running the commands as a regular user, but the system was stable if run as root, or with sudo.