On 9/25/2014 9:56 AM, Rob Roschewsk wrote: > OK ... at first glance the system seems to be operating "normally" > except for the errors every 4 seconds ... that is it's attached to and > using the iscsi target ... > > Is this a problem in iommu OR the emulex driver??
Please make sure your BIOS and NIC firmware are up to date. That usually solves this problem. -- ljk > > On Thu, Sep 25, 2014 at 2:36 AM, Yijing Wang <wangyij...@huawei.com > <mailto:wangyij...@huawei.com>> wrote: > > On 2014/9/25 5:56, Rob Roschewsk wrote: > > Hello All .... wonder if there has been any movement on this issue > .... I'm having a similar issue > > > > I'm running an HP dl380 gen 8 with an Emulex OneConnect 10Gb iSCSI > (14e4:164c) (rev 11) > > also known as " Hewlett-Packard Company NC373i Integrated > Multifunction Gigabit Server Adapter" > > > > 03:00.2 Mass storage controller: Emulex Corporation OneConnect > 10Gb iSCSI Initiator (be3) (rev 01) > > > > 03:00.3 Mass storage controller: Emulex Corporation OneConnect > 10Gb iSCSI Initiator (be3) (rev 01) > > > > Seems as soon as the iscsi target is contacted the following > messages appear in the log every few seconds .... > > > > It seems to a different problem, in my issue, the DMA fault messages > contained a non-exist PCI ID in system. > But in this issue, 03:00.2 is in system, the fault addr is ffffc000, > I guess it's DMA virtual address allocated > by vt-d driver. And it seems to 03:00.2 has no write access authority. > > > Sep 24 15:25:30 kernel: [ 78.682675] dmar: DRHD: handling fault > status reg 2 > > Sep 24 15:25:30 kernel: [ 78.699797] dmar: DMAR:[DMA Write] > Request device [03:00.2] fault addr ffffc000 > > Sep 24 15:25:30 kernel: [ 78.699797] DMAR:[fault reason 05] PTE > Write access is not set > > Sep 24 15:25:30 kernel: [ 78.934546] dmar: DRHD: handling fault > status reg 102 > > Sep 24 15:25:30 kernel: [ 78.934549] dmar: DMAR:[DMA Write] > Request device [03:00.2] fault addr ffffc000 > > Sep 24 15:25:30 kernel: [ 78.934549] DMAR:[fault reason 05] PTE > Write access is not set > > Sep 24 15:25:30 kernel: [ 78.935359] dmar: DRHD: handling fault > status reg 202 > > > > If I pull intel_iommu=on out of the kernel command line the > problem goes away. > > > > System is running Ubuntu 14.04.1 LTS > > > > 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 > x86_64 x86_64 x86_64 GNU/Linux > > > > Looking for help .... I'm not sure where I should be looking next > ..... I need SR-IOV for other adapters in the box. > > > > I have a system up that I can pull any data from that might be > required. > > > > Thanks, > > > > --> Rob > > > > > > > > > > > > _______________________________________________ > > iommu mailing list > > iommu@lists.linux-foundation.org > <mailto:iommu@lists.linux-foundation.org> > > https://lists.linuxfoundation.org/mailman/listinfo/iommu > > > > > -- > Thanks! > Yijing > > > > > _______________________________________________ > iommu mailing list > iommu@lists.linux-foundation.org > https://lists.linuxfoundation.org/mailman/listinfo/iommu > _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
