From: Folkert van Heusden <folkert@vanheusden.com>
To: Andrew Morton <akpm@osdl.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6.15] running tcpdump on 3c905b causes freeze (reproducable)
Date: Mon, 9 Jan 2006 15:45:22 +0100 [thread overview]
Message-ID: <20060109144522.GB10955@vanheusden.com> (raw)
In-Reply-To: <20060109041114.6e797a9b.akpm@osdl.org>
> > My system freezes (crashes) when I run tcpdump on the interface
> > connected to a 3c905b card.
> Works for me with a 3c980-TX. I can dig out a 905b.
> Please send the exact commands which you're using to demonstrate this -
> sufficient info for me to get as close as possible to what you're doing.
The exact command is:
tcpdump -i eth1
Yes, it is that simple. Not only tcpdump gives this problem; iftop as
well.
> Have you tried enabling the NMI watchdog? Enable CONFIG_X86_LOCAL_APIC and
> boot with `nmi_watchdog=1' on the command line, make sure that the NMI line
> of /proc/interrupts is incrementing.
I'll give it a try. I've added it to the append-line in the lilo config.
Am now compiling the kernel.
Folkert van Heusden
--
Try MultiTail! Multiple windows with logfiles, filtered with regular
expressions, colored output, etc. etc. www.vanheusden.com/multitail/
----------------------------------------------------------------------
Get your PGP/GPG key signed at www.biglumber.com!
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
next prev parent reply other threads:[~2006-01-09 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-08 11:43 [2.6.15] running tcpdump on 3c905b causes freeze (reproducable) Folkert van Heusden
2006-01-09 12:11 ` Andrew Morton
2006-01-09 14:45 ` Folkert van Heusden [this message]
2006-01-09 19:37 ` Folkert van Heusden
2006-01-10 6:48 ` Andrew Morton
2006-01-10 14:27 ` Folkert van Heusden
2006-01-14 13:24 ` Folkert van Heusden
2006-01-14 14:04 ` Andrew Morton
2006-01-14 23:36 ` Folkert van Heusden
2006-02-26 14:03 ` Folkert van Heusden
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=20060109144522.GB10955@vanheusden.com \
--to=folkert@vanheusden.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).