From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 68059] with radeon.dpm=1, Xorg crashed a while after resume
Date: Wed, 21 Oct 2015 14:59:52 +0000 [thread overview]
Message-ID: <bug-68059-502-hslrKF88CD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-68059-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 580 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=68059
--- Comment #10 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Thomas DEBESSE from comment #6)
> Hi, also get a graphical hang with "[drm:radeon_pm_resume [radeon]] *ERROR*
> radeon: dpm resume failed" but without having to suspend or hibernate, to
> got this bug I just have to boot my system and wait less than 10min before
> it hangs.
You have very different hardware. It's not likely these two are related.
Please file your own bug.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1443 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:[~2015-10-21 14:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 13:22 [Bug 68059] New: with radeon.dpm=1, Xorg crashed a while after resume bugzilla-daemon
2013-08-13 22:11 ` [Bug 68059] " bugzilla-daemon
2014-01-27 22:52 ` bugzilla-daemon
2014-01-27 22:55 ` bugzilla-daemon
2014-01-27 22:56 ` bugzilla-daemon
2014-05-02 15:30 ` bugzilla-daemon
2015-10-21 0:18 ` bugzilla-daemon
2015-10-21 0:19 ` bugzilla-daemon
2015-10-21 0:20 ` bugzilla-daemon
2015-10-21 0:26 ` bugzilla-daemon
2015-10-21 14:59 ` bugzilla-daemon [this message]
2015-12-08 1:29 ` bugzilla-daemon
2018-04-10 10:52 ` bugzilla-daemon
2018-09-09 23:13 ` bugzilla-daemon
2018-09-10 14:42 ` bugzilla-daemon
2019-11-19 8:37 ` 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-68059-502-hslrKF88CD@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;
as well as URLs for NNTP newsgroup(s).