Hi Rasmus,
On Sat, Dec 05, 2020 at 03:49:02PM +0100, Rasmus Villemoes wrote:
> So I'm out of ideas. I also tried booting a 5.3, but that had some
> horrible UBI/nand failure,
Test with a ramdisk maybe?
> and since the mv88e6250 support only landed
> in 5.3, it's rather difficult to try kernels f
On Sat, Dec 05, 2020 at 03:49:02PM +0100, Rasmus Villemoes wrote:
> So, I found out that the problem disappers when I disable
> vlan_filtering, and googling then led me to Russell's patches from
> around March
> (https://patchwork.ozlabs.org/project/netdev/cover/20200218114515.gl18...@shell.armlinu
On 30/11/2020 23.13, Rasmus Villemoes wrote:
> On 30/11/2020 17.04, Vladimir Oltean wrote:
> Thanks, but I don't think that will change anything. -34 is -ERANGE.
>> But you might also want to look into adding .ndo_change_mtu for
>> ucc_geth.
>
> Well, that was what I first did, but I'm incapable
> > A thought: Shouldn't the initialization of slave_dev->max_mtu in
> > dsa_slave_create() be capped by master->max_mtu minus tag overhead?
>
> Talk to Andrew:
> https://www.spinics.net/lists/netdev/msg645810.html
Yes, this is historic. DSA started life with Marvell switches
connected to Marvell
On 30/11/2020 23.35, Vladimir Oltean wrote:
> On Mon, Nov 30, 2020 at 11:13:39PM +0100, Rasmus Villemoes wrote:
>> FWIW, on a 4.19 kernel, I can do 'ping -s X -M do' for X up to 1472
>> for IPv4 and 1452 for IPv6, but I don't think that tells me much about
>> what the hardware could do.
>
> IP wi
On Mon, Nov 30, 2020 at 11:13:39PM +0100, Rasmus Villemoes wrote:
> On 30/11/2020 17.04, Vladimir Oltean wrote:
> > Hi Rasmus,
> >
> > On Mon, Nov 30, 2020 at 03:30:50PM +0100, Rasmus Villemoes wrote:
> >> Hi,
> >>
> >> Updating our mpc8309 board to 5.9, we're starting to get
> >>
> >> [0.70983
On 30/11/2020 17.04, Vladimir Oltean wrote:
> Hi Rasmus,
>
> On Mon, Nov 30, 2020 at 03:30:50PM +0100, Rasmus Villemoes wrote:
>> Hi,
>>
>> Updating our mpc8309 board to 5.9, we're starting to get
>>
>> [0.709832] mv88e6085 mdio@e0102120:10: nonfatal error -34 setting MTU on
>> port 0
>> [
Hi Rasmus,
On Mon, Nov 30, 2020 at 03:30:50PM +0100, Rasmus Villemoes wrote:
> Hi,
>
> Updating our mpc8309 board to 5.9, we're starting to get
>
> [0.709832] mv88e6085 mdio@e0102120:10: nonfatal error -34 setting MTU on
> port 0
> [0.720721] mv88e6085 mdio@e0102120:10: nonfatal error -34
Hi,
Updating our mpc8309 board to 5.9, we're starting to get
[0.709832] mv88e6085 mdio@e0102120:10: nonfatal error -34 setting
MTU on port 0
[0.720721] mv88e6085 mdio@e0102120:10: nonfatal error -34 setting
MTU on port 1
[0.731002] mv88e6085 mdio@e0102120:10: nonfatal error -34 settin
