From: Pavel Machek <pavel@suse.cz>
To: "René Rebe" <rene@exactcode.de>
Cc: Andi Kleen <ak@suse.de>,
discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: [PATCH] x86_64: Test patch for ATI/Nvidia timer problems
Date: Sun, 27 Nov 2005 13:50:33 +0100 [thread overview]
Message-ID: <20051127125032.GA1641@elf.ucw.cz> (raw)
In-Reply-To: <200511271014.53217.rene@exactcode.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?
Unfortunately, hardware can not go to anything between.
Pavel
--
Thanks, Sharp!
next prev parent reply other threads:[~2005-11-27 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 14:20 Andi Kleen
2005-11-27 9:14 ` René Rebe
2005-11-27 12:50 ` Pavel Machek [this message]
2005-11-27 13:53 ` [discuss] " 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=20051127125032.GA1641@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rene@exactcode.de \
/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®