Feb 23rd here in Australia.

The system is still running flawlessly since turning off all power saving in 
the BIOS. Looks like the power saving stuff in the BIOS for AMD processors 
could be the issue with the clocksource.

Cheers
V

On Fri, 24 Dec 2010 02:10:54 pm Virgil wrote:
> Just a quick pre-xmas report:
> 
> Since turning off all power saving in the BIOS, everything has worked
> flawlessly (now that I've emailed this I'm sure the entire system will
> blow up....).
> 
> So far so good.
> 
> Cheers and merry Xmas
> V.
> 
> On Wed, 15 Dec 2010 01:56:31 pm Virgil wrote:
> > Hi Pasi,
> > 
> > I gave up on the idea of using jiffies as the clocksource.
> > 
> > I was unable to get ntpd to lock onto any time sources with clocksource
> > set to jiffies. The jitter and offsets just went crazy.
> > 
> > I'm now turning off all power saving in the bios and reverting to the
> > default clocksource. I read that the xen time source attempts to do
> > "stuff" if it reckons some ticks went missing. Apparently a cause of
> > missing TSC ticks can be going to sleep on some CPUs.... who knows.
> > Something to do with the max_cstate.
> > 
> > Cheers
> > V
> > 
> > On Tue, 14 Dec 2010 06:07:57 am Pasi Kärkkäinen wrote:
> > > On Mon, Dec 13, 2010 at 11:30:35AM +1100, Virgil wrote:
> > > > Found this in /var/log/messages as the last thing prior to death.
> > > > 
> > > > Clocksource tsc unstable
> > > > 
> > > > Did some Googling and found some people changed the dom0 clocksource.
> > > > 
> > > > Added clocksource=jiffies to the kernel commandline.
> > > 
> > > I believe jiffies is not a very good clocksource..
> > > 
> > > -- Pasi
> > > 
> > > > Will see if it does anything.....
> > > > 
> > > > V
> > > > 
> > > > On Wed, 17 Nov 2010 12:00:01 pm Virgil wrote:
> > > > > Host crashed. Running HVM fc14-32.
> > > > > 
> > > > > Skipping 86000 seconds.
> > > > > Skipping 86000 seconds.
> > > > > Skipping 86000 seconds.
> > > > > Skipping 86000 seconds.
> > > > > Skipping 86000 seconds.
> > > > > Skipping 86000 seconds.
> > > > > Skipping 86000 seconds.
> > > > > ...
> > > > > ...
> > > > > ...
> > > > > ...
> > > > > Kaboom
> > > > > 
> > > > > Cheers
> > > > > V
> > > > > 
> > > > > On Mon, 8 Nov 2010 07:43:36 am M A Young wrote:
> > > > > > I have built another 2.6.32.x based kernel
> > > > > > (2.6.32.25-172.xendom0.fc12) at
> > > > > > http://koji.fedoraproject.org/koji/taskinfo?taskID=2583536 and
> > > > > > the repository
> > > > > > http://repos.fedorapeople.org/repos/myoung/dom0-kernel/ . This
> > > > > > updates the kernel from 2.6.32.25-rc1 to 2.6.32.25 (which may
> > > > > > not actually change anything), and uses a later version of
> > > > > > xen/stable-2.6.3.32.x which adds a couple of xen fixes.
> > > > > > 
> > > > > >     Michael Young
> > > > > > 
> > > > > > --
> > > > > > xen mailing list
> > > > > > xen@lists.fedoraproject.org
> > > > > > https://admin.fedoraproject.org/mailman/listinfo/xen
> > > > > 
> > > > > --
> > > > > xen mailing list
> > > > > xen@lists.fedoraproject.org
> > > > > https://admin.fedoraproject.org/mailman/listinfo/xen
> > > > 
> > > > --
> > > > xen mailing list
> > > > xen@lists.fedoraproject.org
> > > > https://admin.fedoraproject.org/mailman/listinfo/xen
> > 
> > --
> > xen mailing list
> > xen@lists.fedoraproject.org
> > https://admin.fedoraproject.org/mailman/listinfo/xen
> 
> --
> xen mailing list
> xen@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/xen
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Reply via email to