From: Andrey Savochkin <saw@saw.sw.com.sg>
To: "Michael O'Donnell" <mod@mclinux.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: eepro100: card reports no resources [was VM-global...]
Date: Thu, 2 Nov 2000 12:40:20 +0800 [thread overview]
Message-ID: <20001102124020.A19735@saw.sw.com.sg> (raw)
In-Reply-To: <20001031132306.A24147@stormix.com> <200010311932.OAA30422@odonnell.lowell.mclinux.com>
In-Reply-To: <200010311932.OAA30422@odonnell.lowell.mclinux.com>; from "Michael O'Donnell" on Tue, Oct 31, 2000 at 02:32:44PM
Hello,
On Tue, Oct 31, 2000 at 02:32:44PM -0500, Michael O'Donnell wrote:
[snip]
> Also, here's a possibly useless personal note WRT the
> eepro100 resource msgs, FWIW: I was recently using remote
> KGDB to work on an unrelated problem on an MP Pentium
> box with integrated eepro100. Whenever I'd leave one CPU
> stopped in the kernel debugger for a very long time I'd
> get those "no resource" messages from (I believe it was)
> the Enet driver when I finally allowed that CPU to continue
> running. I never noticed any other ill effects though
> I wasn't looking too hard for them at the time. I don't
It may be a legitimate case of "no resource" messages: the receive ring
is full because interrupts aren't served for a long time.
The problem is spurious "no resource" conditions, when there are plenty of
ready buffers.
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/
next prev parent reply other threads:[~2000-11-02 4:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-26 16:35 eepro100: card reports no resources [was VM-global...] Ville Herva
2000-10-30 6:23 ` Andrey Savochkin
2000-10-30 6:57 ` Ville Herva
2000-10-30 7:00 ` pierre
2000-10-31 18:23 ` Simon Kirby
2000-10-31 19:32 ` Michael O'Donnell
2000-11-02 4:40 ` Andrey Savochkin [this message]
2000-10-31 0:03 ` drizzt.dourden
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=20001102124020.A19735@saw.sw.com.sg \
--to=saw@saw.sw.com.sg \
--cc=linux-kernel@vger.kernel.org \
--cc=mod@mclinux.com \
/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