<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [NVE6] GPU lockups" href="https://bugs.freedesktop.org/show_bug.cgi?id=69882#c18">Comment # 18</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [NVE6] GPU lockups" href="https://bugs.freedesktop.org/show_bug.cgi?id=69882">bug 69882</a> from <a class="email" href="mailto:pastas4@gmail.com" title="Dainius Masiliūnas <pastas4@gmail.com>"> Dainius Masiliūnas</a> <pre>Testing it a few more times, it is indeed the read fault by nouveau that's causing the lockup in this case. The general DRM error does not appear during all boots, but the nouveau read fault does. When waiting around for a long time, the kernel log also has this: INFO: task kworker/0:4:956 blocked for more than 480 seconds. Tainted: G W O 4.3.0-1-default #1 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. kworker/0:4 D 0000000000000000 0 956 2 0x00000080 Workqueue: events gk104_fifo_recover_work [nouveau] ffff8800d9d8bbc8 0000000000000046 ffff8801fd2b2080 ffff880214b0e040 ffff8800d9d8c000 ffff8800d9d8bd18 ffff8800d9d8bd10 ffff880214b0e040 ffff8802142d8810 ffff8800d9d8bbe0 ffffffff8166a1aa 7fffffffffffffff Call Trace: [<ffffffff8166a1aa>] schedule+0x3a/0x90 [<ffffffff8166cfb7>] schedule_timeout+0x197/0x260 [<ffffffff8166b526>] wait_for_completion+0x96/0x100 [<ffffffff8108019d>] flush_work+0xed/0x180 [<ffffffffa02b79dd>] gk104_fifo_fini+0x1d/0x50 [nouveau] [<ffffffffa02b443c>] nvkm_fifo_fini+0x1c/0x30 [nouveau] [<ffffffffa02546a0>] nvkm_engine_fini+0x20/0x30 [nouveau] [<ffffffffa0258511>] nvkm_subdev_fini+0x61/0x1e0 [nouveau] [<ffffffffa02b8d3b>] gk104_fifo_recover_work+0xeb/0x290 [nouveau] [<ffffffff81080c89>] process_one_work+0x159/0x470 [<ffffffff81080fe8>] worker_thread+0x48/0x4a0 [<ffffffff81086c79>] kthread+0xc9/0xe0 [<ffffffff8166e80f>] ret_from_fork+0x3f/0x70 DWARF2 unwinder stuck at ret_from_fork+0x3f/0x70 Leftover inexact backtrace: [<ffffffff81086bb0>] ? kthread_worker_fn+0x170/0x170 I'm still not sure if this should be a separate bug report.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>