Created attachment 174121 [details] dmesg Playing counter strike: global offensive with mesa git and PRIME on 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wimbledon XT [Radeon HD 7970M] (rev ff) After a while the graphical output froze with BUG: unable to handle kernel paging request at ffff8002a30769f8. IP: [<ffffffff8140a01b>] reservation_object_add_shared_fence+0x17b/0x2b0 Call Trace: [<ffffffffa0064705>] ttm_eu_fence_buffer_objects+0x55/0xb0 [ttm] [<ffffffffa02312eb>] radeon_cs_parser_fini+0x20b/0x230 [radeon] [<ffffffffa0231ba1>] radeon_cs_ioctl+0x3b1/0x810 [radeon] [<ffffffffa001bcaf>] drm_ioctl+0x1df/0x680 [drm] [<ffffffffa01f704c>] radeon_drm_ioctl+0x4c/0x80 [radeon] [<ffffffffa02fbbf4>] radeon_kms_compat_ioctl+0x14/0x30 [radeon] [<ffffffff81226560>] compat_SyS_ioctl+0xf0/0x1250 [<ffffffff810f37e4>] ? compat_SyS_futex+0x84/0x1a0 [<ffffffff81569572>] ? __schedule+0x382/0xa00 [<ffffffff8156ffc6>] sysenter_dispatch+0x7/0x25 Full dmesg attached. I don't think I have debug symbols here, so no further details at this time. It only happened after quite a while, so it's not easily reproducable. Just putting it here because I haven't seen a report like this.
Created attachment 226841 [details] dmesg with stacktrace used for getting line numbers With 4.7 it's still happening. I finally built a kernel with debug symbols because on Intel graphics I also have something like this... I assume people have looked at the functions, but maybe some line numbers for the 4.7.0 release help. BUG: unable to handle kernel paging request at ffff80048f666920 IP: [<ffffffffa0635502>] ttm_bo_del_from_lru+0x92/0xb0 [ttm] Line 89 of "include/linux/list.h" ... Call Trace: [<ffffffffa063b5a9>] ttm_eu_reserve_buffers+0x2b9/0x370 [ttm] Line 53 of "drivers/gpu/drm/ttm/ttm_execbuf_util.c" [<ffffffffa0bd4d30>] radeon_bo_list_validate+0xa0/0x220 [radeon] Line 532 of "drivers/gpu/drm/radeon/radeon_object.c" [<ffffffff811fba8d>] ? __kmalloc+0x3d/0x240 [<ffffffffa0beb666>] radeon_cs_parser_relocs+0x356/0x440 [radeon] Line 187 of "drivers/gpu/drm/radeon/radeon_cs.c" [<ffffffffa0bec08a>] radeon_cs_ioctl+0x28a/0x7c0 [radeon] Line 675 of "drivers/gpu/drm/radeon/radeon_cs.c" [<ffffffffa0005fde>] drm_ioctl+0x15e/0x550 [drm] [<ffffffff81110d8f>] ? futex_wake+0x9f/0x180 [<ffffffffa0bebe00>] ? radeon_cs_parser_init+0x4f0/0x4f0 [radeon] [<ffffffff811129e5>] ? do_futex+0x2f5/0xc10 [<ffffffffa0bb4062>] radeon_drm_ioctl+0x62/0xa0 [radeon] [<ffffffff812347e2>] do_vfs_ioctl+0xb2/0x5e0 [<ffffffff81644e14>] ? __schedule+0x304/0x7b0 [<ffffffff8124077a>] ? __fget+0x8a/0xc0 [<ffffffff81234d98>] SyS_ioctl+0x88/0xa0 [<ffffffff816497b2>] entry_SYSCALL_64_fastpath+0x1a/0xa4
It's not clear that those are both one and the same bug.