mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josip Loncaric <josip@icase.edu>
To: linux-kernel@vger.kernel.org
Subject: PCI: Failed to allocate resource 0 for PCI device 1011:0019
Date: Sat, 14 Jul 2001 10:52:46 -0400	[thread overview]
Message-ID: <3B505CBE.898A717B@icase.edu> (raw)

Upon installing Red Hat 7.1 w/kernel 2.4.3-12 on an IBM ThinkPad i1460
laptop, the pcmcia network card (NetGear FA510C) does not work.  The
problem is caused by PCI:

PCI: Failed to allocate resource 0 for PCI device 1011:0019

and further investigation ('cat /proc/pci', 'lspci -vvv') indicates that
although I/O port base is correctly identified, the size is not (lspci
shows no size, /proc/pci has end address lower than start address).

I've checked mailing list archives and even compared source differences
between 2.4.6 and 2.4.3 versions of drivers/pci/pci.c, but this problem
does not seem to have been addressed yet.

BTW, the suggestion to scan all subordinate busses instead of just
leaving 4 bus numbers produces mixed results.  The change (see below)
helps (the card is finally seen) but the card does not work right (it
generates tons of Rx traffic which gets discarded).  Also, with the
change, a bootup message "PCI: Unable to handle 64-bit address for
device..." shows up (unmodified kernel does not have this problem).

Any ideas?  Sorry, until the network becomes operational, I cannot
download more detailed information from the laptop...

Sincerely,
Josip

P.S.  The change to linux-2.4.3-12/drivers/pci/pci.c I tested was:

-                if (!is_cardbus) {
+                if (is_cardbus) {
                      /* Now we can scan all subordinate buses... */
                        max = pci_do_scan_bus(child);
                } else {
                        /*
                         * For CardBus bridges, we leave 4 bus numbers
                         * as cards with a PCI-to-PCI bridge can be
                         * inserted later.
                         */
                        max += 3;
                }

                 reply	other threads:[~2001-07-14 14:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3B505CBE.898A717B@icase.edu \
    --to=josip@icase.edu \
    --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®