----- Original Message ----- > On Thu, Jan 08, 2015 at 11:33:46AM +0000, Venkat Duvvuru wrote: > >Hi Gavin, > >We tried to reproduce this in our lab but our observation is that we don't > >see "interrupt storm" in our system. > >Could you please give us the details of the repro scenario? > > > >A few more details will help us understand the problem better as well. > >1. be2net driver version > >2. be2net firmware version > >3. lspci -vvv output of the card (lspci -d 19a2: -vvv) > >4. Is SR-IOV enabled in your card? > > > > Venkat, On IBM's Power7 box, I passed through following adpater to guest with > following ... > > Steps to recreate the issue > =========================== > > 1. Configure the NIC and ping it from external. > 2. Inject EEH error by running following command in host side. After about > 20 seconds, I got following message from host side. With the patch applied > to host kernel, I didn't see the warning messages: This seems really dubious and I don't see any justification at all for declaring DisINTx broken for all devices for the vendor. Typically to call DisINTx broken for a given device, you can just boot the guest with pci=nomsi to force INTx to be used. If that works, then DisINTx masking works. If you require EEH injection to to trigger this, then the problem is more likely some containment issue during EEH recovery. Thanks, Alex -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
