netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: pollockd@magma.ca
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
	netdev@oss.sgi.com, damouse@ntlworld.com,
	brad@mainstreetsoftworks.com, kinetik@orcon.net.nz
Subject: Re: Realtek 8169 Lock-ups
Date: Tue, 13 Jan 2004 11:55:41 -0500	[thread overview]
Message-ID: <1074012941.5886.12.camel@localhost> (raw)
In-Reply-To: <4001A41C.3070205@pobox.com>

[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]

On Sun, 2004-01-11 at 14:29, Jeff Garzik wrote:
> Douglas Pollock wrote:
> The kernel comes with "pktgen" which is a free packet generator you can 
> use for stressing kernels and LANs.  There is also ttcp, nttcp, various 
> filesystems tests over NFS (such as bonnie++), various block device 
> tests over nbd (network block device), ...

Thanks for that.  I should have remembered the packet generator.  Using
pktgen, I am able to reproduce the problem.


HARDWARE:
Intel P4 with hyper-threading enabled
Realtek 8169 (rev. 10)
Switched 100Mbps network
A second machine on the same network (to receive test packets)

SOFTWARE:
Kernel 2.6.0 or 2.6.1-rc1 (possibly others), with SMP for 2 processors,
Realtek 8169 driver, and packet generator


STEPS TO REPRODUCE:
1.) Set up the ipg script to send to the second machine on the 8169 NIC.
2.) pgset pkt_size 9014
3.) pg


OBSERVATIONS:
Soon after step #3, the 8169 NIC will stop responding (note: the netdev
watchdog reports a timeout in dmesg).  No packets get through.  However,
everything else still works.  Disabling SMP in the kernel fixes this
problem.



Doug.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-01-13 16:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-11 16:23 Realtek 8169 Lock-ups Douglas Pollock
     [not found] ` <4001A41C.3070205@pobox.com>
2004-01-13 16:55   ` pollockd [this message]
     [not found] <1073507006.5151.61.camel@localhost>
     [not found] ` <20040107232034.A22930@electric-eye.fr.zoreil.com>
     [not found]   ` <1073596694.6378.6.camel@localhost>
2004-01-11  8:23     ` Jeff Garzik
2004-01-11 11:49       ` Francois Romieu
2004-01-12 23:03         ` Francois Romieu
2004-01-13 23:04           ` Francois Romieu
     [not found]           ` <1074020596.5336.0.camel@localhost>
2004-01-13 23:57             ` Francois Romieu
     [not found]               ` <1074449824.5286.4.camel@localhost>
     [not found]                 ` <20040119005555.A1399@electric-eye.fr.zoreil.com>
2004-01-23 13:00                   ` Douglas Pollock

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=1074012941.5886.12.camel@localhost \
    --to=pollockd@magma.ca \
    --cc=brad@mainstreetsoftworks.com \
    --cc=damouse@ntlworld.com \
    --cc=dpollock@acm.org \
    --cc=jgarzik@pobox.com \
    --cc=kinetik@orcon.net.nz \
    --cc=netdev@oss.sgi.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 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).