PCIe network devices can't work on ti8168-dvr

Wu Drew

Hi, We are using DVRRDK_02.80.00.10(v2.6.37_TI816XPSP_04.04.00.01) on our board designed based on the TI86x_DVR reference board. The following 3 NIC's(Network Interface Control cards) are tested but all of them have issues and cannot work properly. We suppose these problems are related to PCIe. Can anybody tell us what is wrong?

1. Intel e1000e(device:0x10d3 verdor:0x8086)

driver: 2.6.37 CONFIG_E1000E
a. When the PCIe MSI(Message Signaled Interrupts) is turned on, Kernel can recognize and add this device into the system. However, Kernel receives no interrupts from the NIC. Here is some basic information.

b. If the MSI is turned off, Kernel can detect the network cable connection events and receive interrupts, but there are lots of logs saying "Reset adapter".

No matter what the PCIe link configuration was (x1 or x2), the network was not functioning properly.

Here is the result when executing ifconfig

ifconfig

            eth0      Link encap:Ethernet HWaddr 00:00:3E:7F:51:FA
                inet addr:169.254.144.130 Bcast:169.254.255.255 Mask:255.255.0.0
                UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
                RX packets:75307 errors:0 dropped:11467 overruns:0 frame:0
                TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:1000
                RX bytes:12317232 (11.7 MiB) TX bytes:300 (300.0 B)
                Interrupt:48 Memory:20080000-200a0000

c. It didn't do any good even after applying the patches over here http://arago-project.org/git/projects/?p=linux-omap3.git;a=history;f=arch/arm/mach-omap2/pcie-ti81xx.c;h=01119bb7de29696e0e8a7ceb4e719eafcc58f616;hb=0553af404982d17bf760a70ba578385c1097c411

2.Sky2(vendor: 0x11ab, device:0x4380)

driver: 2.6.37 CONFIG_SKY2

a. When turning on MSI, the device can be successfully registered, the interrupts can be received, RX is working. However, there are problems on the TX side. Packet transmission cannot work properly.

b. Applying the patches in 1.c does no good here, either.

3. Atheros alx(device:0x8888 verdor:0x104c)
driver: compat-wireless-2012-05-10-pc CONFIG_ALX

a. Kernel can add this device into the system when MSI is on. However, no interrupt received.

b. When MSI is off. Kernel can receive interrupts from the device. However, executing udhcpc can cause the following error

[ 448.200000] alx 0000:01:00.0: eth2: error when reset mac
[ 448.240000] alx 0000:01:00.0: eth2: error when reset mac

c. a,b occur no matter what type of PCIE Link width is set (x1 or x2).

ifconfig reports:
            eth2      Link encap:Ethernet HWaddr 00:13:74:10:1C:D4
            inet addr:169.254.218.19 Bcast:169.254.255.255 Mask:255.255.0.0
            UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
            RX packets:1784 errors:0 dropped:223 overruns:52 frame:52
            TX packets:5 errors:0 dropped:0 overruns:0 carrier:1
            collisions:0 txqueuelen:1000
            RX bytes:278137 (271.6 KiB) TX bytes:300 (300.0 B)
            Interrupt:48

Best Regards,
Drew,

Synology Inc

over 13 years ago