Created attachment 110609 [details] Frontbuffer tracking HW: BYT RVP Boot from USB with: 1. 1st partition contains grub and kernel bootimage 2. 2nd partition contains rootfs. Kernel: drm-intel-nightly Bug description --------------- After booting up kernel and mouting of rootfs when an Xterm is started using startx, frontbuffer updates are not tracked in intel_frontbuffer.c Calls to intel_frontbuffer_flush and intel_fb_obj_invalidate are not made: 1. When moving from console mode to UI mode and vice-versa (F1 and F7) 2. When mouse movements or keystrokes are performed. In the attached logs, control was moved from F1 to F7 and vice-versa many times but a flush was seen only for the first time.
Can you also clarify whether by cursor you mean the mouse pointer on the screen, or the insertion point (the solid rectangle or rectangle outline) in the xterm?
For the first time when I startX, I don't see mouse pointer. But the cursor (rectangle) is present but in disabled state. So I am unable to enter anything from keyboard. From next time onwards, I start seeing the mouse pointer and I can bring the rectangle pointer to enabled and then I enter text on the terminal. I don't see frontbuffer flush and invalidate for any of the above.
Please test https://freedesktop.org/patch/38393/
(In reply to Daniel Vetter from comment #3) > Please test > > https://freedesktop.org/patch/38393/ In -nightly, I don't see any third argument to intel_fb_obj_flush function which is used in the patch for ORIGIN_GPU/ORIGIN_GTT. Please let me know the equivalent function for this.
Please try first five patches of http://mid.gmane.org/1423500395-1787-1-git-send-email-przanoni@gmail.com
Patches should all have landed now, can you please retest latest -nightly?
(In reply to Daniel Vetter from comment #6) > Patches should all have landed now, can you please retest latest -nightly? No answer since March. Presuming fixed.
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.