Comment 29 for bug 1435363

Hi Chris,

Thanks for the help so far. I'm deploying a new machine right now and I'll be trying to replicate it on -48.

The way I detected it was that i'd see messaging in "dmesg" on guest similar to this:

hrtimer: interrupt took 4352551231 ns

In addition, when pinging the machine, you'd have a few seconds of stable pings, then unresponsive for 2-3s, and it starts responding again (with a huge delay, latency of 3s to 4s because of the delay).

I will be running this machine and monitoring it closely and report on the output, however, I'd like to note that these machines have heavy KSM usage, before turning it off, one had almost ~45-50GB of deduplicated memory on a 256GB node, so I'm not sure if that plays in as a factor..

I'll report back on -48 and see what I can check

Thank you,
Mohammed