| Summary: | [SKL] [bisected] [regression] Artifacts when running window manager remotely | ||||||
|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Mariusz Białończyk <manio> | ||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
| Severity: | normal | ||||||
| Priority: | medium | CC: | chris, intel-gfx-bugs | ||||
| Version: | XOrg git | Keywords: | bisected | ||||
| Hardware: | x86-64 (AMD64) | ||||||
| OS: | Linux (All) | ||||||
| Whiteboard: | ReadyForDev | ||||||
| i915 platform: | SKL | i915 features: | display/Other | ||||
| Attachments: |
|
||||||
|
Description
Mariusz Białończyk
2018-01-07 16:12:31 UTC
Sadly that is just telling you something else is wrong. I reported the same bug with the same artifacts and the same kernel commit ... certainly this means that commit has SOMETHING to do with this display corruption, especially since everything works perfectly before, and after if this commit is reverted (and for many kernel versions afterwards, incl. Linus' tip)? Hello, could you attach full dmesg with drm.debug=0x1e with the corruption captured in the log? First of all. Sorry about spam. This is mass update for our bugs. Sorry if you feel this annoying but with this trying to understand if bug still valid or not. If bug investigation still in progress, please ignore this and I apologize! If you think this is not anymore valid, please comment to the bug that can be closed. If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug. Hi Elizabeth, I compiled a fresh 4.16.0-rc7 kernel today. I am attaching the full dmesg as you requested. Some notes: After clean reboot I started xorg and then exported the DISPLAY and run the display manager. Artifacts started to happen. Then after some time I terminated the xorg and then the lines [drm:gen8_irq_handler] *ERROR* Fault errors on pipe B: 0x00000800 started to flood my log (it is very common when I terminate xorg). Then I created a full dmesg to you. Created attachment 138421 [details]
dmesg
Chris, any advice here? Sorry for the delay... Reporter, do you still have the issue? Please try to reproduce the issue using drm-tip (https://cgit.freedesktop.org/drm-tip) and kernel parameters drm.debug=0x1e log_buf_len=4M, and if the problem persists attach the full dmesg from boot. Frankly, I was skeptical about retesting it again... Fortunately: I DON'T HAVE THIS ISSUE ANYMORE ON LATEST DRM SOURCES (vanilla kernel)! :) I don't need to patch the i915_gem_execbuffer.c file anymore - it is working out of the box without any patch applied. I don't know which commit fixed this problem, but it doesn't matter for me, as it seems it is now back working properly. I am closing this bug. Thank you all involved! (In reply to Mariusz Białończyk from comment #9) > Frankly, I was skeptical about retesting it again... > > Fortunately: I DON'T HAVE THIS ISSUE ANYMORE ON LATEST DRM SOURCES (vanilla > kernel)! :) > I don't need to patch the i915_gem_execbuffer.c file anymore - it is working > out of the box without any patch applied. > > I don't know which commit fixed this problem, but it doesn't matter for me, > as it seems it is now back working properly. I am closing this bug. > > Thank you all involved! Thanks for the feedback. Closing this bug. |
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.