(In reply to comment #97) > (In reply to comment #96) > > (In reply to comment #93) > > > The bad part is - while before I've been getting 3.7Mchar/s in x11perf > > > -aa10text - now it's like 1.3Mchar/s so significantly slower. > > > > That's the sacrifice, we have to stop sending commands to the GPU and wait > > for it complete those in flight (quite frequently). Or else new rectangles > > overwrite vertex entries still being used by later entries > > > > > So the question here would be - isn't the corruption based on triangle > > > surface size ? So i.e. GPU is able to process a lot of small ones - but > > > has > > > bug with bigger ones ? > > > > > But as I said before - if that would be plain hw defect - IMHO it would > simply always appear - but it seems like it's working for a while - then > 'something' happens - and flickering starts to appear - with (assumingly) > same amount > of texels/triangle/vertices - and than something again may happen, > and the problem is gone for a while.
It does. You do not have quite as much control over your tests as you presume. > > Not really, you have to predict when a VUE being used by the end of the > > pipeline will be overwritten by a new rectangle at the start of the > > pipeline. This is completely internal state - the primitive command we want > > to feed to the GPU can contains thousands of rectangles. Instead of counting > > Well I've tried even 8 max triangles - and the error appeared after a while, > so far '6' is magic. > > > rectangles, you want to start counting fragments (actually texel reads since > > that will be the ratelimiting factor) and flush if we queue up too much work > > for the GPU. If you also model how fast the gpu is retiring fragments so > > But in case the same page is rendered with problems as well as without > problems, > then it doesn't look like texel read is problem, it rather looks like some > kind of memory mapping/ordering. No. I did not say the texel reads where the problem, just an indicator as to how long the EU would execute any particular shader for a fragment. Also there is only a single sampler and many EU running many more threads, so contention will also play a factor into how long each fragment takes to process, and so how long buffers will be active for. Look more closely at what it is going on, it is clearly that the hardware is not tracking lifetimes of its URB correctly. > Also is there some explanation why intel_gpu_top is showing so much higher > GPU usage when the flickering is visible ? Other than the flickering correlates with GPU activity? (In reply to comment #98) > Well I should wait a while before posting a comment about magic value 6. > > I'm now observing flickering with value 6 as well. > > So yeah - it's more or less time related - and it takes more or less time > until the problem becomes visible. > > Also is there explanation with the max value 64 starts to make problems > with text rendering in gnome terminal ? > > i.e. I'd have expected if there would be a large press on GPU - but in this > case it just appear random pixel start to be drawn instead of some letter - > maybe some font cache corruption ? It's still the same bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1098489 Title: [gen4] Corruption in Chrome omni bar results using Intel SNA Status in X.org xf86-video-intel: In Progress Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Bug description: After enabling Intel SNA the favicons in the omnibar search results are corrupted. I've attached a screenshot of the issue with the bug report, note the favicon of the first result is corrupted. This bug is probably the same as bug #1098334, more information may be seen there. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0 Uname: Linux 3.7.0-7-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Fri Jan 11 15:31:21 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-12-03 (38 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Alpha amd64+mac (20121203) MarkForUpload: True SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.8-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: raring DistroRelease: Ubuntu 13.04 DistroVariant: kubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00dc] InstallationDate: Installed on 2012-12-03 (38 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Alpha amd64+mac (20121203) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True Package: xserver-xorg-video-intel 2:2.20.17-0ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.7.0-7-generic root=/dev/mapper/kubuntu-root ro quiet splash i915.lvds_channel_mode=2 i915.modeset=1 i915.lvds_use_ssc=0 vt.handoff=7 ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0 Tags: raring kubuntu single-occurrence Uname: Linux 3.7.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section "Device" Identifier "Card0" Driver "intel" Option "AccelMethod" "sna" EndSection dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.40-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.1.901-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.17-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu1 xserver.bootTime: Fri Jan 11 16:00:31 2013 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.1.901-0ubuntu1 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1098489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
