netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srihari Vijayaraghavan <harisri@bigpond.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@oss.sgi.com
Subject: Re: [PROBLEM] r8169 deadlocks
Date: Mon, 19 Jan 2004 22:51:41 +1100	[thread overview]
Message-ID: <200401192251.41323.harisri@bigpond.com> (raw)
In-Reply-To: <20040115220827.A22007@electric-eye.fr.zoreil.com>

Hello Francois,

On Friday 16 January 2004 08:08, Francois Romieu wrote:
> Can you monitor 'vmstat 1' output on the r8169 host during the test ?

Here it is (2.6.1-bk2-netdev4):
procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us sy id wa
 1  0      0 887000  10820  87992    0    0   291    47 1051   170  7  4 83  6

 0  0      0 886800  10820  87992    0    0     0   108 1042    13  0  0 100  
0
 0  0      0 886800  10820  87992    0    0     0     0 1008     3  0  0 100  
0
 0  0      0 886800  10820  87992    0    0     0     0 1008     3  0  0 100  
0
 0  0      0 886800  10820  87992    0    0     0     0 1008     3  0  0 100  
0
 0  0      0 886800  10836  87992    0    0     0    56 1013    18  0  0 100  
0
 0  0      0 886800  10840  87992    0    0     0     4 1009    10  0  0 100  
0
 0  0      0 886800  10840  87992    0    0     0     0 1008     3  0  0 100  
0
 0  0      0 886800  10840  87992    0    0     0     0 1008     3  0  0 100  
0
 0  0      0 886800  10840  87992    0    0     0     0 1008     3  0  0 100  
0
 0  0      0 886800  10848  87992    0    0     0    16 1011    11  0  0 100  
0
 0  0      0 886800  10848  87992    0    0     0     0 1008     7  0  0 100  
0
 0  0      0 886800  10848  87992    0    0     0     0 1008     3  0  0 100  
0
 0  0      0 886800  10848  87992    0    0     0     0 1008     3  0  0 100  
0
 0  0      0 886800  10848  87992    0    0     0     0 1008     3  0  0 100  
0
 0  0      0 886800  10856  87992    0    0     0    16 1011    11  0  0 100  
0
 0  0      0 886800  10864  87992    0    0     0   140 1037    12  0  0 100  
0
 0  0      0 886800  10864  87992    0    0     0     0 1008     3  0  0 100  
0
 2  0      0 886472  10864  87992    0    0     0     0 1305  1958 12 12 76  0

It hung at the final entry.

> You can try 2.6.1-bk2 + Jeff Garzik's -netdev4 +
> http://www.fr.zoreil.com/people/francois/misc/r8169-tx-index-overflow.patch

The r8169-tc-index-overflow.patch does not (cleanly) apply on 2.6.1-bk2 + 
netdev4.

> If it does not perform better, you can try against 2.6.1-bk1 the set at
> http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.1-bk1-b

I am yet to try this combination.

Thanks
Hari

  parent reply	other threads:[~2004-01-19 11:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15  9:38 [PROBLEM] r8169 deadlocks Srihari Vijayaraghavan
2004-01-15 21:08 ` Francois Romieu
2004-01-17  1:34   ` Srihari Vijayaraghavan
2004-01-17 12:53     ` Francois Romieu
2004-01-19 11:51   ` Srihari Vijayaraghavan [this message]
2004-01-19 23:24     ` Francois Romieu
2004-01-20 10:50       ` Srihari Vijayaraghavan
2004-01-20 20:52         ` Francois Romieu
2004-01-21 10:15           ` Srihari Vijayaraghavan
2004-01-21 23:59             ` Francois Romieu
2004-01-22 10:32               ` Srihari Vijayaraghavan

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=200401192251.41323.harisri@bigpond.com \
    --to=harisri@bigpond.com \
    --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).