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

Srihari Vijayaraghavan <harisri@bigpond.com> :
[vmstat 1 output]

Ok, mostly idle.

[...]
> > 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.

Can you verify that your kernel tree is fine or give an (sh-)history of
the applied patches ?

I have just checked and the patch applies cleanly on kernel 2.6.1-bk2 +
Jeff's 2.6.1-bk1-netdev4 as well as on kernel 2.6.1-bk4 + Jeff's
2.6.1-bk4-netdev1. 

--
Ueimor

  reply	other threads:[~2004-01-19 23:24 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
2004-01-19 23:24     ` Francois Romieu [this message]
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=20040120002422.A19029@electric-eye.fr.zoreil.com \
    --to=romieu@fr.zoreil.com \
    --cc=harisri@bigpond.com \
    --cc=netdev@oss.sgi.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).