[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+eFSM3t8U4oV6-JMsmYqaGRsNssTomM+QaETy0v9zEjc9zFhQ@mail.gmail.com>
Date: Wed, 25 May 2016 14:57:40 +0800
From: Gavin Guo <gavin.guo@...onical.com>
To: Yinghai Lu <yinghai@...nel.org>
Cc: "Jiang, Dave" <dave.jiang@...el.com>,
"Koul, Vinod" <vinod.koul@...el.com>,
"dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Williams, Dan J" <dan.j.williams@...el.com>
Subject: Re: ioatdma(Intel(R) I/OAT DMA Engine init failed)
On Fri, May 20, 2016 at 6:17 AM, Yinghai Lu <yinghai@...nel.org> wrote:
> On Thu, May 19, 2016 at 1:17 PM, Jiang, Dave <dave.jiang@...el.com> wrote:
>>> > > And I checked the config and found the CONFIG_PCI_MMCONFIG=y. The
>>> > > following string also can be observed in the dmesg:
>>> > >
>>> > > [ 1.419853] PCI: MMCONFIG for domain 0000 [bus 00-ff] at
>>> > > [mem0x80000000-0x8fffffff] (base 0x80000000)
>>> > > [ 1.419855] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
>>> > >
>>> > > It seems the extended PCI config space is enabled. If there is
>>> > > anything missed?
>
> how about output for "lspci -vvxxxx" ?
Sorry that my client is slow in response. I'll bring it up if I
receive any information.
Powered by blists - more mailing lists