Jesper Krogh wrote:
quoted text
> Not that they seem critical to the system but I do get alot of these. I
> cant remember having seen that before.
 
quoted text
> [    2.904467] system 00:06: iomem range 0x0-0x0 could not be reserved
> [    2.904469] system 00:06: iomem range 0x0-0x0 could not be reserved
> [    2.904471] system 00:06: iomem range 0x0-0x0 could not be reserved
> [    2.904473] system 00:06: iomem range 0x0-0x0 could not be reserved
[...]

I'm getting these too. Not present in the last -rc4 kernel I built.

Reverting this commit (the only recent one to the file the message 
originates from), gets rid of the extra zero-range messages:

commit 4b34fe156455d26ee6ed67b61539f136bf4e439c
Author: Bjorn Helgaas <bjorn.helgaas@hp.com>
Date:   Mon Jun 2 16:42:49 2008 -0600

    PNP: mark resources that conflict with PCI devices "disabled"

    Both the PNP/PCI conflict detection quirk and the PNP system
    driver must use the same mechanism to mark resources as disabled.

    I think it's best to keep the resource and to keep the type bit
    (IORESOURCE_MEM, etc), so that we match the list from firmware
    as closely as possible.

    Fixes this regression from 2.6.25: http://lkml.org/lkml/2008/6/1/82

    Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
    Tested-by: Avuton Olrich <avuton@gmail.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

Relevant CCs added.

Cheers,
FJP
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/