<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED --- - xorg-server-1.13.0 lockups with intel driver >= 2.20.10"
href="https://bugs.freedesktop.org/show_bug.cgi?id=57118#c12">Comment # 12</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED --- - xorg-server-1.13.0 lockups with intel driver >= 2.20.10"
href="https://bugs.freedesktop.org/show_bug.cgi?id=57118">bug 57118</a>
from <span class="vcard"><a class="email" href="mailto:tsdh@gnu.org" title="Tassilo Horn <tsdh@gnu.org>"> <span class="fn">Tassilo Horn</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=57118#c11">comment #11</a>)
<span class="quote">> It is your compositing manager that is not rendering, and the process you
> should be xtracing and inspecting.</span >
I've done that now, and I'm going to attach two tarballs containing the
information from my latest two freezes. I was running with the intel drivers
from git, commit 37eb7343be1aeeb90a860096756603a577df1a77.
Every tarball contains
1. a backtrace of X (which is the same than the previous backtraces attached
to this issue)
2. a backtrace of gnome-shell (the compositing manager of GNOME)
3. a x11trace.txt.N file that contains the information from the command
DISPLAY=:0 x11trace -o ~/x11trace.txt -- /usr/bin/gnome-shell
from the invocation of gnome-shell until several minutes after the freeze.
(x11trace is the xtrace utility. My distro renamed it because glibc also has
an xtrace program.)
After the freezes occured, I ssh-ed into the machine and made several
backtraces of X and gnome-shell, i.e., I did one backtrace, waited a minute,
then did another one. I used a script that attaches GDB to the process, writes
a backtrace to a file, and then detaches again and lets the process continue.
Some observations:
- After a freeze, the backtraces of X and gnome-shell don't change anymore.
Diffing a backtrace with a backtrace I did a minute later doesn't show any
difference. Therefore, I've put only one into each of the tarballs.
- After a freeze, there's still data written to the x11trace.txt file.
- When I try to shutdown or reboot the machine after a freeze by issuing
"systemctl reboot|poweroff" while logged in via ssh, the X windows disappear,
but then the system is completely locked and won't poweroff/reboot.
For the time being, I've switched back to some pre-2.20.10 intel driver. But I
can easily switch back to the git version if you need additional information.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>