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

--- Comment #17 from Andrey Mazo <ahippo-o+MxOtu4lMCHXe+LvDLADg@public.gmane.org> ---
I think, I'm also experiencing the same bug as described in comment 0.
(screen doesn't wake from a sleep after 2-3 days of uptime)

I'm also running Gentoo and have the following packages installed.
Linux version 4.4.6-gentoo-20160401 (root@localhost) (gcc version 4.8.5 (Gentoo
4.8.5 p1.3, pie-0.6.2) ) #1 SMP Fri Apr 1 15:03:40 EDT 2016
x11-base/xorg-server-1.17.4
x11-drivers/xf86-video-nouveau-1.0.12
media-libs/mesa-11.0.6
x11-libs/libdrm-2.4.65
kde-plasma/plasma-workspace-5.6.1
www-client/vivaldi-1.0.344.37_p1 (a chromium-based browser)

eselect qtgraphicssystem is set to native

(as far as I remember, kernel 4.5.0 wasn't able to show me anything on the
screen besides total garbage)

I'm ready to recompile the kernel with whatever debugging options you might
need to investigate the problem (increased CONFIG_NOUVEAU_DEBUG or any generic
kernel hacking options).

I'm also glad to capture an apitrace, but not sure of what.
plasmashell, X, a browser?


zoominee, have you tried disabling the system activity applet that you
suspected could trigger the issue?


Here is a part of my dmesg:
[190683.157049] nouveau 0000:03:00.0: gr: TRAP ch 8 [001faea000
plasmashell[26949]]
[190683.157063] nouveau 0000:03:00.0: gr: GPC0/TPC0/TEX: 80000049
[190683.157082] nouveau 0000:03:00.0: fifo: read fault at 0001115000 engine 00
[PGRAPH] client 01 [GPC0/TEX] reason 02 [PAGE_NOT_PRESENT] on channel 8
[001faea000 plasmashell[26949]]
[190683.157084] nouveau 0000:03:00.0: fifo: gr engine fault on channel 8,
recovering...
[192882.157535] nouveau 0000:03:00.0: fifo: PBDMA0: 04000000 [] ch 2
[001fe71000 X[24266]] subc 0 mthd 001c data 00001004
[192882.157807] nouveau 0000:03:00.0: fifo: PBDMA0: 04000000 [] ch 2
[001fe71000 X[24266]] subc 0 mthd 001c data 00001004
[195081.297439] nouveau 0000:03:00.0: fifo: PBDMA0: 04000000 [] ch 2
[001fe71000 X[24266]] subc 0 mthd 001c data 00001004
[195214.396093] [TTM] Failed to expire sync object before buffer eviction
[195229.455046] [TTM] Failed to expire sync object before buffer eviction


And after initiating reboot:
[197665.853048] nouveau 0000:03:00.0: X[24266]: failed to idle channel 2
[X[24266]]
[197680.853033] nouveau 0000:03:00.0: X[24266]: failed to idle channel 2
[X[24266]]
[197680.853119] nouveau 0000:03:00.0: fifo: read fault at 000001b000 engine 07
[PFIFO] client 07 [BAR_READ] reason 02 [PAGE_NOT_PRESENT] on channel 2
[001fe71000 X[24266]]
...
[197680.853150] =============================================
[197680.853151] [ INFO: possible recursive locking detected ]
[197680.853152] 4.4.6-gentoo-20160401 #1 Not tainted
[197680.853153] ---------------------------------------------
[197680.853154] kworker/0:1/27582 is trying to acquire lock:
[197680.853155]  ((&fifo->fault)){+.+...}, at: [<ffffffffa42cebd0>]
flush_work+0x0/0x280
[197680.853162]
                but task is already holding lock:
[197680.853163]  ((&fifo->fault)){+.+...}, at: [<ffffffffa42cf644>]
process_one_work+0x144/0x430
[197680.853167]
                other info that might help us debug this:
[197680.853168]  Possible unsafe locking scenario:

[197680.853169]        CPU0
[197680.853169]        ----
[197680.853170]   lock((&fifo->fault));
[197680.853171]   lock((&fifo->fault));
[197680.853172]
                 *** DEADLOCK ***

[197680.853173]  May be due to missing lock nesting notation

[197680.853174] 2 locks held by kworker/0:1/27582:
[197680.853175]  #0:  ("events"){.+.+.+}, at: [<ffffffffa42cf644>]
process_one_work+0x144/0x430
[197680.853178]  #1:  ((&fifo->fault)){+.+...}, at: [<ffffffffa42cf644>]
process_one_work+0x144/0x430
[197680.853181]
                stack backtrace:
[197680.853183] CPU: 0 PID: 27582 Comm: kworker/0:1 Not tainted
4.4.6-gentoo-hippo-20160401 #1
[197680.853184] Hardware name: Dell Inc. Precision Tower 7910/0215PR, BIOS A06
01/19/2015
[197680.853187] Workqueue: events gf100_fifo_recover_work
[197680.853189]  0000000000000000 ffff8803875bfaf0 ffffffffa453193e
ffffffffa572ac50
[197680.853191]  ffffffffa572ac50 ffff8803875bfbb0 ffffffffa42fcbda
000000010bc3ca5c
[197680.853193]  ffff88083bcf6140 0000000000000000 0000000000000000
00000002442f617b
[197680.853195] Call Trace:
[197680.853198]  [<ffffffffa453193e>] dump_stack+0x67/0x99
[197680.853201]  [<ffffffffa42fcbda>] __lock_acquire+0x16fa/0x1b90
[197680.853202]  [<ffffffffa42fd7e0>] lock_acquire+0x60/0x80
[197680.853204]  [<ffffffffa42cebd0>] ? mod_delayed_work_on+0x80/0x80
[197680.853206]  [<ffffffffa42cec17>] flush_work+0x47/0x280
[197680.853207]  [<ffffffffa42cebd0>] ? mod_delayed_work_on+0x80/0x80
[197680.853210]  [<ffffffffa463cc16>] ? nvkm_subdev_fini+0x46/0x1f0
[197680.853212]  [<ffffffffa42fb026>] ? mark_held_locks+0x66/0x90
[197680.853214]  [<ffffffffa4319fba>] ? ktime_get+0x6a/0x110
[197680.853216]  [<ffffffffa469b390>] gf100_fifo_fini+0x10/0x20
[197680.853217]  [<ffffffffa469975a>] nvkm_fifo_fini+0x1a/0x30
[197680.853219]  [<ffffffffa4639040>] nvkm_engine_fini+0x20/0x30
[197680.853220]  [<ffffffffa463cc2f>] nvkm_subdev_fini+0x5f/0x1f0
[197680.853222]  [<ffffffffa469bbae>] gf100_fifo_recover_work+0xee/0x200
[197680.853224]  [<ffffffffa42cf6a0>] process_one_work+0x1a0/0x430
[197680.853225]  [<ffffffffa42cf644>] ? process_one_work+0x144/0x430
[197680.853227]  [<ffffffffa42cfa45>] worker_thread+0x115/0x460
[197680.853230]  [<ffffffffa4916a66>] ? __schedule+0x2f6/0x920
[197680.853232]  [<ffffffffa42cf930>] ? process_one_work+0x430/0x430
[197680.853234]  [<ffffffffa42d5959>] kthread+0xf9/0x110
[197680.853236]  [<ffffffffa42d5860>] ? kthread_create_on_node+0x230/0x230
[197680.853238]  [<ffffffffa491cabf>] ret_from_fork+0x3f/0x70
[197680.853239]  [<ffffffffa42d5860>] ? kthread_create_on_node+0x230/0x230

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