From: Steve Simitzis <steve@saturn5.com>
To: Elikster <elik@webspires.com>
Cc: linux mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: e1000 problems in 2.6.x
Date: Sun, 15 Feb 2004 18:12:01 -0800 [thread overview]
Message-ID: <20040216021201.GA23254@saturn5.com> (raw)
In-Reply-To: <121605967.20040215181417@webspires.com>
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?
next prev parent reply other threads:[~2004-02-16 2:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 15:20 Re[2]: e1000 problems in 2.6.x Klaus Dittrich
2004-02-16 1:14 ` Re[3]: " Elikster
2004-02-16 2:12 ` Steve Simitzis [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-16 4:17 Paul Blazejowski
2004-02-17 18:26 ` Anton Blanchard
2004-02-15 0:26 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-14 11:13 Steve Simitzis
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=20040216021201.GA23254@saturn5.com \
--to=steve@saturn5.com \
--cc=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