From: jerome lacoste <jerome.lacoste@gmail.com>
To: john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Marie-Helene Lacoste <manies@tele2.fr>
Subject: Re: 2.6.12.3 clock drifting twice too fast (amd64)
Date: Mon, 6 Feb 2006 18:02:24 +0100 [thread overview]
Message-ID: <5a2cf1f60602060902t40e9dd9fs9574cff2c746d552@mail.gmail.com> (raw)
In-Reply-To: <5a2cf1f605081616116ba521ab@mail.gmail.com>
On 8/17/05, jerome lacoste <jerome.lacoste@gmail.com> wrote:
> On 8/16/05, john stultz <johnstul@us.ibm.com> wrote:
> > On Tue, 2005-08-16 at 12:10 +0200, jerome lacoste wrote:
> > > Installed stock 2.6.12.3 on a brand new amd64 box with an Asus extreme
> > > AX 300 SE/t mainboard.
> > >
> > > I remember seeing a message in the boot saying something along:
> > >
> > > "cannot connect to hardware clock."
> > >
> > > And now I see that the time is changing too fast (about 2 seconds each second).
> > [snip]
> > > 0000:00:00.0 Host bridge: ATI Technologies Inc: Unknown device 5951
> >
> > Looks like the AMD/ATI bug.
> >
> > http://bugzilla.kernel.org/show_bug.cgi?id=3927
>
> Sounds like it. I will have to try the patch.
>
> Good catch John!
Didn't have time to try the patch as my disk died. I installed a fresh
ubuntu with 2.6.12 (+ vendor patches) instead of 2.6.12.3, and the
issue disappeared.
So maybe ubuntu backported the aforementionned fix to their kernel.
Anyway, one less thing to worry.
jerome
prev parent reply other threads:[~2006-02-06 17:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 10:10 jerome lacoste
2005-08-16 18:05 ` Christoph Lameter
2005-08-16 21:15 ` jerome lacoste
2005-08-16 23:17 ` Jeff Mahoney
2005-08-17 6:48 ` yhlu
2005-08-17 13:20 ` Jeff Mahoney
2005-08-17 15:11 ` yhlu
2005-08-16 21:41 ` john stultz
2005-08-16 23:11 ` jerome lacoste
2006-02-06 17:02 ` jerome lacoste [this message]
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=5a2cf1f60602060902t40e9dd9fs9574cff2c746d552@mail.gmail.com \
--to=jerome.lacoste@gmail.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manies@tele2.fr \
/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
all inboxes | Powered by JetHome®