From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 87278] Packet0 not allowed and GPU fault detected errors with Serious Engine games
Date: Mon, 05 Jan 2015 07:14:58 +0000 [thread overview]
Message-ID: <bug-87278-502-jBdrYxTOfv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-87278-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 7098 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #15 from Arash <n5k2la421i2u0eml@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.
[-- Attachment #1.2: Type: text/html, Size: 7916 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
next prev parent reply other threads:[~2015-01-05 7:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-13 10:38 [Bug 87278] Packet0 not allowed and GPU fault detected errors with Serious Engine games bugzilla-daemon
2014-12-13 10:39 ` bugzilla-daemon
2014-12-13 18:45 ` bugzilla-daemon
2014-12-16 8:48 ` bugzilla-daemon
2014-12-16 8:56 ` bugzilla-daemon
2014-12-17 5:52 ` bugzilla-daemon
2014-12-17 9:39 ` bugzilla-daemon
2014-12-17 10:34 ` bugzilla-daemon
2014-12-19 3:36 ` bugzilla-daemon
2014-12-19 3:39 ` bugzilla-daemon
2014-12-19 11:13 ` bugzilla-daemon
2014-12-19 13:32 ` bugzilla-daemon
2014-12-28 16:29 ` bugzilla-daemon
2014-12-28 16:30 ` bugzilla-daemon
2014-12-30 5:15 ` bugzilla-daemon
2015-01-05 7:14 ` bugzilla-daemon [this message]
2015-01-05 8:16 ` bugzilla-daemon
2015-02-07 13:36 ` bugzilla-daemon
2015-02-07 14:56 ` bugzilla-daemon
2015-02-07 15:57 ` bugzilla-daemon
2015-02-07 19:48 ` bugzilla-daemon
2015-02-07 23:08 ` bugzilla-daemon
2015-02-08 10:18 ` bugzilla-daemon
2015-02-18 18:26 ` bugzilla-daemon
2015-02-19 15:44 ` bugzilla-daemon
2015-03-10 18:59 ` bugzilla-daemon
2015-03-31 22:33 ` bugzilla-daemon
2015-04-01 2:08 ` bugzilla-daemon
2015-04-01 11:54 ` bugzilla-daemon
2015-04-01 11:55 ` bugzilla-daemon
2015-05-08 23:09 ` bugzilla-daemon
2015-08-01 18:38 ` bugzilla-daemon
2018-08-09 17:35 ` bugzilla-daemon
2019-09-25 17:51 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-87278-502-jBdrYxTOfv@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox