On 2015.09.18 at 16:42 +, Chris Snook wrote:
> I think atl1e is the victim here, not the cause. It's probably the last
> device being brought up that wants to use the swiotlb, so you haven't seen
> other devices failing for the same reason. Can you post your dmesg or boot
> log from both a
On 2015.09.12 at 08:51 +0200, Markus Trippelsdorf wrote:
> With the current Linus git tree I get an occasional swiotlb allocation
> error during network setup at boot-time:
>
> ATL1E 0000:02:00.0: swiotlb buffer is full (sz: 529461 bytes)
> swiotlb: coherent allocation failed for
On 2015.09.12 at 08:51 +0200, Markus Trippelsdorf wrote:
> With the current Linus git tree I get an occasional swiotlb allocation
> error during network setup at boot-time:
>
> ATL1E 0000:02:00.0: swiotlb buffer is full (sz: 529461 bytes)
> swiotlb: coherent allocation failed for
On 2015.09.18 at 16:42 +, Chris Snook wrote:
> I think atl1e is the victim here, not the cause. It's probably the last
> device being brought up that wants to use the swiotlb, so you haven't seen
> other devices failing for the same reason. Can you post your dmesg or boot
> log from both a
With the current Linus git tree I get an occasional swiotlb allocation
error during network setup at boot-time:
ATL1E :02:00.0: swiotlb buffer is full (sz: 529461 bytes)
swiotlb: coherent allocation failed for device :02:00.0 size=529461
CPU: 0 PID: 200 Comm: ifconfig Not tainted 4.2.0
With the current Linus git tree I get an occasional swiotlb allocation
error during network setup at boot-time:
ATL1E :02:00.0: swiotlb buffer is full (sz: 529461 bytes)
swiotlb: coherent allocation failed for device :02:00.0 size=529461
CPU: 0 PID: 200 Comm: ifconfig Not tainted 4.2.0
6 matches
Mail list logo
