mx6 + rtl8111e driver

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

mx6 + rtl8111e driver

4,389 Views
tarterkit_ru
Contributor III

Hi, i have custom imx6 board Hola-PC http://starterkit.ru/html/index.php?name=shop&op=view&id=99

Now i try create mPCIe plug for this board, based on RTL8111E chip.

After patching of my board file and compiling driver from realtek site r8168-8.038.00, i can see my extension board:

# dmesg | grep PCI

PCI: CLS 0 bytes, default 32

iMX6 PCIe PCIe RC mode imx_pcie_pltfm_probe entering.

PCIE: imx_pcie_pltfm_probe start link up.

IMX PCIe port: link up.

PCI: bus0: Fast back to back transfers disabled

PCI: bus1: Fast back to back transfers disabled

pci 0000:00:00.0: BAR 0: set to [mem 0x01000000-0x010fffff 64bit pref] (PCI address [0x1000000-0x10fffff])

pci 0000:01:00.0: BAR 4: set to [mem 0x01100000-0x01103fff 64bit pref] (PCI address [0x1100000-0x1103fff])

pci 0000:01:00.0: BAR 2: set to [mem 0x01104000-0x01104fff 64bit pref] (PCI address [0x1104000-0x1104fff])

pci 0000:01:00.0: BAR 0: set to [io  0x1e00000-0x1e000ff] (PCI address [0x1e00000-0x1e000ff])

pci 0000:00:00.0: PCI bridge to [bus 01-01]

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

# dmesg | grep 8168

pci 0000:01:00.0: [10ec:8168] type 0 class 0x000200

r8168 Gigabit Ethernet driver 8.038.00-NAPI loaded

r8168 0000:01:00.0: no MSI. Back to INTx.

r8168: This product is covered by one or more of the following patents: US6,570,884, US6,115,776, and US6,327,625.

r8168  Copyright (C) 2013  Realtek NIC software team <nicfae@realtek.com>

r8168: eth2: link up

But, connections working only after software reset (reboot) and can't work any stress interconnections (like iperf, ftp, http), working only ping

Labels (1)
0 Kudos
14 Replies

1,972 Views
carmilili
Contributor III

Hello Pavel

     I meet the same problem with you now.Did you solve it?

     My board is IMX6Q-SDB.The mPCIE card is RTL8111e or RTL8111f.

(1)

root@freescale /app/net$ifconfig

eth0      Link encap:Ethernet  HWaddr 00:04:9F:02:6E:25

          inet addr:192.168.2.67  Bcast:192.168.2.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:109724 errors:0 dropped:903 overruns:0 frame:0

          TX packets:7501 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:17633802 (16.8 MiB)  TX bytes:1108875 (1.0 MiB)

eth1      Link encap:Ethernet  HWaddr 00:13:3B:0E:D1:10

          inet addr:10.0.0.1  Bcast:10.255.255.255  Mask:255.0.0.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:18112 errors:0 dropped:142 overruns:0 frame:0

          TX packets:23 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:1537208 (1.4 MiB)  TX bytes:1494 (1.4 KiB)

          Interrupt:155 Base address:0xe000

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:14 errors:0 dropped:0 overruns:0 frame:0

          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:1136 (1.1 KiB)  TX bytes:1136 (1.1 KiB)

(2)

root@freescale /app/net$ ping 10.0.0.2

PING 10.0.0.2 (10.0.0.2): 56 data bytes

64 bytes from 10.0.0.2: seq=0 ttl=64 time=10.165 ms

64 bytes from 10.0.0.2: seq=1 ttl=64 time=0.230 ms

......

(3)

When I use the commad tftp ssh and iperf to test it ,all to be  failure.

root@freescale /app/net$ ssh -v root@10.0.0.2

OpenSSH_4.3p2, OpenSSL 1.0.1c 10 May 2012

debug1: Reading configuration data /etc/ssh/ssh_config

debug1: Connecting to 10.0.0.2 [10.0.0.2] port 22.

debug1: Connection established.

debug1: permanently_set_uid: 0/0

debug1: identity file /root/.ssh/identity type -1

debug1: identity file /root/.ssh/id_rsa type -1

debug1: identity file /root/.ssh/id_dsa type -1

debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3

debug1: match: OpenSSH_5.3 pat OpenSSH*

debug1: Enabling compatibility mode for protocol 2.0

debug1: Local version string SSH-2.0-OpenSSH_4.3

debug1: SSH2_MSG_KEXINIT sent

debug1: SSH2_MSG_KEXINIT received

debug1: kex: server->client aes128-cbc hmac-md5 none

debug1: kex: client->server aes128-cbc hmac-md5 none

debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent

debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP

It  stops  here.

0 Kudos

1,972 Views
carmilili
Contributor III

When I set the MTU = 500,it looks like work well .But when I use the tools of iperf to test it .The network card can not exit the thread sometimes later.

$ifconfig eth1 mtu 500

0 Kudos

1,973 Views
guochgz
Contributor III

hi, Carmili Li

      We also meet this problem, did you have solved it?  can you tell me what to do ?  thanks!

0 Kudos

1,972 Views
tarterkit_ru
Contributor III

We postponed it.

In progress, we was make different drivers from Realtek and after some edition i have stable link few time but only after software reset ...

After we try use 3.10.17 kernel - not better.

Later begin to development again.

0 Kudos

1,972 Views
carmilili
Contributor III

Can you tell me where do I need to modify?

Thank you .

0 Kudos

1,972 Views
tarterkit_ru
Contributor III

I don't know where You must modify, we postponed it to better time.

0 Kudos

1,971 Views
xiaoqianlin
NXP Employee
NXP Employee

any patch on this issue?

Linda Lin
0 Kudos

1,971 Views
Sasamy
Contributor IV
0 Kudos

1,971 Views
fabio_estevam
NXP Employee
NXP Employee

Hi Alexander,

It would be nice if you could send this patch for review in the netdev@vger.kernel.org list.

0 Kudos

1,972 Views
Sasamy
Contributor IV

Hi Fabio,

thank you for your work in the mainline Linux kernel. This patch is not for mainline Linux - only workaround local problem, change MRRS on the PCIe device side without known host capability  - a bad idea, but on some systems, the removal of this optimization can lead to poor performance. I think more correctly like this

Re: [PATCH - v4] PCI: keystone: add a pci quirk to limit mrrs -- Linux PCI

0 Kudos

1,973 Views
fabio_estevam
NXP Employee
NXP Employee

Hi Alexander,

Thanks for the clarification.

It would be really nice if someone that has access to the rtl8111e hardware could try to come with a proper patch for mainline inclusion. The patch from the link you sent may be worth to explore.

Regards,

Fabio Estevam

0 Kudos

1,972 Views
YixingKong
Senior Contributor IV

Pavel

We have not got your response yet and will close the discussion in 3 days. If you still need help, please feel free to reply with an update to this discussion.

Thanks,

Yixing

0 Kudos

1,972 Views
YixingKong
Senior Contributor IV

Pavel

Could you please reply our engineer's question? If your issue had been resolved, please tell us and we will close the discussion.

Thanks,

Yixing

0 Kudos

1,972 Views
b47504
NXP Employee
NXP Employee

Can you please share your kernel log and user space log when the issue occurred and the normal log using ping command?

If you can provide the TLP data when the issue appeared, it will be more helpful to address the issue.  And please also paste the connect status with AP or other wifi partner as you test.

0 Kudos