Bug 71370 - [BYT] *ERROR* conflict detected with stolen region: [0x7b000000 - 0x7f000000]
Summary: [BYT] *ERROR* conflict detected with stolen region: [0x7b000000 - 0x7f000000]
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: All All
: medium normal
Assignee: Jesse Barnes
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-08 02:17 UTC by Guo Jinxian
Modified: 2017-10-06 14:42 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
[drm:i915_stolen_to_physical] *ERROR* (117.43 KB, text/plain)
2013-11-08 02:17 UTC, Guo Jinxian 		no flags Details
iomen (1.70 KB, text/plain)
2013-11-08 07:59 UTC, Guo Jinxian 		no flags Details
full dmesg after booting (145.57 KB, text/plain)
2013-11-11 05:32 UTC, Guang Yang 		no flags Details
new iomem (1.70 KB, text/plain)
2013-11-11 06:11 UTC, Guang Yang 		no flags Details
debug patch (784 bytes, patch)
2013-11-11 06:57 UTC, Daniel Vetter 		no flags Details | Splinter Review
use gen6 stolen sizing on VLV (636 bytes, patch)
2013-11-11 17:34 UTC, Jesse Barnes 		no flags Details | Splinter Review
View All

Description Guo Jinxian 2013-11-08 02:17:44 UTC 
Created attachment 88867 [details]
[drm:i915_stolen_to_physical] *ERROR*

System Environment:
--------------------------
Platform:       Sandybridge
Kernel:  -next-queue commit  2ec3815f29d1b7659ecf3f1791e7e394efdd6969

Bug detailed description:
-----------------------------
Clean boot system, *ERROR* conflict detected with stolen region: [0x7b000000 - 0x7f000000] appears in dmesg.
It happens on BayTrail with drm-intel-next-queued and drm-intel-testing kernel.
Comment 1 Daniel Vetter 2013-11-08 07:23:16 UTC 
Please attach /proc/iomem from the affected system.
Comment 2 Guo Jinxian 2013-11-08 07:59:33 UTC 
Created attachment 88879 [details]
iomen

Please check iomem in attachment, thanks.
Comment 3 Daniel Vetter 2013-11-08 08:13:37 UTC 
Hm, the dmesg is incomplete, and I need the very beginning with the e820 map. Can you please attach a new one?
Comment 4 Guang Yang 2013-11-11 05:32:23 UTC 
Created attachment 88986 [details]
full dmesg after booting

I attached the full dmesg and the iomem with the latest -dinq.
Comment 5 Guang Yang 2013-11-11 06:11:31 UTC 
Created attachment 88987 [details]
new iomem
Comment 6 Daniel Vetter 2013-11-11 06:57:28 UTC 
Created attachment 88990 [details] [review]
debug patch

Please apply the attached debug patch and then grab a new dmesg from boot.
Comment 7 Jesse Barnes 2013-11-11 17:34:41 UTC 
Created attachment 89040 [details] [review]
use gen6 stolen sizing on VLV

Maybe the BIOS changed things up on us, this patch may make things work again.
Comment 8 Guang Yang 2013-11-12 01:59:18 UTC 
(In reply to comment #7)
> Created attachment 89040 [details] [review] [review]
> use gen6 stolen sizing on VLV
> 
> Maybe the BIOS changed things up on us, this patch may make things work
> again.
Yeah, change the gen3 stolen size to gen6, the issue is gone.
Comment 9 Daniel Vetter 2013-11-12 08:38:45 UTC 
Wut. I really hope we don't have different stolen size bits depending upon the bios version. Assigning to Jesse to figure this out.
Comment 10 Jesse Barnes 2013-11-17 21:50:00 UTC 
commit 7bd40c16ccb2cb6877dd00b0e66249c171e6fa43
Author: Jesse Barnes <jbarnes@virtuousgeek.org>
Date:   Tue Nov 12 10:17:39 2013 -0800

    x86/early quirk: use gen6 stolen detection for VLV
Comment 11 Guo Jinxian 2013-11-22 07:17:11 UTC 
Checked on -testing(f400ddc64ab74ae754896138f1aacd4b4ad62def), this bug had fixed, thanks.
Comment 12 Elizabeth 2017-10-06 14:42:12 UTC 
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.