-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/04/12 19:40, Yinghai Lu wrote: > On Tue, Apr 10, 2012 at 10:02 AM, Steven Newbury > <steve@xxxxxxxxxxxxxxx> wrote: >> >>> >>> Can you please try attached patches with pci=nocrs? >>> >>> for pci=use_crs, we need find safe place beyond _CRS, because >>> your _CRS limit under 4g. >>> > .. >> So far it has changed behaviour: >> >> Many devices now assigned above 4g. >> >> When booted while docked i915 fails to initialise, along with >> radeon as before. >> >> When undocked i915 initialises, but radeon still fails when >> hot-docked. >> >> I've attached output of 'lspci -vvv', 'cat /proc/iomem', and >> "dmesg.log" for the docked case. >> >> Also, "dmesg-hotplug.out" for hot docking after boot. > > looks good, please only apply > > allocate_high_at_first.patch > > Yinghai Seems to be exactly the same. When started docked (so I think both 'cards' try to claim the same preferred addresses) the integrated i965 GFX gets reassigned high: 120000000-12fffffff : 0000:00:02.0 But it's quite possible the i915 module doesn't currently handle this case and so fails to initialise. I'm not sure why the Radeon doesn't get assigned a high address when hot-plugged..? These are the only entries in /proc/iomem above 4GB: Booted UNDOCKED, then hot-docked 100000000-11fffffff : System RAM 120000000-1201fffff : PCI Bus 0000:0b 120200000-1203fffff : PCI Bus 0000:0c 120400000-1205fffff : PCI Bus 0000:09 Booted DOCKED 100000000-11fffffff : System RAM 120000000-12fffffff : 0000:00:02.0 130000000-1301fffff : PCI Bus 0000:0b 130200000-1303fffff : PCI Bus 0000:0c 130400000-1305fffff : PCI Bus 0000:0d 130600000-1307fffff : PCI Bus 0000:09 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+Eg1cACgkQGcb56gMuC61hTgCeLIPkAEr1btlgzwmmGAqbnPZq /CEAn16oEFbgvWH0ifOL0FFiQTodBf1U =JBs3 -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
