Bug 52421 - [SNA] Corrupted video and flickering
Summary: [SNA] Corrupted video and flickering
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Chris Wilson
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-23 23:20 UTC by Victor Machado
Modified: 2012-07-27 07:41 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
SNA ENABLED (274.33 KB, image/png)
2012-07-23 23:26 UTC, Victor Machado
no flags Details
SNA DISABLED (879.47 KB, image/png)
2012-07-23 23:27 UTC, Victor Machado
no flags Details
XORG LOG (31.63 KB, text/plain)
2012-07-24 12:49 UTC, Victor Machado
no flags Details
LSPCI (7.22 KB, text/plain)
2012-07-27 03:04 UTC, Victor Machado
no flags Details

Description Victor Machado 2012-07-23 23:20:36 UTC
Hello everyone i was using the 2.19 intel driver than they released the current 2.20 version and when i enable SNA aceleration the video starts flickering and etc. I also tested 2.20.1 driver and the error continue.

Hardware:
Processor: Intel Core i7-2630QM @ 2.00GHz (8 Cores), Motherboard: Intel Emerald Lake, Chipset: Intel 2nd Generation Core Family DRAM, Memory: 4096MB, Disk: 500GB TOSHIBA MK5065GS, Graphics: Intel Sandybridge Mobile (GT2), Audio: Realtek ALC662 rev1, Network: Realtek RTL8101E/RTL8102E + Atheros AR9285 Wireless

Software:
OS: Linux, Kernel: 3.5.0-1-ARCH (x86_64), Desktop: GNOME Shell 3.4.2, Display Server: X Server 1.12.3, Display Driver: intel 2.20.1, OpenGL: 3.0 Mesa 8.0.4, Compiler: GCC 4.7.1 20120721, File-System: ext4, Screen Resolution: 1366x768
Comment 1 Victor Machado 2012-07-23 23:26:43 UTC
Created attachment 64573 [details]
SNA ENABLED
Comment 2 Victor Machado 2012-07-23 23:27:27 UTC
Created attachment 64574 [details]
SNA DISABLED
Comment 3 Chris Wilson 2012-07-24 06:13:06 UTC
Can you please quickly check whether this only affects OpenGL content (such as gnome-shell) by enabling fallback mode?
Comment 4 Victor Machado 2012-07-24 12:48:07 UTC
This affect fallback mode too.
Comment 5 Victor Machado 2012-07-24 12:49:32 UTC
Created attachment 64611 [details]
XORG LOG
Comment 6 Chris Wilson 2012-07-26 21:15:48 UTC
Hmm, the corruption will be fixed with 

commit 8c5077e4ed055a97bf9deda59c0e9a45e42317ca
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Wed Jul 25 16:59:11 2012 +0100

    Assume all unknown chipsets are future gen
    
    I think the likelihood of a new product being launched based on a 8xx
    design is remote enough not to worry about.

but... The question is why does it think your hardware is unsupported...

Can you please paste lspci -vvn?
Comment 7 Chris Wilson 2012-07-26 21:17:12 UTC
Oh and attach a drm.debug=0xf dmesg from when X starts please.
Comment 8 Chris Wilson 2012-07-26 21:21:45 UTC
And third time lucky, an --enable-debug=full Xorg.log  would be very useful as well.
Comment 9 Chris Wilson 2012-07-26 21:55:09 UTC
Ok, this is very odd as well:

[    13.228] (==) ServerLayout "X.org Configured"
[    13.228] (**) |-->Screen "Screen0" (0)
[    13.228] (**) |   |-->Monitor "Monitor0"
[    13.244] (**) |   |-->Device "Card0"
[    13.244] (**) |-->Screen "Screen1" (1)
[    13.244] (**) |   |-->Monitor "Monitor1"
[    13.244] (**) |   |-->Device "Card1"
[    13.244] (**) |-->Screen "Screen2" (2)
[    13.244] (**) |   |-->Monitor "Monitor2"
[    13.244] (**) |   |-->Device "Card2"
[    13.244] (**) |-->Screen "Screen3" (3)
[    13.244] (**) |   |-->Monitor "Monitor3"
[    13.244] (**) |   |-->Device "Card3"
[    13.244] (**) |-->Screen "Screen4" (4)
[    13.244] (**) |   |-->Monitor "Monitor4"
[    13.244] (**) |   |-->Device "Card4"
[    13.244] (**) |-->Screen "Screen5" (5)
[    13.244] (**) |   |-->Monitor "Monitor5"
[    13.245] (**) |   |-->Device "Card5"
[    13.245] (**) |-->Screen "Screen6" (6)
[    13.245] (**) |   |-->Monitor "Monitor6"
[    13.245] (**) |   |-->Device "Card6"
[    13.245] (**) |-->Screen "Screen7" (7)
[    13.245] (**) |   |-->Monitor "Monitor7"
[    13.245] (**) |   |-->Device "Card7"
[    13.245] (**) |-->Screen "Screen8" (8)
[    13.245] (**) |   |-->Monitor "Monitor8"
[    13.245] (**) |   |-->Device "Card8"
[    13.245] (**) |-->Screen "Screen9" (9)
[    13.245] (**) |   |-->Monitor "Monitor9"
[    13.245] (**) |   |-->Device "Card9"
[    13.245] (**) |-->Screen "Screen10" (10)
[    13.245] (**) |   |-->Monitor "Monitor10"
[    13.245] (**) |   |-->Device "Card10"
[    13.245] (**) |-->Screen "Screen11" (11)
[    13.245] (**) |   |-->Monitor "Monitor11"
[    13.246] (**) |   |-->Device "Card11"
[    13.246] (**) |-->Screen "Screen12" (12)
[    13.246] (**) |   |-->Monitor "Monitor12"
[    13.246] (**) |   |-->Device "Card12"
[    13.246] (**) |-->Screen "Screen13" (13)
[    13.246] (**) |   |-->Monitor "Monitor13"
[    13.246] (**) |   |-->Device "Card13"

I doubt you have quite that many monitors and integrated graphics. Can you please regenerate your xorg.conf, even better would be not to have one, but a snipped to enable sna (if using AccelMethod).
Comment 10 Gordon Jin 2012-07-27 02:17:07 UTC
not to set a bug with non-default option as high priority
Comment 11 Victor Machado 2012-07-27 03:04:56 UTC
Created attachment 64762 [details]
LSPCI
Comment 12 Victor Machado 2012-07-27 03:10:55 UTC
Chris i can not post the Xorg.log with enable debug full the archive has more than 180mb in 60 seconds. Now is everything running ok, i build the driver with:  ./configure --prefix=/usr --enable-sna --with-default-accel=sna
so i dont need a xorg.conf. Xorg.log = http://pastebin.com/LVbU7f8K
Comment 13 Victor Machado 2012-07-27 03:14:49 UTC
(In reply to comment #10)
> not to set a bug with non-default option as high priority

Sorry Gordon that was a mistake.
Comment 14 Chris Wilson 2012-07-27 07:41:49 UTC
Still puzzling over which allocation failed to cause it disable acceleration, but at least the pair of bugs that lead to the situation have been resolved.


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.