From: Niklas Kallman <kjarvel@home.se>
To: Jack Howarth <howarth@bromo.msbb.uc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI error on x86_64 2.6.13 kernel
Date: Wed, 26 Oct 2005 23:06:05 +0200 [thread overview]
Message-ID: <435FEFBD.8010702@home.se> (raw)
In-Reply-To: <fa.gf7dlu0.a4g9qo@ifi.uio.no>
Jack Howarth wrote:
> Has anyone reported the following? For both of the 2.6.13 based
> kernels released so far on Fedora Core 4 for x86_64, we are seeing
> error messages of the form...
>
> Oct 3 11:21:48 XXXXX kernel: MEM window: d0200000-d02fffff
> Oct 3 11:21:48 XXXXX kernel: PREFETCH window: disabled.
> Oct 3 11:21:48 XXXXX kernel: PCI: Failed to allocate mem resource #6:20000 f0000000 for 0000:09:00.0
>
> ..on a Sun W2100Z dual opteron. These memory allocations errors
> don't occur under the 2.6.12 based kernels that Fedora has released
> for FC4. So far the errors don't seem to be manifesting themselves
> as any noticable system errors in using the machine itself.
> Jack
> -
I have the same problem on a Dell Inspiron 510m laptop and Fedora Core 4
when upgrading from 2.6.12 to 2.6.13.* :
I get the following messages at 2.6.13.* 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...
I posted lspci output and more in another mail with subject:
PCI: Failed to allocate I/O resource when upgrading to 2.6.13.*
I'm starting to suspect something in Fedora Core 4 ..
/Niklas
next parent reply other threads:[~2005-10-26 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.gf7dlu0.a4g9qo@ifi.uio.no>
2005-10-26 21:06 ` Niklas Kallman [this message]
2005-11-18 0:24 ` PCI error on x86_64 2.6.13 kernel Rajesh Shah
2005-11-18 7:04 Voluspa
2005-11-19 1:18 ` Greg KH
2005-11-19 5:06 ` Voluspa
2005-11-19 12:05 ` Voluspa
-- strict thread matches above, loose matches on Subject: below --
2005-10-26 13:53 Jack Howarth
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=435FEFBD.8010702@home.se \
--to=kjarvel@home.se \
--cc=howarth@bromo.msbb.uc.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