Displaying 8 results from an estimated 8 matches similar to: "nouveau. swiotlb: coherent allocation failed for device 0000:01:00.0 size=2097152"
2017 Dec 18
0
nouveau. swiotlb: coherent allocation failed for device 0000:01:00.0 size=2097152
On 12/18/17 7:06 PM, Mike Galbraith wrote:
> Greetings,
>
> Kernel bound workloads seem to trigger the below for whatever reason.
> I only see this when beating up NFS. There was a kworker wakeup
> latency issue, but with a bandaid applied to fix that up, I can still
> trigger this.
Hi,
i have seen this one as well with my system, but i could not find an
easy way to
2018 Apr 09
0
nouveau: swiotlb buffer is full (sz: 2097152 bytes)/swiotlb: coherent allocation failed, size=2097152 spam
Greetings,
Box is i4790 w. GTX 980 running virgin master (.today).
All I have to do to trigger a slew of these warnings is to fire up
firefox, point it at a youtube clip, and let it autoplay while I do
routine kernel merge/build maintenance. nouveau doesn't seem to care
deeply, but moans again and again and again...
726 [ 2.743823] fb: switching to nouveaufb from EFI VGA
727 [
2017 Dec 31
0
nouveau. swiotlb: coherent allocation failed for device 0000:01:00.0 size=2097152
On Tue, Dec 19, 2017 at 8:45 AM, Christian König
<ckoenig.leichtzumerken at gmail.com> wrote:
> Am 19.12.2017 um 11:39 schrieb Michel Dänzer:
>>
>> On 2017-12-19 11:37 AM, Michel Dänzer wrote:
>>>
>>> On 2017-12-18 08:01 PM, Tobias Klausmann wrote:
>>>>
>>>> On 12/18/17 7:06 PM, Mike Galbraith wrote:
>>>>>
2017 Dec 19
0
nouveau. swiotlb: coherent allocation failed for device 0000:01:00.0 size=2097152
On 2017-12-19 11:37 AM, Michel Dänzer wrote:
> On 2017-12-18 08:01 PM, Tobias Klausmann wrote:
>> On 12/18/17 7:06 PM, Mike Galbraith wrote:
>>> Greetings,
>>>
>>> Kernel bound workloads seem to trigger the below for whatever reason.
>>> I only see this when beating up NFS. There was a kworker wakeup
>>> latency issue, but with a bandaid
2018 Jan 01
0
nouveau. swiotlb: coherent allocation failed for device 0000:01:00.0 size=2097152
On Sun, Dec 31, 2017 at 3:53 PM, Mike Galbraith <efault at gmx.de> wrote:
> On Sun, 2017-12-31 at 13:27 -0500, Ilia Mirkin wrote:
>> On Tue, Dec 19, 2017 at 8:45 AM, Christian König
>> <ckoenig.leichtzumerken at gmail.com> wrote:
>> > Am 19.12.2017 um 11:39 schrieb Michel Dänzer:
>> >>
>> >> On 2017-12-19 11:37 AM, Michel Dänzer wrote:
2017 Dec 19
2
nouveau. swiotlb: coherent allocation failed for device 0000:01:00.0 size=2097152
On 2017-12-18 08:01 PM, Tobias Klausmann wrote:
> On 12/18/17 7:06 PM, Mike Galbraith wrote:
>> Greetings,
>>
>> Kernel bound workloads seem to trigger the below for whatever reason.
>> I only see this when beating up NFS. There was a kworker wakeup
>> latency issue, but with a bandaid applied to fix that up, I can still
>> trigger this.
>
>
>
2017 Dec 19
2
nouveau. swiotlb: coherent allocation failed for device 0000:01:00.0 size=2097152
Am 19.12.2017 um 11:39 schrieb Michel Dänzer:
> On 2017-12-19 11:37 AM, Michel Dänzer wrote:
>> On 2017-12-18 08:01 PM, Tobias Klausmann wrote:
>>> On 12/18/17 7:06 PM, Mike Galbraith wrote:
>>>> Greetings,
>>>>
>>>> Kernel bound workloads seem to trigger the below for whatever reason.
>>>> I only see this when beating up NFS.
2017 Dec 31
2
nouveau. swiotlb: coherent allocation failed for device 0000:01:00.0 size=2097152
On Sun, 2017-12-31 at 13:27 -0500, Ilia Mirkin wrote:
> On Tue, Dec 19, 2017 at 8:45 AM, Christian König
> <ckoenig.leichtzumerken at gmail.com> wrote:
> > Am 19.12.2017 um 11:39 schrieb Michel Dänzer:
> >>
> >> On 2017-12-19 11:37 AM, Michel Dänzer wrote:
> >>>
> >>> On 2017-12-18 08:01 PM, Tobias Klausmann wrote:
> >>>>