From: Peter Hurley <peter@hurleysoftware.com>
To: Ilia Mirkin <imirkin@alum.mit.edu>,
"Bryan O'Donoghue" <pure.logic@nexus-software.ie>
Cc: Maarten Lankhorst <maarten.lankhorst@canonical.com>,
Ben Skeggs <bskeggs@redhat.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/nouveau/gem: tolerate a buffer specified multiple times
Date: Thu, 30 Jul 2015 10:49:10 -0400 [thread overview]
Message-ID: <55BA3966.1050806@hurleysoftware.com> (raw)
In-Reply-To: <CAKb7UvixeNTEo_o-34QWWcRUmxqKoV_GGQPArn5ZqcrEGS0qGQ@mail.gmail.com>
On 07/30/2015 10:12 AM, Ilia Mirkin wrote:
> Is this happening with libdrm 2.4.60? If so, that's a known
> (user-side) issue and should be fixed by using any version but that
> one.
What's the freedesktop bugzilla # for reference?
Regards,
Peter Hurley
> On Thu, Jul 30, 2015 at 6:28 AM, Bryan O'Donoghue
> <pure.logic@nexus-software.ie> wrote:
>> Ubuntu is shipping Chrome Version 44.0.2403.125 (64-bit). With this version
>> of the browser and current tip-of-tree 86ea07ca846a I get the following
>> error message followed by a lock-up of X.
>>
>> nouveau E[chrome[2737]] multiple instances of buffer 33 on validation list
>> nouveau E[chrome[2737]] validate_init
>> nouveau E[chrome[2737]] validate: -22
>> nouveau E[chrome[2737]] multiple instances of buffer 18 on validation list
>> nouveau E[chrome[2737]] validate_init
>> nouveau E[chrome[2737]] validate: -22
>> nouveau E[ PFIFO][0000:01:00.0] PFIFO: read fault at
>> 0x0003e21000 [PAGE_NOT_PRESENT] from (unknown enum
>> 0x00000000)/GPC0/(unknown enum 0x0000000f) on channel 0x007f80c000
>> [unknown]
>>
>> This patch suggests a fix for this with the kernel simply tolerating an
>> application such as chrome requesting the same buffer more than once.
>>
>> With the version of chrome given above, you can elicit this behaviour by
>> clicking on the bookmarks drop down. This will open another window on-top
>> of the current window. Minus the fix included here, this will lead to hard
>> lockup of all windows on the desktop.
>>
>> Chrome Version 44.0.2403.125 (64-bit)
>> Linux 4.2.0-rc4+ 86ea07ca846a
>>
>> People are suggesting running chrome with -disable-gpu however it is
>> possible to run Chrome in it's default mode, so long as we tolerate the
>> above behaviour.
>>
>> http://tinyurl.com/orvbzf3
>>
>> Signed-off-by: Bryan O'Donoghue <pure.logic@nexus-software.ie>
>> ---
>> drivers/gpu/drm/nouveau/nouveau_gem.c | 4 +---
>> 1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/nouveau/nouveau_gem.c b/drivers/gpu/drm/nouveau/nouveau_gem.c
>> index af1ee51..a9694faad 100644
>> --- a/drivers/gpu/drm/nouveau/nouveau_gem.c
>> +++ b/drivers/gpu/drm/nouveau/nouveau_gem.c
>> @@ -401,9 +401,7 @@ retry:
>> if (nvbo->reserved_by && nvbo->reserved_by == file_priv) {
>> NV_PRINTK(error, cli, "multiple instances of buffer %d on "
>> "validation list\n", b->handle);
>> - drm_gem_object_unreference_unlocked(gem);
>> - ret = -EINVAL;
>> - break;
>> + continue;
>> }
>>
>> ret = ttm_bo_reserve(&nvbo->bo, true, false, true, &op->ticket);
>> --
>> 1.9.1
next prev parent reply other threads:[~2015-07-30 14:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 10:28 Bryan O'Donoghue
2015-07-30 14:12 ` Ilia Mirkin
2015-07-30 14:48 ` Bryan O'Donoghue
2015-07-30 14:49 ` Peter Hurley [this message]
2015-07-30 14:52 ` Bryan O'Donoghue
2015-07-30 14:56 ` Bryan O'Donoghue
2015-07-30 15:02 ` Ilia Mirkin
2015-07-30 15:14 ` Bryan O'Donoghue
2015-07-30 15:26 ` Emil Velikov
2015-07-30 21:45 ` Peter Hurley
2015-07-31 0:03 ` Bryan O'Donoghue
2015-07-31 9:53 ` Bryan O'Donoghue
2015-07-31 9:58 ` Bryan O'Donoghue
2015-07-31 10:27 ` Bryan O'Donoghue
2015-07-31 16:36 ` Ilia Mirkin
2015-07-31 16:43 ` Bryan O'Donoghue
2015-07-31 18:11 ` Bryan O'Donoghue
2015-08-03 0:51 ` Bryan O'Donoghue
2015-07-31 16:19 ` Bryan O'Donoghue
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=55BA3966.1050806@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imirkin@alum.mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@canonical.com \
--cc=pure.logic@nexus-software.ie \
/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
Powered by JetHome