From: Michael Brade <brade@informatik.uni-muenchen.de>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org, nic_swsd@realtek.com,
Hayes <hayeswang@realtek.com>
Subject: Re: r8169 hard-freezes the system on big network loads
Date: Wed, 14 Sep 2011 23:36:16 +0200 [thread overview]
Message-ID: <201109142336.17291.brade@informatik.uni-muenchen.de> (raw)
In-Reply-To: <20110913081126.GA20022@electric-eye.fr.zoreil.com>
On Tuesday 13 September 2011 10:11:26 you wrote:
> Michael Brade <brade@informatik.uni-muenchen.de> :
> [...]
>
> > Does it have to be 3.1.0-rc3 or is 3.0.1 ok as well ?
> :
> :o(
>
> Almost any release may exhibit the bug. The attached patch (#0003)
> should be a better candidate as an official fix though.
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++;
- }
> > If so, I have another bad news: 3.0.1 still crashes with this patch.
> > It took me a lot longer to crash it but eventually it did happen.
> > Not sure why it took longer, I guess I didn't generate enough throughput.
>
> It sure sucks from a user experience viewpoint but it is not _that_ bad.
I disagree - I actually lose data because I mount my data and backups with
iSCSI and exactly then it crashes.
> 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
[ 1613.450630] r8169 0000:13:00.0: eth0: link up
[ 1613.929383] r8169 0000:13:00.0: eth0: link up
[ 1614.950939] r8169 0000:13:00.0: eth0: link up
[ 1615.699660] r8169 0000:13:00.0: eth0: link up
[ 1616.005507] r8169 0000:13:00.0: eth0: link up
[ 1616.746199] r8169 0000:13:00.0: eth0: link up
[ 1617.879670] r8169 0000:13:00.0: eth0: link up
[ 1618.461433] r8169 0000:13:00.0: eth0: link up
so yes but what do you mean with "no real network traffic"? I still get
100 MB/s.
cheers,
Michael
next prev parent reply other threads:[~2011-09-14 21:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-14 11:08 r8169 hard-freezes the system on big network loads Kjun Chen
2011-08-21 12:33 ` Francois Romieu
2011-08-21 13:20 ` Michael Brade
2011-08-21 22:11 ` Francois Romieu
2011-08-23 13:17 ` Francois Romieu
2011-09-11 20:16 ` Michael Brade
2011-09-13 8:11 ` Francois Romieu
2011-09-14 21:36 ` Michael Brade [this message]
2011-09-15 0:03 ` Francois Romieu
2011-09-15 10:26 ` Michael Brade
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=201109142336.17291.brade@informatik.uni-muenchen.de \
--to=brade@informatik.uni-muenchen.de \
--cc=hayeswang@realtek.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=romieu@fr.zoreil.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 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.