From: Elikster <elik@webspires.com>
To: linux-kernel@vger.kernel.org
Subject: Re[2]: e1000 problems in 2.6.x
Date: Sun, 15 Feb 2004 01:16:47 -0700 [thread overview]
Message-ID: <1693736809.20040215011647@webspires.com> (raw)
In-Reply-To: <402EE603.8020106@tmr.com>
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
next prev parent reply other threads:[~2004-02-15 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 0:26 e1000 problems in 2.6.x Feldman, Scott
2004-02-15 2:32 ` Steve Simitzis
2004-02-15 3:22 ` Bill Davidsen
2004-02-15 3:53 ` Steve Simitzis
2004-02-15 8:16 ` Elikster [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-15 15:20 Re[2]: " Klaus Dittrich
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=1693736809.20040215011647@webspires.com \
--to=elik@webspires.com \
--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