On Wed, 2014-02-19 at 00:36 +0100, Christoph Paasch wrote: > rior to cd14ef54d25 (igb: Change to use statically allocated array for > MSIx entries), having msix_entries different from NULL was an > indicator > that MSIX is enabled. > In igb_set_interrupt_capabiliy we may fall back to MSI-only. Prior to > the above patch msix_entries was set to NULL by > igb_reset_interrupt_capability. > > However, now we are checking the flag for IGB_FLAG_HAS_MSIX and so the > stack gets completly confused: > > [ 42.659791] ------------[ cut here ]------------ > <snip>
> [ 47.892146] handlers: > [ 47.919301] [<ffffffff812fbd7d>] igb_intr > > So, this patch unsets the flag to indicate that we are not using MSIX. > This patch does exactly this: Unsetting the flag when falling back to > MSI. > > Fixes: cd14ef54d25b (igb: Change to use statically allocated array for > MSIx entries) > Cc: Carolyn Wyborny <[email protected]> > Signed-off-by: Christoph Paasch <[email protected]> > --- > drivers/net/ethernet/intel/igb/igb_main.c | 1 + > 1 file changed, 1 insertion(+) Thanks Christoph, I have added this to our Jeff's internal queue as well. ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
