similar to: [Bug 76414] New: [NVE4] Flash player triggers freeze with: PFIFO: read fault at ... [UNSUPPORTED_KIND] from PBDMA0/HOST ...

From: Martin Peres <martin.peres at labri.fr> This should fix a deadlock that has been reported to us where fan_update() would hold the fan lock and try to grab the alarm_program_lock to reschedule an update. On an other CPU, the alarm_program_lock would have been taken before calling fan_update(), leading to a deadlock. We should Cc: <stable at vger.kernel.org> # 3.9+ Reported-by:

https://bugs.freedesktop.org/show_bug.cgi?id=92833 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|nouveau E[ |[NV117] nouveau E[ |PFIFO][0000:01:00.0] read |PFIFO][0000:01:00.0] read

https://bugs.freedesktop.org/show_bug.cgi?id=92833 Aaron Plattner <aplattner at nvidia.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Driver/nVidia (open) |Driver/nouveau Assignee|aplattner at nvidia.com |nouveau at lists.freedesktop.o

https://bugs.freedesktop.org/show_bug.cgi?id=92833 --- Comment #2 from barry at barrys-emacs.org --- (In reply to Ilia Mirkin from comment #1) > Are those the first messages? There where some info ones. (sorry I've lost the setup for the moment to repro this). > What kernel are you using? Or to rephrase, > does this still happen with kernel 4.3.0? F23 is on 4.2.5. I will see if I

https://bugs.freedesktop.org/show_bug.cgi?id=92833 --- Comment #3 from barry at barrys-emacs.org --- I can run with kernel 4.4.2-301.fc23.x86_64 and xorg-x11-drv-nouveau-1.0.12-3.fc23.x86_64 and have not seen this problem. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=92833 --- Comment #4 from Mike <bugs.freedesktop.org at pm.port0.org> --- I'm hitting this bug with kernel 4.4.3-amd64 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.3-wily/ There were pure X server (no DM) and three apps: two OpenGL and one Flash - all of them decoding and displaying video. Video stopped on three screens after

https://bugs.freedesktop.org/show_bug.cgi?id=92833 --- Comment #5 from Mike <bugs.freedesktop.org at pm.port0.org> --- Created attachment 122098 --> https://bugs.freedesktop.org/attachment.cgi?id=122098&action=edit part of syslog -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed...

https://bugs.freedesktop.org/show_bug.cgi?id=92833 --- Comment #6 from Mike <bugs.freedesktop.org at pm.port0.org> --- Created attachment 122099 --> https://bugs.freedesktop.org/attachment.cgi?id=122099&action=edit xorg log -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=92833 --- Comment #7 from Mike <bugs.freedesktop.org at pm.port0.org> --- Created attachment 122100 --> https://bugs.freedesktop.org/attachment.cgi?id=122100&action=edit some logs from app I'll also try kernel 4.5-rc6 -- You are receiving this mail because: You are the assignee for the bug. -------------- next part --------------

https://bugs.freedesktop.org/show_bug.cgi?id=92833 Martin Peres <martin.peres at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED --- Comment #8 from Martin Peres

From: Martin Peres <martin.peres at labri.fr> This should fix a deadlock that has been reported to us where fan_update() would hold the fan lock and try to grab the alarm_program_lock to reschedule an update. On an other CPU, the alarm_program_lock would have been taken before calling fan_update(), leading to a deadlock. Reported-by: Marcin Slusarz <marcin.slusarz at gmail.com>

https://bugs.freedesktop.org/show_bug.cgi?id=90276 Bug ID: 90276 Summary: [NVE6] nouveau E[ PFIFO][0000:01:00.0] read fault at 0x000a5c0000 [UNSUPPORTED_KIND] from CE2/GR_CE on channel 0x007f329000 [unknown] Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All)

https://bugs.freedesktop.org/show_bug.cgi?id=98525 Bug ID: 98525 Summary: nouveau graphics freeze when using KDE Plasma 5 with "fifo: PBDMA0: 00200000 subc 0 mthd 000c data 00000000" Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status:

https://bugs.freedesktop.org/show_bug.cgi?id=91988 Bug ID: 91988 Summary: nouveau causes complete system hang - SCHED_ERROR CTXSW_TIMEOUT PGRAPH engine fault PBDMA0 ACQUIRE Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: All Status: NEW Severity: normal

Dear list users, I was wondering if there is any way to know, for an open graphical peripheric, the instruction that was used to call it. For example, if I create a plot using plot(runif(10)) is there any way to have the call returned to me? That would be especially usefull to know it there are any log axes, for example thanks t --------------------------------------- Timothée POISOT -

https://bugs.freedesktop.org/show_bug.cgi?id=73373 Priority: medium Bug ID: 73373 Assignee: nouveau at lists.freedesktop.org Summary: [NVE4] GPU lockup after opening many tabs in Chromium web browser Severity: blocker Classification: Unclassified OS: Linux (All) Reporter: mbarrera at gmx.com

https://bugs.freedesktop.org/show_bug.cgi?id=103467 Bug ID: 103467 Summary: [NVC0/GF108] fifo: read fault at cd90f4d000 engine 07 [PFIFO] client 07 [BAR_READ] reason 00 [PT_NOT_PRESENT] on channel 1 [003fe11000 DRM] Product: xorg Version: 7.7 (2012.06) Hardware: PowerPC OS: All

https://bugs.freedesktop.org/show_bug.cgi?id=89985 Bug ID: 89985 Summary: system video hangs on video switch to fullscreen Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component: Drivers/DRI/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=84721 --- Comment #14 from Krzysztof Katowicz-Kowalewski <vnd at vndh.net> --- After 7 tries... here's the culprit: localhost linux # git bisect good 0e994d645627bb67088ae4860e9a0295b123f7b0 is the first bad commit commit 0e994d645627bb67088ae4860e9a0295b123f7b0 Author: Martin Peres <martin.peres at labri.fr> Date: Wed Feb 19

Detect and workaround the absence of a power device so chips that do not feature one (e.g. GK20A) can still use this driver. Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> --- nvkm/engine/graph/nve4.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/nvkm/engine/graph/nve4.c b/nvkm/engine/graph/nve4.c index 1ba6666da4e5..fb9cb929320d 100644 ---