Message-ID: <20051118200132.jiwizt3ho0ook00w@web.mail.umich.edu>
Date: Fri, 18 Nov 2005 20:01:32 -0500
From: jstipins@umich.edu
To: linux-kernel@vger.kernel.org
Subject: AMD 64 system clock speed
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.3)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 780
Lines: 19

Hi there,

My earlier question regarding the glibc "make check" nptl/tst-clock2.c
failure turns out to be due to my system clock running 3x normal speed.

Evidently, this is a known issue with 2.6.x kernels running on AMD 64
processors.  The "noapic" boot option fixes the clock problem, but disrupts
other things... ethernet does work, etc.  The solution seems to be using
"apci=noirq noapic" as boot options.

I am using the 2.6.14.2 kernel, and still need to use those boot parameters.
What is the current state of this bug?

-Janis
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/