From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 100567] Nouveau system freeze fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
Date: Sun, 05 May 2019 18:24:39 +0000 [thread overview]
Message-ID: <bug-100567-8800-leSaENeknd@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100567-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1523 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100567
--- Comment #28 from Roy <nouveau-NQbd8FSOZ1kdnm+yROfE0A@public.gmane.org> ---
Somewhat surprised that this particular report hasn't received any attention
from a core dev. Sadly, I'm afraid my response will not be hugely satisfying
eiter.
The message "fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]" is not the result of *a bug*
and does not point in the direction of one. Rather it is a symptom of a wide
variety of potential problems with nouveau, (all of) which result in a hang of
the rendering part of the GPU. On itself it doesn't give meaningful information
to any developer as to what may be the culprit. It's like measuring a fever, it
could be the result of many conditions.
Developers would be helped if there was a reliably reproducible situation in
which this event can be triggered. If there is a list of steps that can be
followed that would result in this message and a hang, that somehow doesn't
involve words like "random" or "wait for possibly a few hours", and that can be
traced with tools such as APITrace, we could get a step further in analysing
what goes wrong. However, it seems unlikely this is the case, especially since
we are also aware of multithreading-related issues that make isolating such
problems extremely difficult. Unfortunately, post-mortem syslogs and dmesgs are
unlikely to add any useful information to this or similar bug reports.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2316 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2019-05-05 18:24 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 20:09 [Bug 100567] New: Nouveau system freeze fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-100567-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-04-05 16:18 ` [Bug 100567] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-06 15:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-10 23:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-13 18:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-20 14:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-26 9:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-26 9:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-26 9:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-30 7:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-14 11:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-30 20:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-29 17:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-30 13:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-01 17:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-30 21:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-05 10:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-22 11:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-05 21:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-05 21:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-05 21:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-05 21:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-05 21:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-06 14:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-06 18:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-08 11:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-08 11:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-08 11:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-08 11:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-02-04 21:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-02-07 0:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-02-11 21:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-05 15:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-05 18:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-05-06 16:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-06 17:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-06 17:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-06 20:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-07 19:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-08 14:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-26 19:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-21 15:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-21 15:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-05 14:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-23 21:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-08 7:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:33 ` 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-100567-8800-leSaENeknd@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