From: Vasily Averin <vvs@sw.ru>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
devel@openvz.org
Subject: Re: [2.6.22] negative time jump
Date: Mon, 30 Jul 2007 16:51:38 +0400 [thread overview]
Message-ID: <46ADDEDA.1070201@sw.ru> (raw)
In-Reply-To: <46AD57BF.8090106@sw.ru>
Groundhog Day?
Vasily Averin wrote:
> [root@ts28 ~]# echo 1 > /proc/timer_stats
> [root@ts28 ~]# cat /proc/timer_stats
> Timer Stats Version: v0.1
> Sample period: 17.992 s
> 0 total events
> [root@ts28 ~]# cat /proc/timer_stats
> Timer Stats Version: v0.1
> Sample period: -4366.278 s
> 0 total events
> [root@ts28 ~]# cat /proc/timer_stats
> Timer Stats Version: v0.1
> Sample period: -4359.840 s
> 0 total events
[root@ts28 ~]# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: -5.060 s
0 total events
[root@ts28 ~]# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: 0.365 s
0 total events
[root@ts28 ~]# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: 8.675 s
0 total events
[root@ts28 ~]# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: -4355.978 s
0 total events
[skip]
next loop:
[root@ts28 ~]# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: 9.968 s
0 total events
[root@ts28 ~]# echo q > /proc/sysrq-trigger
Jul 30 11:10:17 ts28 now at 29196596844685 nsecs
[root@ts28 ~]# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: 14.104 s
0 total events
[root@ts28 ~]# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: 17.666 s
0 total events
[root@ts28 ~]# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: 19.791 s
0 total events
[root@ts28 ~]# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: 21.278 s
0 total events
[root@ts28 ~]# echo q > /proc/sysrq-trigger
Jul 30 11:10:28 ts28 now at 24810199356545 nsecs
[root@ts28 ~]# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: -4373.161 s
0 total events
Node is still alive and I'm able to look at proc files and press sysrq keys.
Thank you,
Vasily Averin
next prev parent reply other threads:[~2007-07-30 10:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 3:15 [2.6.22] negative time jump Vasily Averin
2007-07-30 12:51 ` Vasily Averin [this message]
[not found] ` <1f1b08da0707301113r173adba0yd2585263e89fd8@mail.gmail.com>
2007-07-31 1:07 ` john stultz
2007-07-31 4:43 ` Vasily Averin
2007-08-02 9:34 ` broken timer on VIA K8T800 chipset? Vasily Averin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46ADDEDA.1070201@sw.ru \
--to=vvs@sw.ru \
--cc=akpm@linux-foundation.org \
--cc=devel@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.