From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1EmiWn-0006TW-Ib for garchives@archives.gentoo.org; Thu, 15 Dec 2005 02:07:30 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jBF25XGV024635; Thu, 15 Dec 2005 02:05:33 GMT Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.197]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jBF23Ijg004694 for ; Thu, 15 Dec 2005 02:03:19 GMT Received: by wproxy.gmail.com with SMTP id 68so259666wri for ; Wed, 14 Dec 2005 18:03:18 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nhkmP4dGe//Oso0/zl1xjart93IDacdqZxq+PNrxIwB7V49Z8p1ahWrNWm9pYcgw1ymOXHWbPOIiLUlk2vHa8Hd3CpnJevnxWHYPTE1UGkSybzPhH8vtSyxZlFt6MFf2iC1QsU/hj3H3PNFqw76Kc/6NhEPxYeVlDQGAiJzXRp0= Received: by 10.54.122.19 with SMTP id u19mr1559901wrc; Wed, 14 Dec 2005 18:03:18 -0800 (PST) Received: by 10.54.69.9 with HTTP; Wed, 14 Dec 2005 18:03:18 -0800 (PST) Message-ID: <7573e9640512141803r799c9225yfbe802d4a58f3fb@mail.gmail.com> Date: Wed, 14 Dec 2005 19:03:18 -0700 From: Richard Fish Sender: richard.j.fish@gmail.com To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] clock problems software clock 20x fast In-Reply-To: <200512141413.57316.preludelinux@mchsi.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <200512141130.18846.preludelinux@mchsi.com> <7573e9640512140939y2ceedb36occ219469df55719d@mail.gmail.com> <200512141413.57316.preludelinux@mchsi.com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id jBF23Ijg004694 X-Archives-Salt: a47cec13-04d2-426b-b7f3-426bdb8b9d48 X-Archives-Hash: 549d06b03a4b8ca1d3ad0b88efd6a1ba On 12/14/05, Noah J Norris wrote: > On Wednesday 14 December 2005 05:39 pm, Richard Fish wrote: > > 1. Make sure that the first line of /etc/adjtime contains very small > > values. In fact, you might just want to replace the first line with > > "0.0 0 0.0". > i tried changeing this is this for the hardware clock drift ? i dont have any > problem with the hardware clock its the software clock thats fast Oh, you are correct. Sorry. > > > > 2. Take a look at the clock= settings in > > /usr/src/linux/Documentation/kernel-parameters.txt. Maybe you need > > clock=pit. > > looking in this file saw some other options that may help the problem. > i have an ati chipset (newer laptop chipset) ouput of lspci below > > > some options i saw in that file that i may try > > acpi_skip_timer_override [HW,ACPI] > Recognize and ignore IRQ0/pin2 Interrupt Override. > For broken nForce2 BIOS resulting in XT-PIC timer. > > enable_timer_pin_1 [i386,x86-64] > Enable PIN 1 of APIC timer > Can be useful to work around chipset bugs > (in particular on some ATI chipsets). > The kernel tries to set a reasonable default. > > disable_timer_pin_1 [i386,x86-64] > Disable PIN 1 of APIC timer > Can be useful to work around chipset bugs. I'm not sure these will help. They seem to be more related to setting up the frequency for the IRQ0 timer interrupt, for things like running the scheduler. This should not be related at all to the behavior of gettimeofday. I think if you were getting messages about lost ticks or got extra ticks or something like that, these might be helpful, or if your system seemed either to slow or too unresponsive. Of course, if your clock is defaulting to TSC (which would be bad, BTW), then I guess these could have a big impact. Take a look at dmesg or /var/log/messages for the following lines: Using TSC for gettimeofday Using HPET for gettimeofday Using .* for high-res timesource These will tell us what signal the kernel is using for gettimeofday on your system. -Richard -- gentoo-user@gentoo.org mailing list