From: w@1wt.eu (Willy Tarreau)
To: linux-arm-kernel@lists.infradead.org
Subject: Issue found in Armada 370: "No buffer space available" error during continuous ping
Date: Thu, 17 Jul 2014 10:15:27 +0200 [thread overview]
Message-ID: <20140717081527.GJ14723@1wt.eu> (raw)
In-Reply-To: <CAB8gEUt08QVpgW0fs18tNnCkCw36SD6hxgL8O6p6+oOtX0-yJQ@mail.gmail.com>
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
next prev parent reply other threads:[~2014-07-17 8:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 2:20 Issue found in Armada 370: "No buffer space available" error during continuous ping Maggie Mae Roxas
2014-07-08 2:27 ` Maggie Mae Roxas
2014-07-08 8:21 ` Thomas Petazzoni
2014-07-09 6:35 ` Maggie Mae Roxas
2014-07-14 3:55 ` Maggie Mae Roxas
2014-07-15 12:24 ` Thomas Petazzoni
2014-07-15 12:43 ` Willy Tarreau
2014-07-17 5:37 ` Maggie Mae Roxas
2014-07-17 8:15 ` Willy Tarreau [this message]
2014-07-21 1:57 ` Maggie Mae Roxas
2014-07-21 2:45 ` Maggie Mae Roxas
2014-07-21 5:44 ` Willy Tarreau
2014-07-21 6:33 ` Maggie Mae Roxas
2014-07-21 7:03 ` Willy Tarreau
2014-07-23 2:24 ` Maggie Mae Roxas
2014-07-23 6:16 ` Willy Tarreau
2014-07-24 7:24 ` Maggie Mae Roxas
2014-12-01 6:35 ` Maggie Mae Roxas
[not found] ` <CAB8gEUtgo-8nets3tRtqiZ8qRx+SyCq2d8v05scavWNwE5TNXg@mail.gmail.com>
2014-12-01 7:28 ` Willy Tarreau
2014-12-01 8:27 ` Maggie Mae Roxas
2014-12-01 9:28 ` Willy Tarreau
2014-12-01 9:32 ` Thomas Petazzoni
2014-12-01 9:58 ` Willy Tarreau
2014-12-01 10:15 ` Maggie Mae Roxas
2014-12-02 4:09 ` Maggie Mae Roxas
2014-12-02 6:56 ` Willy Tarreau
2014-12-02 7:04 ` Maggie Mae Roxas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140717081527.GJ14723@1wt.eu \
--to=w@1wt.eu \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).