From: "Justin Piszcz" <jpiszcz@lucidpixels.com>
To: "'Bjorn Helgaas'" <bhelgaas@google.com>,
"'Robert Hancock'" <hancockrwd@gmail.com>
Cc: "'Bruno Prémont'" <bonbons@linux-vserver.org>,
support@supermicro.com, linux-kernel@vger.kernel.org,
"'Dan Williams'" <djbw@fb.com>
Subject: RE: Supermicro X9SRL-F - channel enumeration error & ACPI/firmware bug question
Date: Wed, 28 Nov 2012 19:48:50 -0500 [thread overview]
Message-ID: <04b101cdcdcb$4cd6c090$e68441b0$@lucidpixels.com> (raw)
In-Reply-To: <CAErSpo6h4sOmmanXBE3EHBDh2u4yNbpMcs6p05XG1nrO2rwvXg@mail.gmail.com>
-----Original Message-----
From: Bjorn Helgaas [mailto:bhelgaas@google.com]
Sent: Wednesday, November 28, 2012 6:54 PM
To: Justin Piszcz
Cc: Bruno Prémont; support@supermicro.com; linux-kernel@vger.kernel.org; Dan
Williams
Subject: Re: Supermicro X9SRL-F - channel enumeration error & ACPI/firmware
bug question
On Tue, Nov 27, 2012 at 6:49 AM, Justin Piszcz <jpiszcz@lucidpixels.com>
wrote:
>
>> It looks like maybe you don't have CONFIG_PCI_MMCONFIG turned on?
>
> ===> FOR I/OAT DMA
> Latest status, it _appears_ its working on the X9SRL-F now, thank you!
>
> 1) Supermicro X9SRL-F (GOOD)
> [ 0.738510] ioatdma: Intel(R) QuickData Technology Driver 4.00
> [ 0.738719] ioatdma 0000:00:04.0: irq 75 for MSI/MSI-X
> [ 0.739088] ioatdma 0000:00:04.1: irq 76 for MSI/MSI-X
> [ 0.739408] ioatdma 0000:00:04.2: irq 77 for MSI/MSI-X
> [ 0.739739] ioatdma 0000:00:04.3: irq 78 for MSI/MSI-X
> [ 0.740040] ioatdma 0000:00:04.4: irq 79 for MSI/MSI-X
> [ 0.740342] ioatdma 0000:00:04.5: irq 80 for MSI/MSI-X
> [ 0.740670] ioatdma 0000:00:04.6: irq 81 for MSI/MSI-X
> [ 0.740971] ioatdma 0000:00:04.7: irq 82 for MSI/MSI-X
Good. You have two issues, and I'm going to separate them and only
address the first one here. I opened a bug report [1] against the
IOAT driver. It should do something more useful when
CONFIG_PCI_MMCONFIG=n so we don't have to debug this again in the
future. But otherwise, it sounds like this issue is resolved.
[1] https://bugzilla.kernel.org/show_bug.cgi?id=51101
--
Yes--(agree w/ config option) Thank you!
Justin.
next prev parent reply other threads:[~2012-11-29 0:48 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
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 [this message]
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='04b101cdcdcb$4cd6c090$e68441b0$@lucidpixels.com' \
--to=jpiszcz@lucidpixels.com \
--cc=bhelgaas@google.com \
--cc=bonbons@linux-vserver.org \
--cc=djbw@fb.com \
--cc=hancockrwd@gmail.com \
--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