From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 113861] [radeon] Xorg fatal freeze upon startx
Date: Tue, 08 Mar 2016 06:21:40 +0000 [thread overview]
Message-ID: <bug-113861-2300-WgikBZkYsn@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-113861-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=113861
--- Comment #8 from centuryplague@yandex.com ---
(In reply to Michel Dänzer from comment #6)
> Does radeon.runpm=0 on the kernel command line avoid the problem?
Yes, I tried moments ago and radeon.runpm=0 allows x to start! Had no tried
that.
(In reply to Alex Deucher from comment #7)
> Probably the same issue as reported here:
> https://lists.freedesktop.org/archives/dri-devel/2016-March/102379.html
> Does reverting dbb17a21c131eca94eb31136eee9a7fe5aff00d9 fix it?
That sounds exactly the same. I can't compile tonight and may not get it to
work for a couple days (non standard setup). I'll mention to the other guy.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-03-08 6:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 6:53 [Bug 113861] New: [radeon] Xorg fatal freeze upon startx bugzilla-daemon
2016-03-07 6:58 ` [Bug 113861] " bugzilla-daemon
2016-03-07 7:16 ` bugzilla-daemon
2016-03-07 16:30 ` bugzilla-daemon
2016-03-07 17:13 ` bugzilla-daemon
2016-03-07 17:16 ` bugzilla-daemon
2016-03-08 3:56 ` bugzilla-daemon
2016-03-08 5:45 ` bugzilla-daemon
2016-03-08 6:21 ` bugzilla-daemon [this message]
2016-03-08 19:03 ` bugzilla-daemon
2016-03-08 19:04 ` bugzilla-daemon
2016-03-08 19:08 ` bugzilla-daemon
2016-03-13 17:34 ` bugzilla-daemon
2016-03-20 18:44 ` 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-113861-2300-WgikBZkYsn@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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;
as well as URLs for NNTP newsgroup(s).