• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 99 subscribers
  • Views 715 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PCIe Gigabit Ethernet for DM8168

Massimo
Expert 6475 points

Hello,

is there a PCIe Gigabit Ethernet card that was somehow validated on the DM8168 evaluation board?

Which device was used to get the benchmarks in http://processors.wiki.ti.com/index.php/DM816x_C6A816x_AM389x_PSP_04.00.00.10_Feature_Performance_Guide#Performance_and_Benchmarks_4 ?

I'm working with a card based on Marvel's 8e8057 and the sky2 (SysKonnect Yukon 2) driver.
The device is enumerated correctly, the device ID is the one I expect, but I get an error:

root@dm816x-evm:~# insmod /lib/modules/2.6.37/kernel/drivers/net/phy/marvell.ko
root@dm816x-evm:~# insmod /lib/modules/2.6.37/kernel/drivers/net/sky2.kosky2: driver version 1.28
sky2 0000:01:00.0: Yukon-2 UL 2 chip revision 0
sky2 0000:01:00.0: cannot assign irq 370
sky2: probe of 0000:01:00.0 failed with error -22

Best regards
Massimo

  • 0
    TI__Expert 5685 points

    Massimo,

    This looks like MSI issue. The card seems to be using MSI while the mentioned release had MSI support not complete/validated.

    Can you try one of the following (in order)?

    1) Apply the patch from Arago from following link: http://arago-project.org/git/projects/?p=linux-omap3.git;a=commit;h=ef702ecea55c904f144206eea3bf4eddf32d4e93

    2) Disable MSI support in kernel and direct the sky driver not to use MSI -

       - The MSI support can be disabled as described in RC driver user guide section "Kernel Configuration"

       - The sky driver can be passed "disable_msi=1" so that it will use INTx.

       Hemant

  • 0 in reply to HemantPedanekar
    Intellectual 400 points

     

    Hi,

    I have the same issue described by Massimo.

    I applied the patch and I have loaded the sky2 module with the disable_msi parameter. 

    The interface ethX is enabled correctly (or it seems to be so).

    I give to the interface an address.

    Finally I try to open a ssh session toward this interface. But immediately I see this errors:

     

     

    sky2: driver version 1.28

    PCI: enabling device 0000:01:00.0 (0140 -> 0142)

    sky2 0000:01:00.0: Yukon-2 UL 2 chip revision 0

    sky2 0000:01:00.0: eth2: addr 00:00:5a:9b:0f:b1

    udev: renamed network interface eth2 to eth3

    sky2 0000:01:00.0: eth3: enabling interface

    ADDRCONF(NETDEV_UP): eth3: link is not ready

    sky2 0000:01:00.0: eth3: Link is up at 1000 Mbps, full duplex, flow control both

    ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready

    sky2 0000:01:00.0: error interrupt status=0x80000000

    sky2 0000:01:00.0: PCI hardware error (0x2010)

     

    I give you some other informations that maybe can help us:

     

     

    1) root@dm816x-evm:~# cat /sys/bus/pci/devices/0000\:01\:00.0/vendor 

        0x11ab

     

    2) root@dm816x-evm:~# cat /sys/bus/pci/devices/0000\:01\:00.0/device 

    0x4380

    In the pci_ids.h this device corresponds  to 
    #define PCI_DEVICE_ID_ATI_IXP600_SATA 0x4380
    That seems to be a bit strange.
    Dario

     

     

     

  • 0 in reply to Dario_mn
    TI__Expert 5685 points

    Dario,

    As I mentioned in my earlier post, please do only one of the mentioned solutions - if you apply the MSI patch, then you need not force disabling MSI (unless MSI doesn't work still).

    Btw, can you provide the 'lspci -xvv' dump? Also, please provide "cat /proc/interrupts" dump when you up the interface.

    Regarding the DEVICE ID value, it can be repeated across different vendor's devices, it is the combination of VENDOR ID and DEVICE ID that should be unique (you will see multiple devices from different vendors in pci_ids.h having same device IDs).

       Hemant