Re[2]: e1000 problems in 2.6.x

Re[2]: e1000 problems in 2.6.x

[Elikster]

Hello Bill,

    You are not alone.  It happened to all boxes with Intel E1000 network cards and integrated.  It happened on 2.6.2 kernel version and I downgraded back to 2.4.24 version and it was running fine.  The problems I experienced is network lag and lot of network disconnects and such.  It is the kernel 2.6.2 that this problem showed up.

   I haven't tried the latest versions yet that Linus just released to see if they fixed that issue yet.

Saturday, February 14, 2004, 8:22:43 PM, you wrote:

BD> Steve Simitzis wrote:
>> i should have mentioned in my email that i tried every combination of
>> settings: auto-neg on the box and forced on the switch, both forced
>> (to the same settings, of course), forced on the box with auto-neg on
>> the switch, and auto-neg on both sides. in all cases, the result was
>> the same: RX packet errors and the same watchdog messages. what i thought
>> was particularly strange was that the switch refused to auto-negotiate
>> full duplex.



-- 
Best regards,
 Elikster                            mailto:elik@webspires.com

Re[2]: e1000 problems in 2.6.x

[Klaus Dittrich]

I have a Tyan-S2665 mobo which has an intergrated
e1000 and I never saw such errors with 2.6 kernels. 

I use it with 100-MBit Full-Duplex in a switched 
private network.

CONFIG_IP_MULTICAST=y
CONFIG_E1000=y
CONFIG_E1000_NAPI=y

-- 
Klaus

Re[3]: e1000 problems in 2.6.x

[Elikster]

Hello Klaus,

   Hmmm..that might explains it, since I don't use NAPI enabled on the E1000 and it works fine without in the 2.4.x series kernels, but under 2.6, it barfs half the time.

Sunday, February 15, 2004, 8:20:57 AM, you wrote:

KD> I have a Tyan-S2665 mobo which has an intergrated
KD> e1000 and I never saw such errors with 2.6 kernels. 

KD> I use it with 100-MBit Full-Duplex in a switched 
KD> private network.

KD> CONFIG_IP_MULTICAST=y
KD> CONFIG_E1000=y
KD> CONFIG_E1000_NAPI=y




-- 
Best regards,
 Elikster                            mailto:elik@webspires.com

Re: e1000 problems in 2.6.x

[Steve Simitzis]

that doesn't explain it for me. i have NAPI enabled in the kernel, and
i still have problems in 2.6.x, and not in 2.4.22.

CONFIG_E1000=m
CONFIG_E1000_NAPI=y

:(

On 02/15/04, Elikster <elik@webspires.com> wrote: 

> Hello Klaus,
> 
>    Hmmm..that might explains it, since I don't use NAPI enabled on the E1000 and it works fine without in the 2.4.x series kernels, but under 2.6, it barfs half the time.
> 
> Sunday, February 15, 2004, 8:20:57 AM, you wrote:
> 
> KD> I have a Tyan-S2665 mobo which has an intergrated
> KD> e1000 and I never saw such errors with 2.6 kernels. 
> 
> KD> I use it with 100-MBit Full-Duplex in a switched 
> KD> private network.
> 
> KD> CONFIG_IP_MULTICAST=y
> KD> CONFIG_E1000=y
> KD> CONFIG_E1000_NAPI=y
> 
> 
> 
> 
> -- 
> Best regards,
>  Elikster                            mailto:elik@webspires.com
> 
> -
> 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/

-- 

steve simitzis : /sim' - i - jees/
          pala : saturn5 productions
 www.steve.org : 415.282.9979
  hath the daemon spawn no fire?