Attachment 68301 Details for Bug 55745 – Kernel messages when radeon driver crashes

Kernel messages when radeon driver crashes

radeon-crash.dmesg.txt (text/plain), 3.36 KB, created by Ingvar Hagelund on 2012-10-08 23:32:24 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Ingvar Hagelund

Created: 2012-10-08 23:32:24 UTC

Size: 3.36 KB

patch

obsolete

>[  566.388968] radeon 0000:00:10.0: GPU lockup CP stall for more than 10000msec
>[  566.389071] radeon 0000:00:10.0: GPU lockup (waiting for 0x00000000000009a4 last fence id 0x000000000000099e)
>[  566.543324] radeon: wait for empty RBBM fifo failed ! Bad things might happen.
>[  566.694890] Failed to wait GUI idle while programming pipes. Bad things might happen.
>[  566.698299] radeon 0000:00:10.0: Saved 187 dwords of commands on ring 0.
>[  566.698394] radeon 0000:00:10.0: (r100_asic_reset:2693) RBBM_STATUS=0x8002C139
>[  567.187195] radeon 0000:00:10.0: (r100_asic_reset:2714) RBBM_STATUS=0x8002C139
>[  567.671587] radeon 0000:00:10.0: (r100_asic_reset:2722) RBBM_STATUS=0x8002C139
>[  567.671716] radeon 0000:00:10.0: GPU reset succeed
>[  567.671730] radeon 0000:00:10.0: GPU reset succeeded, trying to resume
>[  567.671756] radeon 0000:00:10.0: (r100_asic_reset:2693) RBBM_STATUS=0x8002C139
>[  568.160058] radeon 0000:00:10.0: (r100_asic_reset:2714) RBBM_STATUS=0x8002C139
>[  568.644393] radeon 0000:00:10.0: (r100_asic_reset:2722) RBBM_STATUS=0x8002C139
>[  568.644541] radeon 0000:00:10.0: GPU reset succeed
>[  568.645501] [sched_delayed] sched: RT throttling activated
>[  568.653674] radeon 0000:00:10.0: WB disabled
>[  568.653803] radeon 0000:00:10.0: fence driver on ring 0 use gpu addr 0x0000000000000000 and cpu addr 0xda535000
>[  568.801504] radeon: wait for empty RBBM fifo failed ! Bad things might happen.
>[  568.947903] Failed to wait GUI idle while programming pipes. Bad things might happen.
>[  568.947996] [drm] radeon: ring at 0x0000000000001000
>[  568.949956] [drm] ring test succeeded in 0 usecs
>[  579.532551] radeon 0000:00:10.0: GPU lockup CP stall for more than 10000msec
>[  579.532643] radeon 0000:00:10.0: GPU lockup (waiting for 0x00000000000009a5 last fence id 0x000000000000099e)
>[  579.532667] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35).
>[  579.532681] radeon 0000:00:10.0: ib ring test failed (-35).
>[  579.679307] radeon: wait for empty RBBM fifo failed ! Bad things might happen.
>[  579.826851] Failed to wait GUI idle while programming pipes. Bad things might happen.
>[  579.831451] radeon 0000:00:10.0: (r100_asic_reset:2693) RBBM_STATUS=0x8002C136
>[  580.319881] radeon 0000:00:10.0: (r100_asic_reset:2714) RBBM_STATUS=0x8002C136
>[  580.804314] radeon 0000:00:10.0: (r100_asic_reset:2722) RBBM_STATUS=0x8002C136
>[  580.804440] radeon 0000:00:10.0: GPU reset succeed
>[  580.804487] radeon 0000:00:10.0: GPU reset succeeded, trying to resume
>[  580.804590] radeon 0000:00:10.0: (r100_asic_reset:2693) RBBM_STATUS=0x8002C136
>[  581.292910] radeon 0000:00:10.0: (r100_asic_reset:2714) RBBM_STATUS=0x8002C136
>[  581.777278] radeon 0000:00:10.0: (r100_asic_reset:2722) RBBM_STATUS=0x8002C136
>[  581.777395] radeon 0000:00:10.0: GPU reset succeed
>[  581.788057] radeon 0000:00:10.0: WB disabled
>[  581.788174] radeon 0000:00:10.0: fence driver on ring 0 use gpu addr 0x0000000000000000 and cpu addr 0xda537000
>[  581.935807] radeon: wait for empty RBBM fifo failed ! Bad things might happen.
>[  582.082346] Failed to wait GUI idle while programming pipes. Bad things might happen.
>[  582.082441] [drm] radeon: ring at 0x0000000000001000
>[  582.233889] [drm:r100_ring_test] *ERROR* radeon: ring test failed (scratch(0x15F0)=0xCDCDCDCD)
>[  582.233954] [drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22).
>[  582.233973] radeon 0000:00:10.0: failed initializing CP (-22).

Actions: View

Attachments on bug 55745: 68230 | 68231 | 68232 | 68301 | 68302 | 68355 | 85375 | 85376 | 85664 | 85713

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.