| Summary: | Stange Artifacts on UHD 605 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | HJ <punx665> | ||||||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
| Status: | RESOLVED DUPLICATE | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
| Severity: | normal | ||||||||||
| Priority: | medium | CC: | intel-gfx-bugs | ||||||||
| Version: | unspecified | ||||||||||
| Hardware: | x86-64 (AMD64) | ||||||||||
| OS: | Linux (All) | ||||||||||
| Whiteboard: | |||||||||||
| i915 platform: | i915 features: | ||||||||||
| Attachments: |
|
||||||||||
|
Description
HJ
2019-03-10 19:20:33 UTC
[ 15420.752] (EE) modeset(0): Failed to get GBM bo for flip to new front. [ 15420.752] (EE) modeset(0): present flip failed gbm or i965 or -modesetting? Could you attach the output of glxinfo? Thanks! Actually found the following : https://bugzilla.redhat.com/show_bug.cgi?id=1645553 https://gitlab.freedesktop.org/xorg/xserver/merge_requests/131 Seems to be modesetting issue. Also i disabled the compositor as mentioned here: https://bugzilla.redhat.com/show_bug.cgi?id=1645553#c8 and the messages are gone, however I still have those artifacts. Created attachment 143622 [details]
glxinfo
Created attachment 143623 [details]
new xorg.log
Looks a lot like https://bugs.freedesktop.org/show_bug.cgi?id=108085 I'm inclined to punt it back to i915. Can you boot your kernel with the following option : i915.enable_fbc=0 If this goes away then I'll close with duplicate. there was also one more suggestion to switch from "modesetting" to "intel" driver. https://bugzilla.redhat.com/show_bug.cgi?id=1645553#c11 for checking driver in use you can do this: egrep -i " connected|card detect|primary dev|Setting driver" /var/log/Xorg.0.log >Can you boot your kernel with the following option : i915.enable_fbc=0
thx that did it!
*** This bug has been marked as a duplicate of bug 108085 *** |
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.