From: Yann Dupont <Yann.Dupont@IPv6.univ-nantes.fr>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PATCH 2.4.4.ac9: Tulip net driver fixes
Date: 15 May 2001 10:08:50 +0200 [thread overview]
Message-ID: <989914130.25256.1.camel@olive> (raw)
In-Reply-To: <3B002595.76399CE4@mandrakesoft.com>
In-Reply-To: <3AFD8E2E.302F1AB5@mandrakesoft.com> <20010514112216.A25436@lucon.org> <20010514112407.E781@suse.com> <3B002595.76399CE4@mandrakesoft.com>
Le 14 May 2001 14:36:05 -0400, Jeff Garzik a écrit :
> Mads Martin Jørgensen wrote:
> Attached is a patch against 2.4.4-ac9 which includes the changes found
> in tulip-devel 1.1.6... (tulip-devel is sort of a misnomer; right now
> it's really just a staging and testing point for fixes which go straight
> into the tulip-stable series)
>
> I just checked against ac9 and it applies cleanly here.
Still the same issue here : On a quad port card, if only 1 port is up,
all is fine. This can be eth0, eth1, eth2 or eth3, it doesn't matter.
As soon as more than 1 port is up, the machine freeze. no oops,
not event CTRL-Scrollback, nothing.
As the use I made of the 4 port eth is bridging, you can imagine
the freeze appears very shortly after boot ;-)
Anyway. using the de4x5 driver for now.
Yann.
--
\|/ ____ \|/ Fac. des sciences de Nantes-Linux-Python-IPv6-ATM-BONOM....
"@'/ ,. \@" Tel :(+33) [0]251125865(AM)[0]251125857(PM)[0]251125868(Fax)
/_| \__/ |_\ Yann.Dupont@sciences.univ-nantes.fr
\__U_/ http://www.unantes.univ-nantes.fr/~dupont
next prev parent reply other threads:[~2001-05-15 8:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-12 19:25 PATCH 2.4.4.ac8: Tulip net driver fixes Jeff Garzik
2001-05-14 18:22 ` H . J . Lu
2001-05-14 18:24 ` Mads Martin Jørgensen
2001-05-14 18:36 ` PATCH 2.4.4.ac9: " Jeff Garzik
2001-05-14 19:02 ` H . J . Lu
2001-05-15 8:08 ` Yann Dupont [this message]
2001-05-15 8:09 ` Yann Dupont
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=989914130.25256.1.camel@olive \
--to=yann.dupont@ipv6.univ-nantes.fr \
--cc=jgarzik@mandrakesoft.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 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.