On Fri, Oct 2, 2015 at 4:05 PM, Khalid Aziz wrote:
> On 10/02/2015 04:05 PM, Yinghai Lu wrote:
> I still see lots of "no compatible
> bridge window" messages but overlapping address ranges are no longer
> reserved
Please send boot log to me, I'd like to fix them.
Thanks
Yinghai
--
To unsubscri
On 10/02/2015 04:05 PM, Yinghai Lu wrote:
On Fri, Oct 2, 2015 at 1:00 PM, Khalid Aziz wrote:
On Wed, 2015-09-30 at 22:52 -0700, Yinghai Lu wrote:
Found "no compatible bridge window" warning in boot log from T5-8.
pci :00:01.0: can't claim BAR 15 [mem 0x1-0x4afff pref]: no
com
On Fri, Oct 2, 2015 at 1:00 PM, Khalid Aziz wrote:
> On Wed, 2015-09-30 at 22:52 -0700, Yinghai Lu wrote:
>> Found "no compatible bridge window" warning in boot log from T5-8.
>>
>> pci :00:01.0: can't claim BAR 15 [mem 0x1-0x4afff pref]: no
>> compatible bridge window
>>
>> That
On Wed, 2015-09-30 at 22:52 -0700, Yinghai Lu wrote:
> Found "no compatible bridge window" warning in boot log from T5-8.
>
> pci :00:01.0: can't claim BAR 15 [mem 0x1-0x4afff pref]: no
> compatible bridge window
>
> That resource is above 4G, but does not get offset correctly as
Found "no compatible bridge window" warning in boot log from T5-8.
pci :00:01.0: can't claim BAR 15 [mem 0x1-0x4afff pref]: no
compatible bridge window
That resource is above 4G, but does not get offset correctly as
root bus only report io and mem32.
pci_sun4v f02dbcfc: PCI host
5 matches
Mail list logo