From: "Udo A. Steinberg" <sorisor@Hell.WH8.TU-Dresden.De>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Ion Badulescu <ionut@cs.columbia.edu>,
Andrey Savochkin <saw@saw.sw.com.sg>,
linux-kernel@vger.kernel.org
Subject: Re: eepro100 driver update for 2.4
Date: Mon, 11 Dec 2000 01:09:35 +0100 [thread overview]
Message-ID: <3A341B3F.B5D962A8@Hell.WH8.TU-Dresden.De> (raw)
In-Reply-To: <3A3143D5.98E8E948@Hell.WH8.TU-Dresden.De> <5.0.2.1.2.20001210232808.04affbd0@pop.cus.cam.ac.uk>
Hi,
Anton Altaparmakov wrote:
> Just to say that the patch (including added 4) fixed the "card reports no
> resources" messages for me. - Looking at my logs the messages appeared once
> every 10-40 minutes. - Now the box is up for more than 5 hours with the
> patch and test12-pre7 and not a single no resources message logged so far.
> (Note, I upgraded the kernel at the same time as adding the patch so it is
> actually possible that test12-pre7 vanilla is fixed as well.)
The problem here only ever happens at initialisation/first packets. Once the
network interface has been initialised properly it never produces those
messages anymore. Usually it helps to shut the NIC down with ifconfig and
bringing it back up afterwards to properly initialise it.
If you are bored, try to reboot a couple dozen times and see if you still
see it. I have test12-pre7 also.
> My card is an Ether Express Pro 100, lcpci says: Intel Corporation 82557
> [Ethernet Pro 100] (rev 04) and lspci -n gives: class 0200: 10b7:9004
Mine's a rev 08.
00:0d.0 Class 0200: 8086:1229 (rev 08)
-Udo.
-
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-11 0:40 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
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 [this message]
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=3A341B3F.B5D962A8@Hell.WH8.TU-Dresden.De \
--to=sorisor@hell.wh8.tu-dresden.de \
--cc=aia21@cam.ac.uk \
--cc=ionut@cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=saw@saw.sw.com.sg \
/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®