Attachment 120405 Details for Bug 93288 – syslog (Linux 4.3, mesa git, radeon hawaii r9 390X)

syslog (Linux 4.3, mesa git, radeon hawaii r9 390X)

20151208.syslog-abstract.txt (text/plain), 5.37 KB, created by Thomas DEBESSE on 2015-12-08 01:23:14 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Thomas DEBESSE

Created: 2015-12-08 01:23:14 UTC

Size: 5.37 KB

patch

obsolete

>Dec  8 01:32:07 gollum kernel: [   82.262780] radeon 0000:01:00.0: ring 3 stalled for more than 10368msec
>Dec  8 01:32:07 gollum kernel: [   82.262790] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000000155c last fence id 0x0000000000001655 on ring 3)
>Dec  8 01:32:08 gollum kernel: [   82.366721] radeon 0000:01:00.0: ring 4 stalled for more than 10472msec
>Dec  8 01:32:08 gollum kernel: [   82.366729] radeon 0000:01:00.0: ring 0 stalled for more than 10472msec
>Dec  8 01:32:08 gollum kernel: [   82.366737] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000000089a last fence id 0x000000000000089b on ring 4)
>Dec  8 01:32:08 gollum kernel: [   82.366744] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000000ce4 last fence id 0x0000000000000d0e on ring 0)
>Dec  8 01:32:27 gollum kernel: [  101.898853] radeon 0000:01:00.0: Saved 3901 dwords of commands on ring 0.
>Dec  8 01:32:27 gollum kernel: [  101.898870] radeon 0000:01:00.0: GPU softreset: 0x00000009
>Dec  8 01:32:27 gollum kernel: [  101.898873] radeon 0000:01:00.0:   GRBM_STATUS=0xE5D04028
>Dec  8 01:32:27 gollum kernel: [  101.898874] radeon 0000:01:00.0:   GRBM_STATUS2=0x52000008
>Dec  8 01:32:27 gollum kernel: [  101.898876] radeon 0000:01:00.0:   GRBM_STATUS_SE0=0xEE400000
>Dec  8 01:32:27 gollum kernel: [  101.898878] radeon 0000:01:00.0:   GRBM_STATUS_SE1=0x00000002
>Dec  8 01:32:27 gollum kernel: [  101.898879] radeon 0000:01:00.0:   GRBM_STATUS_SE2=0xEC400000
>Dec  8 01:32:27 gollum kernel: [  101.898881] radeon 0000:01:00.0:   GRBM_STATUS_SE3=0xEE400000
>Dec  8 01:32:27 gollum kernel: [  101.898882] radeon 0000:01:00.0:   SRBM_STATUS=0x20000C40
>Dec  8 01:32:27 gollum kernel: [  101.898884] radeon 0000:01:00.0:   SRBM_STATUS2=0x00000000
>Dec  8 01:32:27 gollum kernel: [  101.898894] radeon 0000:01:00.0:   SDMA0_STATUS_REG   = 0x46CEE557
>Dec  8 01:32:27 gollum kernel: [  101.898896] radeon 0000:01:00.0:   SDMA1_STATUS_REG   = 0x46CEE557
>Dec  8 01:32:27 gollum kernel: [  101.898898] radeon 0000:01:00.0:   CP_STAT = 0x84038600
>Dec  8 01:32:27 gollum kernel: [  101.898899] radeon 0000:01:00.0:   CP_STALLED_STAT1 = 0x00000c00
>Dec  8 01:32:27 gollum kernel: [  101.898901] radeon 0000:01:00.0:   CP_STALLED_STAT2 = 0x00018000
>Dec  8 01:32:27 gollum kernel: [  101.898903] radeon 0000:01:00.0:   CP_STALLED_STAT3 = 0x00000400
>Dec  8 01:32:27 gollum kernel: [  101.898904] radeon 0000:01:00.0:   CP_CPF_BUSY_STAT = 0x00000002
>Dec  8 01:32:27 gollum kernel: [  101.898906] radeon 0000:01:00.0:   CP_CPF_STALLED_STAT1 = 0x00000001
>Dec  8 01:32:27 gollum kernel: [  101.898908] radeon 0000:01:00.0:   CP_CPF_STATUS = 0x80000063
>Dec  8 01:32:27 gollum kernel: [  101.898909] radeon 0000:01:00.0:   CP_CPC_BUSY_STAT = 0x00000000
>Dec  8 01:32:27 gollum kernel: [  101.898911] radeon 0000:01:00.0:   CP_CPC_STALLED_STAT1 = 0x00000000
>Dec  8 01:32:27 gollum kernel: [  101.898912] radeon 0000:01:00.0:   CP_CPC_STATUS = 0x00000000
>Dec  8 01:32:27 gollum kernel: [  101.898914] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
>Dec  8 01:32:27 gollum kernel: [  101.898916] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
>Dec  8 01:32:27 gollum kernel: [  102.251226] radeon 0000:01:00.0: Wait for MC idle timedout !
>Dec  8 01:32:27 gollum kernel: [  102.251229] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00010001
>Dec  8 01:32:27 gollum kernel: [  102.251282] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100
>Dec  8 01:32:27 gollum kernel: [  102.252428] radeon 0000:01:00.0:   GRBM_STATUS=0x00003028
>Dec  8 01:32:27 gollum kernel: [  102.252430] radeon 0000:01:00.0:   GRBM_STATUS2=0x00000008
>Dec  8 01:32:27 gollum kernel: [  102.252432] radeon 0000:01:00.0:   GRBM_STATUS_SE0=0x00000006
>Dec  8 01:32:27 gollum kernel: [  102.252433] radeon 0000:01:00.0:   GRBM_STATUS_SE1=0x00000006
>Dec  8 01:32:27 gollum kernel: [  102.252435] radeon 0000:01:00.0:   GRBM_STATUS_SE2=0x00000006
>Dec  8 01:32:27 gollum kernel: [  102.252437] radeon 0000:01:00.0:   GRBM_STATUS_SE3=0x00000006
>Dec  8 01:32:27 gollum kernel: [  102.252438] radeon 0000:01:00.0:   SRBM_STATUS=0x20000C40
>Dec  8 01:32:27 gollum kernel: [  102.252440] radeon 0000:01:00.0:   SRBM_STATUS2=0x00000000
>Dec  8 01:32:27 gollum kernel: [  102.252441] radeon 0000:01:00.0:   SDMA0_STATUS_REG   = 0x46CEE557
>Dec  8 01:32:27 gollum kernel: [  102.252443] radeon 0000:01:00.0:   SDMA1_STATUS_REG   = 0x46CEE557
>Dec  8 01:32:27 gollum kernel: [  102.252445] radeon 0000:01:00.0:   CP_STAT = 0x00000000
>Dec  8 01:32:27 gollum kernel: [  102.252446] radeon 0000:01:00.0:   CP_STALLED_STAT1 = 0x00000000
>Dec  8 01:32:27 gollum kernel: [  102.252448] radeon 0000:01:00.0:   CP_STALLED_STAT2 = 0x00000000
>Dec  8 01:32:27 gollum kernel: [  102.252450] radeon 0000:01:00.0:   CP_STALLED_STAT3 = 0x00000000
>Dec  8 01:32:27 gollum kernel: [  102.252451] radeon 0000:01:00.0:   CP_CPF_BUSY_STAT = 0x00000000
>Dec  8 01:32:27 gollum kernel: [  102.252453] radeon 0000:01:00.0:   CP_CPF_STALLED_STAT1 = 0x00000000
>Dec  8 01:32:27 gollum kernel: [  102.252454] radeon 0000:01:00.0:   CP_CPF_STATUS = 0x00000000
>Dec  8 01:32:27 gollum kernel: [  102.252456] radeon 0000:01:00.0:   CP_CPC_BUSY_STAT = 0x00000000
>Dec  8 01:32:27 gollum kernel: [  102.252457] radeon 0000:01:00.0:   CP_CPC_STALLED_STAT1 = 0x00000000
>Dec  8 01:32:27 gollum kernel: [  102.252460] radeon 0000:01:00.0:   CP_CPC_STATUS = 0x00000000
>Dec  8 01:32:27 gollum kernel: [  102.252481] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
>

Actions: View

Attachments on bug 93288: 120402 | 120403 | 120404 | 120405 | 120407 | 120408 | 120409 | 125858 | 125859

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.