public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Christopher Allen Wing <wingc@engin.umich.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: clock runs at double speed on x86_64 system w/ATI RS200 chipset (workaround for APIC mode?)
Date: 7 Apr 2005 09:37:13 +0200
Date: Thu, 7 Apr 2005 09:37:13 +0200	[thread overview]
Message-ID: <20050407073713.GA74220@muc.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0504061758150.4573@hammer.engin.umich.edu>

> 
> I'm still seeing 'APIC error on CPU0: 00(40)' messages from time to time.

Thanks for the analysis. The clear_IO_APIC_pin looks quite hackish,
I am not sure I want to put that into the mainline kernel.
The APIC errors are also suspicious.

I don't want to blacklist ATI from just a single report,
but if there are more it is probably best to just disable
the IO-APIC by default there for now.

-Andi



  reply	other threads:[~2005-04-07  7:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-03 12:31 clock runs at double speed on x86_64 system w/ATI RS200 chipset Mikael Pettersson
2005-04-04 14:53 ` Christopher Allen Wing
2005-04-04 15:32   ` Mikael Pettersson
2005-04-04 21:42     ` Christopher Allen Wing
2005-04-05 17:18   ` Andi Kleen
2005-04-05 18:02     ` Christopher Allen Wing
2005-04-05 18:31       ` Andi Kleen
2005-04-05 18:49         ` Christopher Allen Wing
2005-04-05 19:10         ` Christopher Allen Wing
2005-04-05 19:46         ` Christopher Allen Wing
2005-04-06 20:36         ` Christopher Allen Wing
2005-04-06 22:13         ` [PATCH] Re: clock runs at double speed on x86_64 system w/ATI RS200 chipset (workaround for APIC mode?) Christopher Allen Wing
2005-04-07  7:37           ` Andi Kleen [this message]
2005-04-07 17:23             ` Christopher Allen Wing
2005-04-05 18:17     ` clock runs at double speed on x86_64 system w/ATI RS200 chipset (with APIC enabled) Christopher Allen Wing

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=20050407073713.GA74220@muc.de \
    --to=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wingc@engin.umich.edu \
    /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