On Fri, Apr 17, 2015 at 05:14:20PM +0200, Dorian Gray wrote: > On 16 April 2015 at 20:42, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
