linux-kernel - Re: [BUG] jiffies counter leaps in 2.6.24-rc3

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]

Message-ID: <20071129182402.GE12481@redhat.com>
Date:	Thu, 29 Nov 2007 13:24:02 -0500
From:	Dave Jones <davej@...hat.com>
To:	Stefano Brivio <stefano.brivio@...imi.it>
Cc:	Ingo Molnar <mingo@...e.hu>, "Rafael J. Wysocki" <rjw@...k.pl>,
	linux-kernel@...r.kernel.org, Michael Buesch <mb@...sch.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Len Brown <lenb@...nel.org>
Subject: Re: [BUG] jiffies counter leaps in 2.6.24-rc3

On Thu, Nov 29, 2007 at 06:57:43PM +0100, Stefano Brivio wrote:

 > > adjust_jiffies() always gets called on a speed transition. I'm wondering
 > > if perhaps we shouldn't do that if we're using something other than
 > > the tsc for timekeeping.
 > 
 > I gave other clocksources a try:
 > 
 > morte st3 # cat /sys/devices/system/clocksource/clocksource0/available_clocksource
 > acpi_pm pit jiffies tsc
 > 
 > Setting tsc as current clocksource:
 > morte st3 # echo tsc > /sys/devices/system/clocksource/clocksource0/current_clocksource
 > [13367.729060] Time: tsc clocksource has been installed.
 > didn't fix anything. Other weirdness here: it looks like it affects my
 > typematic delay and repeat rate.

*grumble*
 
 > Setting jiffies or pit as current clocksource didn't fix anything, but at
 > least it doesn't cause anything bad.
 > 
 > Do you want me to comment out adjust_jiffies() and see what happens?
 
Just for laughs, why not.

	Dave

-- 
http://www.codemonkey.org.uk
-
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/