search for: pushbuf_valid

...iled. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- nouveau/pushbuf.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nouveau/pushbuf.c b/nouveau/pushbuf.c index ff8e125..e720a08 100644 --- a/nouveau/pushbuf.c +++ b/nouveau/pushbuf.c @@ -524,7 +524,7 @@ pushbuf_validate(struct nouveau_pushbuf *push, bool retry) } } - return 0; + return ret; } int -- 1.8.1.4

...nouveau_dri.so nv50_bufctx_fence 385793 100.000 nv50_context.c:409 nouveau_dri.so nv50_bufctx_fence [self] ------------------------------------------------------------------------------- 151037 20.7947 pushbuf.c:482 libdrm_nouveau.so.2.0.0 pushbuf_validate 151037 100.000 pushbuf.c:482 libdrm_nouveau.so.2.0.0 pushbuf_validate [self] ------------------------------------------------------------------------------- 83835 11.5423 pushbuf.c:149 libdrm_nouveau.so.2.0.0 pushbuf_kref 83835 100.000 pushbuf.c:149...

...EM_PUSHBUF2 0x45 #if defined(__cplusplus) } diff --git a/nouveau/nouveau.h b/nouveau/nouveau.h index 335ce77dca77..70d680700faf 100644 --- a/nouveau/nouveau.h +++ b/nouveau/nouveau.h @@ -226,6 +226,8 @@ void nouveau_pushbuf_reloc(struct nouveau_pushbuf *, struct nouveau_bo *, int nouveau_pushbuf_validate(struct nouveau_pushbuf *); uint32_t nouveau_pushbuf_refd(struct nouveau_pushbuf *, struct nouveau_bo *); int nouveau_pushbuf_kick(struct nouveau_pushbuf *, struct nouveau_object *chan); +int nouveau_pushbuf_kick_fence(struct nouveau_pushbuf *, + struct nouveau_obj...

...efine __NOUVEAU_LIBDRM_PRIVATE_H__ +#include <libdrm.h> #include <xf86drm.h> #include <xf86atomic.h> #include <pthread.h> diff --git a/nouveau/pushbuf.c b/nouveau/pushbuf.c index 4f77881..6e703a4 100644 --- a/nouveau/pushbuf.c +++ b/nouveau/pushbuf.c @@ -529,7 +529,7 @@ pushbuf_validate(struct nouveau_pushbuf *push, bool retry) return ret; } -int +drm_public int nouveau_pushbuf_new(struct nouveau_client *client, struct nouveau_object *chan, int nr, uint32_t size, bool immediate, struct nouveau_pushbuf **ppush) @@ -600,7 +600,7 @@ nouveau_pushbuf_new(struct n...

...stack trace of the segfault with gdb: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xc3dfeb40 (LWP 9387)] 0xf689a323 in pushbuf_kref () from /usr/lib32/libdrm_nouveau.so.2 (gdb) bt #0 0xf689a323 in pushbuf_kref () from /usr/lib32/libdrm_nouveau.so.2 #1 0xf689ab9f in pushbuf_validate () from /usr/lib32/libdrm_nouveau.so.2 #2 0xf6ce47e8 in nv50_state_validate () from /usr/lib32/dri/nouveau_dri.so #3 0xf6cf0a49 in nv50_draw_vbo () from /usr/lib32/dri/nouveau_dri.so #4 0xf6b3846d in cso_draw_vbo () from /usr/lib32/dri/nouveau_dri.so #5 0xf6a5f29e in st_draw_vbo () from /usr...

...<optimized out>) at pushbuf.c:325 #6 0xb5b8a39a in pushbuf_flush (push=push at entry=0x8614038) at pushbuf.c:402 #7 0xb5b8ad27 in nouveau_pushbuf_space (push=push at entry=0x8614038, dwords=0, relocs=0, pushes=<optimized out>, pushes at entry=0) at pushbuf.c:676 #8 0xb5b8ade3 in pushbuf_validate (push=0x8614038, retry=<optimized out>) at pushbuf.c:492 #9 0xb5b8b13e in nouveau_pushbuf_validate (push=0x8614038) at pushbuf.c:749 #10 0xb5cf3906 in nvc0_state_validate (nvc0=nvc0 at entry=0x8625880, mask=mask at entry=4294967295, words=words at entry=8) at nvc0/nvc0_state_...

...thread (arg=0x7f2105ffb700) at pthread_create.c:333 #14 0x00007f2178e83f6f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 19 (Thread 0x7f21067fc700 (LWP 6603)): [KCrash Handler] #6 0x00007f214d47c22f in pushbuf_kref () from /lib64/libdrm_nouveau.so.2 #7 0x00007f214d47c8b9 in pushbuf_validate () from /lib64/libdrm_nouveau.so.2 #8 0x00007f214e0b1dc3 in nv50_blit () from /usr/lib64/dri/nouveau_dri.so #9 0x00007f214dcc67f7 in st_TexSubImage () from /usr/lib64/dri/nouveau_dri.so #10 0x00007f214dc4b5db in _mesa_texture_sub_image () from /usr/lib64/dri/nouveau_dri.so #11 0x00007f214dc4b8...

Hi guys, I'd like to start a new thread about explicit fence synchronization. This time with a Nouveau twist. :-) First, let me define what I understand by implicit/explicit sync: Implicit synchronization * Fences are attached to buffers * Kernel manages fences automatically based on buffer read/write access Explicit synchronization * Fences are passed around independently * Kernel takes

https://bugs.freedesktop.org/show_bug.cgi?id=71116 Priority: medium Bug ID: 71116 Assignee: nouveau at lists.freedesktop.org Summary: [Ubuntu userspace upgrade 13.04 -> 13.10][regression] NV34 card fails to properly resume. QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified