linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anders Widman <andewid@tnonline.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Entire LAN goes boo  with 2.5.64
Date: Thu, 6 Mar 2003 20:58:42 +0100	[thread overview]
Message-ID: <1328248062.20030306205842@tnonline.net> (raw)
In-Reply-To: <3E679878.2090807@datadirectnet.com>

Tried  with  a  Realtek  8139B and the Intel Pro100+ adapter. The same
thing   happens.   The   LAN   goes  crazy  and all programs trying to
access or use the LAN on the Linuxbox goes super-slow or crashes.

I am rather lost when it comes to where I should begin to look.

Have not compiled in IPX, network filtering and most other things. The
only  network  card  I  have compiled in is the Rtl8139 and the Becker
Intel Pro100+ driver.

Here is my net config: http://tnonline.net/conf.png

I  have  not compiled in ACPI or APM or APIC. And they are disabled in
BIOS too.

//Anders


> I've had this happen once, but with a 2.4 kernel. I had compiled in IPX
> and configured it for autodiscovery of frame type. On boot, it would
> flip back and forth between two different types rather fast (as fast as
> the 100base NIC could do it), freaking out every piece of networking
> equipment and every computer. See if you have IPX compiled in. 
> Otherwise, run ethereal or another sniffer to see what exactly the 
> network traffic is; that might be helpful.

> Alexander

> Anders Widman 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?
>> 
>> 
>> --------
>> 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


       reply	other threads:[~2003-03-06 19:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030306094021$7081@gated-at.bofh.it>
     [not found] ` <3E679878.2090807@datadirectnet.com>
2003-03-06 19:58   ` Anders Widman [this message]
2003-03-06 20:38     ` Entire LAN goes boo with 2.5.64 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
     [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=1328248062.20030306205842@tnonline.net \
    --to=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 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).