All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91141] Lots of *ERROR* Couldn't update BO_VA (-22) since drm/radeon: stop using addr to check for BO move
Date: Tue, 07 Jul 2015 13:43:49 +0000	[thread overview]
Message-ID: <bug-91141-502-iAckopIc7X@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91141-502@http.bugs.freedesktop.org/>


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

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

--- Comment #15 from Dave Witbrodt <dawitbro@sbcglobal.net> ---
(In reply to Christian König from comment #12)
> Created attachment 116973 [details]
> Possible fix part 2
> 
> Please apply this one on top of the first fix and see if the problem still
> happen.

Works good on my machine.  The programs that triggered the bug before no longer
cause any problems.

Sanity check:  I had dropped 161ab658 and b13e22ae from my list of cherry picks
before in order to have a working kernel.  After adding those back, and
applying

    0001-drm-radeon-allways-add-the-VM-clear-duplicate.patch
    0001-drm-radeon-check-if-BO_VA-is-set-before-adding-it-to.patch

everything works great again.  I have not yet tested suspend-to-RAM, but after
the testing I've done so far I doubt there will be problems.

HTH,
DW

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

[-- Attachment #1.2: Type: text/html, Size: 2146 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:[~2015-07-07 13:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29 10:38 [Bug 91141] Lots of *ERROR* Couldn't update BO_VA (-22) since drm/radeon: stop using addr to check for BO move bugzilla-daemon
2015-06-29 10:39 ` bugzilla-daemon
2015-06-29 13:05 ` bugzilla-daemon
2015-06-30 11:11 ` bugzilla-daemon
2015-06-30 13:19 ` bugzilla-daemon
2015-06-30 16:17 ` bugzilla-daemon
2015-07-02 16:54 ` bugzilla-daemon
2015-07-03  5:27 ` bugzilla-daemon
2015-07-03 13:50 ` bugzilla-daemon
2015-07-03 14:53 ` bugzilla-daemon
2015-07-03 18:49 ` bugzilla-daemon
2015-07-03 22:04 ` bugzilla-daemon
2015-07-06 12:31 ` bugzilla-daemon
2015-07-06 17:53 ` bugzilla-daemon
2015-07-07 10:04 ` bugzilla-daemon
2015-07-07 13:43 ` bugzilla-daemon [this message]
2015-07-07 14:23 ` bugzilla-daemon
2015-07-07 18:25 ` bugzilla-daemon
2015-07-08  3:26 ` bugzilla-daemon
2016-06-15 11:48 ` bugzilla-daemon
2016-06-15 11:48 ` 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-91141-502-iAckopIc7X@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.