mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Brade <brade@informatik.uni-muenchen.de>
To: linux-kernel@vger.kernel.org
Subject: [SOLVED: r8169 is the culprit] Re: 2.6.39, 3.0.0-rc7+: complete system freeze with rsync on big directory
Date: Sun, 14 Aug 2011 00:17:30 +0200	[thread overview]
Message-ID: <201108140017.31063.brade@informatik.uni-muenchen.de> (raw)
In-Reply-To: <201107212013.14561.brade@informatik.uni-muenchen.de>

Hi,

finally I found the reason for my system freeze: the r8169 module. The freeze 
happens only on heavy network loads, i.e. > 70 MB/s. iSCSI is really fast, 
that's why I only saw the freezes with iSCSI.

> But watching the normal console I get loads of
> 
> r8169 0000:13:00.0: eth0: link up
> r8169 0000:13:00.0: eth0: link up

This does not happen with 2.6.32.28, and the system doesn't freeze either with 
this kernel. So the r8169 is fine on 2.6.32.x. 2.6.37 and above freeze the 
system. I haven't tried any kernel in between .32 and .37.

> [...]
> 
> lspci:
> 
> 13:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B
> PCI Express Gigabit Ethernet controller (rev 03)

The solution with 2.6.37 and above: use the r8168 module from the realtek 
website. I have tested it with >30 GB at rates of 112 MB/s and experienced no 
freeze anymore.

I don't know if you are interested in fixing r8169 but if so and you need 
anything, let me know how I can help.

cheers,
  Michael

  reply	other threads:[~2011-08-13 22:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-21  9:19 Michael Brade
2011-07-21  9:28 ` Lars Täuber
2011-07-21 18:13   ` Michael Brade
2011-08-13 22:17     ` Michael Brade [this message]
2011-08-13 22:49       ` [SOLVED: r8169 is the culprit] " David Miller
2011-07-21 19:40   ` 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=201108140017.31063.brade@informatik.uni-muenchen.de \
    --to=brade@informatik.uni-muenchen.de \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®