From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 96876] system freeze "fifo: gr engine fault on channel 6" NVIDIA
Date: Sat, 23 Jul 2016 17:31:08 +0000 [thread overview]
Message-ID: <bug-96876-8800-dShF5kwUBL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-96876-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1422 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=96876
--- Comment #5 from Ehsan Azar <dashesy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2215 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2016-07-23 17:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 23:31 [Bug 96876] New: system freeze "fifo: gr engine fault on channel 6" NVIDIA bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-96876-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-07-09 23:38 ` [Bug 96876] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-09 23:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-09 23:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-23 16:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-23 17:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2016-07-24 15:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:15 ` 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-96876-8800-dShF5kwUBL@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.