Comment 63 for bug 254668

Although that looks frightening at a first glance it is quite a "normal" state. The important bits (literally) are the ones in the oneshot mask of hpet. They are all 0 which basically means hpet is not used as a broadcast device at the moment. And as long as no CPU enters an idle state where the local APICs are not running, this is just how it is supposed to be.
As soon as one or both CPUs go into long idle, the corresponding bit will be set in the mask and the hpet event timer should be set to the time when the first next event occurs.
So unfortunately nothing out of place here. No stopped tick, both APICs are about to fire soon and all other timers seem reasonable, too. The pause seems to happen after the watchdog this time, compared to the other runs where the "TSC unstable" message was printed with a longer delta.