search for: nv30_transfer

.../gallium/drivers/nv04/nv04_transfer.c | 6 ++++-- src/gallium/drivers/nv10/nv10_transfer.c | 6 ++++-- src/gallium/drivers/nv20/nv20_miptree.c | 5 ++++- src/gallium/drivers/nv20/nv20_transfer.c | 6 ++++-- src/gallium/drivers/nv30/nv30_miptree.c | 5 ++++- src/gallium/drivers/nv30/nv30_transfer.c | 6 ++++-- src/gallium/drivers/nv40/nv40_miptree.c | 5 ++++- src/gallium/drivers/nv40/nv40_transfer.c | 6 ++++-- 8 files changed, 32 insertions(+), 13 deletions(-) diff --git a/src/gallium/drivers/nv04/nv04_transfer.c b/src/gallium/drivers/nv04/nv04_transfer.c index 2dd2e14..f7a64f9...

...input size and 2048x2048 for its output. The code checking this was trying to be clever resulting in it seeing a surface of e.g 1024x256 being outside of the input size limit. This commit fixes this. Signed-off-by: Hans de Goede <hdegoede at redhat.com> --- src/gallium/drivers/nouveau/nv30/nv30_transfer.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/gallium/drivers/nouveau/nv30/nv30_transfer.c b/src/gallium/drivers/nouveau/nv30/nv30_transfer.c index 214da65..2452071 100644 --- a/src/gallium/drivers/nouveau/nv30/nv30_transfer.c +++ b/src/gallium/drivers/nouveau/nv30/n...

Hi there, Sometimes my computer crashes since i use now ubuntu 13.10 with unity/compiz. dmesg tells me: [ 686.209019] nouveau E[ PBUS][0000:00:0d.0] MMIO write of 0x00000000 FAULT at 0x00b020 and later: [ 1425.565441] nouveau E[ PGRAPH][0000:00:0d.0] ERROR nsource: DATA_ERROR nstatus: BAD_ARGUMENT [ 1425.565462] nouveau E[ PGRAPH][0000:00:0d.0] ch 3 [0x00056000 compiz[1970]] subc 2

.../nv30_fragtex.c | 8 +- src/gallium/drivers/nv30/nv30_miptree.c | 239 ---------------------------- src/gallium/drivers/nv30/nv30_screen.c | 13 +-- src/gallium/drivers/nv30/nv30_state.h | 13 -- src/gallium/drivers/nv30/nv30_state_fb.c | 20 ++-- src/gallium/drivers/nv30/nv30_transfer.c | 178 --------------------- src/gallium/drivers/nv40/Makefile | 2 - src/gallium/drivers/nv40/nv40_fragtex.c | 12 +- src/gallium/drivers/nv40/nv40_miptree.c | 235 --------------------------- src/gallium/drivers/nv40/nv40_screen.c | 13 +-- src/gallium/drivers/nv40...

.../nv30_fragtex.c | 8 +- src/gallium/drivers/nv30/nv30_miptree.c | 239 ---------------------------- src/gallium/drivers/nv30/nv30_screen.c | 13 +-- src/gallium/drivers/nv30/nv30_state.h | 13 -- src/gallium/drivers/nv30/nv30_state_fb.c | 20 ++-- src/gallium/drivers/nv30/nv30_transfer.c | 178 --------------------- src/gallium/drivers/nv40/Makefile | 2 - src/gallium/drivers/nv40/nv40_context.h | 2 +- src/gallium/drivers/nv40/nv40_fragtex.c | 12 +- src/gallium/drivers/nv40/nv40_miptree.c | 235 --------------------------- src/gallium/drivers/nv40/...

...14 0x031dc000 > PITCH_IN => 52281344 lookup seems not to work, the package 'lookup' seems to be a different tool, right? > I'm sure that's above some limit. A pitch of 50MB... I wonder how > that's happening... If you feel like debugging, the place to look is > nv30_transfer.c (in mesa). Although I would think this would merely > cause misrendering, not crashes. I'm not going to do that, because I really not that competent for that, even if i know about c programming. I also think that this can cause missrendering, and not crashes, but it also seems that ther...

...mthd 0x0314 data 0x031dc000 A bit more concerning: $ lookup -a 4c -d NV01_SUBCHAN -- -v obj-class NV03_M2MF 0x0314 0x031dc000 PITCH_IN => 52281344 I'm sure that's above some limit. A pitch of 50MB... I wonder how that's happening... If you feel like debugging, the place to look is nv30_transfer.c (in mesa). Although I would think this would merely cause misrendering, not crashes. > > So I don't really know where to start for debugging, > if you could help me that would be great. > > Full dmesg output on http://ubuntuone.com/3AVhp6HT2jU26HdfguAbdV > > thanks, >...

...it, I was just using it to decode that error message to figure out what command triggered the bad argument error. > > >> I'm sure that's above some limit. A pitch of 50MB... I wonder how >> that's happening... If you feel like debugging, the place to look is >> nv30_transfer.c (in mesa). Although I would think this would merely >> cause misrendering, not crashes. > > > I'm not going to do that, because I really not that competent for that, even > if i know about c programming. > > I also think that this can cause missrendering, and not crash...

https://bugs.freedesktop.org/show_bug.cgi?id=109371 Bug ID: 109371 Summary: Textures seem to be byteswapped on big endian architectures Product: Mesa Version: 18.3 Hardware: PowerPC OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=99354 Bug ID: 99354 Summary: [G71] "Assertion `bkref' failed" reproducible with glmark2 Product: Mesa Version: 13.0 Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/gallium/drivers/nouveau/nouveau_buffer.c | 4 +--- src/gallium/drivers/nouveau/nouveau_context.h | 1 - 2 files changed, 1 insertion(+), 4 deletions(-) diff --git a/src/gallium/drivers/nouveau/nouveau_buffer.c b/src/gallium/drivers/nouveau/nouveau_buffer.c index e308ff4..904e2cc 100644 ---

https://bugs.freedesktop.org/show_bug.cgi?id=27603 Summary: [nouveau] Celestia 1.6.0 crashes with nv04_surface_copy_swizzle assertion Product: Mesa Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: