I'm not sure if there is a timing issue on E835-XXV, I didn't see this on E810. Updating nvm to latest had no impact:
dev.ice.0.fw_version: fw 7.10.2 api 1.7 nvm 2.11 etid 80019290 netlist 0.0.1105-7.59.0.f0781d28 oem 1.4031.0
When link_active_on_if_down keeps the PHY active, attach records FIRST_INIT_LINK to avoid reapplying the PHY configuration during the first administrative init. If the physical link becomes active after the attach query without a link-status event reaching the driver, the cached link state remains down. First init then consumes the flag and leaves iflib reporting no carrier until another down/up cycle. Refresh and publish the firmware link status during first init without restarting autonegotiation. Keep the attach refresh request distinct from FIRST_INIT_LINK, which is also used to suppress redundant PHY configuration after reset recovery. Rebuild already refreshes and reports link, so its subsequent iflib init must not publish it again. On an E835 with an Intel 10GBASE-LR optic, rebooting without this change left firmware reporting a 10 Gbps link while the first administrative up reported no carrier; a second down/up recovered it. With this change, the first up after reboot reported active immediately. Three subsequent down/up cycles kept the physical link active and restored carrier. MFC after: 2 weeks Sponsored by: BBOX.io