[Bug 87278] Packet0 not allowed and GPU fault detected errors with Serious Engine games
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sun Jan 4 23:14:58 PST 2015
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #15 from Arash <n5k2la421i2u0eml at gmail.com> ---
same issue, dota2 and with no Packet0 message.
kernel 3.18
llvm git
mesa git
r9-270x/radeonsi
it happens fairly frequently (or every time i pick 'morphling') :(
i haven't had this problem with 6570 (r600g)...
...
Jan 05 06:25:08 -- kernel: switching to power state:
Jan 05 06:25:08 -- kernel: ui class: performance
Jan 05 06:25:08 -- kernel: internal class: none
Jan 05 06:25:08 -- kernel: caps:
Jan 05 06:25:08 -- kernel: uvd vclk: 0 dclk: 0
Jan 05 06:25:08 -- kernel: power level 0 sclk: 30000 mclk:
15000 vddc: 875 vddci: 850 pcie gen: 1
Jan 05 06:25:08 -- kernel: power level 1 sclk: 45000 mclk:
140000 vddc: 950 vddci: 1025 pcie gen: 1
Jan 05 06:25:08 -- kernel: power level 2 sclk: 105000 mclk:
140000 vddc: 1163 vddci: 1025 pcie gen: 1
Jan 05 06:25:08 -- kernel: power level 3 sclk: 112000 mclk:
140000 vddc: 1206 vddci: 1025 pcie gen: 1
Jan 05 06:25:08 -- kernel: status: c r
Jan 05 06:25:40 -- kernel: IPVS: Creating netns size=2056 id=21
Jan 05 06:25:40 -- kernel: IPVS: ftp: loaded support on port[0] = 21
Jan 05 06:28:59 -- kernel: radeon 0000:01:00.0: GPU fault detected: 147
0x00044401
Jan 05 06:28:59 -- kernel: radeon 0000:01:00.0:
VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x01000000
Jan 05 06:28:59 -- kernel: radeon 0000:01:00.0:
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x04044001
Jan 05 06:28:59 -- kernel: VM fault (0x01, vmid 2) at page 16777216, read from
TC (68)
Jan 05 06:28:59 -- kernel: radeon 0000:01:00.0: GPU fault detected: 147
0x00044401
Jan 05 06:28:59 -- kernel: radeon 0000:01:00.0:
VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x01000000
Jan 05 06:28:59 -- kernel: radeon 0000:01:00.0:
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x04044001
Jan 05 06:28:59 -- kernel: VM fault (0x01, vmid 2) at page 16777216, read from
TC (68)
Jan 05 06:29:10 -- kernel: radeon 0000:01:00.0: ring 0 stalled for more than
10293msec
Jan 05 06:29:10 -- kernel: radeon 0000:01:00.0: GPU lockup (current fence id
0x00000000002165c7 last fence id 0x00000000002165e9 on ring 0)
Jan 05 06:29:10 -- kernel: radeon 0000:01:00.0: failed to get a new IB (-35)
Jan 05 06:29:10 -- kernel: [drm:radeon_cs_ib_fill] *ERROR* Failed to get ib !
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: failed to get a new IB (-35)
Jan 05 06:29:11 -- kernel: [drm:radeon_cs_ib_fill] *ERROR* Failed to get ib !
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: Saved 1355 dwords of commands
on ring 0.
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: GPU softreset: 0x0000004D
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: GRBM_STATUS =
0xF7D24028
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: GRBM_STATUS_SE0 =
0xEFC00000
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: GRBM_STATUS_SE1 =
0xEFC00000
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: SRBM_STATUS =
0x200000C0
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: SRBM_STATUS2 =
0x00000000
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 =
0x00000000
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 =
0x40000000
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT =
0x00008006
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: R_008680_CP_STAT =
0x80228647
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG =
0x44483106
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG =
0x44C83D57
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0:
VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0:
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00100100
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: GRBM_STATUS =
0x00003028
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: GRBM_STATUS_SE0 =
0x00000006
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: GRBM_STATUS_SE1 =
0x00000006
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: SRBM_STATUS =
0x200000C0
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: SRBM_STATUS2 =
0x00000000
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 =
0x00000000
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 =
0x00000000
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT =
0x00000000
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: R_008680_CP_STAT =
0x00000000
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG =
0x44C83D57
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG =
0x44C83D57
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: GPU reset succeeded, trying to
resume
Jan 05 06:29:11 -- kernel: [drm] probing gen 2 caps for device 8086:2e31 =
2212501/0
Jan 05 06:29:11 -- kernel: [drm] PCIE GART of 1024M enabled (table at
0x0000000000277000).
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: WB enabled
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu
addr 0x0000000100000c00 and cpu addr 0xffff8800db08fc00
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu
addr 0x0000000100000c04 and cpu addr 0xffff8800db08fc04
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu
addr 0x0000000100000c08 and cpu addr 0xffff8800db08fc08
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu
addr 0x0000000100000c0c and cpu addr 0xffff8800db08fc0c
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu
addr 0x0000000100000c10 and cpu addr 0xffff8800db08fc10
Jan 05 06:29:11 -- kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu
addr 0x0000000000075a18 and cpu addr 0xffffc900048b5a18
Jan 05 06:29:11 -- kernel: [drm] ring test on 0 succeeded in 3 usecs
Jan 05 06:29:11 -- kernel: [drm] ring test on 1 succeeded in 1 usecs
Jan 05 06:29:11 -- kernel: [drm] ring test on 2 succeeded in 1 usecs
Jan 05 06:29:11 -- kernel: [drm] ring test on 3 succeeded in 6 usecs
Jan 05 06:29:11 -- kernel: [drm] ring test on 4 succeeded in 6 usecs
Jan 05 06:29:11 -- kernel: [drm] ring test on 5 succeeded in 2 usecs
Jan 05 06:29:11 -- kernel: [drm] UVD initialized successfully.
Jan 05 06:29:11 -- kernel: switching from power state:
Jan 05 06:29:11 -- kernel: ui class: none
Jan 05 06:29:11 -- kernel: internal class: boot
Jan 05 06:29:11 -- kernel: caps:
Jan 05 06:29:11 -- kernel: uvd vclk: 0 dclk: 0
Jan 05 06:29:11 -- kernel: power level 0 sclk: 15000 mclk:
15000 vddc: 950 vddci: 950 pcie gen: 1
Jan 05 06:29:11 -- kernel: status: c b
...
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150105/2535b3b4/attachment.html>
More information about the dri-devel
mailing list