Re: Zynq macb

2014-03-14 Thread Sören Brinkmann
On Fri, 2014-03-14 at 06:37AM +0100, Michal Simek wrote: > On 03/13/2014 11:33 PM, Sören Brinkmann wrote: > > On Thu, 2014-03-13 at 03:16PM -0700, Sören Brinkmann wrote: > >> Hi Nicolas, > >> > >> I did some testing on the current linux-next tree and ran iperf on Zynq. > >> It seems that network an

Re: Zynq macb

2014-03-14 Thread Sören Brinkmann
On Fri, 2014-03-14 at 06:37AM +0100, Michal Simek wrote: > On 03/13/2014 11:33 PM, Sören Brinkmann wrote: > > On Thu, 2014-03-13 at 03:16PM -0700, Sören Brinkmann wrote: > >> Hi Nicolas, > >> > >> I did some testing on the current linux-next tree and ran iperf on Zynq. > >> It seems that network an

Re: Zynq macb

2014-03-13 Thread Michal Simek
On 03/13/2014 11:33 PM, Sören Brinkmann wrote: > On Thu, 2014-03-13 at 03:16PM -0700, Sören Brinkmann wrote: >> Hi Nicolas, >> >> I did some testing on the current linux-next tree and ran iperf on Zynq. >> It seems that network and even the whole system can collapse when doing >> that. >> I don't r

Re: Zynq macb

2014-03-13 Thread Sören Brinkmann
On Thu, 2014-03-13 at 03:16PM -0700, Sören Brinkmann wrote: > Hi Nicolas, > > I did some testing on the current linux-next tree and ran iperf on Zynq. > It seems that network and even the whole system can collapse when doing > that. > I don't really know what's going on, but once I saw the message

Zynq macb

2014-03-13 Thread Sören Brinkmann
Hi Nicolas, I did some testing on the current linux-next tree and ran iperf on Zynq. It seems that network and even the whole system can collapse when doing that. I don't really know what's going on, but once I saw the message: "inconsistent Rx descriptor chain" printed twice (system froze