Attachment 137284 Details for Bug 105049 – A call trace from the kernel because the process was hung

A call trace from the kernel because the process was hung

calltrace (text/plain), 1.40 KB, created by Hal Gentz on 2018-02-12 02:14:41 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Hal Gentz

Created: 2018-02-12 02:14:41 UTC

Size: 1.40 KB

patch

obsolete

>Warning: I had to type this up manually, there might be some errors
>
>INFO: task GCraft:3985 blocked for more than 120 secounds
>	Not tainted 4.15.2-1-hardened-apparmour-gentz #1
>"echo 0 > /proc/sys/kernel/hung_task_timeout_specs" disables this message.
>GCraft			D	 0  3985	896 0x00000000
>Call Trace:
>? __schedule+0x299/0x8b0
>schedule+0x2f/0x90
>schedule_timeout+0x1fd/0x3a0
>? _raw_spin_unlock_irqrestore+0x26/0x30
>? __wake_up_common_lock+0x89/0xc0
>dma_fence_default_wait+0x1fc/0x2a0
>? dma_fence_release+0xa0/0xa0
>dma_fence_wait_timeout+0x39/0x110
>amdgpu_ctx_wait_prev_fence+0x49/0x80 [amdgpu]
>amdgpu_cs_ioctl+0x99/0x1b40 [amdgpu]
>? amdgpu_cs_find_mapping+0xc0/0xc0 [amdgpu]
>drm_ioctl_kernel+0x5b/0xb0 [drm]
>drm_ioctl+0x2d5/0x370 [drm]
>? amdgpu_cs_find_mapping+0xc0/0xc0 [amdgpu]
>? do_iter_write+0x104/0x1c0
>? do_wait_intr_irq+0xb0/0xb0
>amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
>do_vfs_ioctl+0xa4/0x630
>? __sys_recvmsg+0x7d/0x90
>SyS_ioctl+0x74/0x80
>do_syscall_64+0x68/0x100e
>entry_SYSCALL_64_after_hwframe+0x21/0x86
>RIP: 0033:0x64fc28aacd87
>RSP: 002b:00007544b9675c98 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
>RAX: ffffffffffffffda RBX: 00007544b9675fd0 RCX: 000064fc28aacd87
>RDX: 00007544b9675d10 RSI: 00000000c0186444 RDI: 0000000000000006
>RBP: 00007544b9675d10 R08: 00007544b9675e00 R09: 00007544b9675ce0
>R10: 00007544b9675e00 R11: 0000000000000246 R12: 00000000c0186444
>R13: 0000000000000006 R14: 0000000000000000 R15: 000001f47c522ee0

Actions: View

Attachments on bug 105049: 137278 | 137279 | 137280 | 137281 | 137282 | 137283 | 137284

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.