From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 93629] [NVE6] complete system freeze, PGRAPH engine fault on channel 2, SCHED_ERROR [ CTXSW_TIMEOUT ]
Date: Sat, 08 Dec 2018 22:02:27 +0000 [thread overview]
Message-ID: <bug-93629-8800-ViZfLNRrCS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93629-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1237 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93629
--- Comment #46 from Franco Forza <ucx-hi6Y0CQ0nG0@public.gmane.org> ---
I've tested the 'NvGrUseFw=1' kernel cmdline argument (as stated in old
comments from 2016 above) but it doesn't help anymore (the 4 requested fw files
by nouveau during early boot were served properly and the errors about missing
firmware files vanished as well).
The system freezes maybe once per week. Mostly hard crash with two keyboard
leds blinking and hard reset after some time. Sometimes the kernel survives and
dmesg can be read out. It shows this:
[ 7896.354441] nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
[ 7896.354452] nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery
[ 7896.354458] nouveau 0000:01:00.0: fifo: channel 2: killed
[ 7896.354464] nouveau 0000:01:00.0: fifo: engine 0: scheduled for recovery
[ 7896.354879] nouveau 0000:01:00.0: systemd-logind[473]: channel 2 killed!
If there's something we can do to help debug this let me know.
Arch Linux 4.19.4
xf86-video-nouveau 1.0.15 modesetting
mesa 18.2.6
xorg-server 1.20.3
Nvidia GTX770 (NVE4/GK104/Kepler)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2080 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:[~2018-12-08 22:02 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 14:01 [Bug 93629] New: [NVE6] complete system freeze, PGRAPH engine fault on channel 2, SCHED_ERROR [ CTXSW_TIMEOUT ] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-93629-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-01-07 14:02 ` [Bug 93629] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-07 14:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-07 14:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-07 14:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-07 14:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-07 14:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-08 11:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-20 19:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-20 19:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-20 19:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-20 19:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-20 19:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-20 19:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-05 13:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06 2:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-13 16:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-13 17:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-15 12:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-27 9:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-11 4:46 ` bugzilla-daemon-C9EPM1l/obmE5N/NCR/djmD2FQJk+8+b
2016-05-11 15:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-12 23:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-13 10:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-13 14:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-13 14:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-13 16:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-13 17:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-13 18:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-16 8:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-17 16:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-25 12:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-04 18:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-04 18:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-27 14:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-29 10:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-21 16:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-26 0:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-24 15:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-02 6:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-18 18:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-21 23:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-21 23:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-31 11:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-31 11:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-31 11:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-31 11:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-31 11:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-31 12:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-31 12:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-25 0:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-05-27 9:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-06 16:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-08 22:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2018-12-08 22:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-08 11:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-08 11:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:09 ` 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-93629-8800-ViZfLNRrCS@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox