From: Mike Galbraith <efault@gmx.de>
To: Tobias Klausmann <tobias.johannes.klausmann@mni.thm.de>,
LKML <linux-kernel@vger.kernel.org>
Cc: Ben Skeggs <bskeggs@redhat.com>,
nouveau <nouveau@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: nouveau. swiotlb: coherent allocation failed for device 0000:01:00.0 size=2097152
Date: Mon, 18 Dec 2017 20:12:12 +0100 [thread overview]
Message-ID: <1513624332.7942.8.camel@gmx.de> (raw)
In-Reply-To: <a083d576-215f-eb76-278b-741fc65fb138@mni.thm.de>
On Mon, 2017-12-18 at 20:01 +0100, 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.
>
>
> Hi,
>
> i have seen this one as well with my system, but i could not find an
> easy way to trigger it for bisecting purpose. If you can trigger it
> conveniently, a bisect would be nice!
Workload permitting. To reproduce, mount your box NFS, cd to somewhere
the NFS mount, and just do bonnie -s <memory size>. There, maybe
you'll beat me to it. I hope so, I have multiple kernels doing the
annoying "baby birds in a nest" thing at me literally endlessly :)
-Mike
next prev parent reply other threads:[~2017-12-18 19:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 18:06 nouveau. swiotlb: coherent allocation failed for device 0000:01:00.0 size=2097152 Mike Galbraith
2017-12-18 19:01 ` Tobias Klausmann
2017-12-18 19:12 ` Mike Galbraith [this message]
2017-12-19 10:37 ` Michel Dänzer
2017-12-19 10:39 ` Michel Dänzer
2017-12-19 13:45 ` Christian König
2017-12-31 18:27 ` Ilia Mirkin
2017-12-31 20:53 ` Mike Galbraith
2018-01-01 18:08 ` Ilia Mirkin
2018-01-02 9:43 ` Christian König
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=1513624332.7942.8.camel@gmx.de \
--to=efault@gmx.de \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=tobias.johannes.klausmann@mni.thm.de \
/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