Hi Jamie, Many thanks for your effort. If you need a new kernel for testing please let me know.
Cheers, Christian Sent from my iPhone > On 18. Jan 2018, at 02:59, Jamie Krueger <ja...@bitbybitsoftwaregroup.com> > wrote: > > Hi Madalin, > > On 01/16/2018 11:33 AM, Madalin-cristian Bucur wrote: > > Here are some results from testing on the X5000/20 with 4.15.0-rc8 > (w/CONFIG_FSL_PAMU disabled): > > In my tests I can now get the interface to obtain an IP Address via DHCP, > at least *part* of the time that is. > > Here is a link to a screenshot of a Wireshark capture which shows > a successful DHCP request/response for the X5000/20, followed by some > failed ping attempts. > > (This traffic was captured on an external machine on the same subnet, and not > from the X5000/20 itself) > http://bitbybitsoftwaregroup.com/share/X5000-DHCP-Answered-Wireshark.png > > Additionally, here is a link to the export of the packet data shown in the > above image: > http://bitbybitsoftwaregroup.com/share/Wireshark-X5000-DHCP-Success.html > > As you can see by this example, even when the interface does obtain an IP > address via > DHCP (about half the time), subsequent traffic still fails to receive > responses. > > In this example, I attempt to ping the gateway (192.168.1.1), and one or two > other > local addresses, and nothing pings back (even when trying Skateman's > suggestion > of expanding the buffers for the interface - > > "A workaround to keep the nic alive a bit longer.... is the following command > ip link set eth0 qlen 10000" > > For reference: > > I have attached the Kernel config that the version I tested was built with. > Also, I have attached the dmesg output I am currently seeing. > > -- > Best Regards, > > Jamie Krueger > BITbyBIT Software Group LLC > > <proc_config-4.15.0-rc8-NO_PAMU.txt> > <fsl_dmesg_output.txt>