From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Stefan Assmann <sassmann@redhat.com>
Cc: linux-kernel@vger.kernel.org, jcm@redhat.com,
sdietrich@novell.com, linux-acpi@vger.kernel.org,
andi@firstfloor.org, hpa@zytor.com, mingo@elte.hu,
Olaf.Dabrunz@gmx.net, ktokunag@redhat.com, tglx@linutronix.de,
lenb@kernel.org
Subject: Re: [RFC][PATCH 0/2] boot interrupts on Intel X58 and 55x0
Date: Sun, 6 Sep 2009 22:33:28 -0300 [thread overview]
Message-ID: <20090907013328.GA19670@khazad-dum.debian.net> (raw)
In-Reply-To: <20090904165525.26294.31112.sendpatchset@t500>
On Fri, 04 Sep 2009, Stefan Assmann wrote:
> is more serious namely the onboard NIC (8086:10c9) is malfunctioning on some
> of our test system if the second patch is applied. It fails to acquire an IP
> from DHCP and we're pretty clueless on this issue right now.
> Help is greatly appreciated!
Did you read Intel documet 320839-009, August/2009, already? It is at:
http://www.intel.com/Assets/PDF/specupdate/320839.pdf
I see some stuff there that might be a problem, many of the "issues" are
related to interrupt handling. Errata 40 (EOI to IOAPIC can be blocked)
even states that one should avoid the X58 IOH IOAPIC on stepping B2
completely, and use the IOAPIC in the ICH10R instead.
And the B2 stepping is the one in most motherboards (B3 is quite new).
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2009-09-07 1:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 16:55 [RFC][PATCH 0/2] boot interrupts on Intel X58 and 55x0 Stefan Assmann
2009-09-04 16:55 ` [RFC][PATCH 1/2] show Intel QuickPath Interconnect Routing and Protocol Layer Registers in PCI config space Stefan Assmann
2009-09-04 17:07 ` Yinghai Lu
2009-09-05 9:02 ` Stefan Assmann
2009-09-04 16:55 ` [RFC][PATCH 2/2] disable boot interrupts on Intel X58 and 55x0 Stefan Assmann
2009-09-04 17:06 ` Daniel Walker
2009-09-05 9:07 ` Stefan Assmann
2009-09-05 14:47 ` Daniel Walker
2009-09-05 16:18 ` Olaf Dabrunz
2009-09-05 17:07 ` Daniel Walker
2009-09-07 1:37 ` Henrique de Moraes Holschuh
2009-09-07 1:53 ` Daniel Walker
2009-09-07 1:33 ` Henrique de Moraes Holschuh [this message]
2009-09-07 8:24 ` [RFC][PATCH 0/2] " Stefan Assmann
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=20090907013328.GA19670@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=Olaf.Dabrunz@gmx.net \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=jcm@redhat.com \
--cc=ktokunag@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sassmann@redhat.com \
--cc=sdietrich@novell.com \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).