From: "Justin Piszcz" <jpiszcz@lucidpixels.com>
To: "'Bruno Prémont'" <bonbons@linux-vserver.org>
Cc: <support@Supermicro.com>, <linux-kernel@vger.kernel.org>
Subject: RE: Supermicro X9SRL-F - channel enumeration error & ACPI/firmware bug question
Date: Mon, 26 Nov 2012 19:50:30 -0500 [thread overview]
Message-ID: <002901cdcc39$33ae8550$9b0b8ff0$@lucidpixels.com> (raw)
In-Reply-To: <20121126224245.248f0901@neptune.home>
> [ 0.696357] ioatdma: Intel(R) QuickData Technology Driver 4.00
> [ 0.696487] ioatdma 0000:00:04.0: channel error register unreachable
> I assume this is something Supermicro has to fix?
You are probably missing some kernel config option(s) :) - I did fight
similar
issues on a Fujitsu SandyBridge Xeon based server.
Check if enabling CONFIG_X86_X2APIC helps as well as other APIC/IOMMU
options.
Bruno
=> Enabled:
CONFIG_IOMMU_SUPPORT
CONFIG_INTEL_IOMMU
CONFIG_INTEL_IOMMU_DEFAULT_ON
CONFIG_IRQ_REMAP
Also tried enabling NUMA, etc:
[ 0.330998] ACPI FADT declares the system doesn't support PCIe ASPM, so
disable it
[ 0.331068] ACPI: bus type pci registered
[ 0.615234] ACPI: Dynamic OEM Table Load:
[ 0.615373] ACPI: PRAD (null) 000BE (v02 PRADID PRADTID
00000001 MSFT 04000000)
[ 0.615631] \_SB_:_OSC invalid UUID
[ 0.615633] _OSC request data:1 7
[ 0.663138] pci 0000:ff:13.5: [8086:3c44] type 00 class 0x110100
[ 0.663170] pci 0000:ff:13.6: [8086:3c45] type 00 class 0x088000
[ 0.663211] pci0000:ff: ACPI _OSC support notification failed, disabling
PCIe ASPM
[ 0.663281] pci0000:ff: Unable to request _OSC control (_OSC support
mask: 0x08)
:(
Justin.
next prev parent reply other threads:[~2012-11-27 0:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 19:40 Supermicro X9SRL-F - channel enumeration error & ACPI/firmware bug question Justin Piszcz
2012-11-26 21:42 ` Bruno Prémont
2012-11-27 0:50 ` Justin Piszcz [this message]
2012-11-27 0:56 ` Bjorn Helgaas
2012-11-27 1:00 ` Bjorn Helgaas
2012-11-27 1:00 ` Justin Piszcz
2012-11-27 1:11 ` Bjorn Helgaas
2012-11-27 13:33 ` Justin Piszcz
2012-11-27 13:49 ` Justin Piszcz
2012-11-27 13:56 ` Justin Piszcz
2012-11-27 14:35 ` Justin Piszcz
2012-11-29 0:08 ` Bjorn Helgaas
2012-11-29 0:49 ` Justin Piszcz
2012-11-28 23:54 ` Bjorn Helgaas
2012-11-29 0:48 ` Justin Piszcz
2012-11-29 0:34 ` Robert Hancock
2012-11-29 0:49 ` Justin Piszcz
2012-11-29 0:55 ` Robert Hancock
2012-11-29 8:55 ` Justin Piszcz
2012-11-29 18:16 ` Bjorn Helgaas
2012-11-30 2:39 ` Robert Hancock
2012-11-30 3:38 ` Bjorn Helgaas
2012-12-02 13:26 ` Joerg Roedel
2012-11-27 1:11 ` Dan Williams
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='002901cdcc39$33ae8550$9b0b8ff0$@lucidpixels.com' \
--to=jpiszcz@lucidpixels.com \
--cc=bonbons@linux-vserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=support@Supermicro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox