From: "Michael O'Donnell" <mod@mclinux.com>
To: linux-kernel@vger.kernel.org
Subject: Re: eepro100: card reports no resources [was VM-global...]
Date: Tue, 31 Oct 2000 14:32:44 -0500 [thread overview]
Message-ID: <200010311932.OAA30422@odonnell.lowell.mclinux.com> (raw)
In-Reply-To: Your message of "Tue, 31 Oct 2000 13:23:06 EST." <20001031132306.A24147@stormix.com>
I've not been paying attention to this eepro100 issue but
a coworker mentions that she saw a driver (or patch) posted
here back around 6 Sep 2000 by saw@saw.sw.com.sg with
Subject: "Re: eepro100 trouble" that might be of interest.
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
know what caused those resource messages but the version of
KGDB I was using was not clueful about MP issues - while
that one CPU was breakpointed the other CPU was likely
only held in check as a side-effect, probably by being
prevented from acquiring one of the IRQ-related spinlocks.
Of course, it would probably only be notable if some kind
of resource exhaustion did NOT result from such locking
misbehavior, but it seemed worth at least a mention...
-
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-10-31 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-26 16:35 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 [this message]
2000-11-02 4:40 ` Andrey Savochkin
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=200010311932.OAA30422@odonnell.lowell.mclinux.com \
--to=mod@mclinux.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®