dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 83616] Sydtem crashes in xonotic with kernel 3.17-rc since linux commit 86302eeadebfab94530b00f5e53a23f911ff41e4
Date: Mon, 08 Sep 2014 15:37:52 +0000	[thread overview]
Message-ID: <bug-83616-502-oqiZ9X6I5b@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-83616-502@http.bugs.freedesktop.org/>


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

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

--- Comment #1 from Bug <freedesktop@voorpost.net> ---
commit 86302eeadebfab94530b00f5e53a23f911ff41e4
Author: Christian König <christian.koenig@amd.com>
Date:   Mon Aug 18 16:30:12 2014 +0200

    drm/radeon: Sync ME and PFP after CP semaphore waits v4

    Fixes lockups due to CP read GPUVM faults when running piglit on Cape
    Verde.

    v2 (chk): apply the fix to R600+ as well, on CIK only the GFX CP has
          a PFP, add more comments to R600 code, enable flushing again
    v3: (agd5f): only apply to 7xx+.  r6xx does not have the packet.
    v4: (agd5f): split flush change into a separate patch, fix formatting

    Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
    Signed-off-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Tested-by: Michel Dänzer <michel.daenzer@amd.com>

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

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

  reply	other threads:[~2014-09-08 15:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 15:34 [Bug 83616] New: Sydtem crashes in xonotic with kernel 3.17-rc since linux commit 86302eeadebfab94530b00f5e53a23f911ff41e4 bugzilla-daemon
2014-09-08 15:37 ` bugzilla-daemon [this message]
2014-09-08 16:55 ` [Bug 83616] " bugzilla-daemon
2014-09-08 17:05 ` bugzilla-daemon
2014-09-08 17:18 ` bugzilla-daemon
2014-09-08 18:05 ` bugzilla-daemon
2014-09-08 18:21 ` bugzilla-daemon
2014-09-08 20:14 ` bugzilla-daemon
2014-09-08 20:55 ` bugzilla-daemon
2014-09-08 20:56 ` bugzilla-daemon
2014-09-08 20:58 ` bugzilla-daemon
2014-09-08 21:34 ` bugzilla-daemon
2014-09-08 21:46 ` bugzilla-daemon
2014-09-08 21:56 ` bugzilla-daemon
2014-09-09  6:25 ` [Bug 83616] System " bugzilla-daemon
2014-09-19 11:12 ` bugzilla-daemon
2014-09-19 11:13 ` bugzilla-daemon
2019-11-19  8:55 ` 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-83616-502-oqiZ9X6I5b@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