Skip to contentSkip to conversation

i915: cursor corruption on Arrandale caused by 9b8c4a0b215e

2.6.35-rc regression Andy Isaacson 2 participants 3 messages Jun 6, 2010

lore
Share & tools
lore
#0 lore raw

My x201s (Core i7 L640 according to /proc/cpuinfo) running -rc1 exhibits cursor corruption when changing the cursor image (such as when moving out of xterm onto the desktop). Bisection pointed to 9b8c4a0b215e and reverting that on top of 03cd373981 fixed the problem. I'm running fvwm2 with xterm as my primary X client; the driver is

xserver-xorg-video-intel 2:2.9.1-4

The corruption generally goes away within a second or two, and seems to consist of the previous cursor image interleaved with the new cursor image on a row-by-row basis. Some kind of cache flush issue?

I've attached a JPG of a corrupted cursor.

-andy

#1 lore raw
Quoted 11 lines · Andy Isaacson

My x201s (Core i7 L640 according to /proc/cpuinfo) running -rc1 exhibits cursor corruption when changing the cursor image (such as when moving out of xterm onto the desktop). Bisection pointed to 9b8c4a0b215e and reverting that on top of 03cd373981 fixed the problem. I'm running fvwm2 with xterm as my primary X client; the driver is

xserver-xorg-video-intel 2:2.9.1-4

The corruption generally goes away within a second or two, and seems to consist of the previous cursor image interleaved with the new cursor image on a row-by-row basis. Some kind of cache flush issue?

Exactly; a missing move-to-GTT-domain causing the cursor data to remain in the CPU cache.

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

Signature · 8 lines
Chris Wilson, Intel Open Source Technology Centre

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
--
#2 lore raw
In reply to Andy Isaacson
Quoted 11 lines · Andy Isaacson

My x201s (Core i7 L640 according to /proc/cpuinfo) running -rc1 exhibits cursor corruption when changing the cursor image (such as when moving out of xterm onto the desktop). Bisection pointed to 9b8c4a0b215e and reverting that on top of 03cd373981 fixed the problem. I'm running fvwm2 with xterm as my primary X client; the driver is

xserver-xorg-video-intel 2:2.9.1-4

The corruption generally goes away within a second or two, and seems to consist of the previous cursor image interleaved with the new cursor image on a row-by-row basis. Some kind of cache flush issue?

Exactly; a missing move-to-GTT-domain causing the cursor data to remain in the CPU cache.

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

Signature · 1 line
Chris Wilson, Intel Open Source Technology Centre