All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 72180] [NVE6] Random GPU Lockups, works with blob PGRAPH fw
Date: Sat, 07 Nov 2015 21:48:37 +0000	[thread overview]
Message-ID: <bug-72180-8800-czzlguWvRQ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-72180-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

https://bugs.freedesktop.org/show_bug.cgi?id=72180

--- Comment #43 from xenith-bjxz+0elTSj2eFz/2MeuCQ@public.gmane.org ---
I am definitely having this same bug all the way up to kernel version 4.4

Was using proprietary drivers for this reason on Fedora 22, and since the
release of 23 I've been attempting diligently to only use nouveau. 

With firmware that I extracted from 340 it will run for a while so long as
nothing GL intensive is done. One way I can always reproduce the issue is to
load Kodi, play a video, then stop the video and just let it sit open. 

VDPAU seems to be an aggrivating factor here, as that nearly always crashes the
drier. Even after removing the firmware from /lib/firmware though, the problem
still happens. (even if your player doesn't attempt to use VDPAU)

The following message is from the latest 4.4 kernel in rawhide, running on top
of Fedora 23: 

[  288.888692] nouveau 0000:01:00.0: gr: TRAP ch 5 [023f929000 kodi.bin[3240]]
[  288.888704] nouveau 0000:01:00.0: gr: GPC1/TPC0/MP trap: global 00000004
[MULTIPLE_WARP_ERRORS] warp 000d [GPR_OUT_OF_BOUNDS]
[  288.888710] nouveau 0000:01:00.0: gr: GPC1/TPC1/MP trap: global 00000004
[MULTIPLE_WARP_ERRORS] warp 4000d [GPR_OUT_OF_BOUNDS]
[  288.888726] nouveau 0000:01:00.0: fifo: write fault at 0003846000 engine 00
[GR] client 0f [GPC1/PROP_0] reason 02 [PTE] on channel 5 [023f929000
kodi.bin[3240]]
[  288.888728] nouveau 0000:01:00.0: fifo: gr engine fault on channel 5,
recovering...


While that might not seem related, remember that my initial issues were
identical to this aging bug. Without proprietary firmware loading, it usually
is some kind of PGRAPH error, with it loaded it is usually some kind of PFIFO
error; they vary. The consistent part is that it _always_ crashes with nouveau. 

I have a GTX660SC from EVGA - and I would look more closely at EVGA cards if I
were you. My cursory scouring of the internet to try and fix this has led me to
believe that i'm seeing EVGA cards more often than not, and I'm not sure anyone
has yet made that connection yet. Also, the (SC) stands for super-clock, as in
factory overclocked. I suspect this may have something to do with it.

The version of the nouveau module is as follows, and I also upgraded 'mesa-*'
and 'linux-firmware' and 'xorg-x11-drv-nouveau' to the latest rawhide versions
to, thinking that might have some additional benefits, but the same issues
occur. This is simply NOT fixed in the most recent version of code anywhere.


filename:      
/lib/modules/4.4.0-0.rc0.git2.1.fc24.x86_64/kernel/drivers/gpu/drm/nouveau/nouveau.ko.xz
license:        GPL and additional rights
description:    nVidia Riva/TNT/GeForce/Quadro/Tesla
author:         Nouveau Project
alias:          pci:v000012D2d*sv*sd*bc03sc*i*VRAM
alias:          pci:v000010DEd*sv*sd*bc03sc*i*
depends:        drm,drm_kms_helper,ttm,mxm-wmi,wmi,video,i2c-algo-bit
intree:         Y
vermagic:       4.4.0-0.rc0.git2.1.fc24.x86_64 SMP mod_unload 


mesa versions tried: up to 1.11.1-devel

I will also being attaching my vbios.rom

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3859 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2015-11-07 21:48 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-30 18:05 [Bug 72180] New: Nouveau Random GPU Lockups bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-72180-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-11-30 18:06   ` [Bug 72180] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-30 18:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-30 18:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-30 20:25   ` [Bug 72180] [NVE6] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-30 22:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-30 22:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 13:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 13:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 14:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 14:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 14:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 15:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 15:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 17:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 21:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 23:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-02 18:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-02 23:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-03  0:38   ` [Bug 72180] [NVE6] Random GPU Lockups, works with blob PGRAPH fw bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-03 17:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-17 22:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-17 22:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-17 22:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-02 22:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-08  5:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-08 20:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-09  3:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-03 10:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-03 17:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 13:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-12 18:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-21 17:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-11-22 23:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-01 17:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-01 17:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-01 17:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-01 17:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-01 17:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-01 20:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-02  9:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-02 10:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-25 17:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-28 23:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 21:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2015-11-07 21:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 23:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-15 12:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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=bug-72180-8800-czzlguWvRQ@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.