[Bug 2159608] [NEW] noble/linux-raspi FTBFS: bcmasp phylib managed-EEE backport missing prerequisites

Public bug reported: [ Impact ] The noble/linux-raspi kernel fails to build from source (FTBFS). Rebasing onto Ubuntu-6.8.0-136.136 pulled in a broken stable backport whose defect is latent in the generic/master kernel — master does not compile the Broadcom ASP2 driver — but becomes a fatal compile error in linux-raspi, which enables it on arm64 (CONFIG_BCMASP: “Required for Pi (not in master)”). compiling drivers/net/ethernet/broadcom/asp2/bcmasp_intf.o: bcmasp_intf.c:675:37: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:677:27: error: 'struct phy_device' has no member named 'enable_tx_lpi' bcmasp_intf.c:1081:23: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:1364:41: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:1416:53: error: 'struct phy_device' has no member named 'eee_cfg' Commit e57cfd7faf78 (“net: bcm: asp2: convert to phylib managed EEE”, upstream 21f56ad1b211) was pulled in only as Stable-dep-of: cbfa5be2bf64 (“net: bcmasp: fix double free of WoL irq”). The conversion makes the driver consume phylib managed-EEE fields (phydev->eee_cfg, phydev->enable_tx_lpi) whose infrastructure (Russell King’s phylib managed-EEE series, ~v6.12) was never backported to Noble 6.8 — the managed-EEE consumer was dragged in without its infrastructure. The commit is present in master tags (132.x → 136.136) but master CI stays green because it does not build this driver. [ Fix ] Clean revert of the managed-EEE conversion. The three EEE commits sit beneath a stack (asp-v3.0, the WoL fix, asp-v2.0 removal, probe/clk fixes) that touches the same files, so a zero-hand-edit revert unwinds 10 commits newest-first down to the EEE base (d55c64e4ae98 .. cec1550ce9b3), restoring self-managed EEE. ASP 2.2 support (fa6cc48ea828) is outside the conflict path and is preserved. # Revert commit Reverts in-tree Subject 1 d55c64e4ae98 bfc6bba5abff net: bcmasp: Fix network filter wake for asp-3.0 2 fb1b8c9e8dd7 e307cd953e52 net: bcmasp: Restore programming of TX map vector register 3 0c01abc7dcc9 c2ed77c1f649 net: bcmasp: fix double disable of clk 4 9fcea88c77d8 605c2d7260f5 net: bcmasp: Add support for asp-v3.0 5 fe845d76a9fa 14fa5d8ff619 net: bcmasp: fix double free of WoL irq 6 2bab11107ddf 3f28a3564218 net: bcmasp: streamline early exit in probe 7 88d4b5fa1300 bcbbececeea4 net: bcmasp: Remove support for asp-v2.0 8 ff089f3a67cc e57cfd7faf78 * net: bcm: asp2: convert to phylib managed EEE 9 26f4ed96942e 8d2cc390d968 * net: bcm: asp2: remove tx_lpi_enabled 10 cec1550ce9b3 d1943caf8cd3 * net: bcm: asp2: fix LPI timer handling [ Test Plan ] Kernel should compile properly after patch application. Build noble/linux-raspi (arm64) with CONFIG_BCMASP=m [ Other Info ] Culprit commit: e57cfd7faf78 (bcmasp managed-EEE), in Ubuntu-6.8.0-136.136. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2159608 Title: noble/linux-raspi FTBFS: bcmasp phylib managed-EEE backport missing prerequisites Status in linux package in Ubuntu: New Bug description: [ Impact ] The noble/linux-raspi kernel fails to build from source (FTBFS). Rebasing onto Ubuntu-6.8.0-136.136 pulled in a broken stable backport whose defect is latent in the generic/master kernel — master does not compile the Broadcom ASP2 driver — but becomes a fatal compile error in linux-raspi, which enables it on arm64 (CONFIG_BCMASP: “Required for Pi (not in master)”). compiling drivers/net/ethernet/broadcom/asp2/bcmasp_intf.o: bcmasp_intf.c:675:37: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:677:27: error: 'struct phy_device' has no member named 'enable_tx_lpi' bcmasp_intf.c:1081:23: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:1364:41: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:1416:53: error: 'struct phy_device' has no member named 'eee_cfg' Commit e57cfd7faf78 (“net: bcm: asp2: convert to phylib managed EEE”, upstream 21f56ad1b211) was pulled in only as Stable-dep-of: cbfa5be2bf64 (“net: bcmasp: fix double free of WoL irq”). The conversion makes the driver consume phylib managed-EEE fields (phydev->eee_cfg, phydev->enable_tx_lpi) whose infrastructure (Russell King’s phylib managed-EEE series, ~v6.12) was never backported to Noble 6.8 — the managed-EEE consumer was dragged in without its infrastructure. The commit is present in master tags (132.x → 136.136) but master CI stays green because it does not build this driver. [ Fix ] Clean revert of the managed-EEE conversion. The three EEE commits sit beneath a stack (asp-v3.0, the WoL fix, asp-v2.0 removal, probe/clk fixes) that touches the same files, so a zero-hand-edit revert unwinds 10 commits newest-first down to the EEE base (d55c64e4ae98 .. cec1550ce9b3), restoring self-managed EEE. ASP 2.2 support (fa6cc48ea828) is outside the conflict path and is preserved. # Revert commit Reverts in-tree Subject 1 d55c64e4ae98 bfc6bba5abff net: bcmasp: Fix network filter wake for asp-3.0 2 fb1b8c9e8dd7 e307cd953e52 net: bcmasp: Restore programming of TX map vector register 3 0c01abc7dcc9 c2ed77c1f649 net: bcmasp: fix double disable of clk 4 9fcea88c77d8 605c2d7260f5 net: bcmasp: Add support for asp-v3.0 5 fe845d76a9fa 14fa5d8ff619 net: bcmasp: fix double free of WoL irq 6 2bab11107ddf 3f28a3564218 net: bcmasp: streamline early exit in probe 7 88d4b5fa1300 bcbbececeea4 net: bcmasp: Remove support for asp-v2.0 8 ff089f3a67cc e57cfd7faf78 * net: bcm: asp2: convert to phylib managed EEE 9 26f4ed96942e 8d2cc390d968 * net: bcm: asp2: remove tx_lpi_enabled 10 cec1550ce9b3 d1943caf8cd3 * net: bcm: asp2: fix LPI timer handling [ Test Plan ] Kernel should compile properly after patch application. Build noble/linux-raspi (arm64) with CONFIG_BCMASP=m [ Other Info ] Culprit commit: e57cfd7faf78 (bcmasp managed-EEE), in Ubuntu-6.8.0-136.136. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2159608/+subscriptions