similar to: [Bug 93254] New: [NVA5] The Long Dark (game) is very slow because of "kernel rejected pushbuf" messages in log files

Displaying 20 results from an estimated 1000 matches similar to: "[Bug 93254] New: [NVA5] The Long Dark (game) is very slow because of "kernel rejected pushbuf" messages in log files"

2015 Oct 16
37
[Bug 92504] New: [NVA5] Corruption in Plasma 5 on resume after changing screen configuration
https://bugs.freedesktop.org/show_bug.cgi?id=92504 Bug ID: 92504 Summary: [NVA5] Corruption in Plasma 5 on resume after changing screen configuration Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium
2016 Apr 21
0
nouveau: kernel rejected pushbuf: Invalid argument
If you (or Java, behind your back) is using an indirect draw, that could explain the failures - I only got those "fully" right fairly recently. These, and a few other matters, should be fixed with a more recent mesa version - 11.2.1 was just released, I'd recommend trying with that. Another simple explanation is if your application is multithreaded and is drawing concurrently from
2016 Apr 21
0
nouveau: kernel rejected pushbuf: Invalid argument
On Thu, Apr 21, 2016 at 11:17 AM, Li, Stephen <Steve.Li at imaginecommunications.com> wrote: > Hi, > > > > I am getting a crash in nouveau in my application. It’s basically a java > application, and I am loading a bitmap into an opengl texture and showing it > in a panel. Below is a snippet of the console output. Sometimes I will get a > lock up instead of a crash. My
2018 Sep 17
6
[Bug 107963] New: kernel rejected pushbuf: Invalid argument
https://bugs.freedesktop.org/show_bug.cgi?id=107963 Bug ID: 107963 Summary: kernel rejected pushbuf: Invalid argument Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at
2013 Jul 06
4
[Bug 66642] New: [nva5] Wrong provoking vertex is selected for flat attribute interpolation (clipping?)
https://bugs.freedesktop.org/show_bug.cgi?id=66642 Priority: medium Bug ID: 66642 Assignee: nouveau at lists.freedesktop.org Summary: [nva5] Wrong provoking vertex is selected for flat attribute interpolation (clipping?) Severity: normal Classification: Unclassified OS: Linux (All) Reporter:
2014 Jun 23
0
[Mesa-dev] [PATCH try 2 2/2] gallium/nouveau: move pushbuf and fences to context
op 21-06-14 14:12, Ilia Mirkin schreef: > On Tue, Jun 17, 2014 at 2:34 AM, Maarten Lankhorst > <maarten.lankhorst at canonical.com> wrote: >> nv30 seems to not support dma objects with offset, so simply extend the query_heap to cover the >> entire notifier, and use a offset in nv30_context_kick_notify. > It would be great if you could detail the list of transformations
2014 Jun 23
0
[Mesa-dev] [PATCH try 2 2/2] gallium/nouveau: move pushbuf and fences to context
op 23-06-14 09:24, Ben Skeggs schreef: > On Mon, Jun 23, 2014 at 5:17 PM, Maarten Lankhorst > <maarten.lankhorst at canonical.com> wrote: >> op 21-06-14 14:12, Ilia Mirkin schreef: >>> On Tue, Jun 17, 2014 at 2:34 AM, Maarten Lankhorst >>> <maarten.lankhorst at canonical.com> wrote: >>>> nv30 seems to not support dma objects with offset, so
2009 Aug 22
1
concern about bo "pinned'ness" after gem pushbuf is done
As far as i see, we reserve the bo in the gem pushbuf ioctl, and unreserve after the pushbuf and the fence have been emitted. This assumption holds if bo moves happen on the same channel or if a cpu copy happens and we're waiting on fences. But for nv50 it is very common for the bo move to happen on the kernel fifo, which does not guarantee anything. Is there any safety i missed? Maarten.
2016 Apr 21
2
nouveau: kernel rejected pushbuf: Invalid argument
Hi, I am getting a crash in nouveau in my application. It's basically a java application, and I am loading a bitmap into an opengl texture and showing it in a panel. Below is a snippet of the console output. Sometimes I will get a lock up instead of a crash. My whole desktop will lock up, but I can still move the mouse pointer around. Please let me know if you need more information. Your
2014 Jun 23
2
[Mesa-dev] [PATCH try 2 2/2] gallium/nouveau: move pushbuf and fences to context
On Mon, Jun 23, 2014 at 5:17 PM, Maarten Lankhorst <maarten.lankhorst at canonical.com> wrote: > op 21-06-14 14:12, Ilia Mirkin schreef: >> On Tue, Jun 17, 2014 at 2:34 AM, Maarten Lankhorst >> <maarten.lankhorst at canonical.com> wrote: >>> nv30 seems to not support dma objects with offset, so simply extend the query_heap to cover the >>> entire
2016 Apr 21
2
nouveau: kernel rejected pushbuf: Invalid argument
Thanks for your response. I am able to capture a few more lines of the dump (see console-output.txt). dmesg output attached. My bitmap is 720x512. Below is the library versions, and amount of vram. Any feedback is appreciated. Thanks. Steve [steve at localhost ~]$ lspci -nn -d 10de: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) 01:00.1
2009 Sep 06
3
[Bug 23741] New: Driver pixmaps cause pushbuf validation failure on mode change (nv28, KMS)
http://bugs.freedesktop.org/show_bug.cgi?id=23741 Summary: Driver pixmaps cause pushbuf validation failure on mode change (nv28, KMS) Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau
2014 Jun 17
0
[PATCH try 2 2/2] gallium/nouveau: move pushbuf and fences to context
nv30 seems to not support dma objects with offset, so simply extend the query_heap to cover the entire notifier, and use a offset in nv30_context_kick_notify. Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- src/gallium/drivers/nouveau/nouveau_buffer.c | 14 +- src/gallium/drivers/nouveau/nouveau_context.h | 5 +
2014 Jun 21
3
[Mesa-dev] [PATCH try 2 2/2] gallium/nouveau: move pushbuf and fences to context
On Tue, Jun 17, 2014 at 2:34 AM, Maarten Lankhorst <maarten.lankhorst at canonical.com> wrote: > nv30 seems to not support dma objects with offset, so simply extend the query_heap to cover the > entire notifier, and use a offset in nv30_context_kick_notify. It would be great if you could detail the list of transformations that were done in the commit description, as well as what the
2013 May 23
2
[Bug 64888] New: [nva5] Garbage rendering in Portal
https://bugs.freedesktop.org/show_bug.cgi?id=64888 Priority: medium Bug ID: 64888 Assignee: nouveau at lists.freedesktop.org Summary: [nva5] Garbage rendering in Portal Severity: normal Classification: Unclassified OS: All Reporter: chrisf at ijw.co.nz Hardware: Other Status: NEW
2012 Apr 23
5
[Bug 49086] New: nouveau — Gallium 0 . 4 on NVA5 — 2 .1 Mesa 8.0.2 crashes Firefox Nightly
https://bugs.freedesktop.org/show_bug.cgi?id=49086 Bug #: 49086 Summary: nouveau ? Gallium 0.4 on NVA5 ? 2.1 Mesa 8.0.2 crashes Firefox Nightly Classification: Unclassified Product: Mesa Version: 8.0 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal
2013 Sep 04
0
[PATCH 1/2] drm/nouveau/bios/therm: handle vbioses with duplicate entries (mostly nva5)
On Sat, Aug 31, 2013 at 9:58 AM, Martin Peres <martin.peres at free.fr> wrote: > From: Martin Peres <martin.peres at labri.fr> > > Some vbioses have extra useless entries after "the end" of the table. This is > problematic since all of the vbios I found with this issue redefine the > pwm freq divider to insane levels (52750 Hz instead of 2500), thus breaking
2010 Feb 19
2
[PATCH 1/2] drm/nouveau: Unmap pushbuf BOs when we're done with them.
If you're especially unlucky BOs would move around and their kmaps would end up pointing to something else in GART, then ioctl_pushbuf() would use the kmaps again corrupting textures or other pushbufs (the most noticeable symptom was a PFIFO_DMA_PUSHER from time to time). Signed-off-by: Francisco Jerez <currojerez at riseup.net> --- drivers/gpu/drm/nouveau/nouveau_gem.c | 2 ++ 1
2014 Sep 06
19
[Bug 83550] New: [NVA5] Monitor not restored after resume [regression]
https://bugs.freedesktop.org/show_bug.cgi?id=83550 Priority: medium Bug ID: 83550 Assignee: nouveau at lists.freedesktop.org Summary: [NVA5] Monitor not restored after resume [regression] QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter:
2016 Mar 28
19
[Bug 94727] New: nouveau/pushbuf.c:238: pushbuf_krel: Assertion `bkref` failed.
https://bugs.freedesktop.org/show_bug.cgi?id=94727 Bug ID: 94727 Summary: nouveau/pushbuf.c:238: pushbuf_krel: Assertion `bkref` failed. Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium