nForce4 and Ubuntu

[Darryl Clarke]

On 11/25/05, ulrich steffens <ulrich at barfuss-jerusalem.org> wrote:
> Am Donnerstag, den 24.11.2005, 19:04 +0100 schrieb Jean-Eric Cuendet:
> >  > I just did a little upgrade.
> >  >
> >  > I got an AMD64 Dual Core 3800+ on a Gigabyte A8N-SLI (nForce4) board
> >  > and it too works fantastic....
> >  >
> >  > except:  the kernel has a timer issue.  (apparenly fixed in 2.6.14+,
> >  > but that is beyond breezy).  Have you experienced any 'fast clock'
> >  > issues yet?
> >
> > I had no issues. Which kind of timer? Disk? CPU?
> > And what is "fast clock"?
> >
> i think he means that bug that mostly amd users suffer:
>
> ulrich at rockarolla:~$ uptime
>  14:13:38 up 1 day, 16:06,  3 users,  load average: 0.02, 0.24, 0.31
>
> ulrich at rockarolla:~$ date
> Fr Nov 25 14:14:10 CET 2005
>
> ulrich at rockarolla:~$ sudo /etc/init.d/ntpdate start
> Password:
>  * Synchronizing clock to ntp.ubuntulinux.org...                 [ ok ]
>
> ulrich at rockarolla:~$ date
> Fr Nov 25 13:57:13 CET 2005
>
> i definetly think he meant this bug :)

Yup, that's the one :)

It's quite funny, when i put my system under a heavy load (say,
running UT2004 or Quake4) the seconds on my clock just start running
like mad.  It's amusing more than it is annoying.  ntp has done ok
with keeping my actual clock in sync.  It's just on occasion (again,
under load) where things such as my keyboard input goes into turbo
because of this timer issue.

I'm patient enough to wait. Hopefully there'll be a backport of a
newer kernel (It's in Dapper already) which is supposed to fix this.

--
~ Darryl  ~ smartssa at gmail.com
http://smartssa.com / http://darrylclarke.com