public inbox for linux-kernel@vger.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: [discuss] Re: [PATCH] x86_64: Test patch for ATI/Nvidia timer problems
Date: Sun, 27 Nov 2005 15:02:13 +0100	[thread overview]
Message-ID: <200511271502.18782.rene@exactcode.de> (raw)
In-Reply-To: <20051127135325.GG20775@brahms.suse.de>

[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]

Hi,

On Sunday 27 November 2005 14:53, Andi Kleen wrote:
> On Sun, Nov 27, 2005 at 10:14:53AM +0100, Ren? Rebe wrote:
> > 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.
> 
> But it worked properly before suspend/resume without noapic? 

Without noapic the timer has about the 2x speed compared to real-time. I
only used the machien with noapic since otherwise it is barely useful.

Did you want to know if suspend/resume does behave differently without noapic?

Yours,

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

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-11-27 14:03 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
2005-11-27 12:50   ` [discuss] " Pavel Machek
2005-11-27 13:53   ` Andi Kleen
2005-11-27 14:02     ` René Rebe [this message]
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=200511271502.18782.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox