All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 08 Jan 2013 05:53:46 +0000	[thread overview]
Message-ID: <bug-59089-502-MacujtHUTW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-59089-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 857 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=59089

--- Comment #4 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
(In reply to comment #3)
> I don't want to play the bad guy but for me this is not fixed, just reduced.

Well, I closed it because I don't have the continuous GPU fault flood happening
anymore. However, I was unable to determine if there was still a GPU fault
happening. This bug is really about the flood.

So, I don't have any problem in reopening it if you do experience a flood of
GPU faults. I was getting GB of logs in no time.

Are you still seeing GPU faults only in some circumstances (games or specific
applications) or just opening a session (for me it's with Gnome Shell) is
enough? Also, keep in mind this bug is pinpointing a specific commit.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1899 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

  parent reply	other threads:[~2013-01-08  5:53 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 [this message]
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-MacujtHUTW@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.