From: Mike Galbraith <efault-Mmb7MZpHnFY@public.gmane.org>
To: "Ilia Mirkin" <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>,
"Christian König" <christian.koenig-5C7GfCeVMHo@public.gmane.org>
Cc: nouveau
<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
"Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
dri-devel
<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
"Ben Skeggs" <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: nouveau. swiotlb: coherent allocation failed for device 0000:01:00.0 size=2097152
Date: Sun, 31 Dec 2017 21:53:38 +0100 [thread overview]
Message-ID: <1514753618.20829.3.camel@gmx.de> (raw)
In-Reply-To: <CAKb7Uvgt+SOwf6i2kAzEz65VTGzP6vYb2nBD+78FnXLtMZfOvg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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@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:
> >>>>>
> >>>>> 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!
> >>>
> >>> I'm seeing this (with the amdgpu and radeon drivers) when restic takes a
> >>> backup, creating memory pressure. I happen to have just finished
> >>> bisecting, the result is:
> >>>
> >>> 648bc3574716400acc06f99915815f80d9563783 is the first bad commit
> >>> commit 648bc3574716400acc06f99915815f80d9563783
> >>> Author: Christian König <christian.koenig@amd.com>
> >>> Date: Thu Jul 6 09:59:43 2017 +0200
> >>>
> >>> drm/ttm: add transparent huge page support for DMA allocations v2
> >>>
> >>> Try to allocate huge pages when it makes sense.
> >>>
> >>> v2: fix comment and use ifdef
> >>>
> >>>
> >> BTW, I haven't noticed any bad effects other than the dmesg splats, so
> >> maybe it's just noise about transient failures for which there is a
> >> proper fallback in place.
> >
> >
> > Yeah, I think that is exactly what happens here.
> >
> > We try to allocate a huge page, but fail and so fall back to using multiple
> > 4k pages instead.
> >
> > Going to send out a patch to suppress the warning.
>
> Hi Christian,
>
> Did you ever send out such a patch? I didn't see one on the list, but
> perhaps I missed it. One definitely hasn't made it upstream yet. (I
> just hit the issue myself with Linus's tree from last night.)
Actually, that wants a bit more methinks, because while the stack dump
goes away, you still get spammed, it just comes in smaller chunks.
-Mike
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2017-12-31 20:53 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
[not found] ` <1513620418.7113.51.camel-Mmb7MZpHnFY@public.gmane.org>
2017-12-18 19:01 ` Tobias Klausmann
[not found] ` <a083d576-215f-eb76-278b-741fc65fb138-AqjdNwhu20eELgA04lAiVw@public.gmane.org>
2017-12-18 19:12 ` Mike Galbraith
2017-12-19 10:37 ` Michel Dänzer
[not found] ` <f447948f-cfad-f4ea-4c41-54e42a733c16-otUistvHUpPR7s880joybQ@public.gmane.org>
2017-12-19 10:39 ` Michel Dänzer
2017-12-19 13:45 ` Christian König
[not found] ` <e1b8dd62-4423-2b51-9634-e8938801b5d9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-12-31 18:27 ` Ilia Mirkin
[not found] ` <CAKb7Uvgt+SOwf6i2kAzEz65VTGzP6vYb2nBD+78FnXLtMZfOvg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-31 20:53 ` Mike Galbraith [this message]
[not found] ` <1514753618.20829.3.camel-Mmb7MZpHnFY@public.gmane.org>
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=1514753618.20829.3.camel@gmx.de \
--to=efault-mmb7mzphnfy@public.gmane.org \
--cc=bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=christian.koenig-5C7GfCeVMHo@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michel-otUistvHUpPR7s880joybQ@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).