Comment=
# 5
on bug 98874<=
/a>
from Matthias Nagel
I could obtain the requested dump :) I hope it helps.
Some words are in order: After I knew that the guilty process was /usr/bin/X
and a knew its PID I also tried to get a "gcore <PID>" or t=
o attach gdb to it.
Both failed. Otherwise I also had provided you a backtrace of all threads a=
s I
compiled all packages with "-g -ggdb". (I am a gentoo user.) The =
process is
stuck in state "D". "kill -KILL <PID>" did not wo=
rk either.
A second note (I know it is selfish, because you do a great job, and
off-topic.). I bought this new graphics card, because I was being pestered =
by
with an Nvidia graphics card, a buggy nouveau driver and a lot of crashes d=
ue
to an unstable OpenGL. (I know it Nvidia is to blame for the situation not =
the
maintainers of nouveau.) After 18 month of hope that the situation might
improve, I finally decided to spend money for a new graphics card by AMD. I
thought I would eventually get working PC. Now, it seems I stepped "ou=
t of the
frying pan into the fire". Just now I have still the chance to withdra=
w from my
investment and give the AMD graphics card back to the dealer. Should I do t=
hat?
Or may I hope for a fix soon?