From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 104082] amdgpu 0000:07:00.0: swiotlb buffer is full (sz: 2097152 bytes) Date: Sat, 21 Apr 2018 15:51:35 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1601666785==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 9AEA06E089 for ; Sat, 21 Apr 2018 15:51:35 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1601666785== Content-Type: multipart/alternative; boundary="152432589510.148D4aE0.20543" Content-Transfer-Encoding: 7bit --152432589510.148D4aE0.20543 Date: Sat, 21 Apr 2018 15:51:35 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D104082 --- Comment #41 from Jean Delvare --- Bah, I spoke too fast. Even with commit 9e7f06c8beee ("swiotlb: fix unexpec= ted swiotlb_alloc_coherent failures") backported, I end up seeing the backtraces again, after several hours. So that commit helps but doesn't solve the prob= lem. It seems there are at least 3 different bugs leading to the same problem. --=20 You are receiving this mail because: You are the assignee for the bug.= --152432589510.148D4aE0.20543 Date: Sat, 21 Apr 2018 15:51:35 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comme= nt # 41 on bug 10408= 2 from = Jean Delvare 
Bah, I spoke too fast. Even with commit 9e7f06c8beee ("sw=
iotlb: fix unexpected
swiotlb_alloc_coherent failures") backported, I end up seeing the back=
traces
again, after several hours. So that commit helps but doesn't solve the prob=
lem.
It seems there are at least 3 different bugs leading to the same problem.

You are receiving this mail because:
  • You are the assignee for the bug.
= --152432589510.148D4aE0.20543-- --===============1601666785== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1601666785==--