Before using tcpdump to troubleshoot a network problem, I had a system
uptime of more than 60 days on 2.0.28, but as soon as I start tcpdump (and
leave it running) the system experiences hard lockups (the software
watchdog doesn't even realize it and reset) on a regular and repeatable
basis.
In my testing, I've noticed uptimes of between 10 minutes and 6 hours on a
fairly low traffic network, before the system locks up. After realizing
that this was the problem, I tried a variety of things on several systems
that had no problems until I started using promiscuous mode.
I've tested on previously extrememly stable systems using 2.0.6, 2.0.18,
2.0.24, 2.0.25, 2.0.28 and 2.0.30. I've used tcpdump and netwatch, and
both cause hard lockups. The use of promiscuous mode is the only thing I
can think of that matches all the symptoms. If I don't start apps that
use promiscuous mode, the system runs without problems.
Suggestions? I'll be happy to provide more info as requested.
-- | Evan Harris - Consultant, Harris Enterprises - eharris@puremagic.com | | Custom Solutions for your Software, Networking, and Telephony Needs