linux-kernel - Re: 2.6.25.2 - Jiffies/Time jumping back and forth (Regereesion from 2.6.24)

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: <alpine.LFD.1.10.0805081609080.3318@apollo.tec.linutronix.de>
Date:	Thu, 8 May 2008 16:13:55 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Martin Knoblauch <spamtrap@...bisoft.de>
cc:	Gabriel C <nix.or.die@...glemail.com>,
	Bart Van Assche <bart.vanassche@...il.com>,
	linux-kernel@...r.kernel.org, hmh@....eng.br
Subject: Re: 2.6.25.2 - Jiffies/Time jumping back and forth (Regereesion from
 2.6.24)

On Thu, 8 May 2008, Martin Knoblauch wrote:
> on two different systems running 2.6.25.2:
> 
> ibm x3650(2xDualCore)
> -------------------------------------
> [root@...dm60 ~]# cat /sys/devices/system/clocksource/clocksource0/available_clocksource
> tsc hpet acpi_pm jiffies
> [root@...dm60 ~]# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> tsc
> 
> HP Proliant DL-380G4 (2xSingleCore)
> ------------------------------------------------------------
> [root@...dm52 ~]# cat /sys/devices/system/clocksource/clocksource0/available_clocksource
> tsc hpet acpi_pm jiffies
> [root@...dm52 ~]# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> tsc
> 
> and on the DL380G4 running 2.6.24:
> ---------------------------------------------------------
> [root@...dm52 ~]# cat /sys/devices/system/clocksource/clocksource0/available_clocksource
> hpet acpi_pm jiffies tsc
> [root@...dm52 ~]# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> hpet

So on 2.6.24 the TSC is declared unstable at some point and 2.6.25
thinks it works fine. Is this the same kernel config (aside of the 24/25 fuzz) ?

Thanks,
	tglx
--
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/