Skip to contentSkip to conversation

Ethernet Briding broken on APM Mustang on v4.0-rc1

DISCUSSION Christoffer Dall 2 participants 4 messages Feb 25, 2015

lore
Share & tools
lore
#0 lore raw

Hi,

Configuring bridged networking on the APM Mustang platform doesn't work on v4.0-rc1. It works fine on v3.19-rc1.

When adding the interface to the bridge I get this error:

can't add eth0 to bridge br0: Invalid argument

Has anyone else seen this?

Other ARMv8 platforms don't seem to be affected by this.

Thanks,
-Christoffer

#1 lore raw

Update, apologies for noise,

Quoted 5 lines · Christoffer Dall

Hi,

Configuring bridged networking on the APM Mustang platform doesn't work on v4.0-rc1. It works fine on v3.19-rc1.

Quoted 8 lines

When adding the interface to the bridge I get this error:

can't add eth0 to bridge br0: Invalid argument

Has anyone else seen this?

Other ARMv8 platforms don't seem to be affected by this.

It seems that on v4.0-rc1 the APM ethernet card no longer gets a mac address (or rather, it gets 00:00:00:00:...) so assigning it an appropriate address naturally does the trick.

I have no idea which change caused this behavior though.

-Christoffer

#2 lore raw
Quoted 14 lines · Christoffer Dall

Update, apologies for noise,

Quoted 11 lines · Christoffer Dall

Hi,

Configuring bridged networking on the APM Mustang platform doesn't work on v4.0-rc1. It works fine on v3.19-rc1.

When adding the interface to the bridge I get this error:

can't add eth0 to bridge br0: Invalid argument

Has anyone else seen this?

Quoted 8 lines
Quoted 2 lines

Other ARMv8 platforms don't seem to be affected by this.

It seems that on v4.0-rc1 the APM ethernet card no longer gets a mac address (or rather, it gets 00:00:00:00:...) so assigning it an appropriate address naturally does the trick.

I have no idea which change caused this behavior though.

Did you update your firmware recently? The MAC address is stored as a UEFI shell variable and pushed into ACPI/DTB by the firmware. At one point in the development history, the symbol that held it changed from RGMII_MAC0 to MAC0.

You can reset it by going into the UEFI shell and running:
set MAC0 aa:bb:cc:dd:ee:ff
replacing aa:bb:cc:dd:ee:ff with the MAC address.

--Mark Langsdorf

#3 lore raw
Quoted 22 lines · Mark Langsdorf
Quoted 21 lines · Christoffer Dall

Update, apologies for noise,

Quoted 5 lines · Christoffer Dall

Hi,

Configuring bridged networking on the APM Mustang platform doesn't work on v4.0-rc1. It works fine on v3.19-rc1.

Quoted 8 lines

When adding the interface to the bridge I get this error:

can't add eth0 to bridge br0: Invalid argument

Has anyone else seen this?

Other ARMv8 platforms don't seem to be affected by this.

It seems that on v4.0-rc1 the APM ethernet card no longer gets a mac address (or rather, it gets 00:00:00:00:...) so assigning it an appropriate address naturally does the trick.

Quoted 6 lines
Quoted 1 line

I have no idea which change caused this behavior though.

Did you update your firmware recently? The MAC address is stored as a UEFI shell variable and pushed into ACPI/DTB by the firmware. At one point in the development history, the symbol that held it changed from RGMII_MAC0 to MAC0.

No, only updated my kernel.

Quoted 5 lines

You can reset it by going into the UEFI shell and running:
set MAC0 aa:bb:cc:dd:ee:ff
replacing aa:bb:cc:dd:ee:ff with the MAC address.

I'm not running UEFI, but U-Boot and it doesn't seem like U-Boot manages to configure the hwaddr for Linux.

-Christoffer