All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: "'Bjorn Helgaas'" <bhelgaas@google.com>,
	"'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 18:34:45 -0600	[thread overview]
Message-ID: <50B6ADA5.2030205@gmail.com> (raw)
In-Reply-To: <00b501cdcca6$03f88af0$0be9a0d0$@lucidpixels.com>

On 11/27/2012 07:49 AM, Justin Piszcz 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
>
> It is _not_ working on the:
>
> 2) Supermicro X8DTH-F (the boot drive in this system is running off a PCI-e
> card, could the IRQ for the I/O controller be getting re-mapped and fail?)--
> worse case I can move the SSD from the 6.0gbpa SATA card to the motherboard
> and see if that works, but that kind of defeats the purpose of a 6.0gbps
> SATA SSD.
>
> (Fails to talk to the SSD)
> http://home.comcast.net/~jpiszcz/20121127/photo1-resize.jpg
>
> (then, a few moments later: Kernel panic)
> http://home.comcast.net/~jpiszcz/20121127/photo2-resize.jpg
>
> Would be curious if anyone had any suggestions besides removing the
> controller card?

What does lspci -vv show on that controller? Not sure what actual 
chipset that controller is, but there's a known issue with some Marvell 
6Gbps SATA controllers with DMAR enabled - it seems the device issues 
memory read/write requests from the wrong PCI function ID and the IOMMU 
rightly denies access as the function listed in the requests doesn't 
have any mapping to that memory. I don't think there's presently a 
workaround other than disabling DMAR. We could (and likely should) be 
detecting that device and adding some kind of quirk for it.

>
> --
>
>
> ==> Further issues with the X9SRL-F -- does this board support ASPM or is
> this a Linux/ASPM implementation issue?
> [    0.632170]  pci0000:ff: ACPI _OSC support notification failed, disabling
> PCIe ASPM
> [    0.632239]  pci0000:ff: Unable to request _OSC control (_OSC support
> mask: 0x08)

What's the full dmesg from this machine (or is it already posted somewhere)?

  parent reply	other threads:[~2012-11-29  0:34 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
2012-11-29  0:34               ` Robert Hancock [this message]
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=50B6ADA5.2030205@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=bonbons@linux-vserver.org \
    --cc=djbw@fb.com \
    --cc=jpiszcz@lucidpixels.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 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.