Bug 33062 - Regression for Wine programs
Summary: Regression for Wine programs
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 7.4 (2008.09)
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Chris Wilson
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-01-13 08:05 UTC by denisgolovan
Modified: 2011-07-03 02:47 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
2.11 screenshot. works fine (32.32 KB, image/gif)
2011-01-13 08:05 UTC, denisgolovan
no flags Details
2.14 (git) with regression (29.13 KB, image/gif)
2011-01-13 08:06 UTC, denisgolovan
no flags Details
xserver log (18.54 KB, text/plain)
2011-01-13 08:09 UTC, denisgolovan
no flags Details

Description denisgolovan 2011-01-13 08:05:18 UTC
Hi

I am experiencing a regression for MetaTrader program under latest Wine.
I am using Gentoo Linux with latest intel driver build from git.
See attachments for comparing 2.11 and git (2.14+) versions.
Comment 1 denisgolovan 2011-01-13 08:05:57 UTC
Created attachment 41964 [details]
2.11 screenshot. works fine
Comment 2 denisgolovan 2011-01-13 08:06:25 UTC
Created attachment 41965 [details]
2.14 (git) with regression
Comment 3 denisgolovan 2011-01-13 08:09:23 UTC
Created attachment 41966 [details]
xserver log
Comment 4 denisgolovan 2011-01-13 08:13:07 UTC
# lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)

# grep DRM .config
CONFIG_DRM=y
CONFIG_DRM_KMS_HELPER=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
CONFIG_DRM_I915=y
CONFIG_DRM_I915_KMS=y
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
Comment 5 denisgolovan 2011-01-13 08:20:04 UTC
libdrm is built from git bad5242a59aa8e31cf10749e2ac69b3c66ef7da0 commit.
xf86-video-intel is build from git fd9235ebe03a01982238cdd6e8b55f613e14b6af commit.
Comment 6 Eric Anholt 2011-06-05 21:22:06 UTC
Please retest with 2D driver as of:

commit e0066e77e026b0dd0daa0c3765473c7d63aa6753
Author: Eric Anholt <eric@anholt.net>
Date:   Tue May 31 23:17:16 2011 -0700

    uxa: Simplify Composite solid acceleration for spans by only clipping once.
    
    Unlike the previous commit removing this style of code, the code in
    this one was originally wrong, and would fail to clip in the second
    pass of clipping when y was > pbox->y2.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=37233
    Reviewed-by: Keith Packard <keithp@keithp.com>
Comment 7 denisgolovan 2011-06-06 12:54:17 UTC
No.
Unfortunately, that commit does not help.

I rebuild both libdrm and xf86-video-intel from git.
The latest commit was from 8f97157d2e807d6c9acb521ec59757f419e6518b

The commit you refer to is in.
Comment 8 Chris Wilson 2011-07-02 04:09:00 UTC
commit 855ced5a4eb67e287001ae22cb6489639c548cfa
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Thu Jun 16 13:24:14 2011 +0100

    uxa: Remove the attempt to use the 3D pipeline for core rendering
    
    The attempt was still ridden with bugs, such as
    
    http://bugs.freedesktop.org/show_bug.cgi?id=28768
    http://bugs.freedesktop.org/show_bug.cgi?id=28798
    http://bugs.freedesktop.org/show_bug.cgi?id=28908
    http://bugs.freedesktop.org/show_bug.cgi?id=29401
    
    A fresh approach was taken with SNA, but in the mean time before that
    can be enabled downstream, restore correct behaviour.
    
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Comment 9 denisgolovan 2011-07-03 02:47:17 UTC
Yeap.
I acknowledge the fix.
I tested both with and without sna. It works fine now.
Thanks a lot.

P.S. For those interested - I used x11 overlay, upgraded xorg-server to 1.10.2 and enabled sna use flag for xf86-video-intel


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.