DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=from:organization:to:subject:date:user-agent:cc:mime-version:content-type:content-transfer-encoding:content-disposition:message-id;
        b=XLvIdHn64e/ZoqKPRDZEUy54C/Nn01TmMrlXBK5xfXNS+r3+2s/bURjmuMsqx8xR8mcxNhfD1VQ5IEPLbmnHK0KZWsgk5jzP0YUSNf9rRlySicbtvVpx4JREcTFDkLFA+7DNV0i3qaGGrlNdqH2pA4zIqLdjRSoCO0/yIsmylyc=
From: Balaji Rao <balajirrao@gmail.com>
Organization: NITK
To: linux-kernel@vger.kernel.org
Subject: setting jiffies as the clocksource stops time
Date: Thu, 17 Jan 2008 02:09:42 +0530
User-Agent: KMail/1.9.6 (enterprise 0.20071012.724442)
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200801170209.42138.balajirrao@gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1116
Lines: 25

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 ?

I also encountered the same problem when i ran the kernel in qemu, and set pit as the current_clocksource. Why does this 
happen ?

So, i think should we unregister jiffies as a clocksource when we go into NO_HZ ?

Thomas, Ingo what are your thoughts on this ?

regards,
balaji rao
--
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/