All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 56038] New: "r100_ring_test] *ERROR*" messages sometimes on boot with ati radeon 9000 AGP ( r200 driver, dri2 KMS enabled )
Date: Tue, 16 Oct 2012 17:12:21 +0000	[thread overview]
Message-ID: <bug-56038-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 56038
          Assignee: dri-devel@lists.freedesktop.org
           Summary: "r100_ring_test] *ERROR*" messages sometimes on boot
                    with ati radeon 9000 AGP ( r200 driver, dri2 KMS
                    enabled )
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: mister.freeman@laposte.net
          Hardware: x86 (IA32)
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Radeon
           Product: DRI

Created attachment 68625
  --> https://bugs.freedesktop.org/attachment.cgi?id=68625&action=edit
dmesg output

randomly ( it's very rare, 90% of the time I don't have this error message ) I
can see these error messages on boot :

[    1.516518] [drm] Loading R200 Microcode
[    1.517953] [drm] radeon: ring at 0x00000000E0001000
[    1.665941] [drm:r100_ring_test] *ERROR* radeon: ring test failed
(scratch(0x15E4)=0xCAFEDEAD)
[    1.665996] [drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22).
[    1.666043] radeon 0000:01:00.0: failed initializing CP (-22).
[    1.666084] radeon 0000:01:00.0: Disabling GPU acceleration
[    1.812455] [drm:r100_cp_fini] *ERROR* Wait for CP idle timeout, shutting
down CP.
[    1.812600] [drm] radeon: cp finalized
[    1.812629] [drm] radeon: cp finalized

but the boot process continues and I see no problem on KDE4.9.2 and 3d games,

this bug occurs since the update of ati-dri 9.0 and xorg packages 1.13 on my
archlinux 32 bits installation, before that I had never seen this kind of error
message

my system :

- archlinux 32 bits
- laptop pentium 4 2.4 ghz 1,2 Gb ram
- video card: ati radeon 9000 agp ( M9 rv250, r200 driver, dri2 enabled with
kms early start )
- SIS645DX chipset on motherboard

You can fin an attachment ( dmesg output ) with this message,

this bug may related to another ( startx problems ) :

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

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

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

             reply	other threads:[~2012-10-16 17:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 17:12 bugzilla-daemon [this message]
2012-10-17 15:19 ` [Bug 56038] "r100_ring_test] *ERROR*" messages sometimes on boot with ati radeon 9000 AGP ( r200 driver, dri2 KMS enabled ) bugzilla-daemon
2012-10-17 22:03 ` bugzilla-daemon
2012-10-17 22:10 ` bugzilla-daemon
2012-10-17 22:12 ` bugzilla-daemon
2012-10-27  9:26 ` bugzilla-daemon
2012-10-27  9: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=bug-56038-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.