From mboxrd@z Thu Jan 1 00:00:00 1970 From: w@1wt.eu (Willy Tarreau) Date: Thu, 17 Jul 2014 10:15:27 +0200 Subject: Issue found in Armada 370: "No buffer space available" error during continuous ping In-Reply-To: References: <20140708102142.0f7fe796@free-electrons.com> <20140715142431.4eccbcd6@free-electrons.com> <20140715124333.GF12333@1wt.eu> Message-ID: <20140717081527.GJ14723@1wt.eu> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Maggie, On Wed, Jul 16, 2014 at 10:37:47PM -0700, Maggie Mae Roxas wrote: > Hi Thomas, Willy, > Good day. > > First of all, thanks again for looking further into this. > > > Maggie, do you know if it is possible that for any reason your board > > would not deliver an IRQ on Tx completion ? That could explain things. > > I'm sorrry but I'm not really sure how to check this - all I know is > that the difference in the working and not-working setup (both > software and hardware) is the mvneta.c. In fact I don't know if you're running your own board or a "standard" one (a mirabox or any NAS board). Because that could also be one of the differences between what you observe on your side and our respective experiences with our boards. > > You can easily test reverting commit 4f3a4f701b just in case. If that's > > the case, then the next step will be to figure out how it is possible > > that IRQs are disabled! > I'll try this one, specifcally this combination: > - use 3.13.9 mvneta.c > - apply cd71e246c16b30e3f396a85943d5f596202737ba > - revert 4f3a4f701b59a3e4b5c8503ac3d905c0a326f922 > > I will update you the results within today until latest tomorrow. OK fine, thank you! Willy