Bug 96705 - [Intel HD 5500] keyboard lag in gnome-terminal
Summary: [Intel HD 5500] keyboard lag in gnome-terminal
Status: NEW
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-28 08:04 UTC by Jakub Alba
Modified: 2016-06-28 09:38 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg output (100.95 KB, text/plain)
2016-06-28 08:04 UTC, Jakub Alba
no flags Details
Xorg.0.log (21.48 KB, text/plain)
2016-06-28 08:05 UTC, Jakub Alba
no flags Details
/etc/X11/xorg.conf.d/00-keyboard.conf (232 bytes, text/plain)
2016-06-28 08:06 UTC, Jakub Alba
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jakub Alba 2016-06-28 08:04:57 UTC
Created attachment 124754 [details]
dmesg output

After a while of typing stuff in gnome-terminal there is a lag. Just like described by a guy here[1], except that it also happens in vim (for the prompt displayed at the bottom when starting a command with ':'). So I'll just quote:

"I'm experiencing a serious delay in keyboard input in all terminals I have, except xterm.  gnome-terminal, terminator are the ones with the same issue.

Well, anything that is a letter key that is...  Backspace, arrow keys, enter actually function instantly as expected.  But entering anything such as:

$ asddkdalsdlasdlasd
$ ls -l
$ nano ~/.profile

Are all delayed by 2 to 5 seconds before showing partially, or all of it."

The guys from this forum suggested switching from SNA to UXA. It does seem to fix that, but I'm not really sure, because I have to type for a longer while to reproduce the bug.

Chipset: Intel HD 5500
System architecture: x86_64
xserver version: 1.18.3
xf86-video-intel version: 2.99.917
Kernel version: 4.6.3-1-ARCH
Linux distro: Arch Linux
Machine: Dell Latitude 3450

[1] https://bbs.archlinux.org/viewtopic.php?id=199346
Comment 1 Jakub Alba 2016-06-28 08:05:29 UTC
Created attachment 124755 [details]
Xorg.0.log
Comment 2 Jakub Alba 2016-06-28 08:06:25 UTC
Created attachment 124756 [details]
/etc/X11/xorg.conf.d/00-keyboard.conf
Comment 3 Chris Wilson 2016-06-28 08:37:46 UTC
Either i915.enable_fbc=0 or Option "TearFree" in xorg.conf. Or use an older or more recent kernel than 4.6.
Comment 4 Jakub Alba 2016-06-28 09:30:29 UTC
(In reply to Chris Wilson from comment #3)
> Either i915.enable_fbc=0 or Option "TearFree" in xorg.conf. Or use an older
> or more recent kernel than 4.6.

So in case of a more recent one is this[1] supposed to fix it? 5500 is a Broadwell GPU, so I don't think so. But we'll see.

Anyway, thanks for the help, I've gone for "TearFree".

[1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/i915?id=1e3fa0acfec677e915d7de5ac6e1f18cfa4f805b
Comment 5 Chris Wilson 2016-06-28 09:38:13 UTC
(In reply to Jakub Kucharski from comment #4)
> (In reply to Chris Wilson from comment #3)
> > Either i915.enable_fbc=0 or Option "TearFree" in xorg.conf. Or use an older
> > or more recent kernel than 4.6.
> 
> So in case of a more recent one is this[1] supposed to fix it? 5500 is a
> Broadwell GPU, so I don't think so. But we'll see.

No, there are some FBC tracking fixes that are in the queue.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct.