Bug 1529846 - Intel UXA failure after upgrade to Linux kernel 4.14.8-300.fc27.x86_64
Summary: Intel UXA failure after upgrade to Linux kernel 4.14.8-300.fc27.x86_64
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 27
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-30 05:12 UTC by Narendran Gopalakrishnan
Modified: 2018-11-30 21:46 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-11-30 21:46:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Narendran Gopalakrishnan 2017-12-30 05:12:00 UTC
Description of problem:

I use AccelMethod UXA in intel config, as SNA causes rendering issues in xterm. This was working till 4.13.15-300.fc27.x86_64.

But after the recent upgrade to 4.14.8-300.fc27.x86_64, windows are not rendered, and I only get a black region for any application (chrome, vlc, gnome-tweak-tool etc.,). Correspondingly, ~/.local/share/xorg/Xorg.0.log says:

(EE) intel(0): Failed to submit batch buffer, expect rendering corruption: Invalid agument.

However, if I try SNA instead, windows are rendered correctly (though the old problem with xterm, for which I had switched to UXA in the first place, is still present.)

Workaround: Using the older kernel 4.13.15-300.fc27.x86_64.

Comment 1 Narendran Gopalakrishnan 2018-05-30 08:59:26 UTC
Glad to say this issue could not be reproduced with the kernel-vanilla-mainline 
 kernel-4.17.0-0.rc7.git0.1.vanilla.knurd.1.fc27.x86_84.rpm.

So may be it is just a matter of time before the fix arrives (if it hasn't arelady arrived) in Fedora and CentOS.

Comment 2 Ben Cotton 2018-11-27 15:34:22 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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 3 Ben Cotton 2018-11-30 21:46:51 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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