Created attachment 82358 [details] dmesg System Environment: -------------------------- Platform: Sandybridge Kernel: -nightly commit df4969d4b4f47206323eafc80b7a282a081bd9cc Merge: 88de8dd a3ee4d2 Bug detailed description: ----------------------------- Clean boot system, *ERROR* conflict detected with stolen region: [0xcba00000 - 0xcfa00000] appears in dmesg. It happens on sandybridge with drm-intel-next-queued kernel. It doesn't happen on drm-intel-fixes kernel.
Created attachment 82359 [details] iomem
The latest good commit:b79480ba5074ae81d1c32073bce3981652e0f717 The latest bad commit:fee884ed285a110b665c00b07b134cd2616122bc
Genuine conflict from e820 enlarging the single page of valid memory before the stolen region.
Jesse Barnes volunteered to write an rfc patch to reserve stolen in early platform code and submit it to the x86 maintainers for feedback.
Created attachment 82977 [details] dmesg with patch Test patches（from bug 66726 comment21): http://lists.freedesktop.org/archives/intel-gfx/2013-July/030775.html http://lists.freedesktop.org/archives/intel-gfx/2013-July/030774.html It still happens.
Created attachment 82978 [details] iomem with patch
Can you try these instead? They fix a bug on SNB: http://lists.freedesktop.org/archives/intel-gfx/2013-July/030836.html
Created attachment 83018 [details] dmesg Fixed by these patches.
Created attachment 83019 [details] iomem
Should be fixed on dinq with commit ee75f952998e8365da90300cf1d421fc6c7dafa2 Author: Jesse Barnes <jbarnes@virtuousgeek.org> Date: Fri Jul 26 13:32:52 2013 -0700 x86: add early quirk for reserving Intel graphics stolen memory v5
Verified.Fixed.
Closing old verified.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.