similar to: [Bug 56474] New: 3D app segfaults on NV46

Hi Arno, I think at this point the most helpful thing would be to get an apitrace (https://github.com/apitrace/apitrace) with your "fix" in place. Once you make the trace, change your fix to instead abort the program, and replay the trace. This will allow us to look at the precise call sequence that causes the issue. What is the numerical value of ve->vertex_buffer_index when

Requesting a new real buffer from the kernel and copying all the data is wasteful e.g. if only a few (but widely spread) vertices are accessed. --- src/gallium/drivers/nv50/nv50_context.h | 3 + src/gallium/drivers/nv50/nv50_vbo.c | 409 +++++++++++++++++++++++++++++-- 2 files changed, 394 insertions(+), 18 deletions(-) diff --git a/src/gallium/drivers/nv50/nv50_context.h

Clearing can happen at a time when various state objects are incoherent and not ready for a draw. Some of the validation functions don't handle this well, so only flush the framebuffer state. This has the advantage of also not doing extra work. This works around some crashes that can happen when clearing. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> ---

Suspend to RAM works perfectly with NV40/NV46 (Geforce Go 7400), but not suspend to disk (hibernation). The resume after suspend to disk (hibernation) has as a result, a black screen and it freezes ever keyboard.... Only solution then, is hard poweroff... Is suspend to disk (hibernation) supported with NV40/NV46 ?

http://bugs.freedesktop.org/show_bug.cgi?id=24925 Summary: X server freeze on NV46 Product: xorg Version: 7.5 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:

Hi, While trying to reproduce: https://bugzilla.redhat.com/show_bug.cgi?id=1325667 I also gave glxgears a quick test with mesa master, this resulted in the following errors being printed to the terminal from which glxgears was started : unknown fragment shader param 17 unknown fragment shader param 17 unknown fragment shader param 17 unknown fragment shader param 17 unknown fragment shader

https://bugs.freedesktop.org/show_bug.cgi?id=85444 Bug ID: 85444 Summary: [NV46] Heavy corruption, no hardfreeze, back to console and libexa.so segfault Product: xorg Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=80145 Priority: medium Bug ID: 80145 Assignee: nouveau at lists.freedesktop.org Summary: [NV46] GPU lockup - switching to software fbcon QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter:

https://bugs.freedesktop.org/show_bug.cgi?id=95429 Bug ID: 95429 Summary: NV46 G72M picture is always distorted on VGA output Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

MSI interrupts appear to not work for nv46 based cards. Change the mc subdev oclass for these cards from nv44 to nv4c, the nv4c mc code is identical to the nv44 mc code except that it does not use msi (it does not define a msi_rearm callback). BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=90435 Signed-off-by: Hans de Goede <hdegoede at redhat.com> ---

Hi All, So I've been working~w banging my head against the nv46 vblank bug again and I've been finding out some interesting things. This is all using the latest kernel + ddx + mesa code. All of this was tested with *cold* (power removed from wall outlet for 20 seconds) boots in between the scenarios because this is really weird, all boots where into text mode. Scenario 1: a) startx

https://bugs.freedesktop.org/show_bug.cgi?id=109529 Bug ID: 109529 Summary: [NV46] unable to handle kernel paging request Product: Mesa Version: 18.2 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

Hi, On 24-07-15 04:32, Ben Skeggs wrote: > On 24 July 2015 at 01:20, Hans de Goede <hdegoede at redhat.com> wrote: >> MSI interrupts appear to not work for nv46 based cards. Change the mc >> subdev oclass for these cards from nv44 to nv4c, the nv4c mc code is >> identical to the nv44 mc code except that it does not use msi >> (it does not define a msi_rearm

https://bugs.freedesktop.org/show_bug.cgi?id=95095 Bug ID: 95095 Summary: NV46 (G72) Full screen artifacts in Freespace 2 SW OT mod Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau

- 'joi' on irc pointed out that this triggers a BUG_ON, because kzalloc could sleep. - The irq handler should restore the value NV03_PFIFO_CACHES, but still it's better if this stuff doesn't happen in the middle of fifo create context. I see no reason in spin locking pgraph create context, it isn't activated at that stage. - Move and rename the lock after some discussion with

https://bugs.freedesktop.org/show_bug.cgi?id=88893 Bug ID: 88893 Summary: [NV46] GPU lockup with Quadro NVS 110M Product: xorg Version: 7.7 (2012.06) Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau Assignee:

I am trying to use ggplot to plot the data, and R code, below. The dates (jdate) are printing as Mar 01, Mar 15, etc. I want to have the date printed as MMM DD YYYY (or any other way that will show month, date, and year, e.g. mm/dd/yy). How can I accomplish this? yyy <- structure(list( jdate = structure(c(19052, 19053, 19054, 19055, 19058, 19059, 19060, 19061, 19062,

http://bugs.freedesktop.org/show_bug.cgi?id=23445 Summary: NV46: GPU lockup on VT switch Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

The current code for primitive splitting and emission on pre-nv50 is severely broken. In particular: 1. Quads and lines are totally broken because "&= 3" should be "&= ~3" and similar for lines 2. Triangle fans and polygons are broken because the first vertex must be repeated for each split chunk 3. Line loops are broken because the must be converted to a line strip,

A reworked version of 3 out of 4 patches mentioned earlier. [1/4]: Fixes nearly all piglit vertprog testcases, due to now being able to pass the results on to the fragment shader. V2: rename samplers to texcoords. [2/4]: Fixes shader compiler assertion errors, as some source registers do not exist for certain operations. Fixes several piglit tests when mesa is compiled with --enable-debug [3/4]: