On Monday 09 June 2008, Bjorn Helgaas wrote:
quoted text
> On Saturday 07 June 2008 3:50:59 pm Frans Pop wrote:
> > Jesper Krogh wrote:
> > > Not that they seem critical to the system but I do get alot of
> > > these. I cant remember having seen that before.
> > >
> > > [    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.
>
> The patch below should fix this and is already in Linus' tree.
> Can you give it a whirl to confirm?  Thanks!
>
> PNP: skip UNSET MEM resources as well as DISABLED ones
[...]

Yes, that does the trick. Tested using a kernel built from git head.

Thanks,
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/