Skip to contentSkip to conversation

Regression: pci=realloc fails to modify bridge windows, causing devices to fail BAR allocation

DISCUSSION TJ 2 participants 3 messages Jul 31, 2014 – Aug 11, 2014 PCI

lore
Share & tools
lore

TJ

author
#0 lore raw

See https://bugzilla.kernel.org/show_bug.cgi?id=81431

Summary:

Up until v3.15.7 booting with "pci=realloc,use_crs" successfully modifies the PCI bridge windows to allow an external ExpressCard <> ViDock4 + Nvidia Quadro NVS420 with its 2 GPUs to be configured.

With v3.16rc6 and rc7 it fails to do this, leaving the NVS420 inoperable.

author
#1 lore raw
Quoted 4 lines · TJ

See https://bugzilla.kernel.org/show_bug.cgi?id=81431

Summary:

Quoted 9 lines

Up until v3.15.7 booting with "pci=realloc,use_crs" successfully modifies the PCI bridge windows to allow an external ExpressCard <> ViDock4 + Nvidia Quadro NVS420 with its 2 GPUs to be configured.

With v3.16rc6 and rc7 it fails to do this, leaving the NVS420 inoperable. --
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

This continues to affect 3.16.

maintainer
#2 lore raw
In reply to TJ

[+cc linux-pci]

Quoted 9 lines · TJ

See https://bugzilla.kernel.org/show_bug.cgi?id=81431

Summary:

Up until v3.15.7 booting with "pci=realloc,use_crs" successfully modifies the PCI bridge windows to allow an external ExpressCard <> ViDock4 + Nvidia Quadro NVS420 with its 2 GPUs to be configured.

With v3.16rc6 and rc7 it fails to do this, leaving the NVS420 inoperable.

Thanks for the report and the dmesg logs. I'm just returning from vacation and haven't been able to analyze them yet. If you have a chance to bisect this to a specific commit, we might be able to fix or revert it.

Bjorn