From: Sandesh <sandesh.ahiremath@wipro.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Timer ISR/0: Timer went backwards error...
Date: Thu, 03 Jul 2008 18:39:27 +0530 [thread overview]
Message-ID: <1215090567.4299.9.camel@ec4t16cg-1518809> (raw)
In-Reply-To: <C49284C9.2380E%keir.fraser@eu.citrix.com>
On Thu, 2008-07-03 at 13:29 +0100, Keir Fraser wrote:
>
> Could you also send a few of the 'went backwards' messages, so we can
> see
> how badly time is getting skewed. Perhaps we can work out where the
> issue
> arises from too -- it seems that a significant proprotion of those who
> have
> issues with these messages are seeing them on AMD boxes. I haven't
> confirmed
> the correlation though.
here is the log...repeated many times...
Timer ISR/0: Time went backwards: delta=-9201298748592621662 delta_cpu=-9201298748582621662 shadow=73000238797 off=-9201298747702859870 processed=73890000000 cpu_processed=73880000000
0: 73880000000
Timer ISR/0: Time went backwards: delta=-9201298748575066948 delta_cpu=-9201298748565066948 shadow=73000238797 off=-9201298747685305644 processed=73890000000 cpu_processed=73880000000
0: 73880000000
Timer ISR/0: Time went backwards: delta=-9201298748557613457 delta_cpu=-9201298748547613457 shadow=73000238797 off=-9201298747667852175 processed=73890000000 cpu_processed=73880000000
0: 73880000000
Timer ISR/0: Time went backwards: delta=-9201298748540109642 delta_cpu=-9201298748530109642 shadow=73000238797 off=-9201298747650348375 processed=73890000000 cpu_processed=73880000000
0: 73880000000
Thanks,
Sandesh
Please do not print this email unless it is absolutely necessary.
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
www.wipro.com
next prev parent reply other threads:[~2008-07-03 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 11:44 Timer ISR/0: Timer went backwards error Sandesh
2008-07-03 12:29 ` Keir Fraser
2008-07-03 13:09 ` Sandesh [this message]
2008-07-03 14:35 ` Dan Magenheimer
2008-07-03 16:43 ` Sandesh
2008-07-03 20:40 ` Mukesh Rathor
2008-07-03 22:56 ` Keir Fraser
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=1215090567.4299.9.camel@ec4t16cg-1518809 \
--to=sandesh.ahiremath@wipro.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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.