On (06/19/19 02:07), Ilia Mirkin wrote:
> If all else fails, just remove nouveau_dri.so and/or boot with
> nouveau.noaccel=1 -- should be perfect.
nouveau.noaccel=1 did the trick. Is there any other, let's say
less CPU-intensive, way to fix nouveau?
-ss
On (06/19/19 15:27), Sergey Senozhatsky wrote:
> [..]
>
> > If all else fails, just remove nouveau_dri.so and/or boot with
> > nouveau.noaccel=1 -- should be perfect.
>
> Can give it a try.
That has some impact on system responsiveness:
CPU% COMM
339.7 firefox
Which is
> > > On (06/14/19 11:50), Sergey Senozhatsky wrote:
> > > > > dmesg
> > > > >
> > > > > nouveau :01:00.0: DRM: GPU lockup - switching to software fbcon
> > > > > nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
> >
On (06/14/19 11:50), Sergey Senozhatsky wrote:
> dmesg
>
> nouveau :01:00.0: DRM: GPU lockup - switching to software fbcon
> nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
> nouveau :01:00.0: fifo: runlist 0: scheduled for recovery
> nouveau :01:00.
On (06/19/19 01:20), Ilia Mirkin wrote:
> On Wed, Jun 19, 2019 at 1:08 AM Sergey Senozhatsky
> wrote:
> >
> > On (06/14/19 11:50), Sergey Senozhatsky wrote:
> > > dmesg
> > >
> > > nouveau :01:00.0: DRM: GPU lockup - switching to software fbcon
&
gt; > >
> > > > nouveau :01:00.0: DRM: GPU lockup - switching to software fbcon
> > > > nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
> > > > nouveau :01:00.0: fifo: runlist 0: scheduled for recovery
> > > > nouveau
On Wed, Jun 19, 2019 at 1:08 AM Sergey Senozhatsky
wrote:
>
> On (06/14/19 11:50), Sergey Senozhatsky wrote:
> > dmesg
> >
> > nouveau :01:00.0: DRM: GPU lockup - switching to software fbcon
> > nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
&
5.2.0-rc4-next-20190613
dmesg
nouveau :01:00.0: DRM: GPU lockup - switching to software fbcon
nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
nouveau :01:00.0: fifo: runlist 0: scheduled for recovery
nouveau :01:00.0: fifo: channel 5: killed
nouveau :01:00.0: fifo
