This issue is caused by a patch cherry-pick from linux-xlnx/5.15 that was not upsstreamed, it was submitted in 2022 but a v2 was not sent. A different patch was written and upstreamed in v6.9-rc3, that fixes the same issue. This patch was backported to upstream stable. Xilinx' patch applied cleanly when rebasing the kernel but was not functionally correct anymore. The commit subject of the two patches varied which also prevented us from catching this. Xilinx' patch should reverted and the upstream patch used.
linux-xlnx/5.15 patch: https://github.com/Xilinx/linux-xlnx/commit/08ec50f3ef011b7e91626d5466e562c8daa9bb52 submission: https://lore.kernel.org/all/[email protected]/ upstream patch: https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-xilinx-zynqmp/+git/jammy/commit/?h=master-next&id=3a6feb4f69d905bf247148ce3f6447f614ea4e7b The upstream commit will also be present in the Noble 6.8 kernel and the offending commit is still in linux-xlnx/6.6 . This does not currently impact Xilinx' 5.15 or 6.6 tree since the upstream commit is not present in either. ** Also affects: linux-xilinx-zynqmp (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux-xilinx-zynqmp (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux-xilinx-zynqmp (Ubuntu Noble) Assignee: (unassigned) => Portia Stephens (portias) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072456 Title: boot failure on kv260 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2072456/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
