From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104082] amdgpu 0000:07:00.0: swiotlb buffer is full (sz: 2097152 bytes)
Date: Sat, 10 Feb 2018 19:46:45 +0000 [thread overview]
Message-ID: <bug-104082-502-dEZLSl6Ybx@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104082-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2888 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #26 from mikhail.v.gavrilov@gmail.com ---
[65574.681417] amdgpu 0000:07:00.0: swiotlb buffer is full (sz: 2097152 bytes)
[65574.681436] swiotlb: coherent allocation failed for device 0000:07:00.0
size=2097152
[65574.681439] CPU: 3 PID: 4658 Comm: steam Not tainted 4.15.0-rc4-amd-vega+
#13
[65574.681441] Hardware name: Gigabyte Technology Co., Ltd. Z87M-D3H/Z87M-D3H,
BIOS F11 08/12/2014
[65574.681443] Call Trace:
[65574.681452] dump_stack+0x8e/0xd6
[65574.681457] swiotlb_alloc_coherent+0xe8/0x160
[65574.681466] x86_swiotlb_alloc_coherent+0x43/0x50
[65574.681476] ttm_dma_pool_get_pages+0x230/0x630 [ttm]
[65574.681492] ttm_dma_populate+0x139/0x360 [ttm]
[65574.681534] amdgpu_ttm_tt_populate+0xd0/0xf0 [amdgpu]
[65574.681541] ttm_tt_bind+0x2b/0x60 [ttm]
[65574.681547] ttm_bo_handle_move_mem+0x566/0x5a0 [ttm]
[65574.681552] ? ttm_bo_mem_space+0x37a/0x450 [ttm]
[65574.681566] ttm_bo_validate+0x186/0x1a0 [ttm]
[65574.681577] ? mutex_trylock+0xd4/0xf0
[65574.681585] ttm_bo_init_reserved+0x472/0x500 [ttm]
[65574.681617] amdgpu_bo_do_create+0x216/0x550 [amdgpu]
[65574.681646] ? amdgpu_fill_buffer+0x2f0/0x2f0 [amdgpu]
[65574.681655] ? __lock_acquire+0x2d4/0x1350
[65574.681686] amdgpu_bo_create+0x4d/0x2e0 [amdgpu]
[65574.681721] amdgpu_gem_object_create+0x81/0x110 [amdgpu]
[65574.681752] ? amdgpu_gem_object_close+0x210/0x210 [amdgpu]
[65574.681776] amdgpu_gem_create_ioctl+0x1f4/0x280 [amdgpu]
[65574.681782] ? __might_fault+0x3e/0x90
[65574.681809] ? amdgpu_gem_object_close+0x210/0x210 [amdgpu]
[65574.681829] drm_ioctl_kernel+0x5d/0xb0 [drm]
[65574.681842] drm_ioctl+0x31b/0x3d0 [drm]
[65574.681865] ? amdgpu_gem_object_close+0x210/0x210 [amdgpu]
[65574.681875] ? trace_hardirqs_on_caller+0xf4/0x190
[65574.681880] ? trace_hardirqs_on+0xd/0x10
[65574.681908] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu]
[65574.681941] amdgpu_kms_compat_ioctl+0x14/0x20 [amdgpu]
[65574.681946] compat_SyS_ioctl+0x6f9/0x1d60
[65574.681949] ? trace_hardirqs_on_caller+0xf4/0x190
[65574.681959] do_fast_syscall_32+0xb0/0x374
[65574.681965] entry_SYSENTER_compat+0x51/0x60
[65574.681969] RIP: 0023:0xf7f47db9
[65574.681971] RSP: 002b:00000000ff836fe8 EFLAGS: 00200286 ORIG_RAX:
0000000000000036
[65574.681975] RAX: ffffffffffffffda RBX: 0000000000000013 RCX:
00000000c0206440
[65574.681977] RDX: 00000000ff83707c RSI: 0000000058c9cbc0 RDI:
00000000c0206440
[65574.681979] RBP: 0000000000000013 R08: 0000000000000000 R09:
0000000000000000
[65574.681981] R10: 0000000000000000 R11: 0000000000000000 R12:
0000000000000000
[65574.681983] R13: 0000000000000000 R14: 0000000000000000 R15:
0000000000000000
[65736.626861] Xwayland (2026) used greatest stack depth: 9712 bytes left
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3698 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-02-10 19:46 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 18:47 [Bug 104082] amdgpu 0000:07:00.0: swiotlb buffer is full (sz: 2097152 bytes) bugzilla-daemon
2017-12-22 9:41 ` bugzilla-daemon
2017-12-22 9:41 ` bugzilla-daemon
2017-12-23 16:53 ` bugzilla-daemon
2017-12-23 16:55 ` bugzilla-daemon
2017-12-27 0:40 ` bugzilla-daemon
2018-01-02 12:09 ` bugzilla-daemon
2018-01-16 3:22 ` bugzilla-daemon
2018-01-18 14:41 ` bugzilla-daemon
2018-01-18 15:02 ` bugzilla-daemon
2018-01-28 15:15 ` bugzilla-daemon
2018-01-31 10:21 ` bugzilla-daemon
2018-01-31 11:23 ` bugzilla-daemon
2018-02-06 19:40 ` bugzilla-daemon
2018-02-06 20:20 ` bugzilla-daemon
2018-02-08 13:49 ` bugzilla-daemon
2018-02-09 3:09 ` bugzilla-daemon
2018-02-09 9:09 ` bugzilla-daemon
2018-02-09 9:19 ` bugzilla-daemon
2018-02-09 9:24 ` bugzilla-daemon
2018-02-09 9:28 ` bugzilla-daemon
2018-02-09 9:51 ` bugzilla-daemon
2018-02-09 10:13 ` bugzilla-daemon
2018-02-09 12:27 ` bugzilla-daemon
2018-02-09 13:00 ` bugzilla-daemon
2018-02-09 14:01 ` bugzilla-daemon
2018-02-10 19:46 ` bugzilla-daemon [this message]
2018-02-10 20:55 ` bugzilla-daemon
2018-02-11 10:07 ` bugzilla-daemon
2018-02-11 10:09 ` bugzilla-daemon
2018-02-11 14:25 ` bugzilla-daemon
2018-02-11 18:28 ` bugzilla-daemon
2018-02-12 3:30 ` bugzilla-daemon
2018-02-12 3:31 ` bugzilla-daemon
2018-02-12 8:05 ` bugzilla-daemon
2018-03-03 20:05 ` bugzilla-daemon
2018-03-23 4:07 ` bugzilla-daemon
2018-03-23 4:07 ` bugzilla-daemon
2018-03-23 4:10 ` bugzilla-daemon
2018-03-31 13:46 ` bugzilla-daemon
2018-04-04 21:50 ` bugzilla-daemon
2018-04-20 13:28 ` bugzilla-daemon
2018-04-21 15:51 ` bugzilla-daemon
2018-04-22 7:24 ` bugzilla-daemon
2018-04-25 20:28 ` bugzilla-daemon
2018-04-25 20:29 ` bugzilla-daemon
2018-04-26 8:36 ` bugzilla-daemon
2018-04-26 8:46 ` bugzilla-daemon
2018-04-27 10:50 ` bugzilla-daemon
2018-04-27 23:11 ` bugzilla-daemon
2018-04-27 23:17 ` bugzilla-daemon
2018-05-01 13:34 ` bugzilla-daemon
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-104082-502-dEZLSl6Ybx@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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