Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S934619AbdLRTMe convert rfc822-to-8bit (ORCPT <rfc822;w@1wt.eu>);
        Mon, 18 Dec 2017 14:12:34 -0500
Received: from mout.gmx.net ([212.227.15.19]:56801 "EHLO mout.gmx.net"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S934044AbdLRTM3 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 18 Dec 2017 14:12:29 -0500
Message-ID: <1513624332.7942.8.camel@gmx.de>
Subject: Re: nouveau. swiotlb: coherent allocation failed for device
 0000:01:00.0 size=2097152
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>
Date: Mon, 18 Dec 2017 20:12:12 +0100
In-Reply-To: <a083d576-215f-eb76-278b-741fc65fb138@mni.thm.de>
References: <1513620418.7113.51.camel@gmx.de>
         <a083d576-215f-eb76-278b-741fc65fb138@mni.thm.de>
Content-Type: text/plain; charset="ISO-8859-15"
X-Mailer: Evolution 3.20.5 
Mime-Version: 1.0
Content-Transfer-Encoding: 8BIT
X-Provags-ID: V03:K0:/Wiu3+j3iUw0gs3M23po6mQ8qBLtcCapFqK43evcA2CRtP92Haj
 9KUXnZv5CxdQoJIWDJTBCmE24D4QfzF3S/Cq4pbl49DoEVClOA7hww4zwlBVfsLSK92hng4
 /0e/4HiZ8abo5xhGTIuVzEBYFj4kBorvW/lmrmUnyTE/sYPu0T2hTN2mC9F7K2gEopTwDcn
 v06rkSuiMQv0QgB2f/qag==
X-UI-Out-Filterresults: notjunk:1;V01:K0:QrPFbxmGf08=:K/EXBjDtml+h3TXN7VNute
 wZCF/1cTzBYGHHb+XkiKIL401ZS4eYcaAypVqBe3yXsU+/Xcq5mECKCbNxhu1ZoJ5N5HCPoSc
 cCGe99pX6zAxn3BD4NmgcvWTW9O9VoI63Ef9H+tAdVue15TRZozENKFXhCKyxR2chFwmZNP3R
 5eGKz3bQybRDxWCa82S10pXe5aP4AEuCwSnLZZRSGW9P+DJj//qNZhLK7rbEgliw+91/opVv3
 mChfcabIPp00Xf1bD8cgdYN8GfXQXbx1cAs9wugoZ77xJezgkrnC+nvEFOHpoWBFSm4sATGUe
 tDJIl92yE6FA2JeuTzQMaXhWZVQVZC4TdWONc6wotD/wsj+qcuVsCtgWCXf2140x/VvBKaYDG
 f5G+fCk/KyxJGizTK/eQ1fDg+/LZjKEooFE9a02pYFgc/ZoiK9LaSPK3L4HjPkSkatJMfuXWN
 wsUw9iKylgnHIUjFhVOFwu/eCtTmr2iV9VTFv21zu/rnlQ/4GmJaiNCTKTS9ZXZlOFhNoYVL8
 xJiWWsFb9weFK0EbULV95lBS7EUOVp6YxEljft5v42Ntg5WznaOKCeHKn/DeRmcvTj8R4Sxha
 sS1CSreWhw/EwsX4pQhF8uRYu2cNBITtrmG0NfhvcM0KMvxrxpewaocYLDC1C7rH4893SplBp
 Gbx1dUJoovDWeytc0dNn+wlOvgGKaELpXR14UJbUah2UaVe8s7iksPALXTXmIc2XGhnGGOCEm
 cD3vSHKlA6969mdwzZ9C6jvu80fTEZjdg3PdaFBQhUsimnTi6h1hB51bKkWwN0JAhPuicjSl+
 kk0IrRFSOibdz08nBW/ULaRMri1iGpQ7L+POywtIGGLzZMp+A8=
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 840
Lines: 22

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