From: Jeremy Jackson <jerj@coplanar.net>
To: Matthew Callaway <matt@kindjal.net>
Cc: becker@scyld.com, linux-kernel@vger.kernel.org
Subject: Re: Network init script causes 2.2.18 kernel oops (tulip driver)
Date: Thu, 15 Mar 2001 12:32:56 -0500 [thread overview]
Message-ID: <3AB0FCC8.A54396C6@coplanar.net> (raw)
In-Reply-To: <Pine.LNX.4.32.0103151045490.31295-100000@gummy.wi.securepipe.com>
Matthew Callaway wrote:
> Greetings,
>
> This is a reproducible oops, and my guess is that it's related to
> the tulip driver included in the 2.2.18 source tree. We're using
> a D-Link 4 port NIC, and it appears that it doesn't work well with
> IPV6 interfaces.
I have had problems with this NIC as well... Redhat's installer/kudzu
tries to use de4x5 (sp?) module ... bad news. But it works fine using
old_tulip module with only IPv4. Same with 2.2 series and 2.4 series
kernels. FYI
>
>
> Keywords: linux kernel-2.2.18 tulip D-Link 4-port NIC DFE-570 TX
prev parent reply other threads:[~2001-03-15 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 17:07 Network init script causes 2.2.18 kernel oops (tulip driver) Matthew Callaway
2001-03-15 17:32 ` Jeremy Jackson [this message]
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=3AB0FCC8.A54396C6@coplanar.net \
--to=jerj@coplanar.net \
--cc=becker@scyld.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@kindjal.net \
/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