From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 67002] evergreen: after resume from suspend-to-ram operation is really slow with the latest DPM changes + gpu lockup
Date: Fri, 19 Jul 2013 15:37:50 +0000 [thread overview]
Message-ID: <bug-67002-502-yQMtitYafQ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-67002-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 346 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #3 from jackdachef@gmail.com ---
at least according to the kernel logs the atombios error seems to have been
introduced, is new with the new DPM code (running the new firmware both with
old and new driver)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1221 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-07-19 15:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 15:10 [Bug 67002] New: evergreen: after resume from suspend-to-ram operation is really slow with the latest DPM changes bugzilla-daemon
2013-07-17 15:10 ` [Bug 67002] evergreen: after resume from suspend-to-ram operation is really slow with the latest DPM changes + gpu lockup bugzilla-daemon
2013-07-19 12:54 ` bugzilla-daemon
2013-07-19 15:35 ` bugzilla-daemon
2013-07-19 15:37 ` bugzilla-daemon [this message]
2013-07-19 16:51 ` bugzilla-daemon
2013-07-19 17:26 ` bugzilla-daemon
2013-07-19 17:44 ` bugzilla-daemon
2013-07-20 15:42 ` bugzilla-daemon
2013-07-24 10:07 ` bugzilla-daemon
2013-07-24 14:45 ` bugzilla-daemon
2013-07-24 20:05 ` bugzilla-daemon
2013-07-24 21:30 ` bugzilla-daemon
2013-07-27 21:24 ` bugzilla-daemon
2013-07-27 21:37 ` bugzilla-daemon
2019-11-19 8:36 ` 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-67002-502-yQMtitYafQ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox