From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 59089] [bisected, regression] flood of GPU fault detected in logs caused by 9af20... drm/radeon: fix fence locking in the pageflip callback
Date: Thu, 17 Jan 2013 02:58:26 +0000 [thread overview]
Message-ID: <bug-59089-502-pefOrF57N7@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-59089-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 941 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=59089
--- Comment #8 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
(In reply to comment #7)
> I would consider it a flood, the message continually appears until glxgears
> is exited. Can you confirm whether 3e163a137be7f9a80ec720903c4bda028de5681f
> in mesa stops all of the GPU faults? If it does I will open another bug
> report seeing as it may be different.
Neither glxgears nor Heroes of Newerth produce GPU fault flood since applied
fix in mesa. If you are still experiencing a flood when glxgears is running,
I'm pretty sure it is not the same thing under the hood. Which makes me think:
what kernel version are you using? Did you test with latest mesa version since
fix was pushed in git? Which gpu do you have?
I'm running latest kernel from Linus' git, latest mesa git and I'm using an HD
6950.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1992 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:[~2013-01-17 2:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-06 20:39 [Bug 59089] New: [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-06 20:39 ` [Bug 59089] " 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 [this message]
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-pefOrF57N7@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).