From: Aurelien Jarno <aurel32@debian.org>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>
Cc: 927825@bugs.debian.org, Jason Cooper <jason@lakedaemon.net>,
Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
netdev@vger.kernel.org, Marcin Wojtas <mw@semihalf.com>,
Steve McIntyre <steve@einval.com>
Subject: Re: Bug#927825: arm: mvneta driver used on Armada XP GP boards does not receive packets (regression from 4.9)
Date: Wed, 1 May 2019 22:33:32 +0200 [thread overview]
Message-ID: <20190501203332.GA16945@aurel32.net> (raw)
In-Reply-To: <20190430220421.GA3750@aurel32.net>
[-- Attachment #1: Type: text/plain, Size: 1998 bytes --]
Hi,
On 2019-05-01 00:04, Aurelien Jarno wrote:
> On 2019-04-30 10:12, Uwe Kleine-König wrote:
> > > > More precisely the board is a "Marvell Armada XP Development Board
> > > > DB-MV784MP-GP"
> > > >
> > > > > anymore. Using tcpdump on both the buildd and a remote host, it appears
> > > > > that the packets correctly leave the board and that the reception side
> > > > > fails.
> >
> > If you can send to a remote host at least ARP (or ND) must be working,
> > so some reception still works, right?
>
> I have to try again, but what i have seen is the ARP requests from
> hartmann arriving to the other hosts on the subnet. Steve McIntyre
> (added in Cc:) confirmed me on IRC being able to reproduce the issue on
> another board.
I confirm that. Basically on the other hosts of the same subnet, I can
see the ARP requests:
18:23:45.979860 ARP, Request who-has 172.28.17.1 tell 172.28.17.18, length 46
18:23:47.002990 ARP, Request who-has 172.28.17.1 tell 172.28.17.18, length 46
18:23:48.027262 ARP, Request who-has 172.28.17.1 tell 172.28.17.18, length 46
18:23:52.004248 ARP, Request who-has 172.28.17.1 tell 172.28.17.18, length 46
18:23:53.019252 ARP, Request who-has 172.28.17.1 tell 172.28.17.18, length 46
18:23:54.043276 ARP, Request who-has 172.28.17.1 tell 172.28.17.18, length 46
18:23:58.027937 ARP, Request who-has 172.28.17.1 tell 172.28.17.18, length 46
172.28.17.1 is the gateway, 172.28.17.18 is hartmann.d.o.
> > Is it possible to test a few things on hartmann? I'd suggest:
> >
> > - try (vanilla) 5.1-rc6 with MVNETA=y
I have tried 5.1-rc7 with:
CONFIG_MVNETA_BM_ENABLE=y
CONFIG_MVNETA=y
CONFIG_MVNETA_BM=y
and also with
CONFIG_MVNETA_BM_ENABLE=m
CONFIG_MVNETA=m
CONFIG_MVNETA_BM=m
And the mvneta network driver is not able to receive data in both cases.
Best regards,
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-05-01 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190425125046.GA7210@aurel32.net>
[not found] ` <155605060923.15313.17004641650838278623.reportbug@ohm.local>
[not found] ` <20190425191732.GA28481@aurel32.net>
2019-04-30 8:12 ` Bug#927825: arm: mvneta driver used on Armada XP GP boards does not receive packets (regression from 4.9) Uwe Kleine-König
2019-04-30 22:04 ` Aurelien Jarno
2019-05-01 20:33 ` Aurelien Jarno [this message]
2019-05-02 20:09 ` Uwe Kleine-König
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=20190501203332.GA16945@aurel32.net \
--to=aurel32@debian.org \
--cc=927825@bugs.debian.org \
--cc=andrew@lunn.ch \
--cc=gregory.clement@bootlin.com \
--cc=jason@lakedaemon.net \
--cc=mw@semihalf.com \
--cc=netdev@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=steve@einval.com \
--cc=uwe@kleine-koenig.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).