From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 67800] New: Computer freezes after idle for several hours with dpms off (trinity)
Date: Mon, 05 Aug 2013 19:47:20 +0000 [thread overview]
Message-ID: <bug-67800-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1785 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=67800
Priority: medium
Bug ID: 67800
Assignee: dri-devel@lists.freedesktop.org
Summary: Computer freezes after idle for several hours with
dpms off (trinity)
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: laszlo.kertesz@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: DRI CVS
Component: DRM/Radeon
Product: DRI
I use Debian 64 bit and now i have the 3.11rc4 kernel installed, with mesa from
git, xf86-video-ati from git, libdrm from git, all firmwares put in
/lib/firmware.
The hardware is A8-5500 desktop APU with its built in 7560D card.
The system works very well, opengl, vdpau is functional.
I have xscreensaver set to turn off the monitor after 4 minutes, which it does.
I can wake up after a few minutes by moving the mouse or pressing a key.
All is going well until i leave the computer for a longer time (it varies,
usually a few hours) - the computer becomes totally unresponsive, doesnt react
to keyboard/mouse and network wise is totally dead. The fans are on normally,
no disk activity. I have to reset it from the reset button.
Nothing out of the ordinary in any logs, they just stop logging, presumably
when the computer freezes.
Now if i disable dpms and leave only blanking, this doesnt happen (This is why
i think it has to do with the kernel driver), but this mean the monitor is on
all the tme which isnt good since the computer runs 24/7.
PS. It didnt happen previously with the fglrx driver in any circumstances.
Any ideas why this might happen?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3090 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 reply other threads:[~2013-08-05 19:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 19:47 bugzilla-daemon [this message]
2013-08-06 13:44 ` [Bug 67800] Computer freezes after idle for several hours with dpms off (trinity) bugzilla-daemon
2013-08-06 14:12 ` bugzilla-daemon
2013-08-07 6:44 ` bugzilla-daemon
2013-08-07 6:45 ` [Bug 67800] Computer freezes after idle for several hours (trinity) bugzilla-daemon
2013-08-07 22:41 ` bugzilla-daemon
2013-08-08 7:21 ` bugzilla-daemon
2013-08-09 9:43 ` bugzilla-daemon
2013-08-10 3:25 ` bugzilla-daemon
2013-08-13 6:42 ` bugzilla-daemon
2013-08-23 5:36 ` bugzilla-daemon
2013-08-27 6:33 ` bugzilla-daemon
2013-08-31 19:09 ` bugzilla-daemon
2013-08-31 19:17 ` bugzilla-daemon
2013-09-08 12:35 ` [Bug 67800] Computer freezes " bugzilla-daemon
2013-09-09 1:29 ` [Bug 67800] Computer freezes after " bugzilla-daemon
2013-09-09 2:42 ` bugzilla-daemon
2013-09-28 23:25 ` bugzilla-daemon
2013-10-12 1:34 ` 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-67800-502@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).