All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Suppress APIC errors on UP x86-64.
Date: Thu, 23 Feb 2006 21:27:01 -0500	[thread overview]
Message-ID: <20060224022701.GJ23471@redhat.com> (raw)
In-Reply-To: <200602240318.12239.ak@suse.de>

On Fri, Feb 24, 2006 at 03:18:11AM +0100, Andi Kleen wrote:
 > On Friday 24 February 2006 02:53, Dave Jones wrote:
 > > On Fri, Feb 24, 2006 at 02:45:29AM +0100, Andi Kleen wrote:
 > >  > On Friday 24 February 2006 02:42, Dave Jones wrote:
 > >  > > Quite a few UP x86-64 laptops print APIC error 40's repeatedly
 > >  > > when they run an SMP kernel (And Fedora doesn't ship a UP x86-64 kernel
 > >  > > any more).  We can suppress this as there's not really anything we
 > >  > > can do about them.
 > >  > 
 > >  > No we need to fix the APIC errors, not hide them.
 > > 
 > > What do you need to fix them ?  I've got one laptop here that
 > > is affected, and there's a few other examples with dmesg's
 > > in Red Hat bugzilla that I can trawl.
 > 
 > Some pattern analysis would be useful. All the same chipset, revision?

>From first impression, it seems they're all (including mine) HP laptops
with ATI chipsets.

A quick google seems to confirm this.
http://www.google.com/search?&q=HP+%22apic+error%22

I wonder if this is related at all to the 'time goes double speed'
bug that some folks see (incidentally, I don't on mine).

 > Best you collect boot logs.

I'll try to gather some more data.

		Dave

  reply	other threads:[~2006-02-24  2:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24  1:42 Suppress APIC errors on UP x86-64 Dave Jones
2006-02-24  1:45 ` Andi Kleen
2006-02-24  1:53   ` Dave Jones
2006-02-24  2:18     ` Andi Kleen
2006-02-24  2:27       ` Dave Jones [this message]
2006-02-24  2:37         ` Andi Kleen
2006-02-24 22:56         ` Chris Ball

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=20060224022701.GJ23471@redhat.com \
    --to=davej@redhat.com \
    --cc=ak@suse.de \
    --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.