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 [details]
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.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel