Netdev Archive on
help / color / mirror / Atom feed
From: Andrew Lunn <>
To: George McCollister <>
Cc: netdev <>,
	Richard Cochran <>
Subject: Re: net: dsa: mv88e6xxx: no multicasts rx'd after enabling hw time stamping
Date: Wed, 28 Jul 2021 23:04:59 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Jul 28, 2021 at 03:44:24PM -0500, George McCollister wrote:
> If I do the following on one of my mv88e6390 switch ports I stop
> receiving multicast frames.
> hwstamp_ctl -i lan0 -t 1 -r 12
> Has anyone seen anything like this or have any ideas what might be
> going on? Does anyone have PTP working on the mv88e6390?
> I tried this but it doesn't help:
> ip maddr add 01:xx:xx:xx:xx:xx dev lan0
> I've tried sending 01:1B:19:00:00:00, 01:80:C2:00:00:0E as well as
> other random ll multicast addresses. Nothing gets through once
> hardware timestamping is switched on. The switch counters indicate
> they're making it into the outward facing switch port but are not
> being sent out the CPU facing switch port. I ran into this while
> trying to get ptp4l to work.

Hi George

All my testing was i think on 6352.

I assume you get multicast before using hwstamp_ctl?

Maybe use:

and dump the ATU before and afterwards.

The 6390 family introduced a new way to configured which reserved
management addresses get forwarded to the CPU. Maybe take a look at
mv88e6390_g1_mgmt_rsvd2cpu() and see if you can spot anything odd
going on.

You might also want to check if mv88e6352_port_set_mcast_flood() is
being called.


  reply	other threads:[~2021-07-28 21:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 20:44 George McCollister
2021-07-28 21:04 ` Andrew Lunn [this message]
2021-07-28 22:24   ` Richard Cochran
2021-07-29 13:22     ` George McCollister
2021-07-29 13:42       ` Andrew Lunn
2021-08-11 15:49         ` George McCollister
2021-07-29 13:09   ` George McCollister

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: net: dsa: mv88e6xxx: no multicasts rx'\''d after enabling hw time stamping' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
on how to clone and mirror all data and code used for this inbox