From: "Thomas A. Oehser" <tom@toms.net>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: "Thomas A. Oehser" <tom@toms.net>, netdev@vger.kernel.org
Subject: Re: r8169 locks up in 2.6.16.5
Date: Sun, 16 Apr 2006 18:58:43 -0400 [thread overview]
Message-ID: <20060416225843.GA2274@jupiter.toms.net> (raw)
In-Reply-To: <20060416195327.GA14173@electric-eye.fr.zoreil.com>
[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]
> How much long was the card under load ? A few seconds ?
> The same 1500 bytes mtu is used everywhere and the issue can not be
> reproduced with a simple ping -f -q -l 64 -s what_you_want aimed at
> the 8169, right ?
Correct,
> > What next?
>
> ethtool -d/-S before and after failure, .config and /proc/interrupts.
Ok, here it all is, the attached archive has:
- .before is right after the interface came up
- .mid is after flooding it with ping -f commands from 2 machines at once
- .bad is after doing the cpio over nc that killed it after 170MB
- .back is after ifconfig down / ifconfig up that restored it
Note, the kernel config has SMP etc turned back on, as it doesn't
seem to affect things, and the eepro100 back on eth0, I'm testing
this against eth1 so that the machine can be normally useful as well...
r8169-bad/ifconfig.before
r8169-bad/dmesg.before
r8169-bad/arp-n.before
r8169-bad/ethtool-d.before
r8169-bad/ethtool-S.before
r8169-bad/config.gz
r8169-bad/proc-interrupts.before
r8169-bad/ping-during
r8169-bad/dmesg.mid
r8169-bad/arp-n.mid
r8169-bad/ifconfig.mid
r8169-bad/ethtool-d.mid
r8169-bad/ethtool-S.mid
r8169-bad/proc-interrupts.mid
r8169-bad/ifconfig.bad
r8169-bad/dmesg.bad
r8169-bad/ethtool-d.bad
r8169-bad/ethtool-S.bad
r8169-bad/proc-interrupts.bad
r8169-bad/ifconfig.back
r8169-bad/dmesg.back
r8169-bad/ethtool-d.back
r8169-bad/ethtool-S.back
r8169-bad/proc-interrupts.back
-Thanks, -Tom
[-- Attachment #2: r8169-bad.tar.bz2 --]
[-- Type: application/octet-stream, Size: 18535 bytes --]
next prev parent reply other threads:[~2006-04-16 22:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 20:47 r8169 locks up in 2.6.16.5 Thomas A. Oehser
2006-04-16 0:58 ` Francois Romieu
2006-04-16 13:42 ` Thomas A. Oehser
2006-04-16 14:43 ` Francois Romieu
2006-04-16 17:26 ` Thomas A. Oehser
2006-04-16 19:53 ` Francois Romieu
2006-04-16 22:58 ` Thomas A. Oehser [this message]
2006-04-17 23:09 ` Francois Romieu
2006-04-18 0:43 ` Thomas A. Oehser
2006-04-18 23:04 ` [patch] " Francois Romieu
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=20060416225843.GA2274@jupiter.toms.net \
--to=tom@toms.net \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).