Re: [regression]: soft lockup in dmesg after suspend/resume

[Chase Douglas]

I wanted to ask about potential work arounds for the issue noted at
[1]. I wasn't subscribed to this list when that thread was started, so
unfortunately I can't reply directly. I also haven't found any follow
up to the thread, but please point me in the right direction if there
has been any.

We're seeing a number of reports against Ubuntu Lucid caused by
timestamps being highly warped coming out of suspend/resume. When a
warp occurs, the TSC register is throwing off timestamps with the
upper 32 bits set to 0xFFFFFFFF. I'm not terribly familiar with the
TSC or x86 clocking in general, but such time stamps should be many
many years into the future before we see them (unless I've done my
math wrong :). So with that in mind, it seems that it should be
possible to test for such outlandish values coming out of
suspend/resume. If the values are warped, would it be safe to switch
over to using jiffies in native_sched_clock by setting tsc_disable=1
during runtime?

Thanks,
Chase

[1] http://lkml.org/lkml/2010/1/4/7
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/