From: Niklas Kallman <kjarvel@home.se>
To: linux-kernel@vger.kernel.org
Subject: PCI: Failed to allocate I/O resource when upgrading to 2.6.13.*
Date: Tue, 25 Oct 2005 19:37:19 +0200 [thread overview]
Message-ID: <435E6D4F.3080108@home.se> (raw)
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
Hello,
Since I upgraded my kernel from 2.6.12.6 to 2.6.13.4 (using make
oldconfig), I get the following messages at startup:
PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
PCI: Failed to allocate I/O resource #7:1000@10000 for 0000:01:01.0
PCI: Failed to allocate I/O resource #8:1000@10000 for 0000:01:01.0
PCI: Bus 2, cardbus bridge: 0000:01:01.0
I have tried "pci=routeirq", but it makes no difference.
When running 2.6.13.4 I cannot use my WLAN card (ndiswrapper).
With 2.6.12.6 there is no problem at all...
Is there something I can try to do? I've attached the lspci logs from
both kernels.. The computer is a Dell Inspiron 510m laptop.
Thanks!
/Niklas
[-- Attachment #2: lspcilog.tar.gz --]
[-- Type: application/x-gzip, Size: 6785 bytes --]
next reply other threads:[~2005-10-25 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 17:37 Niklas Kallman [this message]
2005-10-25 18:23 ` PCI: Failed to allocate I/O resource when upgrading to 2.6.13.* Niklas Källman
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=435E6D4F.3080108@home.se \
--to=kjarvel@home.se \
--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