[Bug 58511] [drm:i915_gem_object_bind_to_gtt] *ERROR* Attempting to bind an object larger than the aperture

[bugzilla-daemon at bugzilla.kernel.org]

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





--- Comment #15 from hreuver <h.reuver at aoi-karin.net>  2013-05-21 18:28:36 ---
$ git bisect good
53e587aa5ca81497d0ea6e340320ec5778d1f311 is the first bad commit
commit 53e587aa5ca81497d0ea6e340320ec5778d1f311
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Thu Nov 15 11:32:18 2012 +0000

    drm/i915: Fix detection of base of stolen memory

    commit e12a2d53ae45a69aea499b64f75e7222cca0f12f upstream.

    The routine to query the base of stolen memory was using the wrong
    registers and the wrong encodings on virtually every platform.

    It was not until the G33 refresh, that a PCI config register was
    introduced that explicitly said where the stolen memory was. Prior to
    865G there was not even a register that said where the end of usable
    low memory was and where the stolen memory began (or ended depending
    upon chipset). Before then, one has to look at the BIOS memory maps to
    find the Top of Memory. Alas that is not exported by arch/x86 and so we
    have to resort to disabling stolen memory on gen2 for the time being.

    Then SandyBridge enlarged the PCI register to a full 32-bits and change
    the encoding of the address, so even though we happened to be querying
    the right register, we read the wrong bits and ended up using address 0
    for our stolen data, i.e. notably FBC.

    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch>
    [bwh: Backported to 3.2: adjust filename, context]
    Signed-off-by: Ben Hutchings <ben at decadent.org.uk>

:040000 040000 323812cac24bd796efa71220b496ee5a2a00d298
101967a69bc453f845daf3a7a3024ebd932984dc M      drivers

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.