From: Andrey Savochkin <saw@saw.sw.com.sg>
To: Ion Badulescu <ionut@cs.columbia.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: eepro100 driver update for 2.4
Date: Wed, 6 Dec 2000 20:23:13 +0800 [thread overview]
Message-ID: <20001206202313.A26438@saw.sw.com.sg> (raw)
In-Reply-To: <20001204211633.A16092@saw.sw.com.sg> <Pine.LNX.4.21.0012051104510.7727-100000@age.cs.columbia.edu>
In-Reply-To: <Pine.LNX.4.21.0012051104510.7727-100000@age.cs.columbia.edu>; from "Ion Badulescu" on Tue, Dec 05, 2000 at 11:13:27AM
Hello,
On Tue, Dec 05, 2000 at 11:13:27AM -0800, Ion Badulescu wrote:
> On Mon, 4 Dec 2000, Andrey Savochkin wrote:
>
> > > There is nothing relevant in the errata, unfortunately...
> >
> > Do you have it?
>
> I have the manual in the office, so I can look at it again in a couple of
> days. I've used it to hack on the BSDI driver...
Fine!
> > The sympthomes are that the card triggers Flow Control Pause condition (and
> > interrupt) on the last stages of the initialization or right after.
> > And it happens with flow control being explicitly turned off.
> > High network load considerably increase the chances of the event.
> > After that the card stops to behave sane and reports status 0x7048.
>
> Cool, I'll try to go over the driver init sequence by the end of the
> weekend and let you know if I see anything wrong.
May be, there is a mandatory delay missing somewhere..
> > It may happen that we don't understand something in the initialization
> > sequence, or just a plain hardware bug.
>
> Do you know if only one specific chip revision exhibits this problem? It
> would really help track down the problem. If I remember correctly, 82557
> doesn't have flow control at all, and 82558/9 have different
> implementations -- one is proprietary (82558) and one is standard (82559).
I personally have seen it with 82559ER only.
But there have been some reports about 82559, too.
Best regards
Andrey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-06 12:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 9:23 Andrey Savochkin
2000-11-30 18:41 ` Udo A. Steinberg
2000-12-01 9:51 ` Andrey Savochkin
2000-12-01 12:55 ` Udo A. Steinberg
2000-12-01 21:45 ` Ion Badulescu
2000-12-04 13:16 ` Andrey Savochkin
2000-12-05 19:13 ` Ion Badulescu
2000-12-05 21:37 ` Udo A. Steinberg
2000-12-06 12:23 ` Andrey Savochkin [this message]
2000-12-08 19:44 ` Ion Badulescu
2000-12-08 20:25 ` Udo A. Steinberg
2000-12-08 20:57 ` Ion Badulescu
2000-12-08 22:37 ` Udo A. Steinberg
2000-12-08 22:47 ` Josh Fryman
2000-12-10 23:34 ` Anton Altaparmakov
2000-12-11 0:09 ` Udo A. Steinberg
2000-12-11 3:16 ` Ion Badulescu
2000-12-11 3:29 ` Udo A. Steinberg
2000-12-11 8:19 ` Anton Altaparmakov
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=20001206202313.A26438@saw.sw.com.sg \
--to=saw@saw.sw.com.sg \
--cc=ionut@cs.columbia.edu \
--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
all inboxes | Powered by JetHome®