From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: Freescale FEC packet loss
Date: Thu, 23 Jan 2014 15:20:56 +0100 [thread overview]
Message-ID: <201401231520.56990.marex@denx.de> (raw)
In-Reply-To: <1288e1f778f74c669ad15b62d32e8859@BLUPR03MB373.namprd03.prod.outlook.com>
On Thursday, January 23, 2014 at 02:49:48 AM, fugang.duan at freescale.com wrote:
[...]
> >[ 3] 71.0-72.0 sec 23.4 MBytes 196 Mbits/sec
> >[ 3] 72.0-73.0 sec 12.2 MBytes 103 Mbits/sec
> >[ 3] 73.0-74.0 sec 0.00 Bytes 0.00 bits/sec [ 3] 74.0-75.0 sec 0.00
> >Bytes 0.00 bits/sec [ 3] 75.0-76.0 sec 10.9 MBytes 91.2 Mbits/sec
> >[ 3] 76.0-77.0 sec 22.4 MBytes 188 Mbits/sec
> >[ 3] 77.0-78.0 sec 23.0 MBytes 193 Mbits/sec
>
> I will debug the issue when I am free, and then report the result to you.
> Thanks for your reporting the issue.
Hi Andy,
Thanks for looking into this. Is there any way I can help you with figuring out
the issue ? Do you need any more feedback or anything please ?
Thank you!
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marex@denx.de>
To: "fugang.duan@freescale.com" <fugang.duan@freescale.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Frank.Li@freescale.com" <Frank.Li@freescale.com>,
"Fabio.Estevam@freescale.com" <Fabio.Estevam@freescale.com>,
Hector Palacios <hector.palacios@digi.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Detlev Zundel <dzu@denx.de>,
"Eric Nelson" <eric.nelson@boundarydevices.com>
Subject: Re: Freescale FEC packet loss
Date: Thu, 23 Jan 2014 15:20:56 +0100 [thread overview]
Message-ID: <201401231520.56990.marex@denx.de> (raw)
In-Reply-To: <1288e1f778f74c669ad15b62d32e8859@BLUPR03MB373.namprd03.prod.outlook.com>
On Thursday, January 23, 2014 at 02:49:48 AM, fugang.duan@freescale.com wrote:
[...]
> >[ 3] 71.0-72.0 sec 23.4 MBytes 196 Mbits/sec
> >[ 3] 72.0-73.0 sec 12.2 MBytes 103 Mbits/sec
> >[ 3] 73.0-74.0 sec 0.00 Bytes 0.00 bits/sec [ 3] 74.0-75.0 sec 0.00
> >Bytes 0.00 bits/sec [ 3] 75.0-76.0 sec 10.9 MBytes 91.2 Mbits/sec
> >[ 3] 76.0-77.0 sec 22.4 MBytes 188 Mbits/sec
> >[ 3] 77.0-78.0 sec 23.0 MBytes 193 Mbits/sec
>
> I will debug the issue when I am free, and then report the result to you.
> Thanks for your reporting the issue.
Hi Andy,
Thanks for looking into this. Is there any way I can help you with figuring out
the issue ? Do you need any more feedback or anything please ?
Thank you!
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-01-23 14:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 21:55 Freescale FEC packet loss Marek Vasut
2014-01-22 21:55 ` Marek Vasut
2014-01-23 1:49 ` fugang.duan at freescale.com
2014-01-23 1:49 ` fugang.duan
2014-01-23 14:20 ` Marek Vasut [this message]
2014-01-23 14:20 ` Marek Vasut
2014-01-24 1:28 ` fugang.duan at freescale.com
2014-01-24 1:28 ` fugang.duan
2014-01-26 18:56 ` Ben Hutchings
2014-01-26 18:56 ` Ben Hutchings
2014-01-26 19:12 ` Marek Vasut
2014-01-26 19:12 ` Marek Vasut
2014-01-26 21:33 ` Ben Hutchings
2014-01-26 21:33 ` Ben Hutchings
2014-01-28 1:01 ` Marek Vasut
2014-01-28 1:01 ` Marek Vasut
2014-02-06 9:42 ` Christian Gmeiner
2014-02-06 9:42 ` Christian Gmeiner
2014-02-06 13:41 ` Marek Vasut
2014-02-06 13:41 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2014-02-06 5:30 Christian Ege
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=201401231520.56990.marex@denx.de \
--to=marex@denx.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.