From: Francois Romieu <romieu@fr.zoreil.com>
To: Srihari Vijayaraghavan <harisri@bigpond.com>
Cc: netdev@oss.sgi.com, jgarzik@pobox.com
Subject: Re: [PROBLEM] r8169 deadlocks
Date: Thu, 22 Jan 2004 00:59:40 +0100 [thread overview]
Message-ID: <20040122005940.A26438@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <200401212115.45027.harisri@bigpond.com>; from harisri@bigpond.com on Wed, Jan 21, 2004 at 09:15:44PM +1100
[-- Attachment #1: Type: text/plain, Size: 523 bytes --]
Srihari Vijayaraghavan <harisri@bigpond.com> :
[...]
> I have a good news: I checked out things as usual under vanilla
> linux-2.6.2-rc1, and to my surprise Kernel does not hang anymore :-).
> (although Tx counter not incrementing is altogether another problem).
r8169 did not evolve between 2.6.1 and 2.6.2-rc1. Change of behavior
probably comes from some other part of the kernel. Joy.
> If you want me to I can test your r8169-tc-index-overflow.patch.
See attachment. It applies against plain 2.6.2-rc1.
--
Ueimor
[-- Attachment #2: r8169.c-diff --]
[-- Type: text/plain, Size: 872 bytes --]
--- linux-2.6.2-rc1/drivers/net/r8169.c.orig 2004-01-22 00:41:03.000000000 +0100
+++ linux-2.6.2-rc1/drivers/net/r8169.c 2004-01-22 00:46:46.000000000 +0100
@@ -871,7 +871,6 @@ rtl8169_tx_interrupt(struct net_device *
void *ioaddr)
{
unsigned long dirty_tx, tx_left = 0;
- int entry = tp->cur_tx % NUM_TX_DESC;
assert(dev != NULL);
assert(tp != NULL);
@@ -881,14 +880,14 @@ rtl8169_tx_interrupt(struct net_device *
tx_left = tp->cur_tx - dirty_tx;
while (tx_left > 0) {
+ int entry = dirty_tx % NUM_TX_DESC;
+
if ((tp->TxDescArray[entry].status & OWNbit) == 0) {
- dev_kfree_skb_irq(tp->
- Tx_skbuff[dirty_tx % NUM_TX_DESC]);
- tp->Tx_skbuff[dirty_tx % NUM_TX_DESC] = NULL;
+ dev_kfree_skb_irq(tp->Tx_skbuff[entry]);
+ tp->Tx_skbuff[entry] = NULL;
tp->stats.tx_packets++;
dirty_tx++;
tx_left--;
- entry++;
}
}
next prev parent reply other threads:[~2004-01-21 23:59 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
2004-01-21 10:15 ` Srihari Vijayaraghavan
2004-01-21 23:59 ` Francois Romieu [this message]
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=20040122005940.A26438@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=harisri@bigpond.com \
--cc=jgarzik@pobox.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).