From: Andrey Savochkin <saw@saw.sw.com.sg>
To: vido@ldh.org
Cc: Ion Badulescu <ionut@cs.columbia.edu>, Alan Cox <alan@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: eepro100.c, kernel 2.4.1
Date: Tue, 20 Feb 2001 15:38:45 -0800 [thread overview]
Message-ID: <20010220153845.A29633@saw.sw.com.sg> (raw)
In-Reply-To: <20010212133248.A7147@saw.sw.com.sg> <Pine.LNX.4.30.0102120048160.4687-100000@age.cs.columbia.edu> <20010220153048.A26551@ldh.org> <20010219232136.C26553@saw.sw.com.sg> <20010220171837.A26967@ldh.org>
In-Reply-To: <20010220171837.A26967@ldh.org>; from "Augustin Vidovic" on Tue, Feb 20, 2001 at 05:18:37PM
On Tue, Feb 20, 2001 at 05:18:37PM +0900, Augustin Vidovic wrote:
> 00:0c.0 Ethernet controller: Intel Corporation 82557 (rev 08)
> 00:0d.0 Ethernet controller: Intel Corporation 82557 (rev 08)
It's i82559.
It can't have that original bug which is checked by those EEPROM bits and
workaround for which is implemented.
You probably have another one :-)
What are the symptomes of the lock-ups?
Does TX timeout happen?
Does the card recover and resume operations after that?
Best regards
Andrey
prev parent reply other threads:[~2001-02-20 23:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 5:53 [PATCH] eepro100.c, kernel 2.4.1 Augustin Vidovic
2001-02-08 7:23 ` Ion Badulescu
2001-02-08 7:37 ` Augustin Vidovic
2001-02-08 7:42 ` Alan Cox
2001-02-08 7:55 ` Andrey Savochkin
2001-02-08 7:59 ` [PATCH] " Ion Badulescu
2001-02-08 10:41 ` Augustin Vidovic
2001-02-08 11:00 ` Ion Badulescu
2001-02-08 11:15 ` Augustin Vidovic
2001-02-08 11:26 ` Ion Badulescu
2001-02-08 11:44 ` Augustin Vidovic
2001-02-08 11:53 ` Ion Badulescu
2001-02-08 12:08 ` Augustin Vidovic
2001-02-12 5:32 ` Andrey Savochkin
2001-02-12 9:00 ` Ion Badulescu
2001-02-20 6:30 ` Augustin Vidovic
2001-02-20 7:21 ` Andrey Savochkin
2001-02-20 8:18 ` Augustin Vidovic
2001-02-20 23:38 ` Andrey Savochkin [this message]
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=20010220153845.A29633@saw.sw.com.sg \
--to=saw@saw.sw.com.sg \
--cc=alan@redhat.com \
--cc=ionut@cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=vido@ldh.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