https://bugs.freedesktop.org/show_bug.cgi?id=91125
Ilia Mirkin imir...@alum.mit.edu changed:
What|Removed |Added
Summary|Nouveau read fault, locking |[NVE7] Nouveau read
https://bugs.freedesktop.org/show_bug.cgi?id=91125
exi+freedesk...@wthack.de changed:
What|Removed |Added
Summary|Nouveau read fault after|Nouveau read fault, locking
https://bugs.freedesktop.org/show_bug.cgi?id=89247
--- Comment #26 from exi+freedesk...@wthack.de ---
I just tested the latest linux-4.1 branch from
git://anongit.freedesktop.org/nouveau/linux-2.6 and this issue still persists
for me with this kernel and nouveau driver.
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=91125
--- Comment #1 from exi+freedesk...@wthack.de ---
Created attachment 116800
-- https://bugs.freedesktop.org/attachment.cgi?id=116800action=edit
complete yournal output including dmesg/kernel messages
I just got this bug again freezing up my
We only emit 58 words to the ring, not 60.
Signed-off-by: Ilia Mirkin imir...@alum.mit.edu
---
drm/nouveau/nvc0_fbcon.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drm/nouveau/nvc0_fbcon.c b/drm/nouveau/nvc0_fbcon.c
index 6124667..fcd2e5f 100644
---
https://bugs.freedesktop.org/show_bug.cgi?id=90887
--- Comment #20 from Ilia Mirkin imir...@alum.mit.edu ---
(In reply to jr from comment #19)
I do prefer the map based approach over this last attempt. Keeping track of
the relevant BB is quite obviously correct, but trying to keep track of edge
https://bugs.freedesktop.org/show_bug.cgi?id=90569
--- Comment #3 from Jedet Ilrihm je...@gmx.de ---
How should I test your implementation/fix?
--
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
Hello,
It seems that NVIDIA GPUs, at least starting with G80, have an
optimized path for the sequence
draw;
update consts;
draw;
update consts;
etc
Whereby it will start processing draw2 before draw1 is done. To do
this, it appears there's some magic constbuf cache on the chip which
buffers the
https://bugs.freedesktop.org/show_bug.cgi?id=90569
--- Comment #2 from Ilia Mirkin imir...@alum.mit.edu ---
Does this patch help at all?
http://lists.freedesktop.org/archives/nouveau/2015-June/021416.html
I believe the conditions are the same as the ones I hit...
25: 01 f2
The RING_SPACE macro accounts how much space is used up so it's
important to ask it for the right amount. Incorrect accounting of this
can cause page faults down the line as writes are attempted outside of
the ring.
Signed-off-by: Ilia Mirkin imir...@alum.mit.edu
Cc: sta...@vger.kernel.org
---
https://bugs.freedesktop.org/show_bug.cgi?id=90932
--- Comment #14 from Marcus Moeller marcus.moel...@gmx.ch ---
Created attachment 116784
-- https://bugs.freedesktop.org/attachment.cgi?id=116784action=edit
modesetting driver with latest Xorg updates
Latest test with vmlinuz-4.1.0-1, updated
Only 58 words get written to the ring, not 59. Also, normalize the accel
init wrt nvc0 and nv04 fbcon impls by firing the ring at accel init time
rather than waiting until later.
Signed-off-by: Ilia Mirkin imir...@alum.mit.edu
---
drm/nouveau/nv50_fbcon.c | 3 ++-
1 file changed, 2
On Thu, Jun 25, 2015 at 10:41 AM, Ilia Mirkin imir...@alum.mit.edu wrote:
Hello,
We recently tracked down a bug on Tesla GPUs (i.e. G80-GT218) whereby
it appears that instructions like
0028: b5000409 08000780 add rn f32 $r2 $r2 neg c0[$a1]
0040: b500060d 08004780 add rn f32
https://bugs.freedesktop.org/show_bug.cgi?id=91056
--- Comment #5 from Ilia Mirkin imir...@alum.mit.edu ---
(In reply to Ilia Mirkin from comment #4)
Created attachment 116707 [details] [review]
provisional fix
OK, so this patch appears to fix it. The shaders at the end of that opt
trace
https://bugs.freedesktop.org/show_bug.cgi?id=90932
--- Comment #15 from Ilia Mirkin imir...@alum.mit.edu ---
(In reply to Marcus Moeller from comment #14)
Created attachment 116784 [details]
modesetting driver with latest Xorg updates
Latest test with vmlinuz-4.1.0-1, updated
15 matches
Mail list logo
