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: Sat, 05 Jan 2019 21:29:37 +0000 [thread overview]
Message-ID: <bug-100567-8800-HF5FvhVRCh@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100567-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 4477 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100567
--- Comment #18 from kenorb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org ---
The same problem on Ubuntu 18.10, kernel 4.18.0-13.
I've got 4x GPU: GTX 1080 Ti (3-Way SLI Connector), NVIDIA GeForce GTX 1080 Ti
graphics card with 3584 cores.
$ uname -a
Linux Ubuntu-PC 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:04:24 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
Errors in kern.log file:
nouveau 0000:65:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
nouveau 0000:65:00.0: fifo: runlist 0: scheduled for recovery
nouveau 0000:65:00.0: fifo: channel 2: killed
nouveau 0000:65:00.0: fifo: engine 0: scheduled for recovery
nouveau 0000:65:00.0: Xorg[5447]: channel 2 killed!
nouveau 0000:65:00.0: systemd-logind[3394]: nv50cal_space: -16
nouveau 0000:65:00.0: systemd-logind[3394]: nv50cal_space: -16
(the same message repeated 800x over and over again)
The system got freeze (no mouse or keyboard reaction), however kernel reacted
on few Magic SysRq keys, so here are some stack traces:
INFO: task kworker/u72:8:492 blocked for more than 120 seconds.
Tainted: G O 4.18.0-13-generic #14-Ubuntu
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/u72:8 D 0 492 2 0x80000000
Workqueue: events_unbound nv50_disp_atomic_commit_work [nouveau]
Call Trace at 20:25:50:
__schedule+0x29e/0x840
schedule+0x2c/0x80
schedule_timeout+0x258/0x360
? nv50_wndw_atomic_destroy_state+0x1d/0x20 [nouveau]
dma_fence_default_wait+0x1fc/0x260
? dma_fence_release+0xa0/0xa0
dma_fence_wait_timeout+0x3e/0xf0
drm_atomic_helper_wait_for_fences+0x3f/0xc0 [drm_kms_helper]
nv50_disp_atomic_commit_tail+0x78/0x860 [nouveau]
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
nv50_disp_atomic_commit_work+0x12/0x20 [nouveau]
process_one_work+0x20f/0x3c0
worker_thread+0x34/0x400
kthread+0x120/0x140
? pwq_unbound_release_workfn+0xd0/0xd0
? kthread_bind+0x40/0x40
ret_from_fork+0x35/0x40
Same call trace at 20:29:51 (few minutes later while Xorg was frozen):
Workqueue: events_unbound nv50_disp_atomic_commit_work [nouveau]
Call Trace:
__schedule+0x29e/0x840
? apic_timer_interrupt+0xa/0x20
? __drm_crtc_commit_free+0x12/0x20 [drm]
schedule+0x2c/0x80
schedule_timeout+0x258/0x360
? nv50_wndw_atomic_destroy_state+0x1d/0x20 [nouveau]
dma_fence_default_wait+0x1fc/0x260
? dma_fence_release+0xa0/0xa0
dma_fence_wait_timeout+0x3e/0xf0
drm_atomic_helper_wait_for_fences+0x3f/0xc0 [drm_kms_helper]
nv50_disp_atomic_commit_tail+0x78/0x860 [nouveau]
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
nv50_disp_atomic_commit_work+0x12/0x20 [nouveau]
process_one_work+0x20f/0x3c0
worker_thread+0x34/0x400
kthread+0x120/0x140
? pwq_unbound_release_workfn+0xd0/0xd0
? kthread_bind+0x40/0x40
ret_from_fork+0x35/0x40
Another one:
INFO: task Xorg:5447 blocked for more than 120 seconds.
Tainted: G O 4.18.0-13-generic #14-Ubuntu
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Xorg D 0 5447 5445 0x00000004
Call Trace:
__schedule+0x29e/0x840
schedule+0x2c/0x80
schedule_preempt_disabled+0xe/0x10
__ww_mutex_lock.isra.6+0x3c1/0x660
__ww_mutex_lock_slowpath+0x16/0x20
ww_mutex_lock+0x34/0x50
drm_modeset_lock+0x6e/0xb0 [drm]
drm_crtc_get_sequence_ioctl+0xbc/0x190 [drm]
? drm_wait_vblank_ioctl+0x610/0x610 [drm]
drm_ioctl_kernel+0xa4/0xf0 [drm]
drm_ioctl+0x227/0x400 [drm]
? drm_wait_vblank_ioctl+0x610/0x610 [drm]
? do_iter_write+0xe1/0x1a0
? do_iter_write+0xe1/0x1a0
nouveau_drm_ioctl+0x73/0xc0 [nouveau]
do_vfs_ioctl+0xa8/0x620
? __sys_recvmsg+0x88/0xa0
ksys_ioctl+0x67/0x90
__x64_sys_ioctl+0x1a/0x20
do_syscall_64+0x5a/0x110
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7f3f654b93c7
Code: Bad RIP value.
RSP: 002b:00007ffd57bbf168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007ffd57bbf200 RCX: 00007f3f654b93c7
RDX: 00007ffd57bbf1a0 RSI: 00000000c018643b RDI: 000000000000000e
RBP: 00007ffd57bbf1a0 R08: 0000000000000000 R09: 00005646eb8ff7c0
R10: 00005646eb54ad30 R11: 0000000000000246 R12: 00000000c018643b
R13: 000000000000000e R14: 00005646eb54b800 R15: 00005646eb466880
Full log: https://gist.github.com/kenorb/5b95caa1694dbf7f030ccc808a110856
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 5327 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:[~2019-01-05 21:29 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 [this message]
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
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-HF5FvhVRCh@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