[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2ff8404d-7103-a96d-2749-ac707ce74563@linux.intel.com>
Date: Tue, 11 Jun 2019 09:41:18 +0800
From: Lu Baolu <baolu.lu@...ux.intel.com>
To: Qian Cai <cai@....pw>
Cc: baolu.lu@...ux.intel.com, James Sewart <jamessewart@...sta.com>,
Joerg Roedel <jroedel@...e.de>,
iommu@...ts.linux-foundation.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Kashyap Desai <kashyap.desai@...adcom.com>,
Sumit Saxena <sumit.saxena@...adcom.com>,
Shivasharan S <shivasharan.srikanteshwara@...adcom.com>
Subject: Re: "iommu/vt-d: Delegate DMA domain to generic iommu" series breaks
megaraid_sas
Ah, good catch!
The device failed to be attached by a DMA domain. Can you please try the
attached fix patch?
[ 101.885468] pci 0000:06:00.0: DMAR: Device is ineligible for IOMMU
domain attach due to platform RMRR requirement. Contact your platform
vendor.
[ 101.900801] pci 0000:06:00.0: Failed to add to iommu group 23: -1
Best regards,
Baolu
On 6/10/19 10:54 PM, Qian Cai wrote:
> On Mon, 2019-06-10 at 09:44 -0400, Qian Cai wrote:
>> On Sun, 2019-06-09 at 10:43 +0800, Lu Baolu wrote:
>>> Hi Qian,
>>>
>>> I just posted some fix patches. I cc'ed them in your email inbox as
>>> well. Can you please check whether they happen to fix your issue?
>>> If not, do you mind posting more debug messages?
>>
>> Unfortunately, it does not work. Here is the dmesg.
>>
>> https://raw.githubusercontent.com/cailca/tmp/master/dmesg?token=AMC35QKPIZBYUM
>> FUQKLW4ZC47ZPIK
>
> This one should be good to view.
>
> https://cailca.github.io/files/dmesg.txt
>
View attachment "0001-iommu-vt-d-Allow-DMA-domain-attaching-to-rmrr-locked.patch" of type "text/x-patch" (1363 bytes)
Powered by blists - more mailing lists