From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Micah Gorrell <angelcode@myrealbox.com>
Cc: Tom Sightler <ttsig@tuxyturvy.com>,
linux-kernel@vger.kernel.org, saw@saw.sw.com.sg, Alan@redhat.com
Subject: Re: [PATCH] Re: eepro100 problems in 2.4.0
Date: Thu, 25 Jan 2001 16:19:27 -0500 [thread overview]
Message-ID: <3A70985F.E5A0AB7F@mandrakesoft.com> (raw)
In-Reply-To: <006601c08711$4bdfb600$9b2f4189@angelw2k> <3A709504.5599E0F7@mandrakesoft.com>
Jeff Garzik wrote:
>
> Micah Gorrell wrote:
> > Because of the problems we where having we are no longer using the machine
> > with 3 nics. We are now using a machine with just one and it is going live
> > next week. We do need kernel 2.4 because of the process limits in 2.2.
> > Does the 'Enable Power Management (EXPERIMENTAL)' option fix the no
> > resources problems?
>
> Does the attached patch, against 2.4.1-pre10, help matters any?
> diff -u -r1.1.1.9.42.2 eepro100.c
> --- drivers/net/eepro100.c 2001/01/24 15:56:16 1.1.1.9.42.2
> +++ drivers/net/eepro100.c 2001/01/25 21:00:48
> @@ -560,6 +560,9 @@
> if (speedo_debug > 0 && did_version++ == 0)
> printk(version);
>
> + if (pci_enable_device(pdev))
> + return -EIO;
> +
Oops, sorry guys. Thanks to DaveM for correcting me -- my patch has
nothing to do with the "card reports no resources" problem. My
apologies.
Jeff
--
Jeff Garzik | "You see, in this world there's two kinds of
Building 1024 | people, my friend: Those with loaded guns
MandrakeSoft | and those who dig. You dig." --Blondie
-
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:[~2001-01-25 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 20:54 eepro100 problems in 2.4.0 Micah Gorrell
2001-01-25 21:05 ` [PATCH] " Jeff Garzik
2001-01-25 21:19 ` Jeff Garzik [this message]
2001-01-26 0:50 ` Andrey Savochkin
2001-01-27 16:30 ` Jeff Garzik
2001-01-25 21:06 ` Sergey Kubushin
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=3A70985F.E5A0AB7F@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=Alan@redhat.com \
--cc=angelcode@myrealbox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=saw@saw.sw.com.sg \
--cc=ttsig@tuxyturvy.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