Nouveau - Nov 2015 - [Bug 92971] [GF110] KDE plasma locks randomly due to crash of nouveau driver

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

--- Comment #5 from Philippe Condé <conde.philippe at skynet.be> ---
hello,

it is kde5  (KF5). 
With opensuse Tumbleweed we do a global update (snapshot). Difficult to see
thereafter if this is due to KDE or the kernel. 

Three examples from journalctl:

the very first error after the boot message: the lock occurred during
reactivation of the session:

Nov 14 18:02:58 hpprol2 kernel: nouveau 0000:0a:00.0: timeout at
../drivers/gpu/drm/nouveau/nvkm/engine/fifo/gpfifogf100.c:66/gf100_fifo_gpfifo_engine_fini()!
Nov 14 18:02:58 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: channel 14
[xembedsniproxy[2209]] kick timeout
Nov 14 18:02:58 hpprol2 kernel: nouveau:
xembedsniproxy[2209]:cccc0000:0000906f: detach gr failed, -16
Nov 14 18:02:58 hpprol2 kernel: nouveau 0000:0a:00.0: timeout at
../drivers/gpu/drm/nouveau/nvkm/engine/fifo/gpfifogf100.c:66/gf100_fifo_gpfifo_engine_fini()!
Nov 14 18:02:58 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: channel 20
[xembedsniproxy[2229]] kick timeout
Nov 14 18:02:58 hpprol2 kernel: nouveau:
xembedsniproxy[2229]:cccc0000:0000906f: detach gr failed, -16
Nov 14 18:02:59 hpprol2 audit[2124]: ANOM_ABEND auid=1000 uid=1000 gid=100
ses=1 pid=2124 comm="kactivitymanage"
exe="/usr/bin/kactivitymanagerd" sig=11


2) the first errors with a corrupt screen followed by a lock when loading Yast

Nov 15 10:36:29 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: PBDMA0: 80000000 []
ch 30 [007e6ab000 y2controlcenter[25892]] subc 0 mthd 0000 data 00000000
Nov 15 10:36:29 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: PBDMA0: 80040000 []
ch 30 [007e6ab000 y2controlcenter[25892]] subc 0 mthd 0000 data 00000000
Nov 15 10:36:29 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: PBDMA0: 80000000 []
ch 30 [007e6ab000 y2controlcenter[25892]] subc 0 mthd 0000 data 00000000
Nov 15 10:36:29 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: read fault at
0000000000 engine 07 [PFIFO] client 06 [PFIFO] reason 00 [PT_NOT_PRESENT] on
channel 30 [007e6ab000 y2controlcenter[25892]]
Nov 15 10:36:29 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: fifo engine fault
on channel 30, recovering...
Nov 15 10:36:37 hpprol2 kernel: nouveau 0000:0a:00.0: DRM: GPU lockup -
switching to software fbcon

3) the system locked in the night 15-16 and the first error message are
Nov 16 00:10:32 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: PBDMA0: 80000000 []
ch 30 [007e6ab000 kscreenlocker_g[14277]] subc 0 mthd 0000 data 00000000
Nov 16 00:10:32 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: PBDMA0: 80040000 []
ch 30 [007e6ab000 kscreenlocker_g[14277]] subc 0 mthd 0000 data 00000000
Nov 16 00:10:32 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: PBDMA0: 80000000 []
ch 30 [007e6ab000 kscreenlocker_g[14277]] subc 0 mthd 0000 data 00000000
Nov 16 00:10:32 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: PBDMA0: 80000000 []
ch 30 [007e6ab000 kscreenlocker_g[14277]] subc 0 mthd 0000 data 00000000
Nov 16 00:10:32 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: PBDMA0: 80000000 []
ch 30 [007e6ab000 kscreenlocker_g[14277]] subc 0 mthd 0000 data 00000000
Nov 16 00:10:32 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: PBDMA0: 80000000 []
ch 30 [007e6ab000 kscreenlocker_g[14277]] subc 0 mthd 0000 data 00000000
Nov 16 00:10:32 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: PBDMA0: 80000000 []
ch 30 [007e6ab000 kscreenlocker_g[14277]] subc 0 mthd 0000 data 00000000
Nov 16 00:10:32 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: PBDMA0: 80000000 []
ch 30 [007e6ab000 kscreenlocker_g[14277]] subc 0 mthd 0000 data 00000000


there are a lot of this messages  and then errors about kscreenlocker 
ov 16 00:10:32 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: read fault at
2000000000 engine 07 [PFIFO] client 06 [PFIFO] reason 00 [PT_NOT_PRESENT] on
channel 30 [007e6ab000 kscreenlocker_g[14277]]
Nov 16 00:10:32 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: fifo engine fault
on channel 30, recovering...

the only common process in all case is nouveau 
Regards
Philippe

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151116/d09fc462/attachment-0001.html>