<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [SKL] System boots with [drm:i915_stolen_to_physical] *ERROR* conflict detected with stolen region: [0xc6000000 - 0xc8000000] on dmesg"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97621#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [SKL] System boots with [drm:i915_stolen_to_physical] *ERROR* conflict detected with stolen region: [0xc6000000 - 0xc8000000] on dmesg"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97621">bug 97621</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>So the new BIOS adds a conflicting entry:
[ 0.000000] BIOS-e820: [mem 0x00000000c5300000-0x00000000c7ffffff] reserved
with which the kernel manages to zap our
[ 0.000000] Reserving Intel graphics memory at
0x00000000c6000000-0x00000000c7ffffff
However. In the old BIOS,
[ 0.000000] Reserving Intel graphics memory at
0x00000000c1000000-0x00000000c2ffffff
which was not marked up as reserved inside the e820.
It seems to be e820_reserve_resources_late() is causing the conflict, but our
earlier intel_graphics_stolen() should ideally have fixed up the e820 map.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>