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: Fri, 18 Jan 2002 08:06:16 -0700 [thread overview]
Message-ID: <3C4839E8.6080800@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0201172331130.27276-100000@dlang.diginsite.com>
David Lang wrote:
> On Thu, 17 Jan 2002, Ben Greear wrote:
>
>
>>David Lang wrote:
>>
>>
>>>On Thu, 17 Jan 2002, Ben Greear wrote:
>>>
>>>
>>>
>>>>You're not using a PCI extender/riser card, are you?
>>>>
>>>>
>>>Yes, (it's in a 2u rackmount case). it's a low right-angle extender
>>>
>>
>>You're screwed :)
>>
>>It seems to be a hardware/PCI problem. I replaced 4-port NICS (the DFE-570-TX),
>>motherboards, cpus, entire chassis...the problem followed the riser cards.
>>
>
> then why does the same card work properly with the old driver? if it's
> truely a hardware problem then all versions of the driver should fail. if
> it's possible for one version to work around the problem (or avoid
> triggering it) then other versions should be able to.
That is interesting. (For me, I had some older, slightly slower systems
work, while the newer ones failed. I believe I tried older drivers on my
new hardware, but I'm not sure...) The only excuse I could come up with is
that the newer drivers/machines could utilize the PCI bus faster and
that somehow caused the lockup. Because even sysreq didn't work, I can't
imagine what a driver, buggy or otherwise, could do to lock the system
like it does...
>
>
>>To debug, take off the face-plates of your NICS and run them in your box
>>w/out the riser..or take the MB completely out of the case. I'll bet
>>you a dozen realtec nics that that will fix your lockup problem! :)
>>
>>While you're doing that...order a $54 riser from adexelec.com. Their
>>riser fixed the problem for me. If the riser isn't obvious on
>>Adex's page, let me know and I'll find the version of the one I got.
>>
>>Btw, if you find a butter-fly riser for a 1U chassis that works, let
>>me know..cause I see the same problem in my 1U servers...
>>
>>Enjoy,
>>Ben
>>
>>
>>--
>>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
>>
>>
>>
> -
> 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 15:06 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
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 [this message]
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=3C4839E8.6080800@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 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.