All of lore.kernel.org
 help / color / mirror / Atom feed
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 19:03:34 +0000	[thread overview]
Message-ID: <bug-113861-2300-ZwBfc5rCiz@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 #9 from centuryplague@yandex.com ---
(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?

Went a bit out my way to test this faster. I can now confirm reverting this
commit on a 4.4.4-based kernel (arch linux-grsec 4.4.4.201603032158-1-grsec)
allows startx to start again on my (non-standard) system. I don't know about
the other guy.

Thanks I will report on the arch bug. Will this be in 4.4.5?

-- 
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

  parent reply	other threads:[~2016-03-08 19:03 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
2016-03-08 19:03 ` bugzilla-daemon [this message]
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-ZwBfc5rCiz@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 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.