All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Kitching <skitching@vonos.net>
To: dri-devel@lists.freedesktop.org
Subject: radeon error on resume: "cp failed to get scratch reg" - anyone interested?
Date: Mon, 17 Sep 2012 15:06:08 +0200	[thread overview]
Message-ID: <50572040.2020107@vonos.net> (raw)

Hi,

I've noticed that on resume from suspend, dmesg reports:

[21895.997536] [drm] radeon: 1 quad pipes, 2 z pipes initialized.
[21896.012072] [drm] PCIE GART of 512M enabled (table at 
0x0000000000040000).
[21896.012082] radeon 0000:01:00.0: WB enabled
[21896.012085] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 
0x0000000010000000 and cpu addr 0xffccb000
[21896.012138] [drm] radeon: ring at 0x0000000010001000
[21896.012157] [drm:r100_ring_test] *ERROR* radeon: cp failed to get 
scratch reg (-22).
[21896.012158] [drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22).
[21896.012160] radeon 0000:01:00.0: failed initializing CP (-22).

Graphics still seems to work fine though.

Is this info of interest to anyone? I'm happy to do additional testing 
if that is useful.

System: Radeon Mobility X1600 RV530 (about 5 year old laptop), kernel 
3.6.0-rc5+ 32-bit

Cheers,
Simon

             reply	other threads:[~2012-09-17 13:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-17 13:06 Simon Kitching [this message]
2012-09-19  9:12 ` radeon error on resume: "cp failed to get scratch reg" - anyone interested? Michel Dänzer
2012-09-20  6:54   ` Simon Kitching
2012-09-20  8:09     ` Re: radeon error on resume: "cp failed to get scratch reg" - anyoneinterested? deathsimple
2012-09-20  9:06     ` radeon error on resume: "cp failed to get scratch reg" - anyone interested? Michel Dänzer

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=50572040.2020107@vonos.net \
    --to=skitching@vonos.net \
    --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.