From: Francois Romieu <romieu@fr.zoreil.com>
To: Bernd Fuhrmann <silverbanana@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: usage of RealTek 8169 crashes my Linux system
Date: Mon, 29 Mar 2004 21:56:31 +0200 [thread overview]
Message-ID: <20040329215631.A4694@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <40687B75.3090709@gmx.de>; from silverbanana@gmx.de on Mon, Mar 29, 2004 at 09:39:33PM +0200
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
Bernd Fuhrmann <silverbanana@gmx.de> :
[...]
> problem. Linux still crashes after a couple of MBytes have passed the r8169.
>
> Thanks for your effort. Any other idea how to fix that problem (like
> doing things that make r8169 stable while loosing performance)?
The attached patch applies on top of 2.6.5-rc2-mm5 without fuss.
Could you verify that the computer is otherwise stable if you issue a
'dd if=/dev/hda of=/dev/null bs=1024k' for 120~150 seconds ?
An output of lspci -vx/dmesg/lsmod is always welcome btw.
--
Ueimor
[-- Attachment #2: r8169-break-irq-loop.patch --]
[-- Type: text/plain, Size: 2199 bytes --]
drivers/net/r8169.c | 32 ++++++++++++++++++--------------
1 files changed, 18 insertions(+), 14 deletions(-)
diff -puN drivers/net/r8169.c~r8169-break-irq-loop drivers/net/r8169.c
--- linux-2.6.5-rc2-mm5/drivers/net/r8169.c~r8169-break-irq-loop 2004-03-29 21:45:07.000000000 +0200
+++ linux-2.6.5-rc2-mm5-fr/drivers/net/r8169.c 2004-03-29 21:45:38.000000000 +0200
@@ -1352,21 +1352,21 @@ rtl8169_tx_interrupt(struct net_device *
while (tx_left > 0) {
int entry = dirty_tx % NUM_TX_DESC;
+ struct sk_buff *skb = tp->Tx_skbuff[entry];
+ u32 status = le32_to_cpu(tp->TxDescArray[entry].status);
- if (!(le32_to_cpu(tp->TxDescArray[entry].status) & OWNbit)) {
- struct sk_buff *skb = tp->Tx_skbuff[entry];
+ if (status & OWNbit)
+ break;
- /* FIXME: is it really accurate for TxErr ? */
- tp->stats.tx_bytes += skb->len >= ETH_ZLEN ?
- skb->len : ETH_ZLEN;
- tp->stats.tx_packets++;
- rtl8169_unmap_tx_skb(tp->pci_dev, tp->Tx_skbuff + entry,
- tp->TxDescArray + entry);
- dev_kfree_skb_irq(skb);
- tp->Tx_skbuff[entry] = NULL;
- dirty_tx++;
- tx_left--;
- }
+ /* FIXME: is it really accurate for TxErr ? */
+ tp->stats.tx_bytes += skb->len >= ETH_ZLEN ?
+ skb->len : ETH_ZLEN;
+ tp->stats.tx_packets++;
+ rtl8169_unmap_tx_skb(tp->pci_dev, tp->Tx_skbuff + entry,
+ tp->TxDescArray + entry);
+ dev_kfree_skb_irq(skb);
+ dirty_tx++;
+ tx_left--;
}
if (tp->dirty_tx != dirty_tx) {
@@ -1404,6 +1404,7 @@ rtl8169_rx_interrupt(struct net_device *
{
unsigned long cur_rx, rx_left;
int delta;
+ int max_try = 8192;
assert(dev != NULL);
assert(tp != NULL);
@@ -1412,7 +1413,7 @@ rtl8169_rx_interrupt(struct net_device *
cur_rx = tp->cur_rx;
rx_left = NUM_RX_DESC + tp->dirty_rx - cur_rx;
- while (rx_left > 0) {
+ while ((rx_left > 0) && --max_try) {
int entry = cur_rx % NUM_RX_DESC;
u32 status = le32_to_cpu(tp->RxDescArray[entry].status);
@@ -1455,6 +1456,9 @@ rtl8169_rx_interrupt(struct net_device *
rx_left--;
}
+ if (!max_try)
+ printk(KERN_INFO "%s: strangeness in Rx handler", dev->name);
+
tp->cur_rx = cur_rx;
delta = rtl8169_rx_fill(tp, dev, tp->dirty_rx, tp->cur_rx);
_
next prev parent reply other threads:[~2004-03-29 19:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 20:24 Bernd Fuhrmann
2004-03-28 20:37 ` Jeff Garzik
2004-03-28 21:50 ` Bernd Fuhrmann
2004-03-28 22:35 ` Jeff Garzik
2004-03-28 22:36 ` Francois Romieu
2004-03-29 19:39 ` Bernd Fuhrmann
2004-03-29 19:56 ` Francois Romieu [this message]
2004-03-30 9:08 ` Bernd Fuhrmann
2004-03-29 8:41 ` Claudio Martins
2004-03-29 16:18 ` Francois Romieu
2004-03-29 9:24 ` Daniel Egger
2004-03-29 16:13 ` Francois Romieu
2004-03-29 16:20 ` Francois Romieu
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=20040329215631.A4694@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=silverbanana@gmx.de \
/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
all inboxes | Powered by JetHome®