From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 59089] New: [bisected, regression] flood of GPU fault detected in logs caused by 9af20... drm/radeon: fix fence locking in the pageflip callback
Date: Sun, 06 Jan 2013 20:39:04 +0000 [thread overview]
Message-ID: <bug-59089-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1970 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=59089
Priority: medium
Bug ID: 59089
Assignee: dri-devel@lists.freedesktop.org
Summary: [bisected, regression] flood of GPU fault detected in
logs caused by 9af20... drm/radeon: fix fence locking
in the pageflip callback
Severity: normal
Classification: Unclassified
OS: All
Reporter: alexandre.f.demers@gmail.com
Hardware: All
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
GPU fault detected flood in logs (dmesg, kernel, errors and everything) of the
following form:
[ 533.928472] radeon 0000:03:00.0: GPU fault detected: 146 0x00335514
[ 533.928477] radeon 0000:03:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 533.928483] radeon 0000:03:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
>From time to time, there will be an address value different from 0x00000000.
They are produced at an awful rate, producing GB of logs in no time.
Appeared in kernel 3.8.0-rcX using a cayman GPU (HD 6950).
Bisecting to identify when the flood first appeared points at:
Commit: 4ac0533abaec2b83a7f2c675010eedd55664bc26
Author: Jerome Glisse <jglisse@redhat.com> 2012-12-13 12:08:11
Committer: Alex Deucher <alexander.deucher@amd.com> 2012-12-14 10:45:24
Parent: 9af20792124850369e764965690b99b20623dfc4 (drm/radeon: fix fence locking
in the pageflip callback)
Branch: remotes/origin/master
Follows: v3.7-rc7
Precedes: v3.8-rc1
drm/radeon: fix htile buffer size computation for command stream checker
Fix the size computation of the htile buffer.
Signed-off-by: Jerome Glisse <jglisse@redhat.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Maybe be related to some of the crashes seen in bug 58667.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3679 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 reply other threads:[~2013-01-06 20:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-06 20:39 bugzilla-daemon [this message]
2013-01-06 20:39 ` [Bug 59089] [bisected, regression] flood of GPU fault detected in logs caused by 9af20... drm/radeon: fix fence locking in the pageflip callback bugzilla-daemon
2013-01-07 20:33 ` bugzilla-daemon
2013-01-08 1:20 ` bugzilla-daemon
2013-01-08 1:21 ` bugzilla-daemon
2013-01-08 4:57 ` bugzilla-daemon
2013-01-08 5:53 ` bugzilla-daemon
2013-01-14 3:56 ` bugzilla-daemon
2013-01-14 6:01 ` bugzilla-daemon
2013-01-14 14:13 ` bugzilla-daemon
2013-01-17 2:58 ` bugzilla-daemon
2013-01-17 3:24 ` bugzilla-daemon
2013-01-17 4:03 ` bugzilla-daemon
2013-01-17 5:05 ` bugzilla-daemon
2013-01-18 15:57 ` bugzilla-daemon
2013-01-18 16:49 ` bugzilla-daemon
2013-02-20 5:39 ` 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-59089-502@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;
as well as URLs for NNTP newsgroup(s).