Red Hat Bugzilla – Bug 285251
Memory allocation messages in dmesg with nVidia NV43
Last modified: 2011-12-13 17:28:46 EST
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Get memory allocation messages in dmesg. System seems to function normally.
No memory allocation diagnostics
Relevant section of dmesg, with a little before and after:
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
hpet0: 3 64-bit timers, 14318180 Hz
ACPI: RTC can wake from S4
Time: tsc clocksource has been installed.
pnp: 00:00: iomem range 0x0-0x9ffff could not be reserved
pnp: 00:00: iomem range 0xe0000-0xfffff could not be reserved
pnp: 00:00: iomem range 0x100000-0x3ffaffff could not be reserved
pnp: 00:00: iomem range 0x3ffb0000-0x3ffbffff could not be reserved
pnp: 00:01: iomem range 0xe0000000-0xefffffff has been reserved
pnp: 00:09: ioport range 0x1e0-0x1ef has been reserved
khelper used greatest stack depth: 2860 bytes left
PCI: Failed to allocate mem resource #6:20000@c0000000 for 0000:01:00.0
PCI: Bridge: 0000:00:01.0
IO window: disabled.
MEM window: ce000000-cfffffff
PREFETCH window: b0000000-bfffffff
PCI: Bus 3, cardbus bridge: 0000:02:0b.0
IO window: 0000b000-0000b0ff
lspci -v -s 0000:01:00.0
01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce Go 6600]
(rev a2) (prog-if 00 [VGA])
Subsystem: Toshiba America Info Systems Unknown device 0002
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at cf000000 (32-bit, non-prefetchable) [size=16M]
Memory at b0000000 (64-bit, prefetchable) [size=256M]
Memory at ce000000 (64-bit, non-prefetchable) [size=16M]
Capabilities:  Power Management version 2
Capabilities:  Message Signalled Interrupts: Mask- 64bit+ Queue=0/0
Capabilities:  Express Endpoint IRQ 0
Created attachment 192131 [details]
dmesg output with system as installed
Created attachment 192141 [details]
dmesg with pcitest flag set, as suggested in dmesg
What is in /proc/iomem after the system finishes booting?
I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.
I am CC'ing myself to this bug and will try and assist you in resolving it if I can.
There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?
If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.
Created attachment 293896 [details]
dmesg showing error messages
As attachment id=23896 shows, I still have the bug with kernel-184.108.40.206-107.fc8 .
Could you run:
cat /proc/iomem > iomem.out
and attach as text/plain to this bug as per comment #3
Created attachment 293946 [details]
Contents of /proc/iomem
Okay thanks. I'll re-assign it to Chuck who asked for the data...
Versions of dmesg and iomem in experimental kernel are at
Newer versions of dmesg and iomem in experimental kernel are at
Created attachment 306333 [details]
New version of dmesg in kernel 220.127.116.11-18.fc9.i686
Created attachment 306334 [details]
/proc/iomem for kernel 18.104.22.168-18.fc9.i686
/proc/iomem contents for kernel 22.214.171.124-18.fc9.i686
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.