From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 77001] Radeon R9 270X GPU lockup and resume failure after all night inactivity [drm,radeonsi]
Date: Thu, 29 May 2014 13:37:36 +0000 [thread overview]
Message-ID: <bug-77001-2300-jUiCD0KtZz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-77001-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=77001
--- Comment #2 from Grzegorz Kowal <custos.mentis@gmail.com> ---
This type of hang happened for the first time here. I was logged in the KDE
with KWin compositing based on OpenGL 3.1. I don't use any screensaver.
I switched compositing type to OpenGL 2.0 now, and recompiled the kernel with
suspend to RAM and standby turned off.
My software stack is:
Gentoo default/linux/amd64/13.0/desktop/kde
xorg-server-1.15.0
mesa git -> aa78c4586d42856dcc86b143c2e72c05a1422016
libdrm git -> 8fc62ca8ac010659023bb63c4759eb683de4f9af
glamor git -> a4fbc7732a1e56de385f50b778aafbdd186e015c
xf86-video-ati git -> 851b2cf8714618843725f6d067915375485ade9d
I'll try to do some tests to see if the problem can be reproduced with this
configuration.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-05-29 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 12:50 [Bug 77001] New: Radeon R9 270X GPU lockup and resume failure after all night inactivity bugzilla-daemon
2014-05-28 15:24 ` [Bug 77001] Radeon R9 270X GPU lockup and resume failure after all night inactivity [drm,radeonsi] bugzilla-daemon
2014-05-28 16:17 ` bugzilla-daemon
2014-05-29 13:37 ` bugzilla-daemon [this message]
2014-05-30 12:39 ` bugzilla-daemon
2014-06-03 11:24 ` bugzilla-daemon
2014-06-03 11:25 ` bugzilla-daemon
2014-07-02 20:49 ` 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-77001-2300-jUiCD0KtZz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox