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: Fri, 09 Feb 2018 09:28:17 +0000 [thread overview]
Message-ID: <bug-104082-502-wTsoDOwHeP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104082-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 676 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #20 from Stratos Zolotas <strzol@gmail.com> ---
(In reply to Michel Dänzer from comment #19)
>
> That's either simply coincidence, or means the kernel ran out of memory. The
> messages this report is about are triggered by transient memory allocation
> failures, for which there is a fallback path.
Maybe it is a coincidence, for sure I'm not running out of memory when it is
happening and started with kernel 4.15 and (or) Mesa 18.0 without any change on
Virtualbox side. I'll wait for the fix to see what happens...
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1569 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-09 9:28 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 [this message]
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
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-wTsoDOwHeP@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