All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephan M. Ott" <webmaster@familie-ott.info>
To: lartc@vger.kernel.org
Subject: AW: [Fwd: Re: [LARTC] ssh and cs LAG]
Date: Wed, 13 Oct 2004 21:34:46 +0000	[thread overview]
Message-ID: <001001c4b16c$8d9baa70$3700a8c0@nathanxp> (raw)
In-Reply-To: <416D8C3A.3050602@wp.pl>

Switching back to older kernel won't do much.
I've had this problem much earlier when using two NICs of the same type.
I couldn't figure out why, but there ARE problems is many ways when
using two cards of the same type. I had problems with sharing, with
routing, etc. etc.
Best solution is to use different NICs... don't ask me why... I just
found out that this will solve the problems...



-----Ursprüngliche Nachricht-----
Von: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl] Im
Auftrag von Hariett Jones
Gesendet: Mittwoch, 13. Oktober 2004 22:13
An: lartc@mailman.ds9a.nl
Betreff: [Fwd: Re: [LARTC] ssh and cs LAG]

Got some solutions myself.

LAG is caused by :
NETDEV WATCHDOG eth0 timeout

this is caused bacause of problems with rtl8139 network card in kernel
2.6.x

Solutions :
1.add in lilo.conf : append="noapic"
2.turn apic off in bios
3.if u have 2 rtl8139 cards, then exchange one with some other card type

(chipset)

btw. all above was found in various polish forums, but none has worked 
for me. im switching kernel back to 2.4.22, and will report later .



_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2004-10-13 21:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-13 20:12 [Fwd: Re: [LARTC] ssh and cs LAG] Hariett Jones
2004-10-13 21:34 ` Stephan M. Ott [this message]
2004-10-13 21:58 ` AW: " Jason Boxman
2004-10-13 22:09 ` Mike Slinn
2004-10-13 22:15 ` Andy Furniss
2004-10-13 22:39 ` Mike Slinn
2004-10-13 23:24 ` Andy Furniss

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='001001c4b16c$8d9baa70$3700a8c0@nathanxp' \
    --to=webmaster@familie-ott.info \
    --cc=lartc@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.