Bug 108459

Summary: The X server crashes on present flip failure
Product: xorg Reporter: John <john.ettedgui>
Component: Driver/AMDgpuAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
xorg log none

Description John 2018-10-16 17:48:43 UTC 
Created attachment 142044 [details]
xorg log

Hello,

This may be similar to Bug 97025, but the issue is much newer to me so not sure.

Basically for maybe the past month or so, sometimes either while gaming or watching a video, the X server will crash, auto restart and be fine again. I assume it's related to the DDX, but truly I do not know.

Since the crash is fairly rare, it's not that easy for me to do a proper bisection, as I may need to run something for a few days to get the issue.

I am on Linux 4.18.13 but I've had that issue on at least 4.18.12, maybe also previous point releases not sure anymore.

Xorg is 1.20.1, xf86-video-amdgpu is 18.1, and looking at the date this was released I think it coincides with the beginning of my issues, but not sure.

I'm on Arch Linux.

Thank you!
Comment 1 Michel Dänzer 2018-10-17 07:21:09 UTC 
Please make sure that debugging symbols are available for /usr/lib/xorg/modules/drivers/amdgpu_drv.so and /usr/lib/Xorg, preferably also /usr/lib/libc.so.6, and either get a backtrace with gdb (see https://www.x.org/wiki/Development/Documentation/ServerDebugging/), or make sure Xorg is built with --enable-libunwind and attach a new log file from a crash.
Comment 2 John 2018-10-17 10:50:15 UTC 
Hello Michael,

I do not find an unwind option in the Meson build output for Xorg, is it supported with Meson or do I need to do that the old way?



Thank you!
Comment 3 Michel Dänzer 2018-10-17 14:17:32 UTC 
Doesn't seem supported yet in the meson build.
Comment 4 John 2018-11-06 10:26:35 UTC 
I've changed GPU a few weeks ago, to a 580, and I haven't got the issue since.

So either the issue is related to the path for the specific GPU, or it has been fixed since. In the first case, I cannot debug this anymore, and in the second one there is no need.

Hence I'm closing this.

Thank you!
Comment 5 Michel Dänzer 2018-11-06 11:16:19 UTC 
Looks like bug 108600, which has more information now.

*** This bug has been marked as a duplicate of bug 108600 ***

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.