Andrew Morton <[EMAIL PROTECTED]> writes: > > One possibility is that sched_clock() is bollixed and (say) it's returning > a 32-bit value. That'll cause the softlockup logic to get a bit sick when > time wraps.
FYI, The current ff x86 sched_clock() [which you likely have, it's not mainline] tends to warp backwards by 80-90ms during cpu freq changes on AMD on one of my test systems. I haven't tracked down why it does that yet. Intel or systems with no cpufreq or cpufreq not changing frequencies regularly are not affected -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
