From: "Jon Burgess" <Jon_Burgess@eur.3com.com>
To: andewid@tnonline.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Entire LAN goes boo with 2.5.64
Date: Fri, 7 Mar 2003 19:49:50 +0000 [thread overview]
Message-ID: <80256CE2.006CEFC2.00@notesmta.eur.3com.com> (raw)
Some things you might want to look at:
Is the Linux box sending any traffic (look at the stats in ifconfig)?
Does a packet sniffer like http://www.ethereal.com/ give any clues as to the
type of traffic on the network?
Does the same thing occur if you run less processes, e.g. boot into run level
1 or 3?
Are there any processes consuming an unreasonable amount of CPU time on the
Linux box?
Is there a process which is being restarted many times a second, so top or ps
shows a radiply increasing PID?
It could be some network-aware process which has got stuck in a tight loop
sending requests to your windows box, e.g. a DHCP client.
I mention the DHCP client specifically because they sometimes get upset if you
don't enable some specific kernel networking options like CONFIG_PACKET or
CONFIG_FILTER & WinRoute might be acting as the DHCP server.
Jon
next reply other threads:[~2003-03-07 19:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 19:49 Jon Burgess [this message]
2003-03-07 21:10 ` Entire LAN goes boo with 2.5.64 Anders Widman
2003-03-07 22:35 ` Ricky Beam
2003-03-07 22:39 ` Anders Widman
[not found] <20030306094021$7081@gated-at.bofh.it>
[not found] ` <3E679878.2090807@datadirectnet.com>
2003-03-06 19:58 ` Anders Widman
2003-03-06 20:38 ` Anders Widman
[not found] <68CDBCD4C718204B8E3AE0DE304DDB680154CD85@cdptpaex1.adelphia.com>
2003-03-06 13:58 ` Anders Widman
-- strict thread matches above, loose matches on Subject: below --
2003-03-06 9:36 Anders Widman
2003-03-06 9:39 ` Anders Widman
2003-03-06 9:58 ` Erik Hensema
2003-03-06 11:01 ` Anders Widman
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=80256CE2.006CEFC2.00@notesmta.eur.3com.com \
--to=jon_burgess@eur.3com.com \
--cc=andewid@tnonline.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.