All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90861] Panic on suspend from KDE with radeon
Date: Wed, 14 Jan 2015 01:34:13 +0000	[thread overview]
Message-ID: <bug-90861-2300-aRCzfra3SS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-90861-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=90861

--- Comment #8 from Michel Dänzer <michel@daenzer.net> ---
(In reply to Jon Arne Jørgensen from comment #7)
> I'm trying to bisect now, but I'm troubled by a gpu freeze bug in some of
> the commits that crashes Xorg before I'm able to suspend the computer.
> 
> It looks like a bug early in the v3.18 merge window, but I'm not sure if I
> should skip the crashing commits while doing the bisect?

I'd skip them for now.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-01-14  1:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 20:41 [Bug 90861] New: Panic on suspend from KDE with radeon bugzilla-daemon
2015-01-06 20:44 ` [Bug 90861] " bugzilla-daemon
2015-01-06 21:19 ` bugzilla-daemon
2015-01-06 21:26 ` bugzilla-daemon
2015-01-06 21:27 ` bugzilla-daemon
2015-01-06 21:30 ` bugzilla-daemon
2015-01-07  1:26 ` bugzilla-daemon
2015-01-13 20:14 ` bugzilla-daemon
2015-01-14  1:34 ` bugzilla-daemon [this message]
2015-01-22 20:48 ` bugzilla-daemon
2015-01-22 20:55 ` bugzilla-daemon
2015-01-23  3:24 ` bugzilla-daemon
2015-01-25 23:02 ` bugzilla-daemon
2015-02-23  7:26 ` bugzilla-daemon
2015-03-03 10:48 ` bugzilla-daemon
2015-03-03 10:56 ` bugzilla-daemon
2015-03-03 11:34 ` bugzilla-daemon
2017-04-26 13:35 ` 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-90861-2300-aRCzfra3SS@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.