mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ben Skeggs <skeggsb@gmail.com>
To: Olof Johansson <olof@lixom.net>,
	DRI mailing list <dri-devel@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	David Airlie <airlied@linux.ie>,
	bskeggs@redhat.com, nouveau@lists.freedesktop.org
Subject: Re: Fwd: [Bug 99900] nouveau: freeze / crash after kernel update to 4.10
Date: Wed, 21 Jun 2017 06:51:46 +1000	[thread overview]
Message-ID: <d9132312-d174-a5d3-ff2b-56855266ccf7@gmail.com> (raw)
In-Reply-To: <CAOesGMiES49o_Xt1GxsUj7+hivhcwdFECv8QfqiQqZjO57oj6w@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 5005 bytes --]

On 06/21/2017 02:54 AM, Olof Johansson wrote:
> Hey,
> 
> This was reported back in February and it seems nobody's given a shit?
> 
> I've got a machine here with a Quadro 4000 that the screen locks up on
> every single time the monitor goes to sleep. Userspace is Ubuntu 16.04,
> kernel is recent mainline (4.12-rc4+). It's been happening since 4.10
> though.
> 
> Can we please see this fixed by 4.12? It's an enormous regression and a
> major hassle to deal with as a user.
I'm not sure how exactly it could be related to the PBDMA errors, but
the "flip queue failed" is a bug in the 2D driver that got fixed in
xf86-video-nouveau-1.0.14.

Ben.

> 
> 
> -Olof
> 
> ---------- Forwarded message ----------
> From: ** <bugzilla-daemon@freedesktop.org
> <mailto:bugzilla-daemon@freedesktop.org>>
> Date: Wed, Feb 22, 2017 at 4:03 AM
> Subject: [Bug 99900] nouveau: freeze / crash after kernel update to 4.10
> To: dri-devel@lists.freedesktop.org <mailto:dri-devel@lists.freedesktop.org>
> 
> 
> Bug ID 	99900 <https://bugs.freedesktop.org/show_bug.cgi?id=99900>
> Summary 	nouveau: freeze / crash after kernel update to 4.10
> Product 	DRI
> Version 	XOrg git
> Hardware 	x86-64 (AMD64)
> OS 	Linux (All)
> Status 	NEW
> Severity 	normal
> Priority 	medium
> Component 	DRM/other
> Assignee 	dri-devel@lists.freedesktop.org
> <mailto:dri-devel@lists.freedesktop.org>
> Reporter 	krah.tm@gmail.com <mailto:krah.tm@gmail.com>
> 
> Created attachment 129823
> <https://bugs.freedesktop.org/attachment.cgi?id=129823> [details]
> <https://bugs.freedesktop.org/attachment.cgi?id=129823&action=edit>
> dmesg 4.10 - fifo write fault
> 
> After release of 4.10 kernel i've used that one from here:
> 
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/
> <http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/>
> 
> with my ubuntu trusty LTS.
> Xorg is now crashing whenever my monitors are going to sleep (happens always in
> my lunch time) - after returning its crashed and i need todo a hard reset to
> get the gpu running again.
> This is what is printed to dmesg when this happens (machine is still working
> via ssh):
> 
> [11010.813785] nouveau 0000:01:00.0: fifo: PBDMA0: 04000100 [] ch 2 [001fcc0000
> Xorg[2593]] subc 5 mthd 001c data 00000001
> [11010.813815] nouveau 0000:01:00.0: fifo: PBDMA0: 04000000 [] ch 2 [001fcc0000
> Xorg[2593]] subc 0 mthd 0010 data 00000000
> [11010.813838] nouveau 0000:01:00.0: fifo: PBDMA0: 04000000 [] ch 2 [001fcc0000
> Xorg[2593]] subc 0 mthd 0014 data 0001b020
> [11010.813864] nouveau 0000:01:00.0: fifo: PBDMA0: 04000000 [] ch 2 [001fcc0000
> Xorg[2593]] subc 0 mthd 0018 data 003c9310
> [11010.813886] nouveau 0000:01:00.0: fifo: PBDMA0: 04000000 [] ch 2 [001fcc0000
> Xorg[2593]] subc 0 mthd 001c data 00000002
> [11010.813905] nouveau 0000:01:00.0: fifo: PBDMA0: 04000000 [] ch 2 [001fcc0000
> Xorg[2593]] subc 0 mthd 0020 data 00000000
> [11010.813919] nouveau 0000:01:00.0: fifo: PBDMA0: 04000000 [] ch 2 [001fcc0000
> Xorg[2593]] subc 3 mthd 0200 data 000000cf
> [11010.813937] nouveau 0000:01:00.0: fifo: PBDMA0: 04000000 [] ch 2 [001fcc0000
> Xorg[2593]] subc 3 mthd 0204 data 00000000
> [11010.813954] nouveau 0000:01:00.0: fifo: PBDMA0: 04000000 [] ch 2 [001fcc0000
> Xorg[2593]] subc 3 mthd 0208 data 00000010
> [11010.813973] nouveau 0000:01:00.0: fifo: PBDMA0: 04000000 [] ch 2 [001fcc0000
> Xorg[2593]] subc 3 mthd 020c data 00000001
> [11010.813990] nouveau 0000:01:00.0: fifo: PBDMA0: 04000000 [] ch 2 [001fcc0000
> Xorg[2593]] subc 3 mthd 0210 data 00000000
> [11010.814014] nouveau 0000:01:00.0: fifo: PBDMA0: 04000000 [] ch 2 [001fcc0000
> Xorg[2593]] subc 0 mthd 0010 data 00000000
> [11010.814060] nouveau 0000:01:00.0: fifo: write fault at 000169b000 engine 00
> [PGRAPH] client 0f [GPC0/PROP] reason 02 [PAGE_NOT_PRESENT] on channel 2
> [001fcc0000 Xorg[2593]]
> [11010.814070] nouveau 0000:01:00.0: fifo: gr engine fault on channel 2,
> recovering...
> 
> 
> Xorg.log does have that:
> 
> [    42.993] (WW) NOUVEAU(0): flip queue failed: Device or resource busy
> 
> Trying to restart Xorg is unsuccessful.
> 
> [  8810.799] (WW) NOUVEAU(0): flip queue failed: Invalid argument
> 
> 
> This does not happen with 4.9.6 i've running now.
> Anything i should/can provide or try to get this fixed?
> 
> ------------------------------------------------------------------------
> You are receiving this mail because:
> 
>   * You are the assignee for the bug.
> 
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org <mailto:dri-devel@lists.freedesktop.org>
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
> <https://lists.freedesktop.org/mailman/listinfo/dri-devel>
> 
> 
> 
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

           reply	other threads:[~2017-06-20 20:52 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAOesGMiES49o_Xt1GxsUj7+hivhcwdFECv8QfqiQqZjO57oj6w@mail.gmail.com>]

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=d9132312-d174-a5d3-ff2b-56855266ccf7@gmail.com \
    --to=skeggsb@gmail.com \
    --cc=airlied@linux.ie \
    --cc=bskeggs@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=olof@lixom.net \
    /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

all inboxes | Powered by JetHome®