From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Kinzler Subject: Re: Possible hint for "Clocksource tsc unstable" problem Date: Fri, 02 Dec 2011 20:53:14 +0100 Message-ID: <4ED92CAA.2040008@hfp.de> References: <4E9D94A0.10102@hfp.de> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; Format="flowed" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com Cc: tp@turtle-entertainment.de, Olivier Hanesse , Philippe.Simonet@swisscom.com List-Id: xen-devel@lists.xenproject.org On 01.12.2011 08:49, Olivier Hanesse wrote: > good news ! > Is your "test system" the same hardware as before ? > For example, I don't have time issue with processor having the > 'nonstop_tsc' flag. > I got only time issue on older processor (Xeon L5420 for example) Sorry, but my report was on a machine with Xeon E5620 (has nonstop_tsc). = I did some tests to reproduce the behavior by blocking NTP traffic via = iptables but the problem did not reproduce in a lab setting. Regards Andreas > *From:*Olivier Hanesse [mailto:olivier.hanesse@gmail.com > ] > *Sent:* Wednesday, October 19, 2011 2:48 PM > *To:* Thomas P=F6hler > *Cc:* Simonet Philippe, ITS-SDL-EIS-CNV-DLE-TLC; ml-xen-devel@hfp.de > > *Subject:* Re: [Xen-devel] Possible hint for "Clocksource tsc > unstable" problem____ > > __ __ > > Hi,____ > > __ __ > > Same here.____ > > I am using ntpd in dom0 too (lenny version so 4.2.4)____ > > __ __ > > Regards____ > > __ __ > > Olivier____ > > __ __ > > 2011/10/19 Thomas P=F6hler >____ > > Hi Philippe, > > we are using ntpd in Dom0 too. (also ntpd - NTP daemon program - > Ver. 4.2.6p2). > We are monitoring ntp over a nagios plugin, check_ntp > > Regards > Thomas > > -----Urspr=FCngliche Nachricht----- > Von: Philippe.Simonet@swisscom.com > > [mailto:Philippe.Simonet@swisscom.com > ] > Gesendet: Mittwoch, 19. Oktober 2011 14:40 > An: olivier.hanesse@gmail.com ; > Thomas P=F6hler > Cc: ml-xen-devel@hfp.de > Betreff: RE: [Xen-devel] Possible hint for "Clocksource tsc > unstable" problem____ > > > Hi Olivier and Thomas > > andreas ist using ntpd in DOM0, myself too (ntpd - NTP daemon > program - Ver. 4.2.6p2) > > and you ? > > @andreas : how do you turn on your ntp logging ? > > Philippe > > > > -----Original Message----- > > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel- > > > bounces@lists.xensource.com ] > On Behalf Of Andreas Kinzler > > Sent: Tuesday, October 18, 2011 5:01 PM > > To: xen-devel@lists.xensource.com > > > Subject: [Xen-devel] Possible hint for "Clocksource tsc unstable" > problem > > > > Hello, > > > > I made an interesting observation related to the "Clocksource tsc > > unstable (delta =3D -2999660320319 ns)" problem. In the log of ntpd > I found: > > > > Oct 5 03:46:35 greenville-dom0 ntpd[4020]: kernel time sync status > > change 6001 > > Oct 5 04:03:41 greenville-dom0 ntpd[4020]: kernel time sync status > > change 2001 > > Oct 5 05:29:03 greenville-dom0 ntpd[4020]: kernel time sync status > > change 6001 > > Oct 5 05:46:09 greenville-dom0 ntpd[4020]: kernel time sync status > > change 2001 > > Oct 5 06:54:30 greenville-dom0 ntpd[4020]: synchronized to > > 192.53.103.104 , stratum 1 > > Oct 5 06:54:30 greenville-dom0 ntpd[4020]: kernel time sync status > > change 6001 > > Oct 5 07:28:22 greenville-dom0 ntpd[4020]: kernel time sync status > > change 2001 > > Oct 5 08:19:35 greenville-dom0 ntpd[4020]: synchronized to > > 192.53.103.108 , stratum 1 > > Oct 5 10:53:26 greenville-dom0 ntpd[4020]: kernel time sync status > > change 6001 > > Oct 5 11:27:32 greenville-dom0 ntpd[4020]: kernel time sync status > > change 2001 > > Oct 5 12:01:41 greenville-dom0 ntpd[4020]: kernel time sync status > > change 6001 > > Oct 5 12:18:44 greenville-dom0 ntpd[4020]: kernel time sync status > > change 2001 > > Oct 5 13:09:58 greenville-dom0 ntpd[4020]: kernel time sync status > > change 6001 > > Oct 5 13:27:04 greenville-dom0 ntpd[4020]: kernel time sync status > > change 2001 > > Oct 5 15:26:37 greenville-dom0 ntpd[4020]: kernel time sync status > > change 6001 > > Oct 5 15:43:41 greenville-dom0 ntpd[4020]: kernel time sync status > > change 2001 > > Oct 5 17:43:11 greenville-dom0 ntpd[4020]: kernel time sync status > > change 6001 > > Oct 5 19:08:31 greenville-dom0 ntpd[4020]: synchronized to > > 192.53.103.104 , stratum 1 > > Oct 5 19:08:31 greenville-dom0 ntpd[4020]: kernel time sync status > > change 2001 > > Oct 5 21:23:58 greenville-dom0 ntpd[4020]: no servers reachable > > Oct 5 21:40:58 greenville-dom0 ntpd[4020]: synchronized to > > 192.53.103.104 , stratum 1 > > Oct 5 21:40:58 greenville-dom0 ntpd[4020]: time correction of -30= 00 > > seconds exceeds sanity limit (1000); set clock manually to the > correct > > UTC time. > > > > I had the problem twice on different machines but everytime I saw = the > > line "no servers reachable". Could ntpd and/or linux kernel make s= ome > > stupid stuff when ntp upstream servers are unreachable? > > > > Regards Andreas > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel____ > > __ __ > >