On Thu, 2008-01-17 at 02:09 +0530, Balaji Rao wrote:
quoted text
> Hi,
> 
> When i set jiffies as the current_clocksource, date(1) tells me that wallclock time has stopped, and soon after that, the 
> system becomes unresponsive. This is not seen with CONFIG_NO_HZ disabled.
> 
> This happens in 2.6.24-rc4,rc5, and even in rc8.
> 
> I wonder how can jiffies be used as a clocksource.. Its value depends on the tick and when we turn off ticks, we would stop 
> incrementing jiffies and when we come come out of idle, we update the jiffies by reading the current_clocksource which now 
> is 'jiffies', and hence jiffies wouldn't get updated. Could this be the explanation ?

Your right, It can't be used as a clocksource with nohz , and the system
will refuse to automatically switch to it ..

However, you can manually override the system, which is what your
doing .. That in turn forces the usage of an unstable clock which causes
your time and system not to function any more..

Daniel

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