All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dan Magenheimer" <dan.magenheimer@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
	Sandesh <sandesh.ahiremath@wipro.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: RE: Timer ISR/0: Timer went backwards error...
Date: Thu, 3 Jul 2008 08:35:27 -0600	[thread overview]
Message-ID: <20080703083527671.00000003744@djm-pc> (raw)
In-Reply-To: <C49284C9.2380E%keir.fraser@eu.citrix.com>

Sandesh --

hpet_force was a Xen parameter in Dave Winchell's last hpet
patch that hasn't yet been accepted into the tree.  However
I think it would have only worked on hvm guests.

Xen system time's dependency on tsc is most susceptible on
pre-Barcelona SMP AMD boxes (where tsc isn't synchronized
between processors), though yours seems to have a very
bad skew.  As Keir suggests "clocksource=hpet" as
a Xen command line parameter will hopefully
work for those boxes.

Dan

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com]On Behalf Of Keir Fraser
> Sent: Thursday, July 03, 2008 6:30 AM
> To: Sandesh; xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] Timer ISR/0: Timer went backwards error...
> 
> 
> hpet_force=1 means nothing to Xen. To see what platform timer 
> is being used,
> look for a line 'Platform timer is <foo>' in Xen's boot 
> output. To change
> it, specify for example 'clocksource=hpet' as a Xen boot parameter.
> 
> 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.
> 
>  -- Keir
> 
> On 3/7/08 12:44, "Sandesh" <sandesh.ahiremath@wipro.com> wrote:
> 
> > Hi all,
> >   I am getting lots of Timer ISR/0: Timer went backwards error...
> > due to which my dom0 is crashing. I tried hpet_force=1 
> argument for xen
> > command line even then the problem presists. Other than 
> that i could not
> > find any solution on the net.
> >   Has this problem been resolved??
> >
> > Iam using AMD Athlon(tm) 64bit processor, installed with FC6 &
> > xen-3.2.0.
> >
> > 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
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

  parent reply	other threads:[~2008-07-03 14:35 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
2008-07-03 14:35   ` Dan Magenheimer [this message]
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=20080703083527671.00000003744@djm-pc \
    --to=dan.magenheimer@oracle.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=sandesh.ahiremath@wipro.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.