We have not seen a report of this issue before. Please provide details on the NIC or LOM and system/chipset on which the problem occurs and how the additional 50ms was determined.
> -----Original Message----- > From: prasanna.panchamu...@riverbed.com > [mailto:prasanna.panchamu...@riverbed.com] > Sent: Wednesday, April 18, 2012 5:18 PM > To: Allan, Bruce W; Kirsher, Jeffrey T; Brandeburg, Jesse; Pieper, > Jeffrey E > Cc: e1000-devel@lists.sourceforge.net; > prasanna.panchamu...@riverbed.com > Subject: [PATCH] e1000e: MSI interrupt test failed, using legacy > interrupt > > From: Prasanna S. Panchamukhi <ppanchamu...@riverbed.com> > > Following logs where seen on Systems with multiple NICs, > while using MSI interrupts as shown below: > > Feb 16 15:09:32 (none) user.notice kernel: 0000:00:0d.0: lan0_0: NIC > Link is Up > 1000 Mbps Full Duplex, Flow Control: RX/TX > Feb 16 15:09:32 (none) user.notice kernel: 0000:40:0d.0: wan0_1: NIC > Link is Up > 1000 Mbps Full Duplex, Flow Control: RX/TX > Feb 16 15:09:32 (none) user.notice kernel: 0000:40:0d.0: lan0_1: NIC > Link is Up > 1000 Mbps Full Duplex, Flow Control: RX/TX > Feb 16 15:09:32 (none) user.warn kernel: 0000:40:0e.0: wan4_0: MSI > interrupt > test failed, using legacy interrupt. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Feb 16 15:09:32 (none) user.notice kernel: 0000:00:0e.0: wan1_0: NIC > Link is Up > 1000 Mbps Full Duplex, Flow Control: RX/TX > Feb 16 15:09:33 (none) user.notice kernel: 0000:00:0e.0: lan1_0: NIC > Link is Up > 1000 Mbps Full Duplex, Flow Control: RX/TX > Feb 16 15:09:33 (none) user.notice kernel: 0000:00:0f.0: wan2_0: NIC > Link is Up > 1000 Mbps Full Duplex, Flow Control: RX/TX > Feb 16 15:09:33 (none) user.notice kernel: 0000:00:0f.0: lan2_0: NIC > Link is Up > 1000 Mbps Full Duplex, Flow Control: RX/TX > Feb 16 15:09:33 (none) user.notice kernel: 0000:40:0a.0: wan3_0: NIC > Link is Up > 1000 Mbps Full Duplex, Flow Control: RX/TX > Feb 16 15:09:33 (none) user.notice kernel: 0000:40:0a.0: lan3_0: NIC > Link is Up > 1000 Mbps Full Duplex, Flow Control: RX/TX > Feb 16 15:09:34 (none) user.notice kernel: 0000:40:0e.0: lan4_0: NIC > Link is Up > 1000 Mbps Full Duplex, Flow Control: RX/TX > Feb 16 15:09:34 (none) user.notice kernel: 0000:40:0f.0: wan5_0: NIC > Link is Up > 1000 Mbps Full Duplex, Flow Control: RX/TX > Feb 16 15:09:34 (none) user.notice kernel: 0000:40:0f.0: lan5_0: NIC > Link is Up > 1000 Mbps Full Duplex, Flow Control: RX/TX > > This patch fixes this problem by increasing the msleep from 50 to 100. > > Signed-off-by: Prasanna S. Panchamukhi <ppanchamu...@riverbed.com> > --- > drivers/net/ethernet/intel/e1000e/netdev.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/drivers/net/ethernet/intel/e1000e/netdev.c > b/drivers/net/ethernet/intel/e1000e/netdev.c > index 19ab215..9520a6a 100644 > --- a/drivers/net/ethernet/intel/e1000e/netdev.c > +++ b/drivers/net/ethernet/intel/e1000e/netdev.c > @@ -3799,7 +3799,7 @@ static int e1000_test_msi_interrupt(struct > e1000_adapter *adapter) > /* fire an unusual interrupt on the test handler */ > ew32(ICS, E1000_ICS_RXSEQ); > e1e_flush(); > - msleep(50); > + msleep(100); > > e1000_irq_disable(adapter); > > -- > 1.7.0.4 ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
