Re: dmatest regression in 3.10-rc1

2013-05-21 Thread Andy Shevchenko
On Mon, 2013-05-20 at 10:58 +0100, Will Deacon wrote: > Sure. They way I trigger it is to unload the module whilst the DMA is > ongoing (I'm using a software model, so I can make the DMA nice and slow -- > I guess you could try using some large buffers). Thank you for the script. It looks like I

Re: dmatest regression in 3.10-rc1

2013-05-20 Thread Will Deacon
Hi Andy, On Mon, May 20, 2013 at 08:52:34AM +0100, Andy Shevchenko wrote: > On Fri, 2013-05-17 at 15:18 +0100, Will Deacon wrote: > > On Fri, May 17, 2013 at 01:34:23PM +0100, Vinod Koul wrote: > > > On Thu, May 16, 2013 at 04:35:53PM +0100, Will Deacon wrote: > > > > Right, so I think I understa

Re: dmatest regression in 3.10-rc1

2013-05-20 Thread Andy Shevchenko
On Fri, 2013-05-17 at 15:18 +0100, Will Deacon wrote: > On Fri, May 17, 2013 at 01:34:23PM +0100, Vinod Koul wrote: > > On Thu, May 16, 2013 at 04:35:53PM +0100, Will Deacon wrote: > > > Right, so I think I understand what's causing this, but I'll leave it to > > > Andriy to suggest a fix. Thanks

Re: dmatest regression in 3.10-rc1

2013-05-17 Thread Will Deacon
Hi Vinod, Thanks for the reply. On Fri, May 17, 2013 at 01:34:23PM +0100, Vinod Koul wrote: > On Thu, May 16, 2013 at 04:35:53PM +0100, Will Deacon wrote: > > Right, so I think I understand what's causing this, but I'll leave it to > > Andriy to suggest a fix. The problem comes about because the

Re: dmatest regression in 3.10-rc1

2013-05-17 Thread Vinod Koul
On Thu, May 16, 2013 at 04:35:53PM +0100, Will Deacon wrote: > On Wed, May 15, 2013 at 04:28:03PM +0100, Will Deacon wrote: > > I've been observing a regression in the dmatest module with 3.10-rc1. It > > manifests as either: > > > > - a spurious timeout on one or more of the channel threads > >

Re: dmatest regression in 3.10-rc1

2013-05-16 Thread Will Deacon
On Wed, May 15, 2013 at 04:28:03PM +0100, Will Deacon wrote: > I've been observing a regression in the dmatest module with 3.10-rc1. It > manifests as either: > > - a spurious timeout on one or more of the channel threads > - a complete kernel lockup (loss of console) > - a panic (see below, no