[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] Timer ISR/0: Timer went backwards error...
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@xxxxxxxxxxxxxxxxxxx > [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx]On Behalf Of Keir Fraser > Sent: Thursday, July 03, 2008 6:30 AM > To: Sandesh; xen-devel@xxxxxxxxxxxxxxxxxxx > 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@xxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx > > http://lists.xensource.com/xen-devel > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@xxxxxxxxxxxxxxxxxxx > http://lists.xensource.com/xen-devel > _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |