<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - system freeze "fifo: gr engine fault on channel 6" NVIDIA" href="https://bugs.freedesktop.org/show_bug.cgi?id=96876#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - system freeze "fifo: gr engine fault on channel 6" NVIDIA" href="https://bugs.freedesktop.org/show_bug.cgi?id=96876">bug 96876</a> from <a class="email" href="mailto:dashesy@gmail.com" title="Ehsan Azar <dashesy@gmail.com>"> Ehsan Azar</a> <pre>Ok I am now running: $ uname -a Linux dashesy.wavelet 4.6.4-301.fc24.x86_64 #1 SMP Tue Jul 12 11:50:00 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Is this latest enough? I am waiting to see if lockup happens again, but I am afraid I still see the same kind of precursor: $ journalctl --no-pager -b -p err -- Logs begin at Thu 2016-05-05 05:39:48 PDT, end at Sat 2016-07-23 10:26:44 PDT. -- Jul 23 03:23:01 dashesy.wavelet kernel: nouveau 0000:01:00.0: priv: HUB0: 085014 ffffffff (1a70820b) Jul 23 10:23:12 dashesy.wavelet kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xfed40040-0xfed4103f] Jul 23 10:23:13 dashesy.wavelet mcelog[865]: Family 6 Model 5e CPU: only decoding architectural errors Jul 23 10:23:15 dashesy.wavelet bluetoothd[869]: Failed to obtain handles for "Service Changed" characteristic Jul 23 10:23:41 dashesy.wavelet spice-vdagent[1493]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Jul 23 10:23:56 dashesy.wavelet spice-vdagent[1985]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Jul 23 10:23:58 dashesy.wavelet pulseaudio[2107]: [pulseaudio] pid.c: Daemon already running.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>