On Feb 16, 2015, at 6:44 AM, Tal Abudi <talab...@gmail.com> wrote: > I'm not sure if my question fits this discussion board but it would be > great if anyone could assist. > > I'm back-porting the genirq patch series to my Linux 2.6.18.
This will cause trouble with an out-of-tree driver, because you are changing the features available in a given version of the kernel. > After insmod'ing ixgbe driver 3.9.15 with MQ enabled my machine hangs with > this is the dmesg printed repeatedly: > <1>unexpected IRQ trap at vector 56 > <1>irq 86, desc: ffffffff80530980, depth: 1, count: 0, unhandled: 0 > <1>->handle_irq(): ffffffff80078fc0, handle_bad_irq+0x0/0x280 > <1>->chip(): ffffffff804291c0, msix_irq_type+0x0/0x80 > <1>->action(): 0000000000000000 > <1> IRQ_DISABLED set > > First of all, I'm not sure why the interrupt handler occurs if the > IRQ_DISABLED flag is on. > Second, the kernel irq chip/msi code allocated the irq_desc with > handle_irq=handle_bad_irq > Who's job is it to set the correct handler ? > I don't any reference in the MSIX code nor in the driver.. > > Any ideas ? I don't know the specifics offhand, but to get this to work, at a minimum you will need to use a newer version of the ixgbe driver - one that has support for the newer kernel feature. Then you will have to hack on the kcompat.h file to try to get the driver to use the correct apis for your specific kernel. That is the minimum that would be required - there might be a lot more involved. > Thanks ! A little advice: I used to work on embedded systems, and it was usually better to just update the kernel than to do a lot of backporting, especially of things as sensitive as irq code. Some people - often managers - really freak out at the notion of changing kernel version, but it is really much scarier to be running something totally unique that has not had the kind of community exposure that a released kernel has had. Updating the kernel really is nearly always a lower-risk approach and it is worth making that clear to all involved. It is hard to emphasize this strongly enough! In fact, you should try to move on to a kernel that has a version of ixgbe that supports your hardware and just use the kernel ixgbe driver. If the in-kernel driver supports your hardware, there is seldom a need for the out-of-tree driver. You may not want to use the very latest kernel, but I'm sure there are a number of suitable -stable kernels that should have the features you need. Stay as close to the well-lit paths as you can. -- Mark Rustad, Networking Division, Intel Corporation
signature.asc
Description: Message signed with OpenPGP using GPGMail
------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
_______________________________________________ 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
