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 21:52:30 +0100 [thread overview]
Message-ID: <20040120215230.A8935@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <200401202150.12892.harisri@bigpond.com>; from harisri@bigpond.com on Tue, Jan 20, 2004 at 09:50:12PM +1100
Srihari Vijayaraghavan <harisri@bigpond.com> :
> On Tuesday 20 January 2004 10:24, Francois Romieu wrote:
[...]
> 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
$ cat>foo<<EOD
tar jxf linux-2.6.0.tar.bz2
bunzip2 -c patch-2.6.1.bz2 | patch -p1 -d linux-2.6.0
bunzip2 -c patch-2.6.1-bk2.bz2 | patch -p1 -d linux-2.6.0
bunzip2 -c 2.6.1-bk1-netdev4.patch.bz2 | patch -p1 -d linux-2.6.0
wget http://www.fr.zoreil.com/people/francois/misc/r8169-tx-index-overflow.patch
EOD
$ sh foo
[...]
$ patch -p1 -d linux-2.6.0 < r8169-tx-index-overflow.patch
patching file drivers/net/r8169.c
Okay...
$ md5sum r8169-tx-index-overflow.patch
99b2f5886d6bf1d4df0f7553bb5bef57 r8169-tx-index-overflow.patch
[...]
> In this very thread you mentioned (in which you did not cc me BTW :-) that
> welcomed AMD64-RTL8169 users, that gave me an idea. I tested this computer
I did :o)
----- The following addresses had permanent fatal errors -----
<harisri@bigpond.com>
(reason: 554 recipient <harisri@bigpond.com> exceeds mailbox storage quota)
> 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).
Point taken.
--
Ueimor
next prev parent reply other threads:[~2004-01-20 20:52 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
2004-01-20 20:52 ` Francois Romieu [this message]
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=20040120215230.A8935@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).