From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 63391] Radeon RS880 doesn't resume from suspend with radeon dpm enabled
Date: Tue, 22 Oct 2013 10:56:59 +0000 [thread overview]
Message-ID: <bug-63391-2300-Y7Wd1QKxrn@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-63391-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=63391
--- Comment #6 from Tasev Nikola <tasev.stefanoska@skynet.be> ---
(In reply to Alex Deucher from comment #3)
> (In reply to Tasev Nikola from comment #0)
> > It works also fine with kernel 3.11 with dpm enabled.
>
> Can you bisect?
Hi,
I remember now that i was using 3-4 days 3.12-rc1 before i have reported
this bug https://bugs.freedesktop.org/show_bug.cgi?id=70035 (gpu loockup)
and the kernel was working fine.
I just reinstalled 3.12-rc1 now and i will
report later (maybe tomorow) if it works with dpm.
I also tested 3.12-rc6 this morning but with no success.
I'm reading about bisect the kernel now.
Is this a good tutorial for starting ? :
http://www.project-insanity.org/blog/2013/02/13/how-i-found-a-kernel-regression-using-git-bisect/
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-10-22 10:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 7:42 [Bug 63391] New: Radeon RS880 doesn't resume from suspend with radeon dpm enabled bugzilla-daemon
2013-10-21 7:45 ` [Bug 63391] " bugzilla-daemon
2013-10-21 19:09 ` bugzilla-daemon
2013-10-22 5:00 ` bugzilla-daemon
2013-10-22 10:40 ` bugzilla-daemon
2013-10-22 10:42 ` bugzilla-daemon
2013-10-22 10:56 ` bugzilla-daemon [this message]
2013-10-22 17:29 ` bugzilla-daemon
2013-10-24 6:47 ` bugzilla-daemon
2013-10-27 18:53 ` bugzilla-daemon
2013-11-05 7:47 ` bugzilla-daemon
2013-11-05 7:48 ` 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-63391-2300-Y7Wd1QKxrn@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.