From: Marek Behun <marek.behun@nic•cz>
To: "Tj (Elloe Linux)" <ml.linux@elloe•vision>
Cc: Andrew Lunn <andrew@lunn•ch>,
netdev@vger•kernel.org, chris.packham@alliedtelesis•co.nz,
f.fainelli@gmail•com, vivien.didelot@gmail•com,
info <info@turris•cz>
Subject: Re: dsa: mv88e6xxx not receiving IPv6 multicast packets
Date: Sat, 14 Nov 2020 18:43:57 +0100 [thread overview]
Message-ID: <20201114184357.41902445@nic.cz> (raw)
In-Reply-To: <eed7bc92-e1e6-35df-a2cf-97e74a8730fd@elloe.vision>
On Sat, 14 Nov 2020 16:06:33 +0000
"Tj (Elloe Linux)" <ml.linux@elloe•vision> wrote:
> On 14/11/2020 15:56, Andrew Lunn wrote:
> >> 1) with isc-dhcp-server configured with very short lease times (180
> >> seconds). After mox reboot (or systemctl restart systemd-networkd)
> >> clients successfully obtain a lease and a couple of RENEWs (requested
> >> after 90 seconds) but then all goes silent, Mox OS no longer sees the
> >> IPv6 multicast RENEW packets and client leases expire.
> >
> > So it takes about 3 minutes to reproduce this?
> >
> > Can you do a git bisect to figure out which change broke it? It will
> > take you maybe 5 minutes per step, and given the wide range of
> > kernels, i'm guessing you need around 15 steps. So maybe two hours of
> > work.
> >
> > Andrew
> >
>
> I'll check if we can - the problem might be the Turris Mox kernel is
> based on a board support package drop by Marvell so I'm not clear right
> now how divergent they are. Hopefully the Turris kernel devs can help on
> that.
>
No, TurrisOS kernel is just current OpenWRT 4.14 kernel with some
patches added onto it. Turris MOX is also supported in upstream kernel.
If this error can be reproduced on upstream kernel, you can try bisect
there...
Marek
next prev parent reply other threads:[~2020-11-14 17:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 14:46 dsa: mv88e6xxx losing DHCPv6 solicit packets / IPv6 multicast packets? Marek Behún
2020-07-23 21:27 ` Chris Packham
2020-07-23 21:33 ` Florian Fainelli
2020-07-24 10:24 ` Tj (Elloe Linux)
2020-11-14 15:39 ` dsa: mv88e6xxx not receiving IPv6 multicast packets Tj (Elloe Linux)
2020-11-14 15:56 ` Andrew Lunn
2020-11-14 16:06 ` Tj (Elloe Linux)
2020-11-14 17:43 ` Marek Behun [this message]
2020-11-14 18:49 ` Vladimir Oltean
2020-11-15 10:53 ` Tj (Elloe Linux)
2020-11-15 16:02 ` Andrew Lunn
2020-11-15 17:19 ` Tj (Elloe Linux)
2020-11-15 17:27 ` Andrew Lunn
2020-11-16 7:07 ` Tj (Elloe Linux)
2020-11-16 10:45 ` Tj (Elloe Linux)
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=20201114184357.41902445@nic.cz \
--to=marek.behun@nic$(echo .)cz \
--cc=andrew@lunn$(echo .)ch \
--cc=chris.packham@alliedtelesis$(echo .)co.nz \
--cc=f.fainelli@gmail$(echo .)com \
--cc=info@turris$(echo .)cz \
--cc=ml.linux@elloe$(echo .)vision \
--cc=netdev@vger$(echo .)kernel.org \
--cc=vivien.didelot@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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