Re: Linux 2.6.27-rc5: System boot regression caused by commit a2bd7274b47124d2fc4dfdb8c0591f545ba749dd

[Yinghai Lu]

On Sat, Aug 30, 2008 at 3:41 PM, Linus Torvalds
<torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
>
>
> On Sat, 30 Aug 2008, Yinghai Lu wrote:
>>
>> in old kernel, after BAR3 request_filed, pci_assigned_unassigned
>> should get update resource for that... but it could find that big
>> space for it.

wait, THAT BAR is 64BIT capable, So kernel should assign 64bit range to it...
it request_resource fails...

>
> Exactly. So what happens is that it doesn't actually re-allocate it at
> all. Not that it is necessarily even possible - it's quite possible that
> that field is effectively locked some way and is read-only. Without
> knowing the chipset details, we can only guess.

not touch it at this time...

except Jordan could find some clue with the DOC.

YH
--
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/