All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Slinn <mslinn@zamples.com>
To: lartc@vger.kernel.org
Subject: Re: [Fwd: Re: [LARTC] ssh and cs LAG]
Date: Wed, 13 Oct 2004 22:39:17 +0000	[thread overview]
Message-ID: <416DAE95.5000003@zamples.com> (raw)
In-Reply-To: <416D8C3A.3050602@wp.pl>

We had no problems with smp on 2.6.8.3, and since this cpu supports 
hyperthreading we enjoy a *big* power boost using smp.  :)

Mike


Andy Furniss wrote:

> Hariett Jones wrote:
>
>> 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
>
>
> I had to unselect SMP in kernel config to get my rtl8139 + PCI modem 
> to work with 2.6.8.1
>
> Andy.
>
>> 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/
>


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

  parent reply	other threads:[~2004-10-13 22:39 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 ` AW: " Stephan M. Ott
2004-10-13 21:58 ` Jason Boxman
2004-10-13 22:09 ` Mike Slinn
2004-10-13 22:15 ` Andy Furniss
2004-10-13 22:39 ` Mike Slinn [this message]
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=416DAE95.5000003@zamples.com \
    --to=mslinn@zamples.com \
    --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.