From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Error: DMA: Out of SW-IOMMU space [was: External USB drives become unresponsive after few hours.] Date: Fri, 17 Apr 2015 16:06:24 -0400 Message-ID: <20150417200623.GA14442@l.oracle.com> References: <552FCD25.9060807@gmail.com> <20150416184252.GE7388@x230.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Dorian Gray Cc: USB list , Kernel development list , Alexander Duyck , iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, Alan Stern List-Id: iommu@lists.linux-foundation.org On Fri, Apr 17, 2015 at 05:14:20PM +0200, Dorian Gray wrote: > On 16 April 2015 at 20:42, Konrad Rzeszutek Wilk wrote: > > And easier way is to compile the kernel with CONFIG_DMA_API_DEBUG > > and then load the attached module. > > > > That should tell you who and what else is holding on the buffers. > > Ok, I have compiled 3.19.4 w/ CONFIG_DMA_API_DEBUG=y + the module you sent me. > Now, I'm not sure if I've done it right - I waited until the error > occured and then modprobe'd dump_dma. > I have attached the kernel log, but it tells me not much, if anything... The network driver is quite hungry for DMA. Did it do the same thing in the earlier kernels? Thanks. > > Thanks again. > Jake