From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102500] [polaris10][amd-staging-4.12] GPU fault detected, somethimes lockup
Date: Fri, 01 Sep 2017 21:36:43 +0000 [thread overview]
Message-ID: <bug-102500-502-FBN9fIjJax@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102500-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1588 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102500
Dieter Nützel <Dieter@nuetzel-hh.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |deathsimple@vodafone.de
--- Comment #5 from Dieter Nützel <Dieter@nuetzel-hh.de> ---
(In reply to Dieter Nützel from comment #4)
> (In reply to Alex Deucher from comment #1)
> > can you bisect?
>
> Hello all,
>
> I get the same on 'amd-staging-drm-next' since 1. of Sep (kernel build time:
> 1. Sep 02:14 CEST) update, too. Will go to bisect in the evening.
>
> [ 262.462941] amdgpu 0000:01:00.0: GPU fault detected: 146 0x0a023d14
> [ 262.462946] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
> 0x00101540
> [ 262.462949] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x0903D014
> [ 262.462952] amdgpu 0000:01:00.0: VM fault (0x14, vmid 4) at page 1054016,
> write from 'SDM1' (0x53
> 444d31) (61)
Yes,
git revert fd8bf087dffc
commit fd8bf087dffc0bce047c5aea2afcb8f821e48db1
Author: Christian König <christian.koenig@amd.com>
Date: Tue Aug 29 16:14:32 2017 +0200
drm/amdgpu: bump version for support of local BOs
Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Solve it on 'amd-staging-drm-next', too.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3375 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-09-01 21:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 20:44 [Bug 102500] [polaris10][amd-staging-4.12] GPU fault detected, somethimes lockup bugzilla-daemon
2017-08-31 21:58 ` bugzilla-daemon
2017-09-01 9:55 ` bugzilla-daemon
2017-09-01 10:04 ` bugzilla-daemon
2017-09-01 15:37 ` bugzilla-daemon
2017-09-01 21:36 ` bugzilla-daemon [this message]
2017-09-02 7:37 ` bugzilla-daemon
2017-09-02 7:38 ` bugzilla-daemon
2017-09-02 10:30 ` bugzilla-daemon
2017-09-03 16:34 ` bugzilla-daemon
2017-09-04 19:31 ` [Bug 102500] [polaris10, vega10][amd-staging-4.12, amd-staging-drm-next] " bugzilla-daemon
2017-09-07 20:13 ` bugzilla-daemon
2017-09-07 23:23 ` bugzilla-daemon
2017-09-08 8:18 ` bugzilla-daemon
2017-09-08 10:13 ` bugzilla-daemon
2017-09-08 11:08 ` bugzilla-daemon
2017-09-08 12:19 ` bugzilla-daemon
2017-09-08 15:54 ` bugzilla-daemon
2017-09-09 1:49 ` bugzilla-daemon
2017-09-09 19:11 ` bugzilla-daemon
2017-09-09 19:52 ` bugzilla-daemon
2017-09-10 4:14 ` bugzilla-daemon
2017-09-10 4:21 ` bugzilla-daemon
2017-10-03 21:36 ` bugzilla-daemon
2017-10-03 23:13 ` 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-102500-502-FBN9fIjJax@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