From: Greg KH <gregkh@suse.de>
To: Oliver Neukum <oliver@neukum.org>
Cc: ak@suse.de, acpi-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: Clock going way too fast on 2.6.15 for amd64 processor
Date: Wed, 4 Jan 2006 16:28:18 -0800 [thread overview]
Message-ID: <20060105002818.GA9019@suse.de> (raw)
In-Reply-To: <200601050054.45824.oliver@neukum.org>
On Thu, Jan 05, 2006 at 12:54:45AM +0100, Oliver Neukum wrote:
> Am Donnerstag, 5. Januar 2006 00:39 schrieb Greg KH:
> > Hi,
> >
> > I tried digging through the mess in
> > http://bugzilla.kernel.org/show_bug.cgi?id=3927
> > but got lost in a see of conflicting patches.
> >
> > I too have a amd64 box that is showing that the clock is running way too
> > fast (feels about double speed, haven't checked for sure.) I'm running
> > it in 32bit mode for now, and the boot dmesg is below.
> >
> > Any hints on patches that I should test out to try to track this down?
> > I haven't run any real old kernels on it to see if it is something new
> > (shows up on a 2.6.13 and 2.6.14 kernel too.)
>
> Did you try "disable_timer_pin_1" on the kernel command line?
Nice, that worked just fine, no kernel patch needed. Thanks for
pointing it out to me, I totally missed it.
Now to go fix the usb irq "ignore" issue for this machine, and I'll be
able to switch to using it all the time...
greg k-h
next prev parent reply other threads:[~2006-01-05 0:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 23:39 Clock going way too fast on 2.6.15 for amd64 processor Greg KH
2006-01-04 23:54 ` Oliver Neukum
2006-01-05 0:28 ` Greg KH [this message]
2006-01-05 0:40 ` Oliver Neukum
2006-01-05 3:42 ` Dave Jones
2006-01-05 4:27 ` Kurt Wall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060105002818.GA9019@suse.de \
--to=gregkh@suse.de \
--cc=acpi-devel@lists.sourceforge.net \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox