All of lore.kernel.org
 help / color / mirror / Atom feed
* [Bug 59672] New: Problems initializing Radeon driver: lockup during IB test
@ 2013-01-21 18:06 bugzilla-daemon
  2013-01-21 18:08 ` [Bug 59672] " bugzilla-daemon
                   ` (13 more replies)
  0 siblings, 14 replies; 15+ messages in thread
From: bugzilla-daemon @ 2013-01-21 18:06 UTC (permalink / raw)
  To: dri-devel


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

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

          Priority: medium
            Bug ID: 59672
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Problems initializing Radeon driver: lockup during IB
                    test
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: lucaskt@linux.vnet.ibm.com
          Hardware: PowerPC
            Status: NEW
           Version: XOrg 6.7.0
         Component: DRM/Radeon
           Product: DRI

Created attachment 73396
  --> https://bugs.freedesktop.org/attachment.cgi?id=73396&action=edit
modprobe radeon with drm.debug=1

Hi all,

I've been trying to get a evergreen adapter to work with the Radeon driver on a
ppc64 machine. And while attempting that, I'm running into what seems to be a
infinite loop while running the IB test on ring 3.
I'm using a 3.8.0-rc4 kernel from today.
Follows an excerpt from the logs, the entire modprobe log can be found
attached.

[  171.975487] [drm:evergreen_blit_init], evergreen blit allocated bo 00000600
vs 00000400 ps 00000500
[  171.975631] radeon 0001:01:00.0: WB enabled
[  171.975636] radeon 0001:01:00.0: fence driver on ring 0 use gpu addr
0x0000000020000c00 and cpu addr 0xc0000001d32b0c00
[  171.975642] radeon 0001:01:00.0: fence driver on ring 3 use gpu addr
0x0000000020000c0c and cpu addr 0xc0000001d32b0c0c
[  171.992732] [drm] ring test on 0 succeeded in 0 usecs
[  171.992799] [drm] ring test on 3 succeeded in 1 usecs
[  171.993112] [drm:evergreen_irq_set], evergreen_irq_set: sw int gfx
[  171.993154] [drm] ib test on ring 0 succeeded in 0 usecs
[  171.993197] [drm:evergreen_irq_set], r600_irq_set: sw int dma
[  172.419617] [drm:evergreen_irq_set], r600_irq_set: sw int dma
....
[  182.399612] [drm:evergreen_irq_set], r600_irq_set: sw int dma
[  182.409618] [drm:evergreen_irq_set], r600_irq_set: sw int dma
[  182.419604] radeon 0001:01:00.0: GPU lockup CP stall for more than 10000msec
[  182.419615] radeon 0001:01:00.0: GPU lockup (waiting for 0x0000000000000001
last fence id 0x0000000000000000)
[  182.419626] [drm:r600_dma_ib_test] *ERROR* radeon: fence wait failed (-35).
[  182.419634] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on
ring 3 (-35).

Do you guys have any idea what could be wrong, or what should be looked into? 

Thanks

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

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

end of thread, other threads:[~2013-02-05  2:38 UTC | newest]

Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-01-21 18:06 [Bug 59672] New: Problems initializing Radeon driver: lockup during IB test bugzilla-daemon
2013-01-21 18:08 ` [Bug 59672] " bugzilla-daemon
2013-01-21 18:20 ` bugzilla-daemon
2013-01-21 21:16 ` bugzilla-daemon
2013-01-22 10:26 ` bugzilla-daemon
2013-01-22 15:07 ` bugzilla-daemon
2013-01-22 15:12 ` bugzilla-daemon
2013-01-22 15:25 ` bugzilla-daemon
2013-01-22 15:35 ` bugzilla-daemon
2013-01-22 16:27 ` bugzilla-daemon
2013-01-24 16:00 ` bugzilla-daemon
2013-01-24 17:34 ` bugzilla-daemon
2013-01-28 18:38 ` bugzilla-daemon
2013-02-05  0:08 ` bugzilla-daemon
2013-02-05  2:38 ` bugzilla-daemon

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.