From: Matt Mackall <mpm@selenic.com>
To: Mark Broadbent <markb@wetlettuce.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Lockup with 2.6.9-ac15 related to netconsole
Date: Fri, 17 Dec 2004 13:57:52 -0800 [thread overview]
Message-ID: <20041217215752.GP2767@waste.org> (raw)
In-Reply-To: <34721.192.102.214.6.1103274614.squirrel@webmail.wetlettuce.com>
On Fri, Dec 17, 2004 at 09:10:14AM -0000, Mark Broadbent wrote:
>
> Matt Mackall said:
> > On Thu, Dec 16, 2004 at 04:20:02PM -0000, Mark Broadbent wrote:
> >> Hi,
> >>
> >> I'm having problem using ethereal/tcpdump in conjunction with the
> >> netconsole (built as a module). If the netconsole is loaded and I try
> >> to launch tcpdump on the same interface as the netconsole is
> >> transmitting I get a hard lock-up. The following commands can
> >> consistently do this: # tcpdump -i eth0
> >> eth0: Promiscuous Mode Entered
> >> <... normal output ...>
> >> ^C
> >> # modprobe netconsole
> >> # tcpdump -i eth0
> >> eth0: Promiscuous Mode Entered
> >> <4>NMI Watchdog detected LOCKUP
> >
> > Joy. Can you try it on your other interface to see if it's
> > driver-specific?
>
> Tried using eth1 which is using the r8169 but it doesn't support polling.
> I also tried with 2.6.10-rc3-bk10 but it still doesn't support polling.
> Also it still locks up using eth0 (the tulip driver) with 2.6.10-rc3-bk10.
Please try the attached untested, uncompiled patch to add polling to
r8169:
Index: l/drivers/net/r8169.c
===================================================================
--- l.orig/drivers/net/r8169.c 2004-11-04 10:53:04.779520000 -0800
+++ l/drivers/net/r8169.c 2004-12-17 13:30:35.367771000 -0800
@@ -1120,6 +1120,9 @@
dev->weight = R8169_NAPI_WEIGHT;
printk(KERN_INFO PFX "NAPI enabled\n");
#endif
+#ifdef CONFIG_NET_POLL_CONTROLLER
+ dev->poll_controller = rtl8169_netpoll;
+#endif
tp->intr_mask = 0xffff;
tp->pci_dev = pdev;
tp->mmio_addr = ioaddr;
@@ -1839,6 +1842,15 @@
}
#endif
+#ifdef CONFIG_NET_POLL_CONTROLLER
+static void rtl8169_netpoll(struct net_device *dev)
+{
+ disable_irq(dev->irq);
+ rtl8169_interrupt(dev->irq, netdev, NULL);
+ enable_irq(dev->irq);
+}
+#endif
+
static int
rtl8169_close(struct net_device *dev)
{
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2004-12-17 22:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 16:20 Lockup with 2.6.9-ac15 related to netconsole Mark Broadbent
2004-12-16 21:10 ` Matt Mackall
2004-12-17 9:10 ` Mark Broadbent
2004-12-17 21:57 ` Matt Mackall [this message]
2004-12-17 23:35 ` Francois Romieu
2004-12-18 13:25 ` Mark Broadbent
2004-12-20 9:42 ` Mark Broadbent
2004-12-20 21:14 ` Matt Mackall
2004-12-21 0:22 ` Francois Romieu
2004-12-21 0:55 ` Matt Mackall
2004-12-21 10:23 ` Mark Broadbent
2004-12-21 12:37 ` Francois Romieu
2004-12-21 13:29 ` Mark Broadbent
2004-12-21 20:48 ` Francois Romieu
2004-12-21 21:27 ` Matt Mackall
2004-12-21 22:58 ` Francois Romieu
2004-12-22 9:34 ` Patrick McHardy
2004-12-22 10:54 ` Patrick McHardy
2004-12-22 12:39 ` Francois Romieu
2004-12-22 13:33 ` jamal
2004-12-22 14:57 ` Patrick McHardy
2004-12-22 17:18 ` Matt Mackall
2004-12-25 11:26 ` Wish you all a Merry Christmas Pranav
2004-12-25 11:30 ` Jan Engelhardt
2004-12-28 13:45 ` Lockup with 2.6.9-ac15 related to netconsole jamal
2004-12-22 14:37 ` Mark Broadbent
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=20041217215752.GP2767@waste.org \
--to=mpm@selenic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markb@wetlettuce.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