public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrey Savochkin <saw@saw.sw.com.sg>
To: "Udo A. Steinberg" <sorisor@Hell.WH8.TU-Dresden.De>
Cc: linux-kernel@vger.kernel.org, "David S. Miller" <davem@redhat.com>
Subject: Re: eepro100 driver update for 2.4
Date: Fri, 1 Dec 2000 17:51:09 +0800	[thread overview]
Message-ID: <20001201175109.A4209@saw.sw.com.sg> (raw)
In-Reply-To: <20001117172336.B27444@saw.sw.com.sg> <3A269F47.17336A69@Hell.WH8.TU-Dresden.De>
In-Reply-To: <3A269F47.17336A69@Hell.WH8.TU-Dresden.De>; from "Udo A. Steinberg" on Thu, Nov 30, 2000 at 07:41:11PM

Hello,

On Thu, Nov 30, 2000 at 07:41:11PM +0100, Udo A. Steinberg wrote:
> I've been using an older EEPro100/B card until now and it's been working without any
> problems ever since the transmitter bugs were fixed. The boot output looked like this:
[snip]
> Today I've installed a new model with Wake-on-LAN support and got caught by
> above mentioned
> 
> eth0: card reports no RX buffers.
> eth0: card reports no resources.
> 
> messages as well. Strangely those messages only ever happen during bootup and
> *every* time. Shutting eth0 down and bringing it back up fixes the problem.

It's a known issue.
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.

> What puzzles me a bit is that the newer card (721383-xxx) is an 82559 chip,
> according to the Intel site, but the boot output doesn't say so:
[snip]

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.

> If you have any patches or tests that would help to find and fix this init
> bug, I'd offer to test them out, since I can reliably reproduce the problem.

Sorry, no patches so far...
I may suggest only workarounds that reduces the likelihood of the fails.

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/

  reply	other threads:[~2000-12-01 10:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-17  9:23 eepro100 driver update for 2.4 Andrey Savochkin
2000-11-30 18:41 ` Udo A. Steinberg
2000-12-01  9:51   ` Andrey Savochkin [this message]
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
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=20001201175109.A4209@saw.sw.com.sg \
    --to=saw@saw.sw.com.sg \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sorisor@Hell.WH8.TU-Dresden.De \
    /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