4.14 + amdgpupro opencl: sleepng function called:
Ricardo Ribalda Delgado
ricardo.ribalda at gmail.com
Thu Dec 14 15:39:07 UTC 2017
Hi
I am trying to use amdgpupro opencl on top of amdgpu and everything
seems to run fine except this OOPS that I get once per execution:
[ 120.180229] BUG: sleeping function called from invalid context at
/var/lib/jenkins/workspace/qt5122-dyspro/build/tmp/work-shared/qt5122/kernel-source/mm/slab.h:421
[ 120.181159] in_atomic(): 1, irqs_disabled(): 0, pid: 677, name: clinfo
[ 120.181979] CPU: 1 PID: 677 Comm: clinfo Not tainted 4.14.0-qtec-standard #1
[ 120.181979] Hardware name: AMD FP4/FP4, BIOS qtec 12/29/2016
[ 120.181980] Call Trace:
[ 120.181987] dump_stack+0x4d/0x67
[ 120.181990] ___might_sleep+0xdf/0x100
[ 120.181991] __might_sleep+0x4a/0x80
[ 120.181994] __kmalloc+0x118/0x1d0
[ 120.181997] ? reservation_object_copy_fences+0x38/0x100
[ 120.181998] reservation_object_copy_fences+0x38/0x100
[ 120.182006] ttm_bo_unref+0x12b/0x330 [ttm]
[ 120.182045] amdgpu_bo_unref+0x2a/0x50 [amdgpu]
[ 120.182063] amdgpu_vm_free_levels+0x2b/0x60 [amdgpu]
[ 120.182081] amdgpu_vm_free_levels+0x48/0x60 [amdgpu]
[ 120.182098] amdgpu_vm_fini+0x201/0x280 [amdgpu]
[ 120.182113] amdgpu_driver_postclose_kms+0x111/0x1f0 [amdgpu]
[ 120.182133] drm_release+0x265/0x380 [drm]
[ 120.182136] __fput+0xbe/0x200
[ 120.182137] ____fput+0xe/0x10
[ 120.182139] task_work_run+0x99/0xd0
[ 120.182142] do_exit+0x2e6/0xb70
[ 120.182143] ? __do_page_fault+0x273/0x4f0
[ 120.182145] do_group_exit+0x3b/0xb0
[ 120.182146] SyS_exit_group+0x14/0x20
[ 120.182148] do_syscall_64+0x74/0x1d0
[ 120.182150] entry_SYSCALL64_slow_path+0x25/0x25
[ 120.182151] RIP: 0033:0x3586ebec80
[ 120.182152] RSP: 002b:00007fff00ca6cf8 EFLAGS: 00000246 ORIG_RAX:
00000000000000e7
[ 120.182154] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000003586ebec80
[ 120.182154] RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
[ 120.182155] RBP: 00000035871a28b8 R08: 00000000000000e7 R09: ffffffffffffff78
[ 120.182156] R10: 0000003588c15168 R11: 0000000000000246 R12: 00000035871a28b8
[ 120.182156] R13: 00000035871a7d40 R14: 0000000000000000 R15: 0000000000000000
[ 212.756710] BUG: sleeping function called from invalid context at
/var/lib/jenkins/workspace/qt5122-dyspro/build/tmp/work-shared/qt5122/kernel-source/mm/slab.h:421
[ 212.758876] in_atomic(): 1, irqs_disabled(): 0, pid: 678, name: clpeak
[ 212.760986] CPU: 3 PID: 678 Comm: clpeak Tainted: G W
4.14.0-qtec-standard #1
[ 212.760987] Hardware name: AMD FP4/FP4, BIOS qtec 12/29/2016
[ 212.760989] Call Trace:
[ 212.761004] dump_stack+0x4d/0x67
[ 212.761012] ___might_sleep+0xdf/0x100
[ 212.761017] __might_sleep+0x4a/0x80
[ 212.761024] __kmalloc+0x118/0x1d0
[ 212.761030] ? reservation_object_copy_fences+0x38/0x100
[ 212.761038] reservation_object_copy_fences+0x38/0x100
[ 212.761054] ttm_bo_unref+0x12b/0x330 [ttm]
[ 212.761117] amdgpu_bo_unref+0x2a/0x50 [amdgpu]
[ 212.761160] amdgpu_vm_free_levels+0x2b/0x60 [amdgpu]
[ 212.761206] amdgpu_vm_free_levels+0x48/0x60 [amdgpu]
[ 212.761252] amdgpu_vm_fini+0x201/0x280 [amdgpu]
[ 212.761289] amdgpu_driver_postclose_kms+0x111/0x1f0 [amdgpu]
[ 212.761320] drm_release+0x265/0x380 [drm]
[ 212.761324] __fput+0xbe/0x200
[ 212.761328] ____fput+0xe/0x10
[ 212.761331] task_work_run+0x99/0xd0
[ 212.761336] do_exit+0x2e6/0xb70
[ 212.761339] ? __do_page_fault+0x273/0x4f0
[ 212.761342] do_group_exit+0x3b/0xb0
[ 212.761345] SyS_exit_group+0x14/0x20
[ 212.761348] do_syscall_64+0x74/0x1d0
[ 212.761352] entry_SYSCALL64_slow_path+0x25/0x25
[ 212.761354] RIP: 0033:0x3586ebec80
[ 212.761356] RSP: 002b:00007ffecb885588 EFLAGS: 00000246 ORIG_RAX:
00000000000000e7
[ 212.761359] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000003586ebec80
[ 212.761361] RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
[ 212.761363] RBP: 00000035871a28b8 R08: 00000000000000e7 R09: ffffffffffffff58
[ 212.761364] R10: 0000003588c15168 R11: 0000000000000246 R12: 00000035871a28b8
[ 212.761365] R13: 00000035871a7d40 R14: 0000000000000000 R15: 0000000000000000
before I start digging in the code: have someone seen this issue before?
Thanks!
--
Ricardo Ribalda
More information about the amd-gfx
mailing list