All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 46231] Radeon NI: evergreen_resume fails after GPU lockup
Date: Wed, 19 Sep 2012 08:49:01 +0000 (UTC)	[thread overview]
Message-ID: <20120919084901.3594511FA28@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-46231-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=46231


MikeQ <d511215@rppkn.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |d511215@rppkn.com




--- Comment #1 from MikeQ <d511215@rppkn.com>  2012-09-19 08:49:00 ---
Same problem on a Radeon HD6320M running 3.5.4 kernel. Didn't have this problem
with 3.4 kernels. Happens just after boot when starting X, around 40-50% of the
time.

[   63.387751] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[   63.387861] radeon 0000:00:01.0: WB enabled
[   63.387867] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr
0x0000000018000c00 and cpu addr 0xffff8800d9ad6c00
[   63.566880] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed
(scratch(0x8500)=0xCAFEDEAD)
[   63.566886] [drm:evergreen_resume] *ERROR* evergreen startup failed on
resume

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  reply	other threads:[~2012-09-19  8:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-20  0:55 [Bug 46231] New: Radeon NI: evergreen_resume fails after GPU lockup bugzilla-daemon
2012-09-19  8:49 ` bugzilla-daemon [this message]
2012-09-19  9:35 ` [Bug 46231] " bugzilla-daemon
2012-09-21 22:46 ` bugzilla-daemon
2013-11-19 23:30 ` 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=20120919084901.3594511FA28@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.