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: Tue, 20 Jan 2004 21:50:12 +1100	[thread overview]
Message-ID: <200401202150.12892.harisri@bigpond.com> (raw)
In-Reply-To: <20040120002422.A19029@electric-eye.fr.zoreil.com>

Hello Francois,

On Tuesday 20 January 2004 10:24, Francois Romieu wrote:
> > 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 ?

cd /usr/local/src
tar xfj /media/cdrecorder/v2.6/linux-2.6.0.tar.bz2
cd linux-2.6.0
bunzip2 -c /media/cdrecorder/v2.6/patch-2.6.1.bz2 |patch -p1
bunzip2 -c ~/linux/patch-2.6.1-bk2.bz2 |patch -p1
bunzip2 -c ~/linux/2.6.1-bk1-netdev4.patch.bz2 |patch -p1
patch -p1 --dry-run < ~/linux/r8169/r8169-tx-index-overflow.patch
patching file drivers/net/r8169.c
Hunk #1 succeeded at 1341 (offset 364 lines).
Hunk #2 FAILED at 1351.
Hunk #3 succeeded at 1365 with fuzz 1 (offset 367 lines).
1 out of 3 hunks FAILED -- saving rejects to file drivers/net/r8169.c.rej

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

Interesting.

In this very thread you mentioned (in which you did not cc me BTW :-) that you 
welcomed AMD64-RTL8169 users, that gave me an idea. I tested this computer 
under 32 bit kernel (vanilla Fedora + 2.6.1-mm4) in which it survives my 
torture test (I have verified for no more than 5 minutes though, but then it 
does not survive for more than 5 secs under the 64 bit kernel).

(And BTW I do not like binary only kernel modules, and I do these bug 
reporting "for fun", and there is no fun in binary only modules. I have been 
reading lkml for long enough to understand that :-)

Thanks for help and suggestions so far, I appreciate them.

Hari

  reply	other threads:[~2004-01-20 10:50 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
2004-01-20 10:50       ` Srihari Vijayaraghavan [this message]
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=200401202150.12892.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).