Bug 1388346 - screen corruption with Intel i915 and SNA AccelMethod
Summary: screen corruption with Intel i915 and SNA AccelMethod
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-25 07:20 UTC by Jan Hutař
Modified: 2017-07-26 05:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-26 05:54:41 UTC
Type: Bug


Attachments (Terms of Use)
trimmed labels screenshot (78.94 KB, image/png)
2016-10-25 07:20 UTC, Jan Hutař
no flags Details

Description Jan Hutař 2016-10-25 07:20:48 UTC
Created attachment 1213728 [details]
trimmed labels screenshot

Description of problem:
There is screen corruption with Intel i915 and SNA AccelMethod. Not only what is shown on the screenshot, but other issues as well (do not have screenshots for them now, but will add later if I hit them). In UXA mode configured as per [1] this does not happen (but I have different problem there: bug 1388297).


Version-Release number of selected component (if applicable):
kernel-core-4.7.9-200.fc24.x86_64
xorg-x11-drv-intel-2.99.917-24.20160712.fc24.x86_64
xfce4-session-4.12.1-9.fc24.x86_64

I'm running XFce and HW is Lenovo ThinkPad T540p


How reproducible:
always after boot until I start opening windows and so


Steps to Reproduce:
1. boot and login


Actual results:
Labels of some icons are somehow trimmed.


Expected results:


Additional info:
# lspci -v
[...]
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller])
	Subsystem: Lenovo Device 2210
	Flags: bus master, fast devsel, latency 0, IRQ 30
	Memory at f0000000 (64-bit, non-prefetchable) [size=4M]
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at 4000 [size=64]
	[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [d0] Power Management version 2
	Capabilities: [a4] PCI Advanced Features
	Kernel driver in use: i915
	Kernel modules: i915
[...]
# cat /sys/kernel/debug/dri/0/i915_swizzle_info
bit6 swizzle for X-tiling = bit9/bit10
bit6 swizzle for Y-tiling = bit9
MAD_DIMM_C0 = 0x00620020
MAD_DIMM_C1 = 0x00620020
MAD_DIMM_C2 = 0x00600000
TILECTL = 0x00000001
ARB_MODE = 0x00000020
DISP_ARB_CTL = 0x16663056


[1] https://fedoramagazine.org/solution-graphics-issues-intel-graphics-chipsets-fedora-22/

Comment 1 Fedora End Of Life 2017-07-25 23:36:26 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Jan Hutař 2017-07-26 05:54:41 UTC
Now with F26 I do not have xorg-x11-drv-intel installed, so it is using some different driver and that does not exhibit the issue.


Note You need to log in before you can comment on or make changes to this bug.