From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by dpdk.org (Postfix) with ESMTP id 82DC4DE4 for ; Sun, 5 Jan 2014 13:36:34 +0100 (CET) Received: by mail-pa0-f54.google.com with SMTP id rd3so17549726pab.13 for ; Sun, 05 Jan 2014 04:37:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Yp/R4fArG1uxH0qJkzVvll3IE+JTAWG3Dgtt/WR9oQg=; b=Z5kqsP9D5dxLJetyRBXih8YAc6OYMaLNbL+3oFyVPgOJA8+wT0trRNPdUVjqr9Ks6w hI1NobXGA/4nXN3V1UehducWhOvG0DjY2NuqiQURNnLeTqx2lg3TyWx1XDAPVuttpfBX dFj1ybJxJ+0fKRTkn55WfswHAY/LR+hyVIP+SItiewB+WhZIw/fWUYZQIKgWpvdZ/Hnl +LjO83PyYNcMqzAjsJTRE95qLYXzqRnu8iczSzyzF8Y3IQ/MYfMdqpPadcEzvD8fOCjJ pMqo5wBkov4Pjca8LLGSOVHwVSxD84tMGKHMB4sUggaASuWB1TaE8tptLZKVvlhb636N yVNw== MIME-Version: 1.0 X-Received: by 10.68.130.103 with SMTP id od7mr55225744pbb.87.1388925465140; Sun, 05 Jan 2014 04:37:45 -0800 (PST) Received: by 10.70.53.197 with HTTP; Sun, 5 Jan 2014 04:37:45 -0800 (PST) Date: Sun, 5 Jan 2014 18:07:45 +0530 Message-ID: From: Sridhar S To: dev@dpdk.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] Issue when the kernel parameter intel_iommu=on is being used X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jan 2014 12:36:35 -0000 Hello, I am using DPDK 1.5 for development of host pmd for device =93Connect X3=94= . I am observing issue while the ConnectX3 device DMA to a memory which is allocated with rte_memzone_reserve_aligned() API . The issue(please refer ERROR below) has been observed if the system runs with the kernel parameter =93intel_iommu=3Don=94. ERROR : dmar: DRHD: handling fault status reg 302 dmar: DMAR:[DMA Write] Request device [01:00.0] fault addr 4f883000 DMAR:[fault reason 01] Present bit in root entry is clear The reported "fault Addr" is the physical address which was returned by the Above API. I don=92t see any issue with the same code when the system up with kernel parameter intel_iommu=3Doff. Can you share your comments on this issue? Thanks in advance Sri