linux-kernel - [2.6.22] negative time jump

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]

Message-ID: <46AD57BF.8090106@sw.ru>
Date:	Mon, 30 Jul 2007 10:15:11 +0700
From:	Vasily Averin <vvs@...ru>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
CC:	Andrew Morton <akpm@...l.org>
Subject: [2.6.22] negative time jump

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

[root@...8 ~]# echo q > /proc/sysrq-trigger
Jul 27 14:09:34 ts28 now at 685327961777 nsecs

--- VvS comment: AIM7 test hangs at friday ~Jul 27 20:27:06 2007
48  135.33   98         2.8193   2149.48    167.67   Fri Jul 27 17:42:10 2007
54  127.76   99         2.3660   2561.30    190.97   Fri Jul 27 18:24:51 2007
67  117.00   99         1.7463   3470.13    237.20   Fri Jul 27 19:22:41 2007
72  112.89   99         1.5679   3864.93    248.71   Fri Jul 27 20:27:06 2007
82


---VvS comment: what I do monday morning:
[root@...8 ~]# echo q > /proc/sysrq-trigger
Jul 30 06:15:37 ts28 SysRq : Show Pending Timers
Jul 30 06:15:37 ts28 Timer List Version: v0.3
Jul 30 06:15:37 ts28 HRTIMER_MAX_CLOCK_BASES: 2
Jul 30 06:15:37 ts28 now at 29111288132045 nsecs
--- VvS comment: I would note: 29111 sec is very strange value for node with 3
day uptime...

[root@...8 ~]# echo q > /proc/sysrq-trigger
Jul 30 06:16:21 ts28 now at 29155644785562 nsecs

[root@...8 ~]# echo 1 > /proc/timer_stats
[root@...8 ~]# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: 17.992 s
0 total events
[root@...8 ~]# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: -4366.278 s
0 total events
[root@...8 ~]# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: -4359.840 s
0 total events
[root@...8 ~]# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: -4347.397 s
0 total events
[root@...8 ~]# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: -4331.652 s
0 total events
[root@...8 ~]# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: -4297.293 s
0 total events
[root@...8 ~]# echo q > /proc/sysrq-trigger
Jul 30 06:19:07 ts28 now at 24922828615221 nsecs

[root@...8 ~]# echo q > /proc/sysrq-trigger
Jul 30 06:22:07 ts28 now at 25103332336122 nsecs

[root@...8 ~]# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: -4065.515 s
0 total events
[root@...8 ~]# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: -3913.800 s
0 total events
[root@...8 ~]# echo q > /proc/sysrq-trigger
Jul 30 06:25:47 ts28 now at 25322820465391 nsecs

Full serial console logs are attached, The other hardware details can be found
in http://bugzilla.kernel.org/show_bug.cgi?id=8650

Thank you,
	Vasily Averin

View attachment "timers.log" of type "text/x-log" (39944 bytes)