dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 86267] [drm:evergreen_resume] *ERROR* evergreen startup failed on resume
Date: Thu, 22 Jan 2015 19:23:16 +0000	[thread overview]
Message-ID: <bug-86267-502-mrm7vsOcc4@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-86267-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1675 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=86267

--- Comment #17 from Ismael <isma.casti@gmail.com> ---
(In reply to Michel Dänzer from comment #16)
> Created attachment 112528 [details] [review]
> Reinstate radeon_gart_restore for when the GART table is in VRAM
> 
> Do these two patches help?

Yes it helps. Suspend and resume work perfectly now.

Xan 22 21:20:20 boreal kernel: [drm] enabling PCIE gen 2 link speeds, disable
with radeon.pcie_gen2=0
Xan 22 21:20:20 boreal kernel: [drm] PCIE GART of 1024M enabled (table at
0x000000000025E000).
Xan 22 21:20:20 boreal kernel: radeon 0000:01:00.0: WB enabled
Xan 22 21:20:20 boreal kernel: radeon 0000:01:00.0: fence driver on ring 0 use
gpu addr 0x0000000040000c00 and cpu addr 0xffff88041693cc00
Xan 22 21:20:20 boreal kernel: radeon 0000:01:00.0: fence driver on ring 3 use
gpu addr 0x0000000040000c0c and cpu addr 0xffff88041693cc0c
Xan 22 21:20:20 boreal kernel: radeon 0000:01:00.0: fence driver on ring 5 use
gpu addr 0x000000000005c418 and cpu addr 0xffffc9000471c418
Xan 22 21:20:20 boreal kernel: [drm] ring test on 0 succeeded in 1 usecs
Xan 22 21:20:20 boreal kernel: [drm] ring test on 3 succeeded in 2 usecs
Xan 22 21:20:20 boreal kernel: usb 6-1.6.2: reset high-speed USB device number
5 using ehci-pci
Xan 22 21:20:20 boreal kernel: [drm] ring test on 5 succeeded in 1 usecs
Xan 22 21:20:20 boreal kernel: [drm] UVD initialized successfully.
Xan 22 21:20:20 boreal kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Xan 22 21:20:20 boreal kernel: [drm] ib test on ring 3 succeeded in 0 usecs

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2956 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

  parent reply	other threads:[~2015-01-22 19:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14  1:51 [Bug 86267] [drm:evergreen_resume] *ERROR* evergreen startup failed on resume bugzilla-daemon
2014-11-14  2:12 ` 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 [this message]
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-mrm7vsOcc4@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