https://bugs.freedesktop.org/show_bug.cgi?id=104082
Michel Dänzer changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #49 from Barto ---
full log error, it seems related to ttm code, I use the radeon driver (not
amdgpu) :
[20021.576712] radeon :01:00.0: swiotlb buffer is full (sz: 2097152 bytes)
[20021.576715] radeon :01:00.0: swiotlb: cohe
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #48 from Barto ---
the bug occurs also with radeon driver, and not only amdgpu :
radeon :01:00.0: swiotlb buffer is full (sz: 2097152 bytes)
radeon :01:00.0: swiotlb: coherent allocation failed, size=2097152
CPU: 1 PID: 979
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #47 from Jean Delvare ---
Problem still present in kernel 4.16.5. I guess I'll have to bisect it...
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #46 from ojab ---
Done, https://bugs.freedesktop.org/show_bug.cgi?id=106245
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@l
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #45 from Michel Dänzer ---
(In reply to ojab from comment #43)
> I'm not sure if it's another issue [...]
It is, please file your own report.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=104082
ojab changed:
What|Removed |Added
CC||o...@ojab.ru
--- Comment #44 from ojab ---
Crea
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #43 from ojab ---
Same here on ryzen 2400g + asus a320m-k w/ iommu disabled, vanilla kernel
4.16.4.
I'm not sure if it's another issue since it happens on driver loading and
backtrace looks like:
[Wed Apr 25 20:18:50 2018] dump_st
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #42 from Stratos Zolotas ---
I can confirm that I'm getting the backtraces on Opensuse Tumbleweed with
4.16.2 kernel installed. They appear fewer times now but every time I have a
flickering on my monitors (using a 3 monitor setup).
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #41 from Jean Delvare ---
Bah, I spoke too fast. Even with commit 9e7f06c8beee ("swiotlb: fix unexpected
swiotlb_alloc_coherent failures") backported, I end up seeing the backtraces
again, after several hours. So that commit helps bu
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #40 from Jean Delvare ---
I believe there are 2 incarnations of this bug, with the same symptoms but
different root causes.
The first bug is affecting kernels v4.14 and v4.15, it is caused by 2 MB
allocations failing too verbosely w
https://bugs.freedesktop.org/show_bug.cgi?id=104082
b...@nord-west.org changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #38 from mikhail.v.gavri...@gmail.com ---
Created attachment 138462
--> https://bugs.freedesktop.org/attachment.cgi?id=138462&action=edit
In 4.16.0-rc7 still not fixed
--
You are receiving this mail because:
You are the assignee f
https://bugs.freedesktop.org/show_bug.cgi?id=104082
mikhail.v.gavri...@gmail.com changed:
What|Removed |Added
Attachment #138301|dmesh 4.16-rc6 |dmesg 4.16-rc6
des
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #37 from mikhail.v.gavri...@gmail.com ---
Created attachment 138301
--> https://bugs.freedesktop.org/attachment.cgi?id=138301&action=edit
dmesh 4.16-rc6
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #36 from mikhail.v.gavri...@gmail.com ---
In which kernel mainline version merged patch for this issue?
I see that on `amd-staging-drm-next` branch which branched from 4.16-rc1 this
issue not happens now, but on mainline 4.16-rc6 stil
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #35 from Nick Lee ---
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 :03:00.0: swiotlb buffer is fu
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #34 from Christian König ---
Two seconds (In reply to mikhail.v.gavrilov from comment #33)
> Why are you sure what this totally harmless?
Those messages are a sympton and not a cause. E.g. take a look at your logs
again, gnome-shell
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #33 from mikhail.v.gavri...@gmail.com ---
Why are you sure what this totally harmless?
I have proof this this isn't it.
Look at my system log:
- I got message "amdgpu :07:00.0: swiotlb buffer is full (sz: 2097152
bytes)" at Feb 10
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #32 from mikhail.v.gavri...@gmail.com ---
Created attachment 137285
--> https://bugs.freedesktop.org/attachment.cgi?id=137285&action=edit
system log
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #31 from Christian König ---
(In reply to mikhail.v.gavrilov from comment #30)
> I didn't understand It's already fixed in which commit?
> If yes why I see this issue with latest build amd-staging-drm-next?
See here https://lkml.org
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #30 from mikhail.v.gavri...@gmail.com ---
(In reply to Christian König from comment #28)
> Ok setting this as fixed which hopefully makes people stop adding new
> comments to this bug report.
I didn't understand It's already fixed in
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #29 from Christian König ---
(In reply to Matthew Scheirer from comment #27)
> I do still get the swiotlib OOM errors without DC enabled, but they are
> fairly infrequent and don't panic crash the kernel. With DC enabled,
> swiotlib
https://bugs.freedesktop.org/show_bug.cgi?id=104082
Christian König changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #27 from Matthew Scheirer ---
(In reply to Christian König from comment #25)
> One interesting point is that this only seems to happen when DC is enabled,
> so that points to a possible memory leak there.
I do still get the swiotlib
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #26 from mikhail.v.gavri...@gmail.com ---
[65574.681417] amdgpu :07:00.0: swiotlb buffer is full (sz: 2097152 bytes)
[65574.681436] swiotlb: coherent allocation failed for device :07:00.0
size=2097152
[65574.681439] CPU: 3 PID
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #25 from Christian König ---
(In reply to Andreas Kilgus from comment #24)
> (In reply to Christian König from comment #23)
> > Take a look at /proc/pagetypeinfo. There must at least be pages at order 9
> > or higher for an 2MB swiot
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #24 from Andreas Kilgus ---
(In reply to Christian König from comment #23)
> Take a look at /proc/pagetypeinfo. There must at least be pages at order 9
> or higher for an 2MB swiotlb allocation to succeed.
OK, I had a look and if I
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #23 from Christian König ---
(In reply to Andreas Kilgus from comment #22)
> I am getting these messsages on my machine right now, too.
>
> total used free sharedbuffers cached
> Mem: 163867
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #22 from Andreas Kilgus ---
(In reply to Christian König from comment #21)
> (In reply to Stratos Zolotas from comment #20)
> > Maybe it is a coincidence, for sure I'm not running out of memory when it is
> > happening and started wi
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #21 from Christian König ---
(In reply to Stratos Zolotas from comment #20)
> 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
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #20 from Stratos Zolotas ---
(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
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #19 from Michel Dänzer ---
(In reply to Stratos Zolotas from comment #18)
> I can say that it is not completely harmless. I'm using virtualbox on my KDE
> plasma desktop and I have several crashes on windows VMs which are "aborted"
>
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #18 from Stratos Zolotas ---
(In reply to Michel Dänzer from comment #17)
> The swiotlb messages this report is about are harmless (though a fix is on
> the way anyway), the other issues you mention are probably not directly
> relate
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #17 from Michel Dänzer ---
(In reply to Matthew Scheirer from comment #16)
> I get this as well with a 290 on 4.15 ONLY when DC is enabled. Its a dirty
> enough taint to leave btrfs volumes in inconsistent states so its straight
> cr
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #16 from Matthew Scheirer ---
I get this as well with a 290 on 4.15 ONLY when DC is enabled. Its a dirty
enough taint to leave btrfs volumes in inconsistent states so its straight
crashing the kernel.
Feb 08 17:06:08 system kernel:
https://bugs.freedesktop.org/show_bug.cgi?id=104082
Stratos Zolotas changed:
What|Removed |Added
CC||str...@gmail.com
--- Comment #15 from
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #14 from Przemek ---
Yes, sorry, my bad. Wrong copy-paste action here. Thanks Alex.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #13 from Alex Deucher ---
https://lkml.org/lkml/2018/1/10/132
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedeskt
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #12 from Przemek ---
I dont know if it is related, but:
https://lkml.org/lkml/2018/1/16/106
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #11 from Przemek ---
Similar with Radeon R4 APU - a6 6310
Kernel 4.15, mesa 17.3.3:
"swiotlb_tbl_map_single: 10 callbacks suppressed
[76882.115961] amdgpu :00:01.0: swiotlb buffer is full (sz: 2097152 bytes)
[76882.115964] swiot
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #10 from Ed Tomlinson ---
Happening mesa 17.3 Kernel 4.15-rc9 on RX480 (4G) too
143575.460499] perf: interrupt took too long (3928 > 3910), lowering
kernel.perf_event_max_sample_rate to 50700
[146927.696615] [drm] {1920x1200, 2080x1
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #9 from Vedran Miletić ---
Same on RX580 (polaris10).
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
h
https://bugs.freedesktop.org/show_bug.cgi?id=104082
Alex Deucher changed:
What|Removed |Added
CC||ved...@miletic.net
--- Comment #8 from A
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #7 from mikhail.v.gavri...@gmail.com ---
Created attachment 136745
--> https://bugs.freedesktop.org/attachment.cgi?id=136745&action=edit
dmesg with 4.15.0-rc2 amd-staging-drm-next
--
You are receiving this mail because:
You are th
https://bugs.freedesktop.org/show_bug.cgi?id=104082
Christian König changed:
What|Removed |Added
CC||coolo...@gmail.com
--- Comment #6 fro
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #5 from Tom Englund ---
happends here aswell on various applications, i do however not really notice
any problems in the applications themself when it happends.
lscpi:
VGA compatible controller: Advanced Micro Devices, Inc. [AMD/AT
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #4 from Alexander Schlarb ---
Created attachment 136378
--> https://bugs.freedesktop.org/attachment.cgi?id=136378&action=edit
dmesg on M385X
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #3 from Alexander Schlarb ---
Same issue with AMD Radeon R9 M385X my Lenovo Y700ACZ laptop with linux-next
and Debian unstable Mesa (17.3.1-1).
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #2 from coolo...@gmail.com ---
Created attachment 136362
--> https://bugs.freedesktop.org/attachment.cgi?id=136362&action=edit
dmesg
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #1 from coolo...@gmail.com ---
also getting the same issue with my vega 56, linux 4.15, mesa-git
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mail
https://bugs.freedesktop.org/show_bug.cgi?id=104082
Bug ID: 104082
Summary: amdgpu :07:00.0: swiotlb buffer is full (sz:
2097152 bytes)
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
52 matches
Mail list logo
