On Wed, Jul 16, 2008 at 7:44 AM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
quoted text
> I looked at your dmesg from 2.6.25.10
>
> it tried to use mmconfig, and later fall back to conf1, because
> 1. your MCFG said it support bus [0,255], and range will be
> [0xf0000000, 0xffffffff]
> 2. firmware only reserve [0xf0000000, 0xf4000000)
>
> and 2.5.25 will not check acp reserved range.
>
> from 2.6.26, it will check if the [0xf0000000, 0xffffffff] is reserved
> via acpi dsdt _crs?
> it will fail too.
>
> So MCFG table is broken.
>
> You need to get firmware update from your vendor.
>
> or we need to put that system on DMI check to change end_bus_number
> from 0xff to 0x3f
>
> ps: mem=2g will not work, it will can not change mcfg table etc... you
> need take out 1G ram out.
>
> YH
>

Well shit man, that sucks...
how hard is it to do a DMI check?
regards;

-- 
Justin P. Mattock
--
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/