[Kernel-packages] [Bug 2054366] Re: Fix backported kria device tree changes
** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: Fix Released Status in linux-xilinx-zynqmp source package in Jammy: Fix Released Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Fixes ] * 6.1 compatible string and interrupt-name for gpu: gpu@fd4b incorrectly backported * 6.1 compatible string for ethernet@ff0b incorrectly backported * dwc3_[01] quirks incorrectly updated for 6.1 * xilinx_ams field incorrectly updated. [ Other info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054366] Re: Fix backported kria device tree changes
This bug was fixed in the package linux-xilinx-zynqmp - 5.15.0-1027.31 --- linux-xilinx-zynqmp (5.15.0-1027.31) jammy; urgency=medium * jammy/linux-xilinx-zynqmp: 5.15.0-1027.31 -proposed tracker (LP: #2054500) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/d2024.02.07) * Fix backported kria device tree changes (LP: #2054366) - SAUCE: zynqmp.dtsi fix incorrectly backported changes [ Ubuntu: 5.15.0-94.104 ] * jammy/linux: 5.15.0-94.104 -proposed tracker (LP: #2048777) * [SRU] Duplicate Device_dax ids Created and hence Probing is Failing. (LP: #2028158) - device-dax: Fix duplicate 'hmem' device registration * Add ODM driver f81604 usb-can (LP: #2045387) - can: usb: f81604: add Fintek F81604 support - [Config] updateconfigs for ODM drivers CONFIG_CAN_F81604 * Add ODM driver gpio-m058ssan (LP: #2045386) - SAUCE: ODM: gpio: add M058SSAN gpio driver - [Config] updateconfigs for ODM drivers CONFIG_GPIO_M058SSAN * Add ODM driver rtc-pcf85263 (LP: #2045385) - SAUCE: ODM: rtc: add PCF85263 RTC driver - [Config] updateconfigs for ODM drivers CONFIG_RTC_DRV_PCF85263 * AppArmor patch for mq-posix interface is missing in jammy (LP: #2045384) - SAUCE: (no-up) apparmor: reserve mediation classes - SAUCE: (no-up) apparmor: Add fine grained mediation of posix mqueues * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts [ Ubuntu: 5.15.0-93.103 ] * jammy/linux: 5.15.0-93.103 -proposed tracker (LP: #2048330) * Packaging resync (LP: #1786013) - [Packaging] resync git-ubuntu-log - [Packaging] resync update-dkms-versions helper - [Packaging] remove helper scripts - [Packaging] update annotations scripts - debian/dkms-versions -- update from kernel-versions (main/2024.01.08) * Hotplugging SCSI disk in QEMU VM fails (LP: #2047382) - Revert "PCI: acpiphp: Reassign resources on bridge if necessary" * CVE-2023-6622 - netfilter: nf_tables: bail out on mismatching dynset and set expressions * CVE-2024-0193 - netfilter: nf_tables: skip set commit for deleted/destroyed sets * CVE-2023-6040 - netfilter: nf_tables: Reject tables of unsupported family * Patches needed for AmpereOne (arm64) (LP: #2044192) - clocksource/arm_arch_timer: Add build-time guards for unhandled register accesses - clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read accessors - clocksource/drivers/arm_arch_timer: Extend write side of timer register accessors to u64 - clocksource/drivers/arm_arch_timer: Move system register timer programming over to CVAL - clocksource/drivers/arm_arch_timer: Move drop _tval from erratum function names - clocksource/drivers/arm_arch_timer: Fix MMIO base address vs callback ordering issue - clocksource/drivers/arm_arch_timer: Move MMIO timer programming over to CVAL - clocksource/drivers/arm_arch_timer: Advertise 56bit timer to the core code - clocksource/drivers/arm_arch_timer: Work around broken CVAL implementations - clocksource/drivers/arm_arch_timer: Remove any trace of the TVAL programming interface - clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on CVAL programming - clocksource/drivers/arm_arch_timer: Fix masking for high freq counters - clocksource/drivers/arch_arm_timer: Move workaround synchronisation around * Add quirk to disable i915 fastboot on B PC (LP: #2047630) - SAUCE: i915: force disable fastboot quirk * Some machines can't pass the pm-graph test (LP: #2046217) - wifi: iwlwifi: pcie: rescan bus if no parent * Sound: Add rtl quirk of M90-Gen5 (LP: #2046105) - ALSA: hda/realtek: Enable headset on Lenovo M90 Gen5 * linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision (LP: #2035971) - [Packaging] Statically link libcpupower into cpupower tool * [Debian] autoreconstruct - Do not generate chmod -x for deleted files (LP: #2045562) - [Debian] autoreconstruct - Do not generate chmod -x for deleted files * CVE-2023-6931 - perf/core: Add a new read format to get a number of lost samples - perf: Fix perf_event_validate_size() - perf: Fix perf_event_validate_size() lockdep splat * CVE-2023-6932 - ipv4: igmp: fix refcnt uaf issue when receiving igmp query packet * CVE-2023-6606 - smb: client: fix OOB in smbCalcSize() * CVE-2023-6817 - netfilter: nft_set_pipapo: skip inactive elements during set walk * Jammy update: v5.15.136 upstream stable release (LP: #2046008) - iommu/vt-d: Avoid memory allocation in iommu_suspend() - scsi: core: Use a structure member to track the SCSI command submitter - scsi: core: Rename scsi_mq_done() into scsi_done() and export it - scsi: ib_srp: Call scsi_done() directly - RDMA/srp: Do not call scsi_done() from srp_abort() - RDMA/cxgb4:
[Kernel-packages] [Bug 2054366] Re: Fix backported kria device tree changes
I have tested this on KD240 and verified all 3 regressions listed the bug are fixed. ** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Assignee: (unassigned) => Portia Stephens (portias) ** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided => High ** Tags removed: verification-needed-jammy-linux-xilinx-zynqmp ** Tags added: verification-done-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Fixes ] * 6.1 compatible string and interrupt-name for gpu: gpu@fd4b incorrectly backported * 6.1 compatible string for ethernet@ff0b incorrectly backported * dwc3_[01] quirks incorrectly updated for 6.1 * xilinx_ams field incorrectly updated. [ Other info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054366] Re: Fix backported kria device tree changes
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1027.31 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Fixes ] * 6.1 compatible string and interrupt-name for gpu: gpu@fd4b incorrectly backported * 6.1 compatible string for ethernet@ff0b incorrectly backported * dwc3_[01] quirks incorrectly updated for 6.1 * xilinx_ams field incorrectly updated. [ Other info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054366] Re: Fix backported kria device tree changes
** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Fixes ] * 6.1 compatible string and interrupt-name for gpu: gpu@fd4b incorrectly backported * 6.1 compatible string for ethernet@ff0b incorrectly backported * dwc3_[01] quirks incorrectly updated for 6.1 * xilinx_ams field incorrectly updated. [ Other info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054366] Re: Fix backported kria device tree changes
** Description changed: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. - [ Other Info ] + [ Fixes ] + * 6.1 compatible string and interrupt-name for gpu: gpu@fd4b incorrectly backported + * 6.1 compatible string for ethernet@ff0b incorrectly backported + * dwc3_[01] quirks incorrectly updated for 6.1 + * xilinx_ams field incorrectly updated. + [ Other info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Status in linux-xilinx-zynqmp source package in Jammy: New Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Fixes ] * 6.1 compatible string and interrupt-name for gpu: gpu@fd4b incorrectly backported * 6.1 compatible string for ethernet@ff0b incorrectly backported * dwc3_[01] quirks incorrectly updated for 6.1 * xilinx_ams field incorrectly updated. [ Other info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054366] Re: Fix backported kria device tree changes
** Also affects: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Status in linux-xilinx-zynqmp source package in Jammy: New Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Other Info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054366] Re: Fix backported kria device tree changes
** Description changed: [ Impact ] - * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. + * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] - * QA will run certification testing on the KD240 platform - * Normal certification testing will be run on all other certified platforms + * QA will run certification testing on the KD240 platform + * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Other Info ] - * Private launchpad bugs that contain the regressions: + * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 ** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Other Info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
