Re: ACPIPNP and too large IO resources

[Pierre Ossman]

Bjorn Helgaas wrote:
> Thanks for the report!
>   

Np. Gave me an excuse to try out git bisect. ;)

> It sounds like this might be the same problem as
>     http://bugzilla.kernel.org/show_bug.cgi?id=6292
>
> In short, you probably have a bridge device that consumes the
> entire 0x0-0xffff I/O port range and produces some or all of that
> range for downstream PNP devices.  PNP doesn't know what to do
> with these windows that are both consumed by the bridge and made
> available to downstream devices, so it just marks them as being
> already reserved.
>   

Ah, that explains things.

> Matthieu Castet wrote a nice patch (attached) that makes PNP just
> ignore those windows.  Can you try it and see whether it fixes
> the problem you're seeing?  This patch is already in -mm, but not
> yet in mainline.  We might need to consider this patch as
> 2.6.18 material if it resolves your problem.  I suspect many
> people will see the same problem.
>   

The patch works nicely and removes all memory and io regions for the PCI
bridge but for the range 0xcf8-0xcff.

Thanks
Pierre

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