<div dir="ltr">Thanks,<div><br></div><div>This is new territory for me so bear with.<br><div><br></div><div><div>04:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)</div><div>81:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)</div></div><div><br></div><div>It appears we have MSI enabled, but I'm not sure how to verify that or RSS expressly. This is from the OSS, where eth3 is a private link to the partner OSS, and eth1 is the management subnet, and ixgbe1 is the cluster client path.</div><div>
<p class=""># cat /proc/interrupts | grep -i msi | awk '{print $1,$18,$19}' | grep TxRx</p></div><div><div>157: IR-PCI-MSI-edge eth3-TxRx-0</div><div>158: IR-PCI-MSI-edge eth3-TxRx-1</div><div>159: IR-PCI-MSI-edge eth3-TxRx-2</div><div>160: IR-PCI-MSI-edge eth3-TxRx-3</div><div>161: IR-PCI-MSI-edge eth3-TxRx-4</div><div>162: IR-PCI-MSI-edge eth3-TxRx-5</div><div>163: IR-PCI-MSI-edge eth3-TxRx-6</div><div>164: IR-PCI-MSI-edge eth3-TxRx-7</div><div>175: IR-PCI-MSI-edge eth1-TxRx-0<br></div><div>176: IR-PCI-MSI-edge eth1-TxRx-1</div><div>177: IR-PCI-MSI-edge eth1-TxRx-2</div><div>178: IR-PCI-MSI-edge eth1-TxRx-3</div><div>179: IR-PCI-MSI-edge eth1-TxRx-4</div><div>180: IR-PCI-MSI-edge eth1-TxRx-5</div><div>181: IR-PCI-MSI-edge eth1-TxRx-6</div><div>182: IR-PCI-MSI-edge eth1-TxRx-7</div><div>200: IR-PCI-MSI-edge ixgbe1-TxRx-0</div><div>201: IR-PCI-MSI-edge ixgbe1-TxRx-1</div><div>202: IR-PCI-MSI-edge ixgbe1-TxRx-2</div><div>203: IR-PCI-MSI-edge ixgbe1-TxRx-3</div><div>204: IR-PCI-MSI-edge ixgbe1-TxRx-4</div><div>205: IR-PCI-MSI-edge ixgbe1-TxRx-5</div><div>206: IR-PCI-MSI-edge ixgbe1-TxRx-6</div><div>207: IR-PCI-MSI-edge ixgbe1-TxRx-7</div><div>208: IR-PCI-MSI-edge ixgbe1-TxRx-8</div><div>209: IR-PCI-MSI-edge ixgbe1-TxRx-9</div><div>210: IR-PCI-MSI-edge ixgbe1-TxRx-10</div><div>211: IR-PCI-MSI-edge ixgbe1-TxRx-11</div><div>212: IR-PCI-MSI-edge ixgbe1-TxRx-12</div><div>213: IR-PCI-MSI-edge ixgbe1-TxRx-13</div><div>214: IR-PCI-MSI-edge ixgbe1-TxRx-14</div><div>215: IR-PCI-MSI-edge ixgbe1-TxRx-15</div></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 29, 2015 at 2:02 PM, Ashish Purkar <span dir="ltr"><<a href="mailto:ashish.purkar@seagate.com" target="_blank">ashish.purkar@seagate.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Are you using RSS with MSIX on NIC?<br>
Please provide more details about the NIC and the configuration.</p>
<p dir="ltr">app\u221a</p>
<div class="gmail_quote"><div><div class="h5">On Sep 30, 2015 1:54 AM, "Exec Unerd" <<a href="mailto:execunerd@gmail.com" target="_blank">execunerd@gmail.com</a>> wrote:<br type="attribution"></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Hello,<div><br></div><div>I've been getting these types of error messages on my OSS nodes, and I'm wondering if I have a client sending bad data through RDMA. My googling has been fruitless to discover the meaning of "fault reason 34" but the PCI addresses are my 10Gb and 1Gb NICs. </div><div><br></div><div>I'm not really sure where to begin diagnosing this error, so I'm hoping one of you have seen this before. One thing to note is that no clients should be using the 1Gb NIC to mount the file system; it's just for management so I don't know why I'd see a DMA error on PCI 04:00.1.</div><div><br></div><div><div>dmar: INTR-REMAP: Request device [[81:00.1] fault index 8c</div><div>INTR-REMAP:[fault reason 34] Present field in the IRTE entry is clear</div><div>dmar: DRHD: handling fault status reg 102</div><div>dmar: INTR-REMAP: Request device [[04:00.1] fault index 75</div><div>INTR-REMAP:[fault reason 34] Present field in the IRTE entry is clear</div><div><br></div><div>dmar: DRHD: handling fault status reg 202</div><div>dmar: INTR-REMAP: Request device [[04:00.1] fault index 74</div><div>INTR-REMAP:[fault reason 34] Present field in the IRTE entry is clear</div><div>dmar: DRHD: handling fault status reg 302</div><div>dmar: INTR-REMAP: Request device [[04:00.1] fault index 73</div><div>INTR-REMAP:[fault reason 34] Present field in the IRTE entry is clear</div></div><div><br></div><div><div style="font-size:12.8px"><div><font face="monospace, monospace" style="background-color:rgb(204,204,204)">kernel: 2.6.32-504.23.4.el6.x86_64</font></div><div><font face="monospace, monospace" style="background-color:rgb(204,204,204)">lustre: lustre-2.7.58-2.6.32_504.23.4.el6.x86_64_g051c25b.x86_64</font></div><div><font face="monospace, monospace" style="background-color:rgb(204,204,204)">zfs: zfs-0.6.4-76_g87abfcb.el6.x86_64</font></div><div><font face="monospace, monospace" style="background-color:rgb(204,204,204)"><br></font></div></div></div></div>
<br></div></div>_______________________________________________<br>
lustre-discuss mailing list<br>
<a href="mailto:lustre-discuss@lists.lustre.org" target="_blank">lustre-discuss@lists.lustre.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.lustre.org_listinfo.cgi_lustre-2Ddiscuss-2Dlustre.org&d=BQICAg&c=IGDlg0lD0b-nebmJJ0Kp8A&r=FtYV9f_ig6ynAGsdwsQr2_tmRri3ty7J2xOP7XSVZbg&m=jdYnF_2RoPuBH6V_D188yhO85J9xqOAWB95EUSaL4Hc&s=WcAJJh6R5ABmdqrVboo_uo3opBF0g1jJis_ITccu_z4&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.lustre.org_listinfo.cgi_lustre-2Ddiscuss-2Dlustre.org&d=BQICAg&c=IGDlg0lD0b-nebmJJ0Kp8A&r=FtYV9f_ig6ynAGsdwsQr2_tmRri3ty7J2xOP7XSVZbg&m=jdYnF_2RoPuBH6V_D188yhO85J9xqOAWB95EUSaL4Hc&s=WcAJJh6R5ABmdqrVboo_uo3opBF0g1jJis_ITccu_z4&e=</a><br>
<br></blockquote></div>
</blockquote></div><br></div>