From: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
To: Peter Hurley <peter@hurleysoftware.com>,
Timo Aaltonen <tjaalton@debian.org>
Cc: Emil Velikov <emil.l.velikov@gmail.com>,
Ilia Mirkin <imirkin@alum.mit.edu>,
Maarten Lankhorst <maarten.lankhorst@canonical.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Ben Skeggs <bskeggs@redhat.com>
Subject: Re: [PATCH] drm/nouveau/gem: tolerate a buffer specified multiple times
Date: Fri, 31 Jul 2015 11:27:14 +0100 [thread overview]
Message-ID: <55BB4D82.8070605@nexus-software.ie> (raw)
In-Reply-To: <55BB46D4.9010006@nexus-software.ie>
On 31/07/15 10:58, Bryan O'Donoghue wrote:
> On 31/07/15 10:53, Bryan O'Donoghue wrote:
>> On 31/07/15 01:03, Bryan O'Donoghue wrote:
>>> On 30/07/15 22:45, Peter Hurley wrote:
>>>> [ +cc Debian maintainer ]
>>>>
>>>> On 07/30/2015 11:26 AM, Emil Velikov wrote:
>>>>> On 30 July 2015 at 16:02, Ilia Mirkin <imirkin@alum.mit.edu> wrote:
>>>>>> On Thu, Jul 30, 2015 at 10:56 AM, Bryan O'Donoghue
>>>>>> <pure.logic@nexus-software.ie> wrote:
>>>>>>> On 30/07/15 15:52, Bryan O'Donoghue wrote:
>>>>>>>>
>>>>>>>> On 30/07/15 15:49, Peter Hurley wrote:
>>>>>>>>>
>>>>>>>>> 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
>>>>>>>>
>>>>>>>>
>>>>>>>> I believe it's this one
>>>>>>>>
>>>>>>>> https://bugs.freedesktop.org/show_bug.cgi?id=89842#c19
>>>>>>>>
>>>>>>>
>>>>>>> Not really a world of choice on ubuntu to fix it though...
>>>>>>>
>>>>>>> deckard@aineko:~/Development/projectara$ apt-show-versions libdrm2
>>>>>>> libdrm2:amd64/trusty-updates 2.4.60-2~ubuntu14.04.1 uptodate
>>>>>>> libdrm2:i386/trusty-updates 2.4.60-2~ubuntu14.04.1 uptodate
>>>>>>>
>>>>>>> :(
>>>>>>
>>>>>> That's unfortunate. I know next to nothing about debian/ubuntu or how
>>>>>> they do versions or how to even build packages for them. But they're
>>>>>> big distros, presumably they have support teams of some sort, perhaps
>>>>>> they can help you.
>>>>>>
>>>>>> Assuming that switching away does resolve the issue for you, perhaps
>>>>>> you can also recommend that they avoid shipping that version, or
>>>>>> include this nouveau fix in it:
>>>>>>
>>>>>> http://cgit.freedesktop.org/mesa/drm/commit/?id=812e8fe6ce46d733c30207ee26c788c61f546294
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> Fwiw debian has been tracking this as #789759, and they are shipping
>>>>> 2.4.62 which includes the fix.
>>>>
>>>> Unfortunately the LTS version of Ubuntu (trusty) was updated to 2.4.60
>>>> several days ago without this fix.
>>>>
>>>> I repackaged libdrm 2.4.60 with only the bug fix above and confirm the
>>>> patch above fixes the observed behavior in freedesktop bug# 89842/
>>>> debian bug# 789759.
>>>>
>>>> I pushed the repackage to Launchpad PPA @ ppa:phurley/libdrm
>>>>
>>>> Hopefully the Debian maintainer grabs this fix and updates the official
>>>> distribution version soon.
>>>>
>>>> Regards,
>>>> Peter Hurley
>>>
>>> Yep.
>>>
>>> Dropping down to 2.4.56-1~ubuntu2 definitely removes the
>>>
>>> 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]
>>>
>>> and hard lock-up of X. I'll update these guys with the fix
>>>
>>> http://tinyurl.com/orvbzf3
>>
>> Hmm.
>>
>> Interesting - I spoke way too soon on that.
>>
>> Left my machine up overnight and lo and behold now that I do a dmesg I
>> see...
>>
>> nouveau E[chrome[2870]] multiple instances of buffer 16 on validation
>> list
>> nouveau E[chrome[2870]] multiple instances of buffer 24 on validation
>> list
>> nouveau E[chrome[2870]] multiple instances of buffer 167 on validation
>> list
>> nouveau E[chrome[2870]] multiple instances of buffer 251 on validation
>> list
>> nouveau E[chrome[2870]] multiple instances of buffer 248 on validation
>> list
>> nouveau E[chrome[2870]] multiple instances of buffer 249 on validation
>> list
>> nouveau E[chrome[2870]] multiple instances of buffer 230 on validation
>> list
>> nouveau E[chrome[2870]] multiple instances of buffer 253 on validation
>> list
>> nouveau E[chrome[2870]] multiple instances of buffer 255 on validation
>> list
>> nouveau E[chrome[2870]] multiple instances of buffer 230 on validation
>> list
>> nouveau E[chrome[2870]] multiple instances of buffer 257 on validation
>> list
>> nouveau E[chrome[2870]] multiple instances of buffer 230 on validation
>> list
>>
>> deckard@aineko:~$ dpkg -s libdrm2
>> Package: libdrm2
>> Status: install ok installed
>> Priority: optional
>> Section: libs
>> Installed-Size: 106
>> Maintainer: Ubuntu X-SWAT <ubuntu-x@lists.ubuntu.com>
>> Architecture: amd64
>> Multi-Arch: same
>> Source: libdrm
>> Version: 2.4.56-1~ubuntu2
>> Depends: libc6 (>= 2.17)
>> Pre-Depends: multiarch-support
>> Description: Userspace interface to kernel DRM services -- runtime
>> This library implements the userspace interface to the kernel DRM
>> services. DRM stands for "Direct Rendering Manager", which is the
>> kernelspace portion of the "Direct Rendering Infrastructure" (DRI).
>> The DRI is currently used on Linux to provide hardware-accelerated
>> OpenGL drivers.
>> .
>> This package provides the runtime environment for libdrm.
>> Orig-Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
>>
>> deckard@aineko:~$ uname -a
>> Linux aineko 4.2.0-rc4+ #50 SMP Thu Jul 30 01:22:01 IST 2015 x86_64
>> x86_64 x86_64 GNU/Linux
>>
>> Please note - this machine has the fix I proposed in the original patch
>> applied so X is not locking up when the multiple instances message
>> happens.
>>
>> In any case to answer the original question - I don't believe switching
>> away from 2.4.60 will resolve this issue
>
> 2.40.6 I mean :)
>
ah no... 2.4.60 is right...
Yes so Ilia - I've switched out 2.4.60 as per your suggestion to 2.4.56
(getting the version numbers right :) ) and it's still definitely giving
me the multiple instances message.
next prev parent reply other threads:[~2015-07-31 10:27 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
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 [this message]
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=55BB4D82.8070605@nexus-software.ie \
--to=pure.logic@nexus-software.ie \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=imirkin@alum.mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@canonical.com \
--cc=peter@hurleysoftware.com \
--cc=tjaalton@debian.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
Powered by JetHome