[Nouveau] [Bug 101322] GM108/NV118: 0 MiB DDR3 and boot crash in gf100_ltc_oneinit_tag_ram

2017-08-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101322 --- Comment #8 from Daniel Drake --- Sorry for the slow response. We tested the patch against 4.13.rc5 and the issue is still there. -- You are receiving this mail because: You are the assignee for the bug._

[Nouveau] [PATCH] drm/nouveau: remove redundant null check on array mstm->msto

2017-08-17 Thread Colin King
From: Colin Ian King The check to see if mstm->msto is null is redundant because it is an array and hence can never be null. Remove the redundant check. Detected by CoverityScan, CID#1375915 ("Array compared against 0") Signed-off-by: Colin Ian King --- drivers/gpu/drm/nouveau/nv50_display.c

Re: [Nouveau] [PATCH] drm/nouveau: remove redundant null check on array mstm->msto

2017-08-17 Thread Emil Velikov
On 17 August 2017 at 11:37, Colin King wrote: > From: Colin Ian King > > The check to see if mstm->msto is null is redundant because it is > an array and hence can never be null. Remove the redundant check. > > Detected by CoverityScan, CID#1375915 ("Array compared against 0") > > Signed-off-by:

Re: [Nouveau] [PATCH] drm/nouveau: remove redundant null check on array mstm->msto

2017-08-17 Thread Colin Ian King
On 17/08/17 13:21, Emil Velikov wrote: > On 17 August 2017 at 11:37, Colin King wrote: >> From: Colin Ian King >> >> The check to see if mstm->msto is null is redundant because it is >> an array and hence can never be null. Remove the redundant check. >> >> Detected by CoverityScan, CID#1375915

[Nouveau] [PATCH 08/13] drm/nouveau/imem/gk20a: Use sychronized interface of the IOMMU-API

2017-08-17 Thread Joerg Roedel
From: Joerg Roedel The map and unmap functions of the IOMMU-API changed their semantics: They do no longer guarantee that the hardware TLBs are synchronized with the page-table updates they made. To make conversion easier, new synchronized functions have been introduced which give these guarante

[Nouveau] [Bug 102275] New: Laptop bootup and suspend and wake issues

2017-08-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=102275 Bug ID: 102275 Summary: Laptop bootup and suspend and wake issues Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

[Nouveau] [Bug 100228] [NV137] bus: MMIO read of 00000000 FAULT at 409800 [ TIMEOUT ]

2017-08-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=100228 Rhys Kidd changed: What|Removed |Added CC||majzo...@umsl.edu --- Comment #15 from Rhys

[Nouveau] [Bug 102275] Laptop bootup and suspend and wake issues

2017-08-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=102275 Rhys Kidd changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW

[Nouveau] [PATCH] nvc0: fix handling of inverted render condition

2017-08-17 Thread Tobias Klausmann
Wether we wait on an inverted rendering condition or not, we should not render on a passed query. This fixes the CTS test case 'KHR-GL45.conditional_render_inverted.functional'. Signed-off-by: Tobias Klausmann --- src/gallium/drivers/nouveau/nvc0/nvc0_query.c | 2 +- 1 file changed, 1 insertion

Re: [Nouveau] [PATCH] nvc0: fix handling of inverted render condition

2017-08-17 Thread Ilia Mirkin
So ... how do you handle the case of a query that hasn't completed yet and one of the no-wait enums is passed in? On Thu, Aug 17, 2017 at 4:43 PM, Tobias Klausmann wrote: > Wether we wait on an inverted rendering condition or not, we should not render > on a passed query. > > This fixes the CTS t

[Nouveau] [PATCH][V2] drm/nouveau: perform null check on msto[i] rathern than msto

2017-08-17 Thread Colin King
From: Colin Ian King The null check on the array msto is incorrect since msto is never null. The null check should be instead on msto[i] since this is being dereferenced in the call to drm_mode_connector_attach_encoder. Thanks to Emil Velikov for pointing out the mistake in my original fix and f

Re: [Nouveau] [PATCH][V2] drm/nouveau: perform null check on msto[i] rathern than msto

2017-08-17 Thread Ilia Mirkin
On Thu, Aug 17, 2017 at 6:03 PM, Colin King wrote: > From: Colin Ian King > > The null check on the array msto is incorrect since msto is never > null. The null check should be instead on msto[i] since this is > being dereferenced in the call to drm_mode_connector_attach_encoder. > > Thanks to Em

Re: [Nouveau] [PATCH][V2] drm/nouveau: perform null check on msto[i] rathern than msto

2017-08-17 Thread Colin Ian King
On 17/08/17 23:07, Ilia Mirkin wrote: > On Thu, Aug 17, 2017 at 6:03 PM, Colin King wrote: >> From: Colin Ian King >> >> The null check on the array msto is incorrect since msto is never >> null. The null check should be instead on msto[i] since this is >> being dereferenced in the call to drm_mo

Re: [Nouveau] [PATCH][V2] drm/nouveau: perform null check on msto[i] rathern than msto

2017-08-17 Thread Ben Skeggs
On 08/18/2017 08:16 AM, Colin Ian King wrote: > On 17/08/17 23:07, Ilia Mirkin wrote: >> On Thu, Aug 17, 2017 at 6:03 PM, Colin King wrote: >>> From: Colin Ian King >>> >>> The null check on the array msto is incorrect since msto is never >>> null. The null check should be instead on msto[i] sinc

Re: [Nouveau] [PATCH][V2] drm/nouveau: perform null check on msto[i] rathern than msto

2017-08-17 Thread Ben Skeggs
On 08/18/2017 08:20 AM, Ben Skeggs wrote: > On 08/18/2017 08:16 AM, Colin Ian King wrote: >> On 17/08/17 23:07, Ilia Mirkin wrote: >>> On Thu, Aug 17, 2017 at 6:03 PM, Colin King >>> wrote: From: Colin Ian King The null check on the array msto is incorrect since msto is never