On Fri, Oct 11, 2019 at 5:47 PM Jeff Layton <jlayton@xxxxxxxxxx> wrote: > > What kernel version is this? Do you happen to have a more readable stack > trace? Did this come from a hung task warning in the kernel? $ uname -a Linux sun-gpu225 4.4.0-142-generic #168~14.04.1-Ubuntu SMP Sat Jan 19 11:26:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux This was the best stack trace we could get. /proc was not helpful: root@sun-gpu225:/proc/77292# cat stack [<ffffffffffffffff>] 0xffffffffffffffff We did not get messages of hung tasks from the kernel. This container was running for 9 days when the jobs should have completed in a matter of hours. They were not able to stop the container, but it still was using CPU. So it smells like uninterruptable sleep, but still using CPU which based on the trace looks like it's stuck in spinlock. Do you want me to get something more specific? Just tell me how. > From this, it looks like it's stuck waiting on a spinlock, but it's > rather hard to tell for sure. ---------------- Robert LeBlanc PGP Fingerprint 79A2 9CA4 6CC4 45DD A904 C70E E654 3BB2 FA62 B9F1
