From: Erik Hensema <usenet@hensema.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Entire LAN goes boo with 2.5.64
Date: Thu, 6 Mar 2003 09:58:56 +0000 (UTC) [thread overview]
Message-ID: <slrnb6e6uv.18e.usenet@bender.home.hensema.net> (raw)
In-Reply-To: 185124756546.20030306103945@tnonline.net
Anders Widman (andewid@tnonline.net) wrote:
>
>> Hello,
>
>> Trying out the 2.5.64 kernel to try to solve some IDE specific
>> problems with 2.4.x kernels. Now I have another problem. We have a
>> Windows LAN and a Windows XP with WinRoute Pro as gateway.
>
>> When booting the linux-machine with the 2.5.64 kernel the windows
>> machine goes to 100% cpu and the switch (Dlink) goes crazy (loosing
>> link, other machines get 100k/s instead of 10-12MiB/s etc).
>
>> I compiled the 2.5.64 with as few options as possible, no
>> netfilter, or IPSec or similar stuff.
>
>> What can be the problem?
>
> Forgot to say I am using a Intel Pro100+ NIC and I have tested with
> both the Becker driver and the Intel driver.
I've seen something similar [1] happen to a LAN with one Windows XP machine
running vcool: http://vcool.occludo.net/ . This is also available for Linux
(http://vcool.occludo.net/VC_Linux.html). Are you running this patch or a
similar one?
[1] all machines were seeing frame errors on packets > 250 bytes; it was a
10 mbit coax lan.
--
Erik Hensema <erik@hensema.net>
next prev parent reply other threads:[~2003-03-06 9:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 9:36 Entire LAN goes boo with 2.5.64 Anders Widman
2003-03-06 9:39 ` Anders Widman
2003-03-06 9:58 ` Erik Hensema [this message]
2003-03-06 11:01 ` Anders Widman
[not found] <68CDBCD4C718204B8E3AE0DE304DDB680154CD85@cdptpaex1.adelphia.com>
2003-03-06 13:58 ` 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
2003-03-07 19:49 Jon Burgess
2003-03-07 21:10 ` Anders Widman
2003-03-07 22:35 ` Ricky Beam
2003-03-07 22:39 ` 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=slrnb6e6uv.18e.usenet@bender.home.hensema.net \
--to=usenet@hensema.net \
--cc=erik@hensema.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 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).