dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
Cc: Sergey Senozhatsky
	<sergey.senozhatsky.work-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	David Airlie <airlied-cv59FeDIM0c@public.gmane.org>,
	nouveau
	<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
	LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	dri-devel
	<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
	Ben Skeggs <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Daniel Vetter <daniel-/w4YWyX8dFk@public.gmane.org>
Subject: Re: nouveau: DRM: GPU lockup - switching to software fbcon
Date: Wed, 19 Jun 2019 14:48:26 +0900	[thread overview]
Message-ID: <20190619054826.GA2059@jagdpanzerIV> (raw)
In-Reply-To: <CAKb7UvhdN=RUdfrnWswT4ANK5UwPcM-upDP85=84zsCF+a5-bg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On (06/19/19 01:20), Ilia Mirkin wrote:
> On Wed, Jun 19, 2019 at 1:08 AM Sergey Senozhatsky
> <sergey.senozhatsky.work@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 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
> > >  nouveau 0000:01:00.0: firefox[476]: channel 5 killed!
> > >  nouveau 0000:01:00.0: firefox[476]: failed to idle channel 5 [firefox[476]]
> > >
> > > It lockups several times a day. Twice in just one hour today.
> > > Can we fix this?
> >
> > Unusable
> 
> Are you using a GTX 660 by any chance? You've provided rather minimal
> system info.

01:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 730] (rev a1)

	-ss
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2019-06-19  5:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14  2:49 nouveau: DRM: GPU lockup - switching to software fbcon Sergey Senozhatsky
2019-06-19  5:08 ` Sergey Senozhatsky
2019-06-19  5:20   ` Ilia Mirkin
     [not found]     ` <CAKb7UvhdN=RUdfrnWswT4ANK5UwPcM-upDP85=84zsCF+a5-bg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-06-19  5:48       ` Sergey Senozhatsky [this message]
2019-06-19  6:07         ` Ilia Mirkin
2019-06-19  6:27           ` Sergey Senozhatsky
2019-06-19  6:36             ` Sergey Senozhatsky
     [not found]           ` <CAKb7UvgkEXtmJV67EXeBctgaOxM1D91fBbKw9oFMUaB1ZViZQg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-07-01  2:33             ` Sergey Senozhatsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190619054826.GA2059@jagdpanzerIV \
    --to=sergey.senozhatsky.work-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=airlied-cv59FeDIM0c@public.gmane.org \
    --cc=bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=daniel-/w4YWyX8dFk@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox