From: Raphael Manfredi <Raphael_Manfredi@pobox.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] back from NETDEV WATCHDOG: eth0: transmit timed out
Date: Wed, 31 Oct 2001 23:51:56 +0100 [thread overview]
Message-ID: <22563.1004568716@nice.ram.loc> (raw)
I found a way to get me out of the dreadful
NETDEV WATCHDOG: eth0: transmit timed out
condition, which irremediably used to hang the network on my machine,
forcing me to reboot.
This fix was inspired by the long thread between Manfred Spraul and
Franck de Lange, a while back.
The fix leads to the following trail in kern.log:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Tx queue start entry 23742746 dirty entry 23742742.
eth0: Tx descriptor 0 is 00002000.
eth0: Tx descriptor 1 is 00002000.
eth0: Tx descriptor 2 is 00002000. (queue head)
eth0: Tx descriptor 3 is 00002000.
eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 45e1.
Kicking IO-APIC pin #16:
NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
Before:
00 003 03 0 1 1 1 0 1 1 91
After switching to edge:
00 003 03 0 0 1 1 0 1 1 91
After switch back:
00 003 03 0 1 1 1 0 1 1 91
nfs: server lyon not responding, still trying
nfs: server lyon not responding, still trying
nfs: server lyon OK
nfs: server lyon OK
Here's the patch. It only fixes the 8139too.c network driver, because
this is the one relevant for me. Perhaps this can be added to other
drivers as well?
NOTE: the printk(KERN_EMERG) is probably too high for logging everything.
A KERN_CRIT would perhaps be more suitable, but Manfred had used this
in his patch, and I respected his decision. However, having all my xterms
clogged with:
Message from syslogd@nice at Wed Oct 31 23:37:36 2001 ...
nice kernel: Kicking IO-APIC pin #16:
is probably excessive ;-)
Raphael
--- ./drivers/net/8139too.c.orig Mon Oct 29 19:33:34 2001
+++ ./drivers/net/8139too.c Mon Oct 29 19:47:09 2001
@@ -1732,6 +1732,7 @@
/* ...and finally, reset everything */
rtl8139_hw_start (dev);
+ kick_IOAPIC_pin(dev->irq); /* Added by RAM */
netif_wake_queue (dev);
}
--- ./arch/i386/kernel/io_apic.c.orig Mon Oct 29 19:34:42 2001
+++ ./arch/i386/kernel/io_apic.c Mon Oct 29 19:45:18 2001
@@ -1616,3 +1616,59 @@
check_timer();
print_IO_APIC();
}
+
+/*
+ * Added by RAM, from Manfred Spraul
+ */
+static void print_line(struct IO_APIC_route_entry* entry)
+{
+ printk(KERN_EMERG " %02x %03X %02X ",
+ 0,
+ entry->dest.logical.logical_dest,
+ entry->dest.physical.physical_dest
+ );
+ printk("%1d %1d %1d %1d %1d %1d %1d %02X\n",
+ entry->mask,
+ entry->trigger,
+ entry->irr,
+ entry->polarity,
+ entry->delivery_status,
+ entry->dest_mode,
+ entry->delivery_mode,
+ entry->vector
+ );
+}
+
+void kick_IOAPIC_pin(int pin)
+{
+ unsigned long flags;
+ struct IO_APIC_route_entry entry;
+
+ spin_lock_irqsave(&ioapic_lock, flags);
+
+ *(((int *)&entry) + 1) = io_apic_read(0, 0x11 + 2 * pin);
+ *(((int *)&entry) + 0) = io_apic_read(0, 0x10 + 2 * pin);
+
+ printk(KERN_EMERG "Kicking IO-APIC pin #%d:\n", pin);
+ printk(KERN_EMERG " NR Log Phy Mask Trig IRR Pol"
+ " Stat Dest Deli Vect: \n");
+ printk(KERN_EMERG "Before:\n");
+ print_line(&entry);
+
+ entry.trigger = 0;
+ io_apic_write(0, 0x11 + 2 * pin, *(((int *)&entry) + 1));
+ io_apic_write(0, 0x10 + 2 * pin, *(((int *)&entry) + 0));
+ udelay(10);
+ printk(KERN_EMERG "After switching to edge:\n");
+ print_line(&entry);
+
+ entry.trigger = 1;
+ io_apic_write(0, 0x11 + 2 * pin, *(((int *)&entry) + 1));
+ io_apic_write(0, 0x10 + 2 * pin, *(((int *)&entry) + 0));
+ udelay(10);
+ printk(KERN_EMERG "After switch back:\n");
+ print_line(&entry);
+
+ spin_unlock_irqrestore(&ioapic_lock, flags);
+}
+
reply other threads:[~2001-10-31 23:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=22563.1004568716@nice.ram.loc \
--to=raphael_manfredi@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/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