2 Replies Latest reply on Sep 18, 2013 1:30 AM by marcfreynet

    strange issue with DPDK_1.3.1 igb_uio.ko module

    marcfreynet Green Belt

      We observed one issue on DPDK_1.3.1 igb_uio.ko module.

        DPDK_1.3.1 igb_uio.ko module has not initialized and Kernel hanged at “kernel: Use MSIX interrupt by default” when inserting the igb_uio.ko module.

       

      We lost the console connection also after igb_uio.ko inserted

      We observed only one time. We are not able to re-produce this issue.

          

        We are currently using  “kernel: Linux version 2.6.32-220.el6.x86_64”

       

         Working time logs:

         kernel: Use MSIX interrupt by default

      kernel: ixgbe 0000:07:00.0: complete

      kernel: ixgbe 0000:07:00.0: PCI INT A disabled

      kernel: igb_uio 0000:07:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21

      kernel: igb_uio 0000:07:00.0: setting latency timer to 64

      kernel: igb_uio 0000:07:00.0: irq 35 for MSI/MSI-X

      kernel: uio device registered with irq 23

      kernel: ixgbe 0000:07:00.1: complete

      kernel: ixgbe 0000:07:00.1: PCI INT B disabled

      kernel: igb_uio 0000:07:00.1: PCI INT B -> GSI 22 (level, low) -> IRQ 22

      kernel: igb_uio 0000:07:00.1: setting latency timer to 64

      kernel: igb_uio 0000:07:00.1: irq 36 for MSI/MSI-X

       

      Problematic time logs;

           kernel: Use MSIX interrupt by default….. Kernel hanged at this time and we are not able to debug the system since console connection lost.

        

        We rebooted the board to bring it back. Anybode have seen this before ?

        • Re: strange issue with DPDK_1.3.1 igb_uio.ko module
          muthurajanjayakumar Green Belt

          When you see "Kernel: Use MSIX interrupt by default", it seems indicate that your insmod command is working unless your system doesn't support MSIX". It is very strange your system hung when insmod succeeded. I am suspecting that you might have an un-cooperated process try to access the same module

            • Re: strange issue with DPDK_1.3.1 igb_uio.ko module
              marcfreynet Green Belt

              Thanks for your answer. Based on your 2 answers (this one and the one regarding the huge page initialization: strange issue with DPDK_1.3.1 igb_uio.ko module); we may have a problem in the Linux boot / start up order. I should have say that the 2 problems: MSIX problem and the failure to allocated to huge pages occurred on the same test board and was never seen in other other boards running the same application. We may have a Linux configuration / installation issue with this board that generate a different start up sequence comparing with the other platforms that run the DPDK without any problem.