Re: frequent lockups in 3.18rc4

From: Linus Torvalds
Date: Wed Dec 03 2014 - 14:25:36 EST

On Wed, Dec 3, 2014 at 11:00 AM, Dave Jones <davej@xxxxxxxxxx> wrote:
> So right after sending my last mail, I rebooted, and restarted the run
> on the same kernel again.
> As I was writing this mail, this happened.
> [ 524.420897] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [trinity-c178:20182]
> and that's all that made it over the console. I couldn't log in via ssh,
> and thought "ah-ha, so it IS bad". I walked over to reboot it, and
> found I could actually log in on the console. check out this dmesg..
> [ 503.683055] Clocksource tsc unstable (delta = -95946009388 ns)
> [ 503.692038] Switched to clocksource hpet
> [ 524.420897] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [trinity-c178:20182]

Interesting. That whole NMI watchdog thing happens pretty much 22s
after the "TSC unstable" message.

Have you ever seen that TSC issue before? The watchdog relies on
comparing get_timestamp() differences, so if the timestamp was

Maybe that whole "clocksource_watchdog()" is bogus. That delta is
about 96 seconds, sounds very odd. I'm not seeing how the TSC could
actually scew up that badly, so I'd almost be more likely to blame the
"watchdog" clock.

I don't know. This piece of code:

delta = clocksource_delta(wdnow, cs->wd_last, watchdog->mask);

makes no sense to me. Shouldn't it be

delta = clocksource_delta(wdnow, watchdog->wd_last, watchdog->mask);

Thomas? John?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at