From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98874] Desktop suddenly freezes, login via ssh possible, no error messages, unable to power off
Date: Mon, 28 Nov 2016 19:34:12 +0000 [thread overview]
Message-ID: <bug-98874-502-YdtxYT3xQP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98874-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1368 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98874
--- Comment #5 from Matthias Nagel <matthias.h.nagel@gmail.com> ---
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 to attach gdb to it.
Both failed. Otherwise I also had provided you a backtrace of all threads as I
compiled all packages with "-g -ggdb". (I am a gentoo user.) The process is
stuck in state "D". "kill -KILL <PID>" did not work 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 due
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 "out of the
frying pan into the fire". Just now I have still the chance to withdraw from my
investment and give the AMD graphics card back to the dealer. Should I do that?
Or may I hope for a fix soon?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2298 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-11-28 19:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-98874-502@http.bugs.freedesktop.org/>
2016-11-28 7:22 ` [Bug 98874] Desktop suddenly freezes, login via ssh possible, no error messages, unable to power off bugzilla-daemon
2016-11-28 8:36 ` bugzilla-daemon
2016-11-28 19:20 ` bugzilla-daemon
2016-11-28 19:22 ` bugzilla-daemon
2016-11-28 19:34 ` bugzilla-daemon [this message]
2016-11-29 2:08 ` bugzilla-daemon
2016-11-29 7:13 ` bugzilla-daemon
2016-11-29 7:14 ` bugzilla-daemon
2016-12-01 20:38 ` bugzilla-daemon
2016-12-04 12:12 ` bugzilla-daemon
2016-12-04 12:14 ` bugzilla-daemon
2016-12-04 12:17 ` bugzilla-daemon
2017-01-03 16:01 ` bugzilla-daemon
2017-05-25 9:16 ` [Bug 98874] amdgpu: [drm:amdgpu_job_timedout] *ERROR* ring gfx timeout, [drm] IP block:5 is hang bugzilla-daemon
2017-08-20 22:55 ` bugzilla-daemon
2019-09-25 17:55 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-98874-502-YdtxYT3xQP@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox