[cairo-bugs] [Bug 31547] New: [bisected piketon]some cairo test regressed

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=31547

           Summary: [bisected piketon]some cairo test regressed
           Product: cairo
           Version: 1.10.1
          Platform: All
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: xlib backend
        AssignedTo: cworth at cworth.org
        ReportedBy: xunx.fang at intel.com
         QAContact: cairo-bugs at cairographics.org
                CC: chris at chris-wilson.co.uk


System Environment:
--------------------------
Arch    x86_64
Platform    piketon
Libdrm:  (master)2.4.22-14-g877b2ce15b80975b4dac42657bdfb0a3da833e1c
Mesa:   (master)5b8ed2f6d2e14303c55aeca65cdbc20791e820f6
Xserver: 
(server-1.9-branch)xorg-server-1.9.2-7-g46314e1e7ad05d6ff6a2f722b09a76f2931db7f5
Xf86_video_intel: (master)2.13.901-2-g3c5b1399e29ef577b8b91655b5e1c215d1b6dfbb
Kernel: (drm-intel-fixes)69669455b049c0f1f04bb306625c5d4db6838b11


Bug detailed description:
-------------------------
cairo test operator-source, clear-source, device-offset-fractional,
filter-nearest-offset, pixman-rotate and xcomposite-projection regresses on
piketon.
Bisect shows 3c5b1399e29ef577b8b91655b5e1c215d1b6dfbb is first bad commit.
commit 3c5b1399e29ef577b8b91655b5e1c215d1b6dfbb
Author:     Chris Wilson <chris at chris-wilson.co.uk>
AuthorDate: Tue Nov 9 20:20:06 2010 +0000
Commit:     Chris Wilson <chris at chris-wilson.co.uk>
CommitDate: Tue Nov 9 20:20:06 2010 +0000

    i915: Disable maximum state addresses

    As the kernel controls the relocation of state buffers, we should not
    hard code the maximum permissible value for them.

    Fixes an eventual hang with full-gtt.

    Reported-by: Peter Clifton <pcjc2 at cam.ac.uk>
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.