mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: Peter Hurley <peter@hurleysoftware.com>,
	Timo Aaltonen <tjaalton@debian.org>,
	Emil Velikov <emil.l.velikov@gmail.com>,
	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 19:11:10 +0100	[thread overview]
Message-ID: <55BBBA3E.5010102@nexus-software.ie> (raw)
In-Reply-To: <55BBA5B7.9040809@nexus-software.ie>

On 31/07/15 17:43, Bryan O'Donoghue wrote:
> On 31/07/15 17:36, Ilia Mirkin wrote:
>> Do you have a reproducible way of achieving the multiple buffer on
>> validation list thing?

Reliable enough. Start Chrome, then get Chrome to open a menu on top of 
it's own screen - for example click the top right menu bar - the thing 
with the three horizontal bars, scroll down to 'recent tabs' and let the 
mouse hover.

You'll get a menu that opens up over the main chrome screen and at that 
point you'll also get a 'multiple instances of buffer'

Basically drawing one window on top of another inside of the same Chrome 
tab.

I guess the same PID is mapping the same piece of memory twice because 
if I open a seperate Chrome window (which will have a seperate PID) and 
drag one window over the other we don't see a repeat.

If it helps

deckard@aineko:~$ dmesg | tail -n 5
[ 6900.249427] nouveau E[chrome[3176]] multiple instances of buffer 456 
on validation list
[ 6920.992475] nouveau E[chrome[3176]] multiple instances of buffer 458 
on validation list
[ 6934.277352] nouveau E[chrome[3176]] multiple instances of buffer 458 
on validation list
[ 6994.303600] nouveau E[chrome[3176]] multiple instances of buffer 458 
on validation list
[ 7067.436049] nouveau E[chrome[3176]] multiple instances of buffer 456 
on validation list


deckard@aineko:~$ ps -ax | grep chrome | grep 3176
  3176 pts/6    Sl+    0:29 /opt/google/chrome/chrome --type=gpu-process 
--channel=3143.0.1295591 ives-passed-by-fd --v8-snapshot-passed-by-fd 
--supports-dual-gpus=false --gpu-driver-bug-workarounds=2,29,32,45,55,57 
--disable-accelerated-video-decode --gpu-vendor-id=0x10de 
--gpu-device-id=0x0fe9 --gpu-driver-vendor --gpu-driver-version 
--v8-natives-passed-by-fd --v8-snapshot-passed-by-fd

> What GPU do you have? (Looking for a codename,
>> not a marketing name... lspci should have it... GFxxx or GKxxx or
>
> 01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT
> 750M Mac Edition] (rev a1) (prog-if 00 [VGA controller])
>      Subsystem: Apple Inc. Device 0130
>      Flags: bus master, fast devsel, latency 0, IRQ 45
>      Memory at c0000000 (32-bit, non-prefetchable) [size=16M]
>      Memory at 80000000 (64-bit, prefetchable) [size=256M]
>      Memory at 90000000 (64-bit, prefetchable) [size=32M]
>      I/O ports at 1000 [size=128]
>      Expansion ROM at c1000000 [disabled] [size=512K]
>      Capabilities: [60] Power Management version 3
>      Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
>      Capabilities: [78] Express Endpoint, MSI 00
>      Capabilities: [b4] Vendor Specific Information: Len=14 <?>
>      Capabilities: [100] Virtual Channel
>      Capabilities: [128] Power Budgeting <?>
>      Capabilities: [420] Advanced Error Reporting
>      Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1
> Len=024 <?>
>      Capabilities: [900] #19
>      Kernel driver in use: nouveau
>
> Macbook pro retina 2014


  reply	other threads:[~2015-07-31 18:11 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
2015-07-31 16:36                       ` Ilia Mirkin
2015-07-31 16:43                         ` Bryan O'Donoghue
2015-07-31 18:11                           ` Bryan O'Donoghue [this message]
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=55BBBA3E.5010102@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