From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com, keir.fraser@eu.citrix.com
Cc: konrad.wilk@oracle.com
Subject: [PATCH 0 of 1] Intel VT-d fix.
Date: Tue, 09 Mar 2010 12:04:00 -0500 [thread overview]
Message-ID: <patchbomb.1268154240@phenom.dumpdata.com> (raw)
On a SuperMicro X8DTN+ I found Linux baremetal booting fine, while
Xen would hang while enabling PCI-X devices, such as:
(XEN) CPU 10 initiali[ 5.118255] scsi0 : 3ware Storage Controller
[ 5.118898] 3w-xxxx: scsi0: Found a 3ware Storage Controller at 0xc100, IRQ: 52.
(XEN) do_IRQ: 1.40 No irq handler for vector (irq -1)
[ 25.711139] scsi 0:0:0:0: WARNING: Command (0x12) timed out, resetting card.
[ 47.191274] scsi 0:0:0:0: WARNING: Command (0x0) timed out, resetting card.
[ 58.671124] scsi 0:0:0:0: Device offlined - not ready after error recovery
[ 79.711194] scsi 0:0:1:0: WARNING: Command (0x12) timed out, resetting card.
[ 101.191071] scsi 0:0:1:0: WARNING: Command (0x0) timed out, resetting card.
[ 112.671065] scsi 0:0:1:0: Device offlined - not ready after error recovery
[ 133.710995] scsi 0:0:2:0: WARNING: Command (0x12) timed out, resetting card.
[ 155.190891] scsi 0:0:2:0: WARNING: Command (0x0) timed out, resetting card.
Traced it down the fact that I've three IOAPICs, but only one DRHD. The
DRHD covers the first IOAPIC, but not the other two. Well, the PCI-X device
was on the last IOAPIC, which was not under the DRHD control.
Linux upstream has a check where it looks for all the IOAPICs covered by the DRHDs
and compares them with the IOAPICs it found via MADT. If the count is off it
disables x2APIC.
This patch follows that logic.
next reply other threads:[~2010-03-09 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 17:04 Konrad Rzeszutek Wilk [this message]
2010-03-09 17:04 ` [PATCH 1 of 1] Intel VT-D: Don't turn x2APIC if there is a missing DRHD entry for the IOAPIC Konrad Rzeszutek Wilk
2010-03-11 6:04 ` Alex Williamson
2010-03-11 20:25 ` Konrad Rzeszutek Wilk
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=patchbomb.1268154240@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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.