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-next>] [day] [month] [year] [list]
Date:	Mon, 30 Jul 2007 18:07:19 -0700
From:	"john stultz" <johnstul@...ibm.com>
To:	"Vasily Averin" <vvs@...ru>
Cc:	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [2.6.22] negative time jump

Whoops, forgot to CC lkml.

---------- Forwarded message ----------
From: john stultz <johnstul@...ibm.com>
Date: Jul 30, 2007 11:13 AM
Subject: Re: [2.6.22] negative time jump
To: Vasily Averin <vvs@...ru>


On 7/29/07, Vasily Averin <vvs@...ru> wrote:
> I've investigated why my testnode freezes. When I found that node is freezed
> again I've started to press Sysrq keys and noticed the following negative time jump.
>
> Could anybody please help me to understand the reasons of this issue?
>
> --- VvS comment: some pre-history: node boot
> Jul 27 13:58:10 ts28 Linux version 2.6.22 (vvs@....work.ve) (gcc version 3.4.6
> 20060404 (Red Hat 3.4.6-3)) #11 SMP Fri Jul 27 12:47:45 MSD 2007
> Jul 27 13:58:10 ts28 Command line: ro root=LABEL=/1 console=ttyS0,115200
> console=tty debug silencelevel=8 crashkernel=128M@...M acpc=noirq clocksource=tsc

clocksource=tsc?

I suspect you're forcing the clocksource as its not selected by
default. Could you provide dmesg output without that option. It might
shed some light as to why the clocksource isn't chosen.

It may very well be your TSCs are not synched or are otherwise not
reliable for timekeeping , and thus time is not consistent between
cpus.

-john

PS: also, you might want to check that acpc=noirq bit as well.. i
think you mean "acpi=noirq"
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ