similar to: [Bug 97021] New: Screen locks up randomly while only mouse pointer moves, system responsive via ssh

Hi, On 04-12-15 09:54, Samuel Pitoiset wrote: > > > On 12/04/2015 09:45 AM, Hans de Goede wrote: <snip> >>> Please give a shot at this branch : >>> http://cgit.freedesktop.org/~hakzsam/mesa/log/?h=nvf0_compute >>> >>> It fixes the initialization of the compute state and allows me to >>> launch 'test_input_global' (ie. ./compute

https://bugs.freedesktop.org/show_bug.cgi?id=98138 Bug ID: 98138 Summary: Random Freeze - nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=96553 --- Comment #2 from simonF <simonfalicon at gmail.com> --- I have same trouble my computer freeze, I can mouve mouse but nothing else. in my log: Oct 28 16:07:12 simon-Precision-T1700 kernel: [ 2191.290651] nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Oct 28 16:07:12 simon-Precision-T1700 kernel: [ 2191.290656] nouveau

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

I begin to find a way that help me investigate fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] errors. See https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/339 I believe this affects mostly Fermi, Kepler and Maxwell1 graphic cards. I'd like first to describe a bit how I proceed, then talk about separating this issue in many. I am working on Gnome Debian Testing. This environment

https://bugs.freedesktop.org/show_bug.cgi?id=96562 Bug ID: 96562 Summary: nouveau crashes with SCHED_ERROR 0a [CTXSW_TIMEOUT] Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=96553 --- Comment #1 from Agostino Sarubbo <ago at gentoo.org> --- When the problem happens, In dmesg there is the following messages: [11449.585126] nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] [11449.585132] nouveau 0000:01:00.0: fifo: sw engine fault on channel 2, recovering... [11451.584882] nouveau 0000:01:00.0: fifo: runlist

https://bugs.freedesktop.org/show_bug.cgi?id=96802 Bug ID: 96802 Summary: Upgrading mesa from 11.0.6 -> 11.2.2 causes graphics deadlock Product: Mesa Version: 11.2 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component:

On (06/14/19 11:50), Sergey Senozhatsky wrote: > dmesg > > nouveau 0000:01:00.0: DRM: GPU lockup - switching to software fbcon > nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] > nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery > nouveau 0000:01:00.0: fifo: channel 5: killed > nouveau 0000:01:00.0: fifo: engine 6: scheduled for recovery >

https://bugs.freedesktop.org/show_bug.cgi?id=99202 Bug ID: 99202 Summary: system freeze - fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] - MULTIPLE_WARP_ERRORS - DATA_ERROR 00000004 [INVALID_VALUE] - ILLEGAL_CLASS ch 11 - RT_STORAGE_TYPE_MISMATCH - CLASS_SUBCH_MISMATCH Product: xorg Version: unspecified

On Wed, Jun 19, 2019 at 1:08 AM Sergey Senozhatsky <sergey.senozhatsky.work at gmail.com> wrote: > > On (06/14/19 11:50), Sergey Senozhatsky wrote: > > dmesg > > > > nouveau 0000:01:00.0: DRM: GPU lockup - switching to software fbcon > > nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] > > nouveau 0000:01:00.0: fifo: runlist 0: scheduled for

5.2.0-rc4-next-20190613 dmesg nouveau 0000:01:00.0: DRM: GPU lockup - switching to software fbcon nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery nouveau 0000:01:00.0: fifo: channel 5: killed nouveau 0000:01:00.0: fifo: engine 6: scheduled for recovery nouveau 0000:01:00.0: fifo: engine 0: scheduled for recovery

https://bugs.freedesktop.org/show_bug.cgi?id=92922 Bug ID: 92922 Summary: Xorg random freeze Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau Assignee: nouveau at

In https://nouveau.freedesktop.org/KernelModuleParameters.html, there is: Here is a list of engines: DEVICE DMAOBJ PBSP PCE0 PCE1 PCE2 PCRYPT PDISP PFIFO PGRAPH PMPEG PPM PPPP PVP SW Also, in debug: CLIENT I have tried to find a description of those. https://envytools.readthedocs.io/en/latest/ help a bit, but I don't find a

On Mon, 4 Dec 2023 at 05:04, Paul Dufresne <dufresnep at zoho.com> wrote: > > In https://nouveau.freedesktop.org/KernelModuleParameters.html, there is: > Here is a list of engines: > DEVICE > DMAOBJ > PBSP > PCE0 > PCE1 > PCE2 > PCRYPT > PDISP > PFIFO > PGRAPH > PMPEG > PPM > PPPP > PVP

Hi, Using 3 monitors on the GeForce GTX 650 Ti card (2 DVI and 1 VGA) works great out of the box on Fedora 20. However, every couple of days the graphics driver seems to crash. The same thing used to happen when 2 monitors were in use, but that has pretty much stabilized as of late. Does anyone have a stable setup with this card using 3 monitors? Will 3 monitors be supported? Thanks, Rob $

https://bugs.freedesktop.org/show_bug.cgi?id=99900 --- Comment #18 from andrewb03 at gmail.com --- According to the HangDiagnosis page - https://nouveau.freedesktop.org/wiki/HangDiagnosis - this is my crash level: Display is frozen in X, but mouse cursor moves. SSH works as well but keyboard freezes so I'm forced to either reboot the PC via ssh or restart X via ssh. Any updates on this bug?

On (06/19/19 01:20), Ilia Mirkin wrote: > On Wed, Jun 19, 2019 at 1:08 AM Sergey Senozhatsky > <sergey.senozhatsky.work at gmail.com> wrote: > > > > On (06/14/19 11:50), Sergey Senozhatsky wrote: > > > dmesg > > > > > > nouveau 0000:01:00.0: DRM: GPU lockup - switching to software fbcon > > > nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a

Well, I downgraded back to 2 monitors and it turns out that this problem has reappeared when using only 2 monitors as well. There must have been a regression of some sort somewhere along the line, possibly in one of the latest kernels? What can I provide to help this issue get fixed? -Rob > On Dec 5, 2014, at 8:07 AM, Rob Jansen <rob.g.jansen at nrl.navy.mil> wrote: > > Hi, >

On Wed, Jun 19, 2019 at 1:48 AM Sergey Senozhatsky <sergey.senozhatsky.work at gmail.com> wrote: > > On (06/19/19 01:20), Ilia Mirkin wrote: > > On Wed, Jun 19, 2019 at 1:08 AM Sergey Senozhatsky > > <sergey.senozhatsky.work at gmail.com> wrote: > > > > > > On (06/14/19 11:50), Sergey Senozhatsky wrote: > > > > dmesg > > > >