From: Ben Greear <greearb@candelatech.com>
To: David Lang <david.lang@digitalinsight.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Tulip driver bug in 2.4.17 (fwd)
Date: Thu, 17 Jan 2002 17:33:21 -0700 [thread overview]
Message-ID: <3C476D51.2070303@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0201171423050.26448-100000@dlang.diginsite.com>
You're not using a PCI extender/riser card, are you?
What motherboard?
By lockup, how hard is it? Will the reset button work quickly?
After 5 or so seconds?
You should probably send an lspci -vv and the interesting parts from
dmesg (or /var/log/messages)...
David Lang wrote:
> as I have not received any response directly I am sending this to the full
> list for help.
>
> David Lang
>
> ---------- Forwarded message ----------
> Date: Mon, 14 Jan 2002 15:10:42 -0800 (PST)
> From: David Lang <dlang@diginsite.com>
> To: Jeff Garzik <jgarzik@mandrakesoft.com>
> Subject: Tulip driver bug in 2.4.17
>
> I am running a dlink DFE-570TX quad card that works fine with the 0.9.14
> driver in 2.4.8, but with the 2.4.15-pre9 driver in 2.4.14-2.4.17 I run
> into a bug when trying to use all the interfaces.
>
> if I use eth3 alone it works
> if I use eth0, eth1, eth2 it works
> if I use eth0, eth1, eth3 it locks up immediatly following the ifconfig,
> locking up to the point that the magic sysreq stuff doesn't work!
>
> if I work the other direction and ifconfig eth3, eth2, eth1, eth0 I get a
> shell prompt back after the last ifconfig before it locks up.
>
> I posted this friday on sourceforge, but looking today at the activity
> there it doesn't look like it's in use much now so I'm sending this
> directly to you. If there is any other place I should send it or any
> additional tests I should perform, please let me know (I have 50 of these
> cards either in production or headed there soon :-)
>
> David Lang
> -
> 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/
>
>
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2002-01-18 0:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 22:23 Tulip driver bug in 2.4.17 (fwd) David Lang
2002-01-18 0:33 ` Ben Greear [this message]
2002-01-18 1:49 ` David Lang
2002-01-18 3:58 ` Ben Greear
2002-01-18 7:33 ` David Lang
2002-01-18 15:06 ` Ben Greear
2002-01-18 18:10 ` David Lang
2002-01-18 19:28 ` Ben Greear
2002-01-18 20:33 ` David Lang
2002-01-18 20:52 ` David Lang
2002-01-18 21:16 ` Ben Greear
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=3C476D51.2070303@candelatech.com \
--to=greearb@candelatech.com \
--cc=david.lang@digitalinsight.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