Hi Andrew,
How can we fix the buffer problem?
Thanks,
Christian
On 7. Feb 2018, at 22:17, Andrew Lunn wrote:
On Wed, Feb 07, 2018 at 10:00:45PM +0100, mad skateman wrote:
Hi,
I just found out that something goes wrong within the ARP table (well thats
what i think). I hope
S . Miller <da...@davemloft.net>
> > > Cc: linuxppc-dev@lists.ozlabs.org; net...@vger.kernel.org;
> > > madskate...@gmail.com; 'Madalin-cristian Bucur' <
> madalin.bu...@nxp.com>;
> > > Andrew Lunn <and...@lunn.ch>; Joakim Tjernlund
> >
On Wed, Feb 07, 2018 at 10:00:45PM +0100, mad skateman wrote:
> Hi,
>
> I just found out that something goes wrong within the ARP table (well thats
> what i think). I hope someone has a clue..
This looks like 'normal' behaviour. It has been reported that the
device runs out of buffers. That
@gmail.com; 'Madalin-cristian Bucur'
<madalin.bu...@nxp.com>;
> > Andrew Lunn <and...@lunn.ch>; Joakim Tjernlund
> > <joakim.tjernl...@infinera.com>
> > Subject: RE: DPAA Ethernet traffice troubles with Linux kernel
> >
> > > --
.@lunn.ch>; Joakim Tjernlund
> > <joakim.tjernl...@infinera.com>
> > Subject: RE: DPAA Ethernet traffice troubles with Linux kernel
> >
> > > -Original Message-
> > > From: netdev-ow...@vger.kernel.org [mailto:netdev-owner@vger.
> kernel.org]
On Thu, 1970-01-01 at 00:00 +, Andrew Lunn wrote:
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
>
>
> > > commit 4d8ee1935bcd666360311dfdadeee235d682d69a
> > >
> > commit 4d8ee1935bcd666360311dfdadeee235d682d69a
> > Author: Florian Fainelli
> > Date: Tue Aug 22 15:24:47 2017 -0700
> > fsl/man: Inherit parent device and of_node
> >
> > and was later addressed by this patch set:
> >
> >
On Thu, 1970-01-01 at 00:00 +, Madalin-cristian Bucur wrote:
>
> > -Original Message-
> > From: Joakim Tjernlund [mailto:joakim.tjernl...@infinera.com]
> > Sent: Tuesday, January 16, 2018 7:58 PM
> > To: and...@lunn.ch
> > Subject: Re: DPAA Ethernet tr
> > the content is safe.
> >
> >
> > > -Original Message-
> > > From: Joakim Tjernlund [mailto:joakim.tjernl...@infinera.com]
> > > Sent: Tuesday, January 16, 2018 7:58 PM
> > > To: and...@lunn.ch
> > > Subject: Re: DPAA Etherne
> > From: Joakim Tjernlund [mailto:joakim.tjernl...@infinera.com]
> > Sent: Tuesday, January 16, 2018 7:58 PM
> > To: and...@lunn.ch
> > Subject: Re: DPAA Ethernet traffice troubles with Linux kernel
> >
> > On Thu, 1970-01-01 at 00:00 +, Andrew Lunn wrote:
&
...@nxp.com>;
> Andrew Lunn <and...@lunn.ch>; Joakim Tjernlund
> <joakim.tjernl...@infinera.com>
> Subject: RE: DPAA Ethernet traffice troubles with Linux kernel
>
> > -Original Message-
> > From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...
era.com>
> Cc: linuxppc-dev@lists.ozlabs.org; net...@vger.kernel.org;
> madskate...@gmail.com; David S . Miller <da...@davemloft.net>
> Subject: RE: DPAA Ethernet traffice troubles with Linux kernel
>
> > -Original Message-
> > From: Andrew Lunn [mailto:a
> -Original Message-
> From: Andrew Lunn [mailto:and...@lunn.ch]
> Sent: Wednesday, January 17, 2018 3:44 PM
> To: Joakim Tjernlund <joakim.tjernl...@infinera.com>
> Subject: Re: DPAA Ethernet traffice troubles with Linux kernel
>
> > That doesn't work reall
> -Original Message-
> From: Joakim Tjernlund [mailto:joakim.tjernl...@infinera.com]
> Sent: Tuesday, January 16, 2018 7:58 PM
> To: and...@lunn.ch
> Subject: Re: DPAA Ethernet traffice troubles with Linux kernel
>
> On Thu, 1970-01-01 at 00:00 +, Andrew Lunn wro
> That doesn't work really, having users to hit the bug, debug it, fix it and
> then
> find it fixed already in upstream, then specifically request it to be
> backported to stable.
> I don't need this fix to be backported, already got it. Someone else might
> though.
The "someone else might
After using the new compiled 4.14 rc8 kernel without PAMU support posted by
Christian Zigotzky the X5000 can use the Network interface with some minor
issues.
I had to give the Eth0 a manual IP due to not responding on DHCP requests.
I can ping my Gateway, and even DNS queries work..
But when i
On Thu, 1970-01-01 at 00:00 +, Andrew Lunn wrote:
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
>
>
> > > You appear to be using an old kernel. Take a look at:
> >
FYI
Sent from my iPhone
> On 17. Jan 2018, at 06:50, Christian Zigotzky wrote:
>
> Hi Skateman,
>
> Fantastic! Many thanks for testing the RC8 of kernel 4.15 without PAMU
> support.
>
> @All
> Further information:
>
This makes me really start to wonder if the mainboard producer Varisys/AEON
has Purchased MAC`s for these boards at IEEE
Uboot system info gives for both MAC adresses the value NULL ... and i have
checked the mainboard for any stickers regarding the MAC adresses but there
is none..
I also tried
Hi,
I have been looking deeper into my wireshark packet captures and found
something that could be helpfull.
I can see that the Ethernet NIC at least does something. ARP BROADCAST
traffic is seen.
But i also found some packets...which have LG BITs set to 1 .. when i think
0 should be the correct
Hi,
I have been looking deeper into my wireshark packet captures and found
something that could be helpfull.
I can see using wireshark that the Ethernet NIC at least does something.
ARP BROADCAST traffic is seen.
But i also found some packets...which have LG BITs set to 1 .. when i think
0
Hi,
I have been looking deeper into my wireshark packet captures and found
something that could be helpfull.
I can see using wireshark that the Ethernet NIC at least does something.
ARP BROADCAST traffic is seen.
But i also found some packets...which have LG BITs set to 1 .. when i think
0
Hi,
I have been looking deeper into my wireshark packet captures and found
something that could be helpfull.
I can see that the Ethernet NICS at least do something. ARP BROADCAST
traffic is seen.
But i also found some packets...which have LG BITs set to 1 .. when i think
0 should be the correct
> *Given this if we disable that bit, we get the matching "Universally
> Administered Address" 0100 (Binary), 04 (Hex) -> "04:00:00", hence my
> question:"*
>
> This has something to do with the MAC adresses being locally administered
> .. and since whe can use Uboot and choose any Mac addr
> > You appear to be using an old kernel. Take a look at:
>
> Not really, I am using 4.14.x and I don't think that is old.
Development for 4.14 stopped somewhere around the beginning of
September. So there has been over 4 months of work since then. We are
clearly interested in fixing bugs in
On Thu, 1970-01-01 at 00:00 +, Andrew Lunn wrote:
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
>
>
> > Hi, just saw this and thought of a small patch I just wrote
osoft.de>; Joakim Tjernlund
> <joakim.tjernl...@infinera.com>; linuxppc-dev@lists.ozlabs.org; Madalin-
> cristian Bucur <madalin.bu...@nxp.com>; net...@vger.kernel.org
> Subject: Re: DPAA Ethernet traffice troubles with Linux kernel
>
> > When i use mii-tool too Kick the t
> Hi, just saw this and thought of a small patch I just wrote for mdio bus, o
> idea
> if it is relevant but here goes:
>
> From fe0b98d54a79779482700676331b4d10a0f3cada Mon Sep 17 00:00:00 2001
> From: Joakim Tjernlund
> Date: Sun, 14 Jan 2018 21:27:20 +0100
>
> When i use mii-tool too Kick the tranceiver... it comes alive.. i can
> ping the eth0 itself
>
> root@X5000LNX:/home/skateman# mii-tool -R eth0
> resetting the transceiver...
> root@X5000LNX:/home/skateman# ping 192.168.22.44
> PING 192.168.22.44 (192.168.22.44) 56(84) bytes of data.
> 64 bytes
Some extra info:
When Ubuntu boots, Eth0 (192.168.22.44) is not brought up automaticly..
When i bring up eth0 by hand, its still not active..
root@X5000LNX:/home/skateman# ifconfig eth0 up
root@X5000LNX:/home/skateman# ping 192.168.22.44
connect: Network is unreachable
When i use mii-tool too
Hi All,
I have been testing with the rc8 kernel as Christian sugested.
At this moment still the same issues..
Here some of my finding...
A dump of dmesg regarding the FSL_DPAA:
[4.597949] libphy: Fixed MDIO Bus: probed
[4.599095] libphy: Freescale PowerQUICC MII Bus: probed
[
On Thu, 1970-01-01 at 00:00 +, Madalin-cristian Bucur wrote:
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
>
>
> > -Original Message-
> > From: Linuxppc-dev
> -Original Message-
> From: Linuxppc-dev [mailto:linuxppc-dev-
> bounces+madalin.bucur=nxp@lists.ozlabs.org] On Behalf Of mad skateman
> Sent: Wednesday, January 10, 2018 10:39 PM
> To: linuxppc-dev@lists.ozlabs.org
> Subject: DPAA Ethernet traffice troubles with Linux kernel
>
> Hi
33 matches
Mail list logo