From: Dan Magenheimer Subject: RE: Time goes backwards in dom0 in xen-unstable Date: Wed, 15 Apr 2009 17:12:25 +0000 (GMT) Message-ID: <5f47fb38-b194-4752-a243-c67ae20ee656@default> References: <227c70ed-d4d1-4a9d-ab08-46c2c5598b9e@default> Mime-Version: 1.0 Content-Type: text/plain; charset=Windows-1252 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <227c70ed-d4d1-4a9d-ab08-46c2c5598b9e@default> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: dan.magenheimer@oracle.com, Keir Fraser , "Xen-Devel (E-mail)" , "Tian, Kevin" List-Id: xen-devel@lists.xenproject.org Double hmmm... after destroying the domain and restarting it has been running fine for over two hours. So apparently it was a coincidence. > -----Original Message----- > From: Dan Magenheimer=20 > Sent: Wednesday, April 15, 2009 8:59 AM > To: Dan Magenheimer; Keir Fraser; Xen-Devel (E-mail); Tian, Kevin > Subject: RE: [Xen-devel] Time goes backwards in dom0 in xen-unstable >=20 >=20 > Hmmm... after only a few minutes with cpuidle=3Doff, > my test domPV froze up after printing a number of > call traces starting with: >=20 > INFO: task xxx:nnn blocked for more than 480 seconds. >=20 > At the top of all of the traces is either > getnstimeofday+51 or io_schedule+44. >=20 > (Note that this PV domain is a 2.6.29 kernel... don't > know if the messages are the same on an older kernel.) >=20 > > -----Original Message----- > > From: Dan Magenheimer=20 > > Sent: Wednesday, April 15, 2009 8:22 AM > > To: Keir Fraser; Xen-Devel (E-mail); Tian, Kevin > > Subject: RE: [Xen-devel] Time goes backwards in dom0 in xen-unstable > >=20 > >=20 > > I can confirm that cpuidle=3Doff makes the timer_interrupt > > scaleability problem go away. > >=20 > > It also appears that the max cycles for the MSI > > interrupts becomes reasonably small again. Was > > this expected? > >=20 > > I'll leave it running for awhile but may not be > > able to confirm the "Time went backwards" error > > goes away as it seemed to appear only after a > > random long period of time. > >=20 > > (BTW, Kevin, hpetbroadcast did not make the problem > > go away.) > >=20 > > Dan > >=20 > > > -----Original Message----- > > > From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > > > Sent: Wednesday, April 15, 2009 1:31 AM > > > To: Dan Magenheimer; Xen-Devel (E-mail) > > > Subject: Re: [Xen-devel] Time goes backwards in dom0 in=20 > xen-unstable > > >=20 > > >=20 > > > On 14/04/2009 20:36, "Dan Magenheimer"=20 > > > wrote: > > >=20 > > > > I'm seeing some "Time went backwards" errors reported > > > > in dom0 in near-tip (c/s 19515) xen-unstable build. > > > > It's rare and random and not reproducible, but here's > > > > the report that just showed up. There was no load > > > > running at the time. > > > >=20 > > > > I can move to 3.4-rc1 if that would be helpful but I > > > > don't remember seeing any time-related changes recently. > > > >=20 > > > > This was on my dual-core test machine which reports > > > > lots of power management info during Xen boot. > > >=20 > > > If you specify 'cpuidle=3Doff' as a Xen boot parameter, does=20 > > > that make the > > > timer_interrupt scalability problem go away, and this=20 > time backwards > > > problem? I was going to enable by default in 3.4 but could go=20 > > > the other way. > > >=20 > > > -- Keir > > >=20 > > >=20 > > >=20 > > > _______________________________________________ > > > Xen-devel mailing list > > > Xen-devel@lists.xensource.com > > > http://lists.xensource.com/xen-devel > > >