dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99851] [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)
Date: Sat, 07 Oct 2017 15:06:52 +0000	[thread overview]
Message-ID: <bug-99851-502-c05OZ8ugzq@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99851-502@http.bugs.freedesktop.org/>


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

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

--- Comment #55 from erhard_f@mailbox.org ---
Joshuas comment #54 made me curious if it's a card specific issue. So I swapped
some cards around my boxes. I run both machines on Kernel 4.13.5.

on my PowerMac G5 11,2:
Radeon HD 5450: hits the bug
Radeon HD 6570: hits the bug
   Radeon X600: WORKS

on Athlon X4 845:
Radeon HD 5450: WORKS
Radeon HD 6570: WORKS
   Radeon X600: WORKS

The r380 Radeon X600 passes the ring test whereas the r600 cards fail:
# dmesg | grep -i drm
[    9.523830] [drm] radeon kernel modesetting enabled.
[    9.525292] [drm] initializing kernel modesetting (RV380 0x1002:0x5B62
0x1002:0x0F02 0x00).
[    9.595072] [drm] GPU not posted. posting now...
[    9.740409] [drm] Generation 2 PCI interface, using max accessible memory
[    9.740442] [drm] Detected VRAM RAM=128M, BAR=128M
[    9.740445] [drm] RAM width 64bits DDR
[    9.740785] [drm] radeon: 128M of VRAM memory ready
[    9.740789] [drm] radeon: 512M of GTT memory ready.
[    9.740810] [drm] GART: num cpu pages 131072, num gpu pages 131072
[    9.742591] [drm] radeon: 1 quad pipes, 1 Z pipes initialized
[    9.763583] [drm] PCIE GART of 512M enabled (table at 0x0000000088040000).
[    9.763705] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    9.763708] [drm] Driver supports precise vblank timestamp query.
[    9.763818] [drm] radeon: irq initialized.
[    9.763825] [drm] Loading R300 Microcode
[   10.233486] [drm] radeon: ring at 0x0000000068001000
[   10.233545] [drm] ring test succeeded in 0 usecs
[   10.234665] [drm] ib test succeeded in 0 usecs
[   10.235279] [drm] Radeon Display Connectors
[   10.235284] [drm] Connector 0:
[   10.235287] [drm]   DVI-I-1
[   10.235289] [drm]   HPD1
[   10.235293] [drm]   DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
[   10.235296] [drm]   Encoders:
[   10.235299] [drm]     CRT1: INTERNAL_DAC1
[   10.235302] [drm]     DFP1: INTERNAL_TMDS1
[   10.308511] [drm] fb mappable at 0x880C0000
[   10.308521] [drm] vram apper at 0x88000000
[   10.308525] [drm] size 8294400
[   10.308527] [drm] fb depth is 24
[   10.308530] [drm]    pitch is 7680
[   10.372575] radeon 0001:06:00.0: fb0: radeondrmfb frame buffer device
[   10.372649] [drm] Initialized radeon 2.50.0 20080528 for 0001:06:00.0 on
minor 0

So I conclued this issue is produced by some interaction of the r600 DRM with
PowerPC-specific or Mac-PCIe-specific things?

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

[-- Attachment #1.2: Type: text/html, Size: 3462 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-10-07 15:06 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-99851-502@http.bugs.freedesktop.org/>
2017-02-20  4:00 ` [Bug 99851] [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) bugzilla-daemon
2017-02-20 22:13 ` bugzilla-daemon
2017-02-20 22:17 ` bugzilla-daemon
2017-02-20 22:19 ` bugzilla-daemon
2017-02-20 22:47 ` bugzilla-daemon
2017-02-21 22:01 ` bugzilla-daemon
2017-02-21 23:09 ` bugzilla-daemon
2017-02-22 21:44 ` bugzilla-daemon
2017-02-22 22:25 ` bugzilla-daemon
2017-02-22 22:41 ` bugzilla-daemon
2017-02-27 15:20 ` bugzilla-daemon
2017-02-27 17:32 ` bugzilla-daemon
2017-02-27 18:32 ` bugzilla-daemon
2017-03-02  8:03 ` bugzilla-daemon
2017-03-24 10:18 ` bugzilla-daemon
2017-03-24 16:48 ` bugzilla-daemon
2017-03-24 17:03 ` bugzilla-daemon
2017-03-24 17:54 ` bugzilla-daemon
2017-05-18 13:48 ` bugzilla-daemon
2017-05-18 21:00 ` bugzilla-daemon
2017-05-18 21:01 ` bugzilla-daemon
2017-05-18 21:09 ` bugzilla-daemon
2017-05-19  1:35 ` bugzilla-daemon
2017-05-19  1:36 ` bugzilla-daemon
2017-05-19 18:14 ` bugzilla-daemon
2017-05-19 18:15 ` bugzilla-daemon
2017-05-24 10:59 ` bugzilla-daemon
2017-05-25 18:42 ` bugzilla-daemon
2017-05-27  8:22 ` bugzilla-daemon
2017-05-27  8:24 ` bugzilla-daemon
2017-05-27  8:24 ` bugzilla-daemon
2017-05-29  7:18 ` bugzilla-daemon
2017-05-29  9:42 ` bugzilla-daemon
2017-06-02 22:49 ` bugzilla-daemon
2017-06-02 22:52 ` bugzilla-daemon
2017-06-02 22:53 ` bugzilla-daemon
2017-06-02 22:53 ` bugzilla-daemon
2017-06-05  2:31 ` bugzilla-daemon
2017-06-13 13:25 ` bugzilla-daemon
2017-07-17 13:20 ` bugzilla-daemon
2017-08-10 22:37 ` bugzilla-daemon
2017-09-15 19:36 ` bugzilla-daemon
2017-09-15 20:33 ` bugzilla-daemon
2017-09-15 21:44 ` bugzilla-daemon
2017-10-07 15:06 ` bugzilla-daemon [this message]
2017-10-11  7:45 ` bugzilla-daemon
2017-12-06 22:00 ` bugzilla-daemon
2017-12-08  7:00 ` bugzilla-daemon
2018-06-21 22:25 ` bugzilla-daemon
2018-08-25 22:59 ` bugzilla-daemon
2019-11-19  9:24 ` 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-99851-502-c05OZ8ugzq@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;
as well as URLs for NNTP newsgroup(s).