[Nouveau] [Bug 71900] [NV40] GPU lockup and segmentation fault of Nouveau-1.0.10 on PowerMac G5 with acceleration

2015-07-30 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=71900

--- Comment #11 from Ben Skeggs  ---
(In reply to Brock Wittrock from comment #10)
> From what I was reading, Ben's patches weren't necessarily ideal for final
> inclusion into the driver.  Still trying to wrap my head around the comments
> from that thread in the mailing list archives to see what changes need to be
> made to get 64k page sizes working for G5 owners with Nvidia cards. 
> 
> Anybody able to provide any assistance with this somehow?
I plan on attempting to untangle the vm mess in the next few weeks, and this
will be one of the things I'll attempt to address while doing so.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 71900] [NV40] GPU lockup and segmentation fault of Nouveau-1.0.10 on PowerMac G5 with acceleration

2015-07-30 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=71900

--- Comment #10 from Brock Wittrock  ---
>From what I was reading, Ben's patches weren't necessarily ideal for final
inclusion into the driver.  Still trying to wrap my head around the comments
from that thread in the mailing list archives to see what changes need to be
made to get 64k page sizes working for G5 owners with Nvidia cards. 

Anybody able to provide any assistance with this somehow?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 91413] INFO: task Xorg:2419 blocked for more than 120 seconds.

2015-07-30 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=91413

--- Comment #3 from Olivier Diotte  ---
This doesn't happen on 3.13.0

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 91373] Nouveau fills kern.log with gigabytes of data when molecule screensaver is run

2015-07-30 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=91373

--- Comment #9 from Olivier Diotte  ---
After a week's worth of usage on kernel 3.13.0, I'm confident enough to assert
that that kernel version is usable.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau


Re: [Nouveau] [PATCH 2/2] Add Option "DRI" to allow selection of maximum DRI level. (v2)

2015-07-30 Thread Emil Velikov
On 29 July 2015 at 13:39, Mario Kleiner  wrote:
> Allow user to select the maximum level of DRI implementation
> to use, DRI2 or DRI3.
>
> exa accel supports both DRI2 and, if the kernel supports
> rendernodes, also DRI3. However, DRI3 still seems to have
> some bugs on current implementations, and additionally it
> doesn't work well at all for X-Servers older than 1.16.3
> due to X-Server bugs. Therefore we default to DRI2 on exa,
> but allow the user to enable DRI3 with this new option.
>
> nouveau's glamor accel backend currently doesn't work under
> DRI2 at all, so we continue to use DRI3 whenever it is
> supported and ignore this new option for now.
>
> Also add a bit more output about status of Present and
> DRI3 to aid debugging.
>
> Note: This was originally meant to be a boolean parameter,
>   to just select between DRI3 on and off, but changed
>   here to a DRI level to make it consistent with the
>   same option in the released Intel-ddx.
>
> v2: Use fixed up Bool return type of nouveau_present_init().
>
> Signed-off-by: Mario Kleiner 
> Cc: Ilia Mirkin 
> Cc: Emil Velikov 
> Cc: Martin Peres 
> Cc: Ben Skeggs 
> ---
>  man/nouveau.man  |  6 ++
>  src/nouveau_dri2.c   | 11 ++-
>  src/nouveau_glamor.c |  2 +-
>  src/nv_const.h   |  2 ++
>  src/nv_driver.c  | 30 --
>  src/nv_type.h|  1 +
>  6 files changed, 48 insertions(+), 4 deletions(-)
>
> diff --git a/man/nouveau.man b/man/nouveau.man
> index 129bb7f..3d5a428 100644
> --- a/man/nouveau.man
> +++ b/man/nouveau.man
> @@ -125,6 +125,12 @@ that relies on correct presentation timing behaviour as 
> defined in that
>  specification.
>  .br
>  Default: 1.
> +.TP
> +.BI "Option \*qDRI\*q \*q" integer \*q
> +Define the maximum level of DRI to enable. Valid values are 2 or 3.
> +exa acceleration will honor the maximum level if it is supported.
> +Under glamor acceleration DRI3 is always enabled if supported,
> +as glamor currently does not support DRI2. Default: 2 on exa, 3 on glamor.
>  .SH "SEE ALSO"
>  __xservername__(__appmansuffix__), __xconfigfile__(__filemansuffix__), 
> Xserver(__appmansuffix__), X(__miscmansuffix__)
>  .SH AUTHORS
> diff --git a/src/nouveau_dri2.c b/src/nouveau_dri2.c
> index ce6f53e..81ee9be 100644
> --- a/src/nouveau_dri2.c
> +++ b/src/nouveau_dri2.c
> @@ -1134,7 +1134,16 @@ nouveau_dri3_screen_init(ScreenPtr screen)
> if (buf && stat(buf, &render) == 0 &&
> master.st_mode == render.st_mode) {
> pNv->render_node = buf;
> -   return dri3_screen_init(screen, &nouveau_dri3_screen_info);
> +   if (dri3_screen_init(screen, &nouveau_dri3_screen_info)) {
> +   xf86DrvMsg(pScrn->scrnIndex, X_INFO,
> +  "DRI3 on EXA enabled\n");
> +   return TRUE;
> +   }
> +   else {
> +   xf86DrvMsg(pScrn->scrnIndex, X_WARNING,
> +  "DRI3 on EXA initialization failed\n");
> +   return FALSE;
> +   }
> } else
> free(buf);
>  #endif
> diff --git a/src/nouveau_glamor.c b/src/nouveau_glamor.c
> index b8bca17..a8e9206 100644
> --- a/src/nouveau_glamor.c
> +++ b/src/nouveau_glamor.c
> @@ -240,7 +240,7 @@ nouveau_glamor_init(ScreenPtr screen)
> screen->SharePixmapBacking = nouveau_glamor_share_pixmap_backing;
> screen->SetSharedPixmapBacking = 
> nouveau_glamor_set_shared_pixmap_backing;
>
> -   xf86DrvMsg(scrn->scrnIndex, X_INFO, "[GLAMOR] initialised\n");
> +   xf86DrvMsg(scrn->scrnIndex, X_INFO, "[GLAMOR] initialised with 
> DRI3\n");
> pNv->Flush = nouveau_glamor_flush;
> return TRUE;
>  }
> diff --git a/src/nv_const.h b/src/nv_const.h
> index f1b4e9b..3f18d23 100644
> --- a/src/nv_const.h
> +++ b/src/nv_const.h
> @@ -18,6 +18,7 @@ typedef enum {
>  OPTION_SWAP_LIMIT,
>  OPTION_ASYNC_COPY,
>  OPTION_ACCELMETHOD,
> +OPTION_DRI,
>  } NVOpts;
>
>
> @@ -34,6 +35,7 @@ static const OptionInfoRec NVOptions[] = {
>  { OPTION_SWAP_LIMIT,   "SwapLimit",OPTV_INTEGER,   {0}, FALSE },
>  { OPTION_ASYNC_COPY,   "AsyncUTSDFS",  OPTV_BOOLEAN,   {0}, FALSE },
>  { OPTION_ACCELMETHOD,  "AccelMethod",  OPTV_STRING,{0}, FALSE },
> +{ OPTION_DRI,  "DRI",  OPTV_INTEGER,   {0}, FALSE },
>  { -1,   NULL,   OPTV_NONE,  {0}, FALSE }
>  };
>
> diff --git a/src/nv_driver.c b/src/nv_driver.c
> index 4218e4f..514a8bc 100644
> --- a/src/nv_driver.c
> +++ b/src/nv_driver.c
> @@ -1095,6 +1095,25 @@ NVPreInit(ScrnInfoPtr pScrn, int flags)
> pNv->ce_enabled =
> xf86ReturnOptValBool(pNv->Options, OPTION_ASYNC_COPY, FALSE);
>
> +   /* Define maximum allowed level of DRI implementation to use.
> +* We default to DRI2 on EXA for now, as DRI3 still has some
> +* problems. 

Re: [Nouveau] "enable dri3 support without glamor" causes gnome-shell regression on nv4x

2015-07-30 Thread Ilia Mirkin
FWIW this is a fail on nv50+ as well. See for example
https://bugs.freedesktop.org/show_bug.cgi?id=91445

My suspicion is that this is due to the lack of PUSH_KICK in the *Done
exa handlers -- works fine with DRI2, but DRI3 has no synchronization
and so the commands never get flushed out. Easily verified by sticking
PUSH_KICK's everywhere.

Note that I'm going to land Mario's patch today to disable DRI3 by
default when using EXA.

  -ilia

On Thu, Jul 30, 2015 at 9:16 AM, Hans de Goede  wrote:
> Hi Maarten,
>
> xf86-video-nouveau causes a garbled display when running
> gnome-shell on nv4x (tested with nv43 and nv46) since this commit:
>
> http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=241e7289f25a342a457952b9b0e539c2f0b81d99
>
> I've seen some discussion about issues caused by enabling dri,
> but AFAIK no solution let.
>
> I have time to help with debugging / fixing this, but I will
> need some guidance where to start as I'm still learning
> the ropes wrt nouveau.
>
> Regards,
>
> Hans
> ___
> Nouveau mailing list
> Nouveau@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/nouveau
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] "enable dri3 support without glamor" causes gnome-shell regression on nv4x

2015-07-30 Thread Hans de Goede

Hi Maarten,

xf86-video-nouveau causes a garbled display when running
gnome-shell on nv4x (tested with nv43 and nv46) since this commit:

http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=241e7289f25a342a457952b9b0e539c2f0b81d99

I've seen some discussion about issues caused by enabling dri,
but AFAIK no solution let.

I have time to help with debugging / fixing this, but I will
need some guidance where to start as I'm still learning
the ropes wrt nouveau.

Regards,

Hans
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau


Re: [Nouveau] [PATCH] nouveau: nv46: Change mc subdev oclass from nv44 to nv4c

2015-07-30 Thread Hans de Goede

Hi,

On 27-07-15 17:52, Hans de Goede wrote:


Slightly offtopic:

I decided to be bold and try gnome-shell on the nv46 with msi disabled,
which sofar was a guaranteed way to freeze the system, and it now works
somewhat (latest kernel, ddx and mesa). I see something which shows
horizontal lines which are small parts from my desktop background, and
things change significantly when I switch to the overview mode.

But other then that the display is completely wrong, it looks a bit
like a framebuffer pitch problem, but then different. I think it
is likely some tiling problem or some such.

Note that metacity + glxgears works, this only shows with
gnome-shell, any hints where to start looking wrt debugging this?

Or should I first try to run piglet and see if some tests there
point out the culprit?


I've been working on this today, I decided to first make sure
that the latest ddx + mesa did not have a regression on nv4x in
general, so I plugged in my nv43 card which used to run gnome-shell
fine and that shows the same problem.

Some debugging with that card shows that things break with this
ddx commit:

http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=241e7289f25a342a457952b9b0e539c2f0b81d99

"enable dri3 support without glamor"

Using an older ddx + latest mesa master gnome-shell runs fine
on my nv43 card.

And adding my patch to disable msi interrupts on nv46 makes
gnome-shell run fine on my nv46 card too :)

So unless someone has a good idea to fix msi interrupts on
nv46, I suggest we merge my patch to disable them
(with a Cc: sta...@vger.kernel.org), which should fix most
problems nv46 users have been seeing.

Regards,

Hans
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau