From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTP id 042B0DDE3E for ; Sat, 19 Jan 2008 10:16:53 +1100 (EST) Message-ID: <47913371.3040908@freescale.com> Date: Fri, 18 Jan 2008 17:17:05 -0600 From: Scott Wood MIME-Version: 1.0 To: DI BACCO ANTONIO - technolabs Subject: Re: ping 127.0.0.1 takes too much References: <47912CDA.9020603@freescale.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , DI BACCO ANTONIO - technolabs wrote: > > >Are you sure the timebase clock is what the kernel thinks it is? Does > >the time-of-day clock progress at the correct rate? > > The kernel receives the CPU clock from the bdinfo structure and thus I > think the kernel knows how fast the CPU is. That wasn't what I asked. I asked whether you checked whether it was actually correct or not. I've seen it be wrong quite often. -Scott