From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 86267] [drm:evergreen_resume] *ERROR* evergreen startup failed on resume
Date: Fri, 14 Nov 2014 01:51:57 +0000 [thread overview]
Message-ID: <bug-86267-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1523 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=86267
Bug ID: 86267
Summary: [drm:evergreen_resume] *ERROR* evergreen startup
failed on resume
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: jasa.bartelj@gmail.com
Created attachment 109443
--> https://bugs.freedesktop.org/attachment.cgi?id=109443&action=edit
corrupt display
After resuming from suspend on kernel 3.18-rc4 the graphics card locks
:
[55325.256071] [drm] enabling PCIE gen 2 link speeds, disable with
radeon.pcie_gen2=0
[55325.261268] [drm] PCIE GART of 1024M enabled (table at 0x000000000025E000).
[55325.261400] radeon 0000:03:00.0: WB enabled
[55325.261402] radeon 0000:03:00.0: fence driver on ring 0 use gpu addr
0x0000000040000c00 and cpu addr 0xffff8800d7caac00
[55325.261404] radeon 0000:03:00.0: fence driver on ring 3 use gpu addr
0x0000000040000c0c and cpu addr 0xffff8800d7caac0c
[55325.262271] radeon 0000:03:00.0: fence driver on ring 5 use gpu addr
0x000000000005c418 and cpu addr 0xffffc9000581c418
[55325.437301] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed
(scratch(0x8504)=0xCAFEDEAD)
[55325.437302] [drm:evergreen_resume] *ERROR* evergreen startup failed on
resume
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2871 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:[~2014-11-14 1:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 1:51 bugzilla-daemon [this message]
2014-11-14 2:12 ` [Bug 86267] [drm:evergreen_resume] *ERROR* evergreen startup failed on resume bugzilla-daemon
2014-11-14 2:17 ` bugzilla-daemon
2014-11-17 17:40 ` bugzilla-daemon
2014-11-18 20:46 ` bugzilla-daemon
2014-11-19 6:40 ` bugzilla-daemon
2014-11-23 13:39 ` bugzilla-daemon
2014-12-01 16:57 ` bugzilla-daemon
2014-12-02 1:48 ` bugzilla-daemon
2014-12-02 1:52 ` bugzilla-daemon
2014-12-02 6:57 ` bugzilla-daemon
2014-12-02 11:18 ` bugzilla-daemon
2014-12-08 6:32 ` bugzilla-daemon
2014-12-08 14:55 ` bugzilla-daemon
2014-12-26 10:01 ` bugzilla-daemon
2014-12-27 11:43 ` bugzilla-daemon
2015-01-20 10:11 ` bugzilla-daemon
2015-01-20 10:12 ` bugzilla-daemon
2015-01-22 19:23 ` bugzilla-daemon
2015-01-23 3:31 ` 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-86267-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 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.