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: [PATCH] Re: eepro100 problems in 2.4.0
Date: Thu, 25 Jan 2001 16:05:08 -0500 [thread overview]
Message-ID: <3A709504.5599E0F7@mandrakesoft.com> (raw)
In-Reply-To: <006601c08711$4bdfb600$9b2f4189@angelw2k>
[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]
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?
pci_enable_device() must to be called before any accesses to the
pci_dev->irq and pci_dev->resource[] members. Plug-n-play may fill in
those values. I didn't see your original report, but "no resources"
sounds to me like pci_enable_device() needs to be called earlier in the
speedo_init_one function. The attached patch does just that.
Jeff
> -----Original Message-----
> From: "Tom Sightler" <ttsig@tuxyturvy.com>
> To: "Micah Gorrell" <angelcode@myrealbox.com>;
> <linux-kernel@vger.kernel.org>
> Date: Thursday, January 25, 2001 1:48 PM
> Subject: Re: eepro100 problems in 2.4.0
[...]
> >I had a similar problem with a server that had dual embedded eepro100
> >adapters however selecting the 'Enable Power Management (EXPERIMENTAL)'
> >option for the eepro100 seemed to make the problem go away. I don't really
> >know why but it might be worth trying if it wasn't already selected.
--
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
[-- Attachment #2: eepro100.patch --]
[-- Type: text/plain, Size: 872 bytes --]
Index: drivers/net/eepro100.c
===================================================================
RCS file: /cvsroot/gkernel/linux_2_4/drivers/net/eepro100.c,v
retrieving revision 1.1.1.9.42.2
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;
+
if (!request_region(pci_resource_start(pdev, 1),
pci_resource_len(pdev, 1), "eepro100")) {
printk (KERN_ERR "eepro100: cannot reserve I/O ports\n");
@@ -597,9 +600,6 @@
pci_read_config_word(pdev, pm + PCI_PM_CTRL, &pwr_command);
acpi_idle_state = pwr_command & PCI_PM_CTRL_STATE_MASK;
}
-
- if (pci_enable_device(pdev))
- goto err_out_free_mmio_region;
pci_set_master(pdev);
next prev parent reply other threads:[~2001-01-25 21:06 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 ` Jeff Garzik [this message]
2001-01-25 21:19 ` [PATCH] " Jeff Garzik
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=3A709504.5599E0F7@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;
as well as URLs for NNTP newsgroup(s).