https://bugs.freedesktop.org/show_bug.cgi?id=93458
Ilia Mirkin changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=93458
--- Comment #7 from Matt Whitlock ---
FYI: Ilia Mirkin submitted the patch from Comment 4 to the Nouveau listserv on
6 Mar 2016. I think I'll apply this patch to my 4.4.7 kernel.
http://permalink.gmane.org/gmane.comp.freedesktop.xorg.nouveau/240
https://bugs.freedesktop.org/show_bug.cgi?id=93458
--- Comment #6 from Matt Whitlock ---
(In reply to Matt Whitlock from comment #5)
> I would venture a guess that the memory allocated for a GPU FIFO buffer
> needs to be physically continuous, as it will be used for DMA
I take it back. Looking i
https://bugs.freedesktop.org/show_bug.cgi?id=93458
Matt Whitlock changed:
What|Removed |Added
CC||freedesk...@mattwhitlock.na
https://bugs.freedesktop.org/show_bug.cgi?id=93458
--- Comment #4 from Zlatko Calusic ---
Created attachment 121071
--> https://bugs.freedesktop.org/attachment.cgi?id=121071&action=edit
Use vzalloc instad of kzalloc in nvkm_ramht_new()
I've had lots of success using the attached patch. 4 days
https://bugs.freedesktop.org/show_bug.cgi?id=93458
--- Comment #3 from Pierre Moreau ---
I have seen this one as well on my G96 and MCP79, running 4.3.3. It seems to
happen once RAM has been filled (should it be with buffers kept around or by
applications currently running), even if SWAP is compl
https://bugs.freedesktop.org/show_bug.cgi?id=93458
--- Comment #2 from Sven Joachim ---
Same here on kernel 4.4.0-rc7, NV86 (GeForce 8500 GT). Right now even glxgears
produces the error:
[160746.465409] glxgears: page allocation failure: order:5, mode:0x26040c0
[160746.465415] CPU: 0 PID: 18218
https://bugs.freedesktop.org/show_bug.cgi?id=93458
--- Comment #1 from Stefan-W. Hahn ---
I can confirm this problem also for Kernel 4.3.3:
commit 35483418917d63df90bae5b2d0b7b047d7ed8ec7
Author: Greg Kroah-Hartman
Date: Mon Dec 14 21:41:43 2015 -0800
Linux 4.3.3
running nouveau with:
V
