From: Mike Fowler <linux-smp@mlfowler.com>
To: Ian Brandt <ian@ianbrandt.com>
Cc: Linux SMP <linux-smp@vger.kernel.org>
Subject: Re: I/O APIC: AMD Errata #22 may be present.
Date: Tue, 25 Oct 2005 10:48:07 +0000 [thread overview]
Message-ID: <435E0D67.9030505@mlfowler.com> (raw)
In-Reply-To: <435D5670.1070803@ianbrandt.com>
Ian,
I hava two Athlon MP 1.4 processors with the same errata present. I've
used the noapic option without any "noticeable" performance loss. I say
"noticeable" as I have not done any performance tests to qualify that
statement, but it certainly hasn't hindered me in any way.
Hope this helps!
> Hi,
>
> I have an Appro 1124s server with a Tyan Thunder K7 S2462 motherboard,
> two AMD Athlon MP 1600 processors, the 760 MP chipset, and a single
> PCI device that is an Adaptec 2100S SCSI RAID controller (on a PCI
> riser/adapter of unknown origin). I've just upgraded to 2.6.13, and
> occasionally my server fails to boot. It seems to hang at this line:
>
> I/O APIC: AMD Errata #22 may be present. In the event of instability
> try booting with the "noapic" option.
>
> That line is however present in my kernel messages even on a
> successful boot. My entire dmesg from a successful boot,
> /proc/interrupts, and proc/cpuinfo are below.
>
> I've read Documentation/i386/IO-APIC.txt and have a vague
> understanding of what it means. I will certainly try the noapic
> option to see if things settle down, but is there any real world
> performance loss in doing so? Should I be looking into using "...the
> pirq= boot parameter to 'hand-construct' IRQ entries"? Is there
> anything else I could do to help squash this bug?
>
> Thanks!
>
> Ian
>
[snip]
--
Mike Fowler
Registered Linux user: 379787
"I could be a genius if I just put my mind to it, and I,
I could do anything, if only I could get 'round to it"
-PULP 'Glory Days'
prev parent reply other threads:[~2005-10-25 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 21:47 I/O APIC: AMD Errata #22 may be present Ian Brandt
2005-10-25 10:48 ` Mike Fowler [this message]
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=435E0D67.9030505@mlfowler.com \
--to=linux-smp@mlfowler.com \
--cc=ian@ianbrandt.com \
--cc=linux-smp@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.