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: Wed, 02 Jul 2014 20:49:30 +0000 [thread overview]
Message-ID: <bug-77001-2300-OImn3mOgXx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-77001-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=77001
Grzegorz Kowal <custos.mentis@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |UNREPRODUCIBLE
--- Comment #6 from Grzegorz Kowal <custos.mentis@gmail.com> ---
With the recent kernels 3.14.8 to 3.14.10 and mesa, xf86-video-ati, and libdrm
from git I didn't get the resume failures anymore. My usual uptime is of
several days (reboot only after the minor kernel version update).
However, when the machine is booted after being shut down completely, sometimes
I am getting problems with the video initialization at the BIOS POST stage. But
it looks like a different problem, maybe BIOS settings or hardware issues, so I
am closing this bug report as resolved.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2014-07-02 20:49 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
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 [this message]
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-OImn3mOgXx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.