From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 110572] Regularly System Crash: (ca. 1 hour) nouveau 0000:08:00.0: gr: PGRAPH TLB flush idle timeout fail and nouveau 0000:08:00.0: mmu: ce0 mmu invalidate timeout
Date: Sat, 11 May 2019 18:21:32 +0000 [thread overview]
Message-ID: <bug-110572-8800-7Lab7356IA@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110572-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2214 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110572
--- Comment #3 from Linux Freak <Linuxfreak-RbZlAiThDcE@public.gmane.org> ---
Created attachment 144236
--> https://bugs.freedesktop.org/attachment.cgi?id=144236&action=edit
a huge: journalctl -p 4 -b -1 of the last crash
A lot of hang up messages...
e.g.
Call Trace:
Mai 11 19:58:16 kernel: ? nvkm_ioctl_new+0x1a0/0x200 [nouveau]
Call Trace:
Mai 11 19:58:18 kernel: nvkm_vmm_ptes_get_map+0x246/0x3f0 [nouveau]
Call Trace:
Mai 11 19:58:22 kernel: nv50_vmm_flush+0x1f2/0x220 [nouveau]
Call Trace:
Mai 11 19:58:24 kernel: nvkm_vmm_ptes_get_map+0x246/0x3f0 [nouveau]
Call Trace:
Mai 11 19:58:28 kernel: nv50_vmm_flush+0x1f2/0x220 [nouveau]
INFO: task kworker/u8:2:1002 blocked for more than 122 seconds.
Mai 11 20:01:38 kernel: Tainted: G W 5.1.0-1-MANJARO #1
Mai 11 20:01:38 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
Mai 11 20:01:38 kernel: Call Trace:
Mai 11 20:01:38 kernel: ? __schedule+0x30b/0x8b0
Mai 11 20:01:38 kernel: ? g84_fifo_uevent_init+0x1a/0x40 [nouveau]
Mai 11 20:01:38 kernel: schedule+0x32/0x80
Mai 11 20:01:38 kernel: schedule_timeout+0x311/0x4a0
Mai 11 20:01:38 kernel: ? nouveau_fence_is_signaled+0x39/0x40 [nouveau]
Mai 11 20:01:38 kernel: dma_fence_default_wait+0x204/0x280
Mai 11 20:01:38 kernel: ? dma_fence_wait_timeout+0x120/0x120
Mai 11 20:01:38 kernel: dma_fence_wait_timeout+0x105/0x120
Mai 11 20:01:38 kernel: drm_atomic_helper_wait_for_fences+0x38/0xc0
[drm_kms_helper]
Mai 11 20:01:38 kernel: nv50_disp_atomic_commit_tail+0x72/0x690 [nouveau]
Mai 11 20:01:38 kernel: ? finish_task_switch+0x84/0x2d0
Mai 11 20:01:38 kernel: ? __switch_to_asm+0x40/0x70
Mai 11 20:01:38 kernel: process_one_work+0x1eb/0x410
Mai 11 20:01:38 kernel: worker_thread+0x2d/0x3d0
Mai 11 20:01:38 kernel: ? process_one_work+0x410/0x410
Mai 11 20:01:38 kernel: kthread+0x112/0x130
Mai 11 20:01:38 kernel: ? kthread_park+0x80/0x80
Mai 11 20:01:38 kernel: ret_from_fork+0x35/0x40
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3412 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-11 18:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 7:52 [Bug 110572] New: System Crash: nouveau 0000:08:00.0: gr: PGRAPH TLB flush idle timeout fail and nouveau 0000:08:00.0: mmu: ce0 mmu invalidate timeout bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-110572-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-05-08 22:12 ` [Bug 110572] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-08 22:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-08 22:17 ` [Bug 110572] Regularly System Crash: (ca. 1 hour) " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-09 8:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-09 12:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-11 18:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-05-11 18:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-11 18:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-11 19:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-11 19:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-14 14:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-14 14:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-14 14:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-14 16:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-14 16:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-15 8:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-16 17:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-19 12:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-24 8:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-05 8:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-05 8:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-05 8:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-11-10 20:54 ` 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-110572-8800-7Lab7356IA@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;
as well as URLs for NNTP newsgroup(s).