[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110915000332.GA13821@electric-eye.fr.zoreil.com>
Date: Thu, 15 Sep 2011 02:03:32 +0200
From: Francois Romieu <romieu@...zoreil.com>
To: Michael Brade <brade@...ormatik.uni-muenchen.de>
Cc: netdev@...r.kernel.org, nic_swsd@...ltek.com,
Hayes <hayeswang@...ltek.com>
Subject: Re: r8169 hard-freezes the system on big network loads
Michael Brade <brade@...ormatik.uni-muenchen.de> :
[...]
> ok, good news: I did not experience any freeze anymore even though I
> transfered 60 GB. And I applied both of your patches and
>
> - if (status & RxFOVF) {
> - rtl8169_schedule_work(dev, rtl8169_reset_task);
> - dev->stats.rx_fifo_errors++;
> - }
It should not be necessary to remove this part : the status mask is
supposed to take care of it. One of my patches is wrong if this part
needs to go away.
[...]
> > Are the symptoms in any way different or do you still notice more-or-less
> > periodic link-up messages and no real network traffic ?
>
> dmesg looks like this:
>
> [ 1611.380420] r8169 0000:13:00.0: eth0: link up
> [ 1611.995417] r8169 0000:13:00.0: eth0: link up
> [ 1612.323050] r8169 0000:13:00.0: eth0: link up
> [ 1612.574016] r8169 0000:13:00.0: eth0: link up
I will have to figure why there are so much of theses messages.
[...]
> so yes but what do you mean with "no real network traffic"? I still get
> 100 MB/s.
100 MB/s as 100 Mbyte/s on a gigabit link or 100 Mbit/s on a {gigabit / fast}
ethernet link ?
Thanks.
--
Ueimor
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists