From: Francois Romieu <romieu@fr.zoreil.com>
To: Seblu <seblu@seblu.net>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>, Ivan Vecera <ivecera@redhat.com>
Subject: Re: Mass udp flow reboot linux with RealTek RTL-8169 Gigabit
Date: Thu, 10 Mar 2011 13:08:56 +0100 [thread overview]
Message-ID: <20110310120856.GA14219@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <AANLkTim6tt4yC+1VQ3AtDMf1KKLRqf5kErpipqNSbQkX@mail.gmail.com>
Seblu <seblu@seblu.net> :
[...]
> I catched the following trace during my previous torture session.
> Maybe it can help.
It's the usual r8169 TX timeout watchdog.
[...]
> > Can you apply the two attached patches on top of the previous ones and
> > give it a try ? The debug should not be too verbose if things are stationary
> > enough.
> 2.6.38-rc7 with your 2 previous patch change the game. No reboot. No
> strange message in dmesg.
?
"strange message" as :
[ ] netdev watchdog messages
[ ] 0001 0001 0001 0001 (or similar) message
[ ] net_ratelimit message
> But some sent packets are lost from some host. Example:
[...]
> This is maybe normal under stress, card discard packet after all.
It seems so. 0.08% packet loss. 10 ~ 20kpps (right ?). Sample at 0.1 Hz (ping).
[...]
> I've a serial cable and a second computer, but my first computer
> doesn't have a com port. Is it then possible?
Hardly. Forget it for now.
> Do you need more test?
1. 2.6.38-rc7 without the patches
2. 2.6.38-rc7 with the r8169.c driver of 2.6.38-rc5, without the patches
3. current setup + pktgen. Lower the packet size as long as it increases
the sender's pps.
I do not understand why the bug would be gone if it was in the r8169
proper.
--
Ueimor
next prev parent reply other threads:[~2011-03-10 12:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 1:35 Seblu
2011-02-13 7:17 ` Eric Dumazet
2011-02-13 13:56 ` Francois Romieu
2011-02-13 17:27 ` Seblu
2011-02-13 18:02 ` Seblu
2011-02-13 20:34 ` Francois Romieu
2011-02-18 2:54 ` Seblu
2011-02-18 9:30 ` Francois Romieu
2011-03-06 0:29 ` Seblu
2011-03-10 12:08 ` Francois Romieu [this message]
2011-02-21 11:56 Hans Nieser
2011-02-22 17:33 Hans Nieser
2011-02-23 9:55 ` Francois Romieu
2011-02-23 12:21 ` Hans Nieser
2011-02-23 18:31 ` Hans Nieser
2011-02-25 13:45 ` Hans Nieser
2011-03-03 19:53 ` Hans Nieser
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=20110310120856.GA14219@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=eric.dumazet@gmail.com \
--cc=ivecera@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=seblu@seblu.net \
/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®