From: Anders Widman <andewid@tnonline.net>
To: "Sam James" <sam.james@adelphia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Entire LAN goes boo with 2.5.64
Date: Thu, 6 Mar 2003 14:58:18 +0100 [thread overview]
Message-ID: <406624312.20030306145818@tnonline.net> (raw)
In-Reply-To: <68CDBCD4C718204B8E3AE0DE304DDB680154CD85@cdptpaex1.adelphia.com>
> Sounds like a bpdu storm, are you somehow looping the network?
Not that I am aware of.. Running only one 8 port switch. Works good
with the 2.4.x kernels, but not with 2.5.. very odd.
//Anders
> -----Original Message-----
> From: Anders Widman [mailto:andewid@tnonline.net]
> Sent: Thursday, March 06, 2003 6:02 AM
> To: Erik Hensema
> Cc: linux-kernel@vger.kernel.org; erik@hensema.net
> Subject: Re: Entire LAN goes boo with 2.5.64
>> 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?
> Nope, no vcool or anything similar. But it is very odd that the switch
> would go crazy too!
>> [1] all machines were seeing frame errors on packets > 250 bytes; it
>> was a 10 mbit coax lan.
> Using 100mbit switched network.
> --------
> PGP public key: https://tnonline.net/secure/pgp_key.txt
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in the body of a message to majordomo@vger.kernel.org More majordomo
> info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--------
PGP public key: https://tnonline.net/secure/pgp_key.txt
next parent reply other threads:[~2003-03-06 13:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <68CDBCD4C718204B8E3AE0DE304DDB680154CD85@cdptpaex1.adelphia.com>
2003-03-06 13:58 ` Anders Widman [this message]
2003-03-07 19:49 Entire LAN goes boo with 2.5.64 Jon Burgess
2003-03-07 21:10 ` 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
-- 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=406624312.20030306145818@tnonline.net \
--to=andewid@tnonline.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sam.james@adelphia.com \
/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).