From: Dennis <dennis@etinc.com>
To: <michael@pmcl.ph.utexas.edu>, "Allen, David B" <David.B.Allen@chase.com>
Cc: linux-kernel@vger.kernel.org
Subject: RE: intel etherpro100 on 2.2.18p21 vs 2.2.18p17
Date: Tue, 14 Nov 2000 17:18:25 -0500 [thread overview]
Message-ID: <5.0.0.25.0.20001114171416.01f7b8f0@mail.etinc.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10011111111390.18876-100000@pmcl.ph.utexas.e du>
In-Reply-To: <93BA6BFC5E48D4118A8200508B6BBC4924AB7A@sf1-mail01.hamquist.com>
At 12:15 PM 11/11/2000, michael@pmcl.ph.utexas.edu wrote:
>We have the SUPER 370DL3 SuperMicro boards w/ the integrated Intel NIC,
>unfortunately a warm boot does not help. The problem also seems to happen
>when I turn on the alias ip feature in the kernel under network options.
>
>
>On Fri, 10 Nov 2000, Allen, David B wrote:
>
> > FWIW, I have a dual-proc SuperMicro motherboard P3DM3 with integrated
> > Adaptec SCSI and Intel 8255x built-in NIC.
> >
> > Sometimes on a cold boot I get the "kernel: eth0: card reports no RX
> > buffers" that repeats, but if I follow it with a warm boot the message
> > doesn't appear (even on subsequent warm boots). So this is definitely
> > reproducible, but it doesn't happen every time.
> >
> > I can't offer much more than that, but at least you know you're not the
> only
> > one experiencing this.
> >
There is a flaw in the eepro100 driver that apparently doesnt initialise
something properly. The problem is exasperated by the fact that the
eepro100 driver doesn handle the buffer problem properly. We've corrected
it by (effectively) resetting the card (by calling close and then open)
when the first out of resources event occurs. Its not elegant, but it seems
to work.
We have identical hardware with dual boot disks (linux and freebsd) and the
problem only occurs with linux, and it only seems to occur with linux. Of
course on the DLE supermicro boards FreeBSD complains about an unsupport
PHY, so there is no joy in mudville no matter what you do :-)
Dennis
-
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-11-14 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10011111111390.18876-100000@pmcl.ph.utexas.e du>
2000-11-11 0:24 ` Allen, David B
2000-11-11 17:15 ` michael
2000-11-13 9:31 ` Andrey Savochkin
2000-11-14 22:18 ` Dennis [this message]
2000-11-17 9:06 ` Andrey Savochkin
2000-11-10 17:00 michael
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=5.0.0.25.0.20001114171416.01f7b8f0@mail.etinc.com \
--to=dennis@etinc.com \
--cc=David.B.Allen@chase.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@pmcl.ph.utexas.edu \
/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®