From: Andrey Savochkin <saw@saw.sw.com.sg>
To: Ion Badulescu <ionut@moisil.cs.columbia.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: eepro100 driver update for 2.4
Date: Mon, 4 Dec 2000 21:16:33 +0800 [thread overview]
Message-ID: <20001204211633.A16092@saw.sw.com.sg> (raw)
In-Reply-To: <20001201175109.A4209@saw.sw.com.sg> <200012012145.eB1LjOl03300@moisil.dev.hydraweb.com>
In-Reply-To: <200012012145.eB1LjOl03300@moisil.dev.hydraweb.com>; from "Ion Badulescu" on Fri, Dec 01, 2000 at 01:45:24PM
Hello,
On Fri, Dec 01, 2000 at 01:45:24PM -0800, Ion Badulescu wrote:
> On Fri, 1 Dec 2000 17:51:09 +0800, Andrey Savochkin <saw@saw.sw.com.sg> wrote:
>
> > I've been promised that this issue would be looked up in Intel's errata by
> > people who had the access to it, but I haven't got the results yet.
>
> There is nothing relevant in the errata, unfortunately...
Do you have it?
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.
It may happen that we don't understand something in the initialization
sequence, or just a plain hardware bug.
> > The card itself doesn't report its revision in details.
> > It can be checked by `lspci'.
> > Rev 8 is 82559, if I remember, and rev 9 is 82559ER.
>
> No, 82559ER has its own PCI id, 0x1209. There is also a newer 82559 chip
> which reports a different PCI device id, 0x1030 (I have one of those).
Yes, you're right.
> For the old chips reporting 0x1229, revisions 1-3 are 82557, revisions
> 4-5 are 82558 and revisions 6-8 are 82559.
Best regards
Andrey V.
Savochkin
-
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-04 13:47 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 [this message]
2000-12-05 19:13 ` Ion Badulescu
2000-12-05 21:37 ` Udo A. Steinberg
2000-12-06 12:23 ` Andrey Savochkin
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=20001204211633.A16092@saw.sw.com.sg \
--to=saw@saw.sw.com.sg \
--cc=ionut@moisil.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®