search for: fb_flush_timeout

...been reading mail on the second desktop, then tried to go back to the first to check progress. After waiting a little I rebooted. The system log had what I thought was a lot of output (about 50000 lines, I think), starting Mar 28 16:39:00 origin kernel: [41644.858087] nouveau 0000:26:00.0: fifo: FB_FLUSH_TIMEOUT Mar 28 16:40:02 origin kernel: [41707.692180] nouveau 0000:26:00.0: fifo: FB_FLUSH_TIMEOUT Mar 28 16:40:02 origin kernel: [41707.692215] nouveau 0000:26:00.0: fifo: CHSW_ERROR 00000001 Mar 28 16:40:02 origin kernel: [41707.692264] nouveau 0000:26:00.0: fifo: CHSW_ERROR 00000003 Mar 28 16:40:16 orig...

...;-( >From these failures I have extracted the following from my syslog, several (but not all) show UNSUPPORTED_KIND. The 'scheduled for recovery' messages imply it might self-correct, but it doesn't seem to. Mar 28 18:50:05 origin kernel: [ 7715.267689] nouveau 0000:26:00.0: fifo: FB_FLUSH_TIMEOUT Mar 28 18:50:05 origin kernel: [ 7715.273911] nouveau 0000:26:00.0: fifo: write fault at 0003228000 engine 1b [CE2] client 18 [GR_CE] reason 0c [UNSUPPORTED_KIND] on channel 2 [003fbfa000 Xorg[22520]] Mar 28 18:50:05 origin kernel: [ 7715.273921] nouveau 0000:26:00.0: fifo: channel 2: killed Mar 28...

On Sun, May 29, 2016 at 12:22 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Sun, May 29, 2016 at 3:07 PM, Andy Lutomirski <luto at kernel.org> wrote: >> On Sat, May 28, 2016 at 5:48 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >>> Do you have mesa 11.2 or later? GM20x support was only added in mesa 11.2. >>> >> >> I just upgraded

...y with >> actual valid test results. >> > > I replaced the monitor (turns out that my monitor had a known DP > problem), and now the screen lights up reliably. I still get Great to hear! > occasional log lines like this: > > [Jun26 09:25] nouveau 0000:09:00.0: fifo: FB_FLUSH_TIMEOUT > [Jun26 09:30] nouveau 0000:09:00.0: fifo: FB_FLUSH_TIMEOUT > [Jun26 09:32] nouveau 0000:09:00.0: fifo: CHSW_ERROR 00000004 > [ +0.000162] nouveau 0000:09:00.0: fifo: CHSW_ERROR 00000005 These don't sound good at all! > [Jun26 09:46] nouveau 0000:09:00.0: disp: outp 04:0006:0f44...

...4.5 without noticing. I'll post back later today with > actual valid test results. > I replaced the monitor (turns out that my monitor had a known DP problem), and now the screen lights up reliably. I still get occasional log lines like this: [Jun26 09:25] nouveau 0000:09:00.0: fifo: FB_FLUSH_TIMEOUT [Jun26 09:30] nouveau 0000:09:00.0: fifo: FB_FLUSH_TIMEOUT [Jun26 09:32] nouveau 0000:09:00.0: fifo: CHSW_ERROR 00000004 [ +0.000162] nouveau 0000:09:00.0: fifo: CHSW_ERROR 00000005 [Jun26 09:46] nouveau 0000:09:00.0: disp: outp 04:0006:0f44: link training failed [ +0.107894] nouveau 0000:09:00.0...

.... >>> >> >> I replaced the monitor (turns out that my monitor had a known DP >> problem), and now the screen lights up reliably. I still get > > Great to hear! > >> occasional log lines like this: >> >> [Jun26 09:25] nouveau 0000:09:00.0: fifo: FB_FLUSH_TIMEOUT >> [Jun26 09:30] nouveau 0000:09:00.0: fifo: FB_FLUSH_TIMEOUT >> [Jun26 09:32] nouveau 0000:09:00.0: fifo: CHSW_ERROR 00000004 >> [ +0.000162] nouveau 0000:09:00.0: fifo: CHSW_ERROR 00000005 > > These don't sound good at all! > >> [Jun26 09:46] nouveau 0000:09:...

This is an initial series of patches to improve channel recovery on Turing GPUs with the goal of improving reliability enough to eventually enable SVM for Turing. It's likely follow up patches will be required to fully address problems with less trivial workloads than what I have been able to test thus far. This series primarily addresses a number of hardware changes to interrupt layout and

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

...After loading to WM (swayWM), when opening the Firefox, the screen was immediately frosted and nothing was done. dmesg output itself: https://gist.github.com/nolik/1179a25a7a84f979aaca3d9b0badb08f [ 99.818101] nouveau 0000:26:00.0: fifo: CHSW_ERROR 00000002 [ 99.818106] nouveau 0000:26:00.0: fifo: FB_FLUSH_TIMEOUT According ArchWiki i try to add nouveau.noaccel=1 to kernel params => as a result WM stop freezing and able to use, but ALL LAGS and snowing on the screen. I try to disable GPU acceleration in Firefox, and run it => it's not work. Try to add QT_XCB_FORCE_SOFTWARE_OPENGL=1 to env variable...

https://bugs.freedesktop.org/show_bug.cgi?id=90453 Bug ID: 90453 Summary: Desktop periodically freezes when using Nouveau & getting "nouveau E[PDISP]" errors in dmesg Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity:

https://bugs.freedesktop.org/show_bug.cgi?id=70354 Priority: medium Bug ID: 70354 Assignee: nouveau at lists.freedesktop.org Summary: Failed to initialise context object: 2D_NVC0 (0) (for my GeForce GT 750M) QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: