All of lore.kernel.org
 help / color / mirror / Atom feed
From: "René Rebe" <rene@exactcode.de>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86_64: Test patch for ATI/Nvidia timer problems
Date: Sun, 27 Nov 2005 10:14:53 +0100	[thread overview]
Message-ID: <200511271014.53217.rene@exactcode.de> (raw)
In-Reply-To: <20051126142030.GA26449@wotan.suse.de>

Hi,

On Saturday 26 November 2005 15:20, Andi Kleen wrote:
> Everybody who saw timing problems with ATI IXP based boards with x86-64
> or some Nvidia NForce4 boards please test this patch. Please send
> success/failure to me.

I try to give your patch a try on the ATI based MSI Megabook S270, today - 
however even with the workaround of "noapic" I had timer drift on resuem from 
ram if the cpu was scaled to a lower frequency when it was suspended.

The k8 cpufreq code failed to assert the current frequency and thus assumed a 
wrong one:

Restarting tasks...<3>powernow-k8: ignoring illegal change in lo freq table-0 
to 0x0
powernow-k8: transition frequency failed
 done

Also my ACPI table only has two frequency entries, 800000 and 1600000 MHz - I 
wonder if one could rework the powernow-k8 driver to interpolate values in 
between to get smoother adaption of the frequency?

Yours,

-- 
René Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany)
            http://www.exactcode.de | http://www.t2-project.org
            +49 (0)30  255 897 45

  reply	other threads:[~2005-11-27  9:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-26 14:20 [PATCH] x86_64: Test patch for ATI/Nvidia timer problems Andi Kleen
2005-11-27  9:14 ` René Rebe [this message]
2005-11-27 12:50   ` [discuss] " Pavel Machek
2005-11-27 13:53   ` Andi Kleen
2005-11-27 14:02     ` René Rebe
2005-11-27 14:11       ` Andi Kleen
2005-12-05 15:14         ` René Rebe
2005-12-08  6:16           ` Andi Kleen

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=200511271014.53217.rene@exactcode.de \
    --to=rene@exactcode.de \
    --cc=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.