From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: mad skateman <madskateman@gmail.com>,
Madalin-cristian Bucur <madalin.bucur@nxp.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Jamie Krueger <jamie@bitbybitsoftwaregroup.com>
Subject: Re: DPAA Ethernet traffice troubles with Linux kernel
Date: Tue, 6 Feb 2018 12:20:57 +0100 [thread overview]
Message-ID: <1d62c827-0ff7-0372-a2f8-f1930e9f788c@xenosoft.de> (raw)
In-Reply-To: <CAHkrCmGxFUbfEyufdYhFYA4jyOkh+W2z=1yZsZwv+O4t+hE_1w@mail.gmail.com>
Hello,
I have tried to figure out why there is a problem with the buffer space
but unfortunately without any success. Any ideas? Could you please watch
Skateman's video? [1]
Thanks,
Christian
[1] https://drive.google.com/file/d/18RhksfcavRJPr86asQDTzrmsN20D0Xim/view
On 03 February 2018 at 12:54PM, mad skateman wrote:
>
> For those interested... i have recorded a video of my X5000 DPAA
Ethernet, and the weird problems..
> In this Video i am also transfering hundereds of megabytes from my
NAS to the X5000.
> You will also see pings die... mostly after the 12th packet and
giving the no buffer space error..
> Hopefully someone might have a clue about what is happening.
>
> https://drive.google.com/file/d/18RhksfcavRJPr86asQDTzrmsN20D0Xim/view
>
> On Wed, Jan 17, 2018 at 3:43 PM, Madalin-cristian Bucur
<madalin.bucur@nxp.com> wrote:
>
> > -----Original Message-----
> > From: Madalin-cristian Bucur
> > Sent: Wednesday, January 17, 2018 4:25 PM
> > To: David S . Miller <davem@davemloft.net>
> > Cc: linuxppc-dev@lists.ozlabs.org; netdev@vger.kernel.org;
> > madskateman@gmail.com; 'Madalin-cristian Bucur'
<madalin.bucur@nxp.com>;
> > Andrew Lunn <andrew@lunn.ch>; Joakim Tjernlund
> > <Joakim.Tjernlund@infinera.com>
> > Subject: RE: DPAA Ethernet traffice troubles with Linux kernel
> >
> > > -----Original Message-----
> > > From: netdev-owner@vger.kernel.org
[mailto:netdev-owner@vger.kernel.org]
> > > On Behalf Of Madalin-cristian Bucur
> > > Sent: Wednesday, January 17, 2018 4:16 PM
> > > To: Andrew Lunn <andrew@lunn.ch>; Joakim Tjernlund
> > > <Joakim.Tjernlund@infinera.com>
> > > Cc: linuxppc-dev@lists.ozlabs.org; netdev@vger.kernel.org;
> > > madskateman@gmail.com; David S . Miller <davem@davemloft.net>
> > > Subject: RE: DPAA Ethernet traffice troubles with Linux kernel
> > >
> > > > -----Original Message-----
> > > > From: Andrew Lunn [mailto:andrew@lunn.ch]
> > > > Sent: Wednesday, January 17, 2018 3:44 PM
> > > > To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
> > > > Subject: Re: DPAA Ethernet traffice troubles with Linux kernel
> > > >
> > > > > 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 though" is a big point of asking
for it to
> > > > added to stable. The other reason is it means one less
patch you need
> > > > to maintain in your build.
> > >
> > > I've sent that patch [1] for net but I guess the timing was
wrong and
> > > it was merged to net-next.
> > >
> > > > > I would be interested in bug fixes upstream which fixes:
> > > >
> > > > Did you try upstream? Does it give the same errors?
> > > >
> > > > Andrew
> > >
> > > [1] https://patchwork.kernel.org/patch/10146119/
> > >
> > > Madalin
> >
> > Hi Dave,
> >
> > Can you please add the fix [1] to stable?
> >
> > Thank you,
> > Madalin
>
> Sorry,
>
> I've provided the wrong link towards the patch (v1 instead of v3),
> here's the correct one:
>
> https://patchwork.kernel.org/patch/10151969/
>
> Madalin
>
>
next prev parent reply other threads:[~2018-02-06 11:21 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 20:39 DPAA Ethernet traffice troubles with Linux kernel mad skateman
2018-01-15 16:38 ` Madalin-cristian Bucur
2018-01-15 16:59 ` Joakim Tjernlund
2018-01-15 19:03 ` Christian Zigotzky
2018-01-15 19:09 ` Christian Zigotzky
2018-01-15 20:21 ` mad skateman
2018-01-15 21:32 ` mad skateman
2018-01-16 15:04 ` Andrew Lunn
2018-01-16 17:07 ` Madalin-cristian Bucur
2018-01-16 14:38 ` Andrew Lunn
2018-01-16 17:57 ` Joakim Tjernlund
2018-01-16 18:16 ` mad skateman
2018-01-16 18:38 ` mad skateman
2018-01-16 18:39 ` mad skateman
2018-01-17 5:54 ` Christian Zigotzky
2018-01-16 18:44 ` mad skateman
2018-01-16 21:00 ` Andrew Lunn
2018-01-16 21:15 ` mad skateman
2018-01-16 20:53 ` Andrew Lunn
2018-01-17 11:47 ` Joakim Tjernlund
2018-01-17 12:06 ` mad skateman
2018-01-17 13:43 ` Andrew Lunn
2018-01-17 14:15 ` Madalin-cristian Bucur
2018-01-17 14:24 ` Madalin-cristian Bucur
2018-01-17 14:43 ` Madalin-cristian Bucur
2018-02-03 11:54 ` mad skateman
2018-02-06 11:20 ` Christian Zigotzky [this message]
2018-02-07 21:00 ` mad skateman
2018-02-07 21:17 ` Andrew Lunn
2018-02-07 22:13 ` Christian Zigotzky
2018-01-17 14:11 ` Madalin-cristian Bucur
2018-01-17 15:00 ` Joakim Tjernlund
2018-01-18 9:04 ` Joakim Tjernlund
2018-01-19 8:00 ` Joakim Tjernlund
2018-01-19 13:22 ` Andrew Lunn
2018-01-19 13:42 ` Joakim Tjernlund
2018-02-04 16:47 ` PA Semi PWRficient Gigabit Ethernet doesn't work anymore since the first networking updates for the kernel 4.16 Christian Zigotzky
2018-02-04 17:16 ` Andrew Lunn
2018-02-04 20:01 ` Florian Fainelli
2018-02-05 9:38 ` Christian Zigotzky
2018-02-05 14:29 ` Andrew Lunn
2018-02-05 15:27 ` Christian Zigotzky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1d62c827-0ff7-0372-a2f8-f1930e9f788c@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=andrew@lunn.ch \
--cc=jamie@bitbybitsoftwaregroup.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@nxp.com \
--cc=madskateman@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).