From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 72159] Zapping 1.15.0 RC3 hangs system on Radeon
Date: Wed, 04 Dec 2013 03:51:14 +0000 [thread overview]
Message-ID: <bug-72159-502-ueCC1HCOZi@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-72159-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 741 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=72159
--- Comment #11 from Michel Dänzer <michel@daenzer.net> ---
(In reply to comment #8)
> When I run "sudo Xorg -configure" I get:
Why -configure? You want to run the X server, not configure it. :)
What I'm looking for, but not seeing, is this line at the end of the X server
shutdown:
(EE) Server terminated successfully (0). Closing log file.
So it seems like the X server either dies uncleanly for you, or hangs during
shutdown. In the former case, there should be more information in the X
server's stderr output. The latter case will be hard to debug without ssh
access I'm afraid.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1600 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-12-04 3:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-72159-502@http.bugs.freedesktop.org/>
2013-12-02 7:11 ` [Bug 72159] Zapping 1.15.0 RC3 hangs system on Radeon bugzilla-daemon
2013-12-02 8:30 ` bugzilla-daemon
2013-12-02 8:31 ` bugzilla-daemon
2013-12-02 8:32 ` bugzilla-daemon
2013-12-02 10:17 ` bugzilla-daemon
2013-12-02 12:27 ` bugzilla-daemon
2013-12-03 4:31 ` bugzilla-daemon
2013-12-03 10:10 ` bugzilla-daemon
2013-12-03 15:10 ` bugzilla-daemon
2013-12-03 15:21 ` bugzilla-daemon
2013-12-04 3:51 ` bugzilla-daemon [this message]
2013-12-04 8:41 ` 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-72159-502-ueCC1HCOZi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.