dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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, 03 Mar 2018 20:05:05 +0000	[thread overview]
Message-ID: <bug-104082-502-cwuy6KNJyl@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104082-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2620 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104082

--- Comment #35 from Nick Lee <nvlbox@gmail.com> ---
The same on NVIDIA Corporation C79 [GeForce 9300 / nForce 730i] (rev b1).
This happens when high disk IO load. For example - copy foles from HDD to USB.

[30790.063300] nouveau 0000:03:00.0: swiotlb buffer is full (sz: 2097152 bytes)
[30790.063304] nouveau 0000:03:00.0: swiotlb: coherent allocation failed,
size=2097152
[30790.063308] CPU: 1 PID: 2071 Comm: gnome-shell Not tainted
4.16.0-0.rc3.git2.1.vanilla.knurd.1.fc27.x86_64 #1
[30790.063309] Hardware name: NVIDIA MCP7A/MCP7A, BIOS 6.00 PG 04/22/2009
[30790.063310] Call Trace:
[30790.063321]  dump_stack+0x5c/0x85
[30790.063326]  swiotlb_alloc_coherent+0x1be/0x1d0
[30790.063338]  ttm_dma_pool_get_pages+0x235/0x620 [ttm]
[30790.063345]  ttm_dma_populate+0x25e/0x350 [ttm]
[30790.063350]  ttm_tt_bind+0x2c/0x60 [ttm]
[30790.063356]  ttm_bo_handle_move_mem+0x577/0x5b0 [ttm]
[30790.063362]  ttm_bo_validate+0x120/0x130 [ttm]
[30790.063393]  ? drm_pcie_get_speed_cap_mask+0x8e/0xe0 [drm]
[30790.063398]  ttm_bo_init_reserved+0x378/0x420 [ttm]
[30790.063403]  ttm_bo_init+0x62/0xd0 [ttm]
[30790.063473]  ? nouveau_bo_invalidate_caches+0x10/0x10 [nouveau]
[30790.063516]  nouveau_bo_new+0x416/0x590 [nouveau]
[30790.063562]  ? nouveau_bo_invalidate_caches+0x10/0x10 [nouveau]
[30790.063605]  ? nouveau_gem_new+0x120/0x120 [nouveau]
[30790.063648]  nouveau_gem_new+0x5d/0x120 [nouveau]
[30790.063692]  nouveau_gem_ioctl_new+0x51/0xd0 [nouveau]
[30790.063706]  drm_ioctl_kernel+0x5b/0xb0 [drm]
[30790.063720]  drm_ioctl+0x2d5/0x370 [drm]
[30790.063764]  ? nouveau_gem_new+0x120/0x120 [nouveau]
[30790.063809]  nouveau_drm_ioctl+0x64/0xc0 [nouveau]
[30790.063815]  do_vfs_ioctl+0xa4/0x620
[30790.063818]  SyS_ioctl+0x74/0x80
[30790.063822]  do_syscall_64+0x74/0x180
[30790.063826]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[30790.063829] RIP: 0033:0x7f2a2164b8e7
[30790.063830] RSP: 002b:00007ffdc53b6bd8 EFLAGS: 00000246 ORIG_RAX:
0000000000000010
[30790.063833] RAX: ffffffffffffffda RBX: 000055c99031d960 RCX:
00007f2a2164b8e7
[30790.063834] RDX: 00007ffdc53b6c30 RSI: 00000000c0306480 RDI:
000000000000000c
[30790.063836] RBP: 00007ffdc53b6c30 R08: 0000000000000004 R09:
000055c99031d950
[30790.063837] R10: ffffffffffffffb0 R11: 0000000000000246 R12:
00000000c0306480
[30790.063839] R13: 000000000000000c R14: 000055c98cfab250 R15:
000055c98a0e4140
[30790.110592] nouveau 0000:03:00.0: swiotlb buffer is full (sz: 2097152 bytes)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3477 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

  parent reply	other threads:[~2018-03-03 20:05 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
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 [this message]
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-cwuy6KNJyl@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