[Kernel-packages] [Bug 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 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-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. 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-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
This bug is awaiting verification that the linux-nvidia/5.15.0-1007.7 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' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6 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' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
This bug was fixed in the package linux - 5.15.0-47.51 --- linux (5.15.0-47.51) jammy; urgency=medium * jammy/linux: 5.15.0-47.51 -proposed tracker (LP: #1983903) * Jammy update: v5.15.46 upstream stable release (LP: #1981864) - UBUNTU: [Packaging] Move python3-dev to build-depends * touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N) (LP: #1884232) - x86/PCI: Eliminate remove_e820_regions() common subexpressions - x86: Log resource clipping for E820 regions - x86/PCI: Clip only host bridge windows for E820 regions - x86/PCI: Add kernel cmdline options to use/ignore E820 reserved regions - x86/PCI: Disable E820 reserved region clipping via quirks - x86/PCI: Revert "x86/PCI: Clip only host bridge windows for E820 regions" * [SRU][H/OEM-5.13/OEM-5.14/U][J/OEM-5.17/U] Fix invalid MAC address after hotplug tbt dock (LP: #1942999) - SAUCE: igc: wait for the MAC copy when enabled MAC passthrough * Mass Storage Gadget driver truncates device >2TB (LP: #1981390) - usb: gadget: storage: add support for media larger than 2T * AMD Rembrandt: DP tunneling fails with Thunderbolt monitors (LP: #1983143) - SAUCE: drm/amd: Fix DP Tunneling with Thunderbolt monitors - drm/amd/display: Fix for dmub outbox notification enable - Revert "drm/amd/display: Fix DPIA outbox timeout after S3/S4/reset" - drm/amd/display: Reset link encoder assignments for GPU reset - drm/amd/display: Fix DPIA outbox timeout after S3/S4/reset - drm/amd/display: Fix new dmub notification enabling in DM - SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered. * Fix sub-optimal I210 network speed (LP: #1976438) - igb: Make DMA faster when CPU is active on the PCIe link * e1000e report hardware hang (LP: #1973104) - e1000e: Enable GPT clock before sending message to CSME - Revert "e1000e: Fix possible HW unit hang after an s0ix exit" * ioam6.sh in net from ubuntu_kernel_selftests fails with 5.15 kernels in Focal (LP: #1982930) - selftests: net: fix IOAM test skip return code * Additional fix for TGL + AUO panel flickering (LP: #1983297) - Revert "UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO panel" - drm/i915/display: Fix sel fetch plane offset calculation - drm/i915: Nuke ORIGIN_GTT - drm/i915/display: Drop PSR support from HSW and BDW - drm/i915/display/psr: Handle plane and pipe restrictions at every page flip - drm/i915/display/psr: Do full fetch when handling multi-planar formats - drm/i915/display: Drop unnecessary frontbuffer flushes - drm/i915/display: Handle frontbuffer rendering when PSR2 selective fetch is enabled - drm/i915/display: Fix glitches when moving cursor with PSR2 selective fetch enabled - SAUCE: drm/i915/display/psr: Reinstate fix for TGL + AUO panel flicker * AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes (LP: #1957026) - drm/amd/display: Optimize bandwidth on following fast update - drm/amd/display: Fix surface optimization regression on Carrizo - drm/amd/display: Reset DMCUB before HW init * GPIO character device v1 API not enabled in kernel (LP: #1953613) - [Config] Enable CONFIG_GPIO_CDEV_V1 * intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes (LP: #1982104) - iommu/vt-d: Fix RID2PASID setup/teardown failure * Headset mic with Cirrus logic codec doesn't work (LP: #1972815) - ASoC: cs42l42: Move CS42L42 register descriptions to general include - ALSA: hda/cs8409: Use general cs42l42 include in cs8409 hda driver - ALSA: hda/cs8409: Support manual mode detection for CS42L42 * Failed to resume from S3 blocked by atlantic driver[1d6a:94c0] (LP: #1981950) - net: atlantic: remove deep parameter on suspend/resume functions - net: atlantic: remove aq_nic_deinit() when resume * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * Clear PCI errors left from BIOS (LP: #1981173) - PCI: Clear PCI_STATUS when setting up device * Fix AMDGPU blank screen when Type-C DP alt is in use (LP: #1980060) - drm/amd/display: Query DMCUB for dp alt status - drm/amd/display: Add version check before using DP alt query interface * Fix WD22TB4 suspend and resume, two external monitor can not output (LP: #1979267) - drm/dp/mst: Read the extended DPCD capabilities during system resume * [SRU] bcache deadlock during read IO in writeback mode (LP: #1980925) - bcache: memset on stack variables in bch_btree_check() and bch_sectors_dirty_init() * Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9 (LP: #1982716) - ALSA: hda/realtek: fix mute/micmute LEDs for HP machines * Enable WiFi hotspot feature for MediaTek MT7921 (LP: #1979173) - mt76: mt7921: Add AP mode support - mt76: mt7921:
[Kernel-packages] [Bug 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
** Changed in: hwe-next Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
** Changed in: hwe-next Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
** Changed in: linux (Ubuntu Jammy) Importance: High => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: Incomplete Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
SRU: https://lists.ubuntu.com/archives/kernel-team/2022-July/132126.html (jammy, V2) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: Incomplete Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
All proposed patches have been in 5.17 or above. ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: Incomplete Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1024.26 --- linux-oem-5.14 (5.14.0-1024.26) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1024.26 -proposed tracker (LP: #1961191) * Packaging resync (LP: #1786013) - [Config] Update config to match upstream stable release - [Packaging] update variants * CVE-2022-0435 - tipc: improve size validations for received domain records * CVE-2022-0492 - cgroup-v1: Require capabilities to set release_agent * Use EC GPE for s2idle wakeup on AMD platforms (LP: #1960771) - ACPI: PM: Revert "Only mark EC GPE for wakeup on Intel systems" * USB port lost function after unplugging usb drive (LP: #1958850) - block: add disk sequence number - mm: hide laptop_mode_wb_timer entirely behind the BDI API - block: pass a gendisk to blk_queue_update_readahead - block: add a queue_has_disk helper - block: move the bdi from the request_queue to the gendisk - block: remove the bd_bdi in struct block_device - nvme: use blk_mq_alloc_disk - st: do not allocate a gendisk - sg: do not allocate a gendisk - block: cleanup the lockdep handling in *alloc_disk - block: remove alloc_disk and alloc_disk_node - block: remove the minors argument to __alloc_disk_node - block: pass a request_queue to __blk_alloc_disk - block: hold a request_queue reference for the lifetime of struct gendisk - block: add an explicit ->disk backpointer to the request_queue - writeback: make the laptop_mode prototypes available unconditionally - sg: pass the device name to blk_trace_setup - block: factor out a blk_try_enter_queue helper - block: drain file system I/O on del_gendisk - block: keep q_usage_counter in atomic mode after del_gendisk - block: drain queue after disk is removed from sysfs - nvdimm/pmem: stop using q_usage_count as external pgmap refcount - nvdimm/pmem: cleanup the disk if pmem_release_disk() is yet assigned * Focal update: upstream stable patchset 2022-01-31 (LP: #1959569) - iommu/amd: Restore GA log/tail pointer on host resume -- Timo Aaltonen Thu, 17 Feb 2022 13:23:43 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0435 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0492 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
Verified linux-oem-5.14/focal-proposed version 5.14.0-1023 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
Released with linux-firmware 20220124.git0c6a7b3b-0ubuntu1 in Jammy. ** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
This bug was fixed in the package linux-firmware - 1.187.26 --- linux-firmware (1.187.26) focal; urgency=medium * [SRU][F] Add firmware of MT7922 (LP: #1958153) - linux-firmware: add firmware for MT7922 - linux-firmware: add frimware for mediatek bluetooth chip (MT7922) * linux-firmware missing renoir_ta (LP: #1958283) - amdgpu: update renoir firmware for 20.10 - amdgpu: update renoir firmware from 20.20 release - amdgpu: update renoir firmware for 20.30 - amdgpu: update renoir firmware for 20.40 - amdgpu: update renoir firmware for 20.45 - amdgpu: update renoir firmware for 20.50 - amdgpu: update renoir firmware from 21.10 - amdgpu: update renoir firmware from 21.20 - amdgpu: update vcn firmware for renoir for 21.20 - amdgpu: update renoir firmware from 21.30 - amdgpu: update VCN firmware for renoir * mt7921e :02:00.0: PM: failed to resume async: error -110 (LP: #1958286) - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for mediatek bluetooth chip(MT7921) * [SRU][F] Add mt8183 SCP firmware (LP: #1959064) - mediatek: Add mt8183 SCP firmware * AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes (LP: #1957026) - amdgpu: update yellow carp dmcub firmware -- Juerg Haefliger Fri, 28 Jan 2022 10:54:30 +0100 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
verified linux-firmware/focal-proposed version 1.187.26. ** Description changed: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] - So far all the patches can be cleanly applied, and they're being - progressively proposed to linux-stable. + On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support + S0ix and has to be disabled. For the kernel side, the driver fixes + addressed a few procedure errors that should be unlikely to introduce + regressions; for the firmware side, also tested loading new firmware on + unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
could you update the "where problems.." part, it doesn't make sense for the firmware -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] So far all the patches can be cleanly applied, and they're being progressively proposed to linux-stable. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
** Changed in: linux-firmware (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] So far all the patches can be cleanly applied, and they're being progressively proposed to linux-stable. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
SRU: * https://lists.ubuntu.com/archives/kernel-team/2022-January/127429.html (linux-firmware/focal) ** Description changed: - TBD. + [SRU Justification] + + [Impact] + + On AMD Yellow Carp B0 platforms, S0i3 is still not working. + + [Fix] + + This denpends on a few fixes for kernel driver that are all either in + v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed + dmcub firmware. + + [Test Case] + + On AMD RMT CRB board, + 1. apply both kernel and firmware fixes + 2. module blacklist amd_sfh as it's still under development, + 3. trigger system suspend. Use power button to wake up the device. + 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero + + On without any of above, the board may not cut device power during + suspend, and/or fail to resume and leaving a blank screen, and/or s0ix + stats remain all zeros. + + [Where problems could occur] + + So far all the patches can be cleanly applied, and they're being + progressively proposed to linux-stable. + + [Other Info] + + For kernel driver fixes, patches for both oem-5.14 and jammy are + necessary; for firmware, that has been available in jammy branch but not + yet released, so only Focal will be nominated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] So far all the patches can be cleanly applied, and they're being progressively proposed to linux-stable. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
Already in jammy branch but not yet released. ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1957026 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
** Tags added: kern-1850 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
** Package changed: linux (Ubuntu) => linux-firmware (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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