Bug 1854672
Summary: | Bug in xf86-video-intel (xorg-x11-drv-intel) prevents iris driver from working properly when DRI2 and intel DDX driver are in use | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tomasz Tomasik <scx.mail> | ||||||||||||||||||||||
Component: | xorg-x11-drv-intel | Assignee: | Adam Jackson <ajax> | ||||||||||||||||||||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||
Severity: | urgent | Docs Contact: | |||||||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||||||
Version: | 32 | CC: | ajax, domfe, jglisse, scx.mail, xgl-maint | ||||||||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||||||||||
OS: | Linux | ||||||||||||||||||||||||
Whiteboard: | |||||||||||||||||||||||||
Fixed In Version: | Doc Type: | --- | |||||||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||||||
Last Closed: | 2021-05-25 17:11:30 UTC | Type: | Bug | ||||||||||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||
Embargoed: | |||||||||||||||||||||||||
Attachments: |
|
Description
Tomasz Tomasik
2020-07-08 00:12:01 UTC
Created attachment 1700218 [details]
Upstream patch for xf86-video-intel (xorg-x11-drv-intel)
In mesa i915/i965 pass the bpp to use when creating the surface, but the gallium state tracker passed the depth. As it happens that BitsPerPixel(format) will do the right thing for both, use that.
Created attachment 1700219 [details]
X.Org configuration
X.Org configuration with DRI2 and the intel DDX driver instead of modesetting
Created attachment 1700220 [details]
RPM SPEC
RPM SPEC with "0002-dri2-Interpret-DRI2ATTACH_FORMAT-as-depth-not-bpp.patch"
Created attachment 1700221 [details]
dmesg log
Error in libgallium_dri.so
Created attachment 1700223 [details]
gdb log
Error in /usr/lib/x86_64-linux-gnu/GL/default/lib/dri/iris_dri.so
Created attachment 1700225 [details]
SRPM for EL6
SRPM for EL6 with "0002-dri2-Interpret-DRI2ATTACH_FORMAT-as-depth-not-bpp.patch"
Created attachment 1700226 [details]
SRPM for EL7
SRPM for EL7 with "0002-dri2-Interpret-DRI2ATTACH_FORMAT-as-depth-not-bpp.patch"
Created attachment 1700227 [details]
SRPM for EL8
SRPM for EL8 with "0002-dri2-Interpret-DRI2ATTACH_FORMAT-as-depth-not-bpp.patch"
Created attachment 1700228 [details]
SRPM for FC30-FC31
SRPM for FC30-FC31 with "0002-dri2-Interpret-DRI2ATTACH_FORMAT-as-depth-not-bpp.patch"
Created attachment 1700229 [details]
SRPM for FC32-FC33
SRPM for FC32-FC33 with "0002-dri2-Interpret-DRI2ATTACH_FORMAT-as-depth-not-bpp.patch"
I think I'm affected by this bug in Fedora 32. I don't have problem with kernel version 5.6.19. Kernel version from 5.7 are freezing my machine if acceleration is enabled. See my opened bug https://bugzilla.redhat.com/show_bug.cgi?id=1855558 I installed xorg-x11-drv-intel-2.99.917-46.20200205.fc32.x86_64 but this doesn't resolved the issue. Is it the same bug or are they possibly related? > Is it the same bug or are they possibly related?
I think it may be an another problem with the iris driver.
You can try to force use i965. However, please keep in mind that Gen12+ GPUs are supported only by iris.
At first, try this:
MESA_LOADER_DRIVER_OVERRIDE=i965 vlc
or this:
export MESA_LOADER_DRIVER_OVERRIDE=i965; vlc
If that helps, put this in ~/.drirc (user), /etc/drirc or /usr/share/drirc.d/01-i915-force-i965.conf (system):
<?xml version="1.0" standalone="yes"?>
<driconf>
<device driver="loader" kernel_driver="i915">
<option name="dri_driver" value="i965" />
</device>
</driconf>
Same problem on Fedora 33 with new kernel. Using kernel 5.11.0-0.rc7.149.fc34.x86_64 on Intel G3420. So far, so good. This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 '32'. 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 32 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. Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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. |