Description of problem:
For every FC5 kernel to date, I have gotten the following error as the first
thing that comes up on the screen during boot (aside from the penguins). I
have been experiencing sever instability issues under SMP that causes it to
randomly lock up, usually within minutes.
PCI: Failed to allocate mem resource #6:20000@d0000000 for 0000:02:00.0
En excerpt from lspci -v:
02:00.0 VGA compatible controller: nVidia Corporation GE Force Go 7800 GTX
(rev a1) (prog-if 00 [VGA])
Subsystem: CLEVO/KAPOK Computer Unknown device 0901
Flags: bus master, fast devsel, latency 0, IRQ 22
Memory at d1000000 (32-bit, non-prefetchable) [size=16M]
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at d0000000 (64-bit, non-prefetchable) [size=16M]
I/O ports at 5000 [size=128]
Capabilities:  Power Management version 2
Capabilities:  Message Signalled Interrupts: 64bit+ Queue=0/0
Capabilities:  Express Endpoint IRQ 0
Capabilities:  Virtual Channel
Capabilities:  Power Budgeting
Note that this error did not occur with FC4 to my recollection. SMP was
certainly stable enough then. The error message definitely does NOT occur when
booting from a KNOPPIX cd that runs 2.6.12.
Version-Release number of selected component (if applicable):
All FC5 releases through 2111
Always occurs, but after random delay
Steps to Reproduce:
UI stops responding to input and gkrellm shows the load increasing at a 45
degree angle. CPU's look stuck at 0%.
The hardware is a Sager 9750 laptop (also known as a Clevo D900K)
You may note that I'm currently booted into a Linuxant kernel that has 16K
stacks. This is just because my wireless is more stable under it. The error
I'm reporting occurs regardless of which kernel I'm in (i.e. don't get
distracted by the Linuxant kernel, it's a red herring :)
Created attachment 128915 [details]
complete dmesg and lspci
Created attachment 129105 [details]
dmesg from 2.6.16-1.2111_FC5 kernel
After further testing this weekend, I'm not sure that this error is related to
the instability issue I mentioned. I'll open up a separate ticket for that.
Here is a dmesg dump from running the 2.6.16-1.2111_FC5 kernel.
The only question I have on this now is whether this is an actual problem or
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
This bug has been mass-closed along with all other bugs that
have been in NEEDINFO state for several months.
Due to the large volume of inactive bugs in bugzilla, this
is the only method we have of cleaning out stale bug reports
where the reporter has disappeared.
If you can reproduce this bug after installing all the
current updates, please reopen this bug.
If you are not the reporter, you can add a comment requesting
it be reopened, and someone will get to it asap.