linux-kernel - Re: Clock incorrect on 2.6.31-rc2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	14 Jul 2009 11:35:30 -0700
From:	Philippe Troin <phil@...i.org>
To:	Stephen Hemminger <shemminger@...tta.com>
Cc:	john stultz <johnstul@...ibm.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: Clock incorrect on 2.6.31-rc2

Stephen Hemminger <shemminger@...tta.com> writes:

> > I'm a little stumped.  Does the problem occur on every reboot? How long
> > does the box need to be up before you see an issue?  Or does it go away
> > after a little while?
> 
> It seemed to take a while (several hours). I will leave it running overnight

Interestingly, I am seeing the same problem on two boxes with
2.6.2{5,6}.  I haven't checked yet more recent kernels.

The odd thing was that booting with "nohz=off highres=off" did not
help, the only cure was to recompile the kernel and disable
CONFIG_HIGH_RES_TIMERS and CONFIG_NO_HZ.

This is the thread back then:
http://marc.info/?t=121563147700003&r=1&w=2

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