From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 68178] evergreen: hard lockup on suspend and resume with dpm
Date: Tue, 24 Sep 2013 19:40:35 +0000 [thread overview]
Message-ID: <bug-68178-502-me9SurflsO@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-68178-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1046 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=68178
--- Comment #6 from nine@detonation.org ---
It seems like I have two independent problems which may explain the confusing
results I got:
* with DPM enabled I get hard locks on suspend and sometimes on resume. After
suspend I have to turn off power manually but it seems like it successfully
writes the suspend image to disk. On resume it sometimes locks with disabled
output, sometimes it works.
* Regardless of DPM enabled or not I get X server crashes within minutes after
a suspend/resume cycle. This happens with kernel 3.11.1 with current firmware.
When I downgrade my kernel-firmware package to 20130114git-1.2.1, this problem
vanishes. But the firmware may be the original cause. With the old firmware I
for example do not have direct rendering or acceleration.
At least I found a logfile giving more information about the X server crash.
Attaching.
Is there anything else I can do to debug these problems?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1807 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-09-24 19:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 9:56 [Bug 68178] New: evergreen: hard lockup on suspend and resume with current firmware bugzilla-daemon
2013-08-16 12:46 ` [Bug 68178] evergreen: hard lockup on suspend and resume with dpm bugzilla-daemon
2013-08-16 13:56 ` bugzilla-daemon
2013-08-16 13:57 ` bugzilla-daemon
2013-08-16 14:01 ` bugzilla-daemon
2013-08-16 15:03 ` bugzilla-daemon
2013-09-24 19:40 ` bugzilla-daemon [this message]
2013-09-24 19:41 ` bugzilla-daemon
2013-09-24 19:43 ` bugzilla-daemon
2013-09-24 20:14 ` bugzilla-daemon
2013-09-24 21:10 ` bugzilla-daemon
2013-10-31 8:41 ` bugzilla-daemon
2013-10-31 13:11 ` [Bug 68178] xserver crashes with uvd bugzilla-daemon
2013-12-08 16:58 ` 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-68178-502-me9SurflsO@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).