From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201847] nouveau 0000:01:00.0: fifo: fault 01 [WRITE] at 000000000a721000 engine 00 [GR] client 0f [GPC0/PROP_0] reason 82 [] on channel 4 [00ff85c000 X[3819]]
Date: Sun, 05 May 2019 15:18:50 +0000 [thread overview]
Message-ID: <bug-201847-2300-0FcyuxDGtt@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201847-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201847
--- Comment #1 from Marc B. (kernel.org@marc.ngoe.de) ---
It would be soooo cool if anyone would actually read this bug report and maybe
try to fix it. I will assist in testing patches until this is resolved.
And: I am willing to offer $100 for fixing this annoying bug! Keeps freezing my
4.19.39 kernel out of nowhere.
Some things I would like to get into discussion:
a) - it might have something to do with memory pressure
_and_
b)
- high CPU load
_or_
- high number of context switches.
For the latter I'm not sure. The bug actually always occurs when I ie. compile
two kernels at -j24 and habe some other work besides this, say a YT video. The
bug is, however, definitely triggered by a graphics event, ie.
resizing/creating a window, scrolling a Web page or watching a video.
[2019-05-04 15:43:24] err kern 03 kernel : [ 523.906459] nouveau 0000:01:00.0:
fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
[2019-05-04 15:43:24] notice kern 05 kernel : [ 523.906467] nouveau
0000:01:00.0: fifo: runlist 0: scheduled for recovery
[2019-05-04 15:43:24] notice kern 05 kernel : [ 523.906473] nouveau
0000:01:00.0: fifo: channel 2: killed
[2019-05-04 15:43:24] notice kern 05 kernel : [ 523.906479] nouveau
0000:01:00.0: fifo: engine 0: scheduled for recovery
[2019-05-04 15:43:24] warning kern 04 kernel : [ 523.906789] nouveau
0000:01:00.0: X[8006]: channel 2 killed!
[2019-05-04 15:43:24] err kern 03 kernel : nouveau 0000:01:00.0: fifo:
SCHED_ERROR 0a [CTXSW_TIMEOUT]
[2019-05-04 15:43:24] notice kern 05 kernel : nouveau 0000:01:00.0: fifo:
runlist 0: scheduled for recovery
[2019-05-04 15:43:24] notice kern 05 kernel : nouveau 0000:01:00.0: fifo:
channel 2: killed
[2019-05-04 15:43:24] notice kern 05 kernel : nouveau 0000:01:00.0: fifo:
engine 0: scheduled for recovery
[2019-05-04 15:43:24] warning kern 04 kernel : nouveau 0000:01:00.0: X[8006]:
channel 2 killed!
[2019-05-04 15:44:24] info kern 06 kernel : [ 584.121331] sysrq: SysRq :
Keyboard mode set to system default
[2019-05-04 15:44:24] info kern 06 kernel : sysrq: SysRq : Keyboard mode set to
system default
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-05 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-02 21:47 [Bug 201847] New: nouveau 0000:01:00.0: fifo: fault 01 [WRITE] at 000000000a721000 engine 00 [GR] client 0f [GPC0/PROP_0] reason 82 [] on channel 4 [00ff85c000 X[3819]] bugzilla-daemon
2019-05-05 15:18 ` bugzilla-daemon [this message]
2019-07-21 15:08 ` [Bug 201847] " bugzilla-daemon
2019-08-13 14:00 ` bugzilla-daemon
2023-08-16 16:02 ` bugzilla-daemon
2023-08-17 10:12 ` bugzilla-daemon
2023-08-17 14:20 ` bugzilla-daemon
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-201847-2300-0FcyuxDGtt@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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