From: Andrew Morton <akpm@osdl.org>
To: Folkert van Heusden <folkert@vanheusden.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6.15] running tcpdump on 3c905b causes freeze (reproducable)
Date: Sat, 14 Jan 2006 06:04:57 -0800 [thread overview]
Message-ID: <20060114060457.06efae88.akpm@osdl.org> (raw)
In-Reply-To: <20060114132414.GN6087@vanheusden.com>
Folkert van Heusden <folkert@vanheusden.com> wrote:
>
> > > > > > 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.
> > > > No change. Well, that is: the last message on the console now is
> > > > "setting eth1 to promiscues mode".
> > > Did you confirm that the NMI counters in /proc/interrupts are incrementing?
> > Yes:
> > root@muur:/home/folkert# for i in `seq 1 5` ; do cat /proc/interrupts | grep NMI ; sleep 1 ; done
> > NMI: 6949080 6949067
> > NMI: 6949182 6949169
> > NMI: 6949284 6949271
> > NMI: 6949386 6949373
> > NMI: 6949488 6949475
>
> Is there anything else I can try?
argh. I haven't forgotten. Hopefully after -rc1 I'll have more time...
Your report didn't mention whether that card work OK under earlier 2.6
kernels. If it does, a bit of bisection searching would really help.
next prev parent reply other threads:[~2006-01-14 14:05 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
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 [this message]
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=20060114060457.06efae88.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=folkert@vanheusden.com \
--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).