[Kernel-packages] [Bug 1961121] Re: Not able to enter s2idle state on AMD platforms
** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: Alex Hung (alexhung) => (unassigned) -- 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/1961121 Title: Not able to enter s2idle state on AMD platforms Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] AMD Systems don't enter PC6 at runtime and cause failures to enter s2idle. Currently the fix is from kernel driver rather than MP2 firmware, which disable interrupts from kernel driver to fix MP2 firmware blocking CPUOFF. [Fix] The fixes involve 1) cancelling delayed work when entering s0ix and re-scheduling it when resuming from s0ix, and 2) clearing interrupts during the driver initialization and sensor command operations. [Test] This is requested by AMD and was tested on AMD CRB. [Where problems could occur] Risk is low to medium. Some code flow changes are guarded by reasonable conditions, but the fixes introduced additional suspend and resume operations. Having said that, clearing interrupts before driver initialization and cancelling work before entering sleeping states are standard approaches are usually safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961121/+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 1952132] Re: [ADL] Thermal Support
** Changed in: linux (Ubuntu) Assignee: Alex Hung (alexhung) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952132 Title: [ADL] Thermal Support Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] The patches enable thermal supports. [Fix] Intel provides a list of patches to add new PCI driver which register a thermal zone and allows to get notification [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952132/+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 1952153] Re: [EHL][TGL][ADL] power management controller driver enabling
** Changed in: linux (Ubuntu) Assignee: Alex Hung (alexhung) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952153 Title: [EHL][TGL][ADL] power management controller driver enabling Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] The patches enable power management controller supports. [Fix] The driver is the Kernel gateway to the PMC hardware for Intel processors and it provides debug hooks to developers and end-users to quickly figure out why their platform is not entering a deeper idle state such as S0ix. [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel ElkhartLake / TigerLake / AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952153/+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 1952006] Re: [TGL][ADL] ACRN hypervisor support
** Changed in: linux (Ubuntu) Assignee: Alex Hung (alexhung) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952006 Title: [TGL][ADL] ACRN hypervisor support Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] The driver enables the host to run ACRN hypervisor which is a flexible, lightweight reference hypervisor, built with real-time and safety-criticality in mind, optimized to streamline embedded development through an open-source platform. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable ACRN hypervisor [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel TigerLake/AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952006/+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 1952007] Re: [ADL] ITBM support for Hybrid platforms
** Changed in: linux (Ubuntu) Assignee: Alex Hung (alexhung) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952007 Title: [ADL] ITBM support for Hybrid platforms Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] Need ITBM support for Hybrid platforms. Need to change the scheduling order from Core, HT, ATOM to Core, ATOM, HT. When using ITBM on systems that has a mixture of CPUs supporting Hyper-Threading and others not supporting it (even offlining HT siblings may cause the issue to be reproducible). Hybrid topologies meet the aforementioned condition. In such cases, threads will be consolidated on CPUs of high priority using got HT siblings, while CPUs of medium priority will remain idle. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable AlderLake [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952007/+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 1952356] Re: [EHL][TGL][ADL] PMU support
** Changed in: linux (Ubuntu) Assignee: Alex Hung (alexhung) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952356 Title: [EHL][TGL][ADL] PMU support Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] The patches enable PMU support [Fix] Intel provides a list of patches to provide Linux perf supports [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel ElkhartLake/TigerLake/AdlerLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952356/+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 1961120] Re: SFH sensors are not working on some AMD platforms
** Changed in: hwe-next Status: In Progress => Fix Released ** Changed in: hwe-next Status: Fix Released => 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/1961120 Title: SFH sensors are not working on some AMD platforms Status in HWE Next: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] When amd-sfh is loaded the sensors connected do not change values at all (ALS sensor). Here is the monitor sensors output, which doesn't change. $ sudo monitor-sensor Waiting for iio-sensor-proxy to appear +++ iio-sensor-proxy appeared === No accelerometer === Has ambient light sensor (value: 0.00, unit: lux) [Fix] The SRU contains two fixes: 1. increasing sensor command timeout from from 80 to 160. 2. using first valid 15 bits only ALS max illuminance values. [Test] This is requested by AMD. This was also verified by an AMD's engineer on CRB. [Where problems could occur] Low. The patches only increase timeout value and discard an invalid bit. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961120/+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 1952006] Re: [TGL][ADL] ACRN hypervisor support
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952006 Title: [TGL][ADL] ACRN hypervisor support Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] The driver enables the host to run ACRN hypervisor which is a flexible, lightweight reference hypervisor, built with real-time and safety-criticality in mind, optimized to streamline embedded development through an open-source platform. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable ACRN hypervisor [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel TigerLake/AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952006/+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 1952007] Re: [ADL] ITBM support for Hybrid platforms
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952007 Title: [ADL] ITBM support for Hybrid platforms Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] Need ITBM support for Hybrid platforms. Need to change the scheduling order from Core, HT, ATOM to Core, ATOM, HT. When using ITBM on systems that has a mixture of CPUs supporting Hyper-Threading and others not supporting it (even offlining HT siblings may cause the issue to be reproducible). Hybrid topologies meet the aforementioned condition. In such cases, threads will be consolidated on CPUs of high priority using got HT siblings, while CPUs of medium priority will remain idle. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable AlderLake [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952007/+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 1952356] Re: [EHL][TGL][ADL] PMU support
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952356 Title: [EHL][TGL][ADL] PMU support Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] The patches enable PMU support [Fix] Intel provides a list of patches to provide Linux perf supports [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel ElkhartLake/TigerLake/AdlerLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952356/+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 1961119] Re: Lower the volume of expected s0i3 WARN_ON
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal ** 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/1961119 Title: Lower the volume of expected s0i3 WARN_ON Status in HWE Next: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] AMD has a known BIOS bug right now that leads to the following WARN traceback during s0i3 resume (see below). This doesn't have (measurable) functional impact to the system or GPU, but it is an ugly message to have in place and makes it look like a potentially major problem. AMD is working on fixing this in BIOS, but it may not be ready by the time the first platforms launch. [Fix] Print a shorter message warning instead: "Watermarks table not configured properly by SMU". The fixed was cherry-picked from mainline kernel v5.17-rc4. [Test] This is requested by AMD, and tested and verified on the AMD CRB. [Where problems could occur] Low. This only changes the behavors of message printing There are no functional changes. --- WARN_ON messages --- [ cut here ] WARNING: CPU: 8 PID: 60399 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn31/dcn31_smu.c:123 dcn31_smu_send_msg_with_param+0xec/0x130 [amdgpu] Modules linked in: btrfs blake2b_generic xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cpuid michael_mic hid_logitech_hidpp snd_usb_audio snd_usbmidi_lib hid_logitech_dj usbhid cdc_ether usbnet r8152 mii qrtr_mhi joydev intel_rapl_msr intel_rapl_common bnep snd_soc_dmic snd_acp6x_pdm_dma snd_soc_acp6x_mach snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine edac_mce_amd amdgpu snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi nls_iso8859_1 kvm_amd kvm snd_hda_intel qrtr snd_intel_dspcfg ns snd_intel_sdw_acpi snd_hda_codec ath11k_pci crct10dif_pclmul input_leds snd_pci_acp6x ghash_clmulni_intel ath11k snd_hda_core snd_hwdep qmi_helpers aesni_intel snd_pcm uvcvideo crypto_simd videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 iommu_v2 cryptd platform_profile btusb snd_seq_midi gpu_sched rapl mac80211 serio_raw snd_seq_midi_event videobuf2_common sparse_keymap drm_ttm_helper btrtl snd_rawmidi btbcm videodev btintel ttm efi_pstore wmi_bmof hid_multitouch mc bluetooth snd_seq drm_kms_helper snd_seq_device ecdh_generic cfg80211 ecc snd_timer cec rc_core i2c_algo_bit snd fb_sys_fops syscopyarea sysfillrect mhi sysimgblt libarc4 soundcore snd_rn_pci_acp3x snd_pci_acp3x ccp ucsi_acpi typec_ucsi amd_pmc wireless_hotkey mac_hid typec acpi_tad sch_fq_codel msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul thunderbolt nvme i2c_piix4 xhci_pci xhci_pci_renesas nvme_core iosm wmi i2c_hid_acpi video i2c_hid hid Workqueue: events_unbound async_run_entry_fn RIP: 0010:dcn31_smu_send_msg_with_param+0xec/0x130 [amdgpu] Code: 00 e8 38 60 fc ff 48 8b 3b 4c 89 ea be 9b 62 01 00 e8 c8 60 fc ff 85 c0 75 40 bf c6 a7 00 00 e8 aa da 0c c6 41 83 ec 01 75 dc <0f> 0b 48 8b 3b b9 80 84 1e 00 44 89 fa 44 89 f6 e8 af 9c fc ff 48 RSP: 0018:b76d03167bc8 EFLAGS: 00010202 RAX: 00ff RBX: 9dc54f492800 RCX: 0008 RDX: RSI: 0001629b RDI: 9dc548bc RBP: b76d03167bf8 R08: 0009 R09: 0320 R10: 0191 R11: 04451a00 R12: 00030b48 R13: c1717d90 R14: 0011 R15: 0001 FS: () GS:9dcc7e80() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 55f79ba89f68 CR3: 00052681 CR4: 00750ee0 PKRU: 5554 Call Trace: dcn31_smu_transfer_wm_table_dram_2_smu+0x23/0x30 [amdgpu] dcn31_notify_wm_ranges+0x145/0x180 [amdgpu] dcn31_init_hw+0x465/0x8e0 [amdgpu] dc_set_power_state+0x113/0x160 [amdgpu] dm_resume+0x2b5/0x610 [amdgpu] amdgpu_device_ip_resume_phase2+0x58/0xc0 [amdgpu] amdgpu_device_resume+0xd9/0x210 [amdgpu] amdgpu_pmops_resume+0x1d/0x40 [amdgpu] pci_pm_resume+0x5b/0x90 ? pci_pm_thaw+0x80/0x80 dpm_run_callback+0x52/0x160 device_resume+0xdd/0x1e0 async_resume+0x1f/0x60 async_run_entry_fn+0x33/0x120 process_one_work+0x236/0x420 worker_thread+0x34/0x410 ? process_one_work+0x420/0x420 kthread+0x12f/0x150 ? set_kthread_struct+0x40/0x40 ret_from_fork+0x22/0x30 ---[ end trace 71d329758d0428b2 ]--- [ cut here ] WARNING: CPU: 8 PID: 60399 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn31/dcn31_smu.c:105 dcn31_smu_send_msg_with_param+0x56/0x130 [amdgpu]
[Kernel-packages] [Bug 1961121] Re: Not able to enter s2idle state on AMD platforms
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal ** Changed in: hwe-next Assignee: Alex Hung (alexhung) => (unassigned) -- 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/1961121 Title: Not able to enter s2idle state on AMD platforms Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] AMD Systems don't enter PC6 at runtime and cause failures to enter s2idle. Currently the fix is from kernel driver rather than MP2 firmware, which disable interrupts from kernel driver to fix MP2 firmware blocking CPUOFF. [Fix] The fixes involve 1) cancelling delayed work when entering s0ix and re-scheduling it when resuming from s0ix, and 2) clearing interrupts during the driver initialization and sensor command operations. [Test] This is requested by AMD and was tested on AMD CRB. [Where problems could occur] Risk is low to medium. Some code flow changes are guarded by reasonable conditions, but the fixes introduced additional suspend and resume operations. Having said that, clearing interrupts before driver initialization and cancelling work before entering sleeping states are standard approaches are usually safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961121/+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 1961121] Re: Not able to enter s2idle state on AMD platforms
** Description changed: [Impact] AMD Systems don't enter PC6 at runtime and cause failures to enter s2idle. Currently the fix is from kernel driver rather than MP2 firmware, which disable interrupts from kernel driver to fix MP2 firmware blocking CPUOFF. [Fix] + The fixes involve 1) cancelling delayed work when entering s0ix and re- + scheduling it when resuming from s0ix, and 2) clearing interrupts during + the driver initialization and sensor command operations. + [Test] + This is requested by AMD and was tested on AMD CRB. + [Where problems could occur] + + Risk is low to medium. Some code flow changes are guarded by reasonable + conditions, but the fixes introduced additional suspend and resume + operations. + + Having said that, clearing interrupts before driver initialization and + cancelling work before entering sleeping states are standard approaches + are usually safe. -- 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/1961121 Title: Not able to enter s2idle state on AMD platforms Status in HWE Next: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] AMD Systems don't enter PC6 at runtime and cause failures to enter s2idle. Currently the fix is from kernel driver rather than MP2 firmware, which disable interrupts from kernel driver to fix MP2 firmware blocking CPUOFF. [Fix] The fixes involve 1) cancelling delayed work when entering s0ix and re-scheduling it when resuming from s0ix, and 2) clearing interrupts during the driver initialization and sensor command operations. [Test] This is requested by AMD and was tested on AMD CRB. [Where problems could occur] Risk is low to medium. Some code flow changes are guarded by reasonable conditions, but the fixes introduced additional suspend and resume operations. Having said that, clearing interrupts before driver initialization and cancelling work before entering sleeping states are standard approaches are usually safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961121/+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 1961120] Re: SFH sensors are not working on some AMD platforms
** Description changed: [Impact] When amd-sfh is loaded the sensors connected do not change values at all (ALS sensor). + Here is the monitor sensors output, which doesn't change. - Here is the monitor sensors output, which doesn't change. - - $ sudo monitor-sensor + $ sudo monitor-sensor Waiting for iio-sensor-proxy to appear - +++ iio-sensor-proxy appeared - === No accelerometer - === Has ambient light sensor (value: 0.00, unit: lux) + +++ iio-sensor-proxy appeared + === No accelerometer + === Has ambient light sensor (value: 0.00, unit: lux) [Fix] + The SRU contains two fixes: + 1. increasing sensor command timeout from from 80 to 160. + 2. using first valid 15 bits only ALS max illuminance values. + + [Test] + This is requested by AMD. This was also verified by an AMD's engineer + on CRB. + [Where problems could occur] + + Low. The patches only increase timeout value and discard an invalid + bit. -- 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/1961120 Title: SFH sensors are not working on some AMD platforms Status in HWE Next: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] When amd-sfh is loaded the sensors connected do not change values at all (ALS sensor). Here is the monitor sensors output, which doesn't change. $ sudo monitor-sensor Waiting for iio-sensor-proxy to appear +++ iio-sensor-proxy appeared === No accelerometer === Has ambient light sensor (value: 0.00, unit: lux) [Fix] The SRU contains two fixes: 1. increasing sensor command timeout from from 80 to 160. 2. using first valid 15 bits only ALS max illuminance values. [Test] This is requested by AMD. This was also verified by an AMD's engineer on CRB. [Where problems could occur] Low. The patches only increase timeout value and discard an invalid bit. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961120/+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 1961119] Re: Lower the volume of expected s0i3 WARN_ON
** Description changed: [Impact] AMD has a known BIOS bug right now that leads to the following WARN traceback during s0i3 resume (see below). This doesn't have (measurable) functional impact to the system or GPU, but it is an ugly message to have in place and makes it look like a potentially major problem. AMD is working on fixing this in BIOS, but it may not be ready by the time the first platforms launch. [Fix] + Print a shorter message warning instead: "Watermarks table not configured properly by SMU". + + The fixed was cherry-picked from mainline kernel v5.17-rc4. [Test] + This is requested by AMD, and tested and verified on the AMD CRB. [Where problems could occur] + Low. This only changes the behavors of message printing There are no + functional changes. --- WARN_ON messages --- [ cut here ] WARNING: CPU: 8 PID: 60399 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn31/dcn31_smu.c:123 dcn31_smu_send_msg_with_param+0xec/0x130 [amdgpu] Modules linked in: btrfs blake2b_generic xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cpuid michael_mic hid_logitech_hidpp snd_usb_audio snd_usbmidi_lib hid_logitech_dj usbhid cdc_ether usbnet r8152 mii qrtr_mhi joydev intel_rapl_msr intel_rapl_common bnep snd_soc_dmic snd_acp6x_pdm_dma snd_soc_acp6x_mach snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine edac_mce_amd amdgpu snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi nls_iso8859_1 kvm_amd kvm snd_hda_intel qrtr snd_intel_dspcfg ns snd_intel_sdw_acpi snd_hda_codec ath11k_pci crct10dif_pclmul input_leds snd_pci_acp6x ghash_clmulni_intel ath11k snd_hda_core snd_hwdep qmi_helpers aesni_intel snd_pcm uvcvideo crypto_simd videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 iommu_v2 cryptd platform_profile btusb snd_seq_midi gpu_sched rapl mac80211 serio_raw snd_seq_midi_event videobuf2_common sparse_keymap drm_ttm_helper btrtl snd_rawmidi btbcm videodev - btintel ttm efi_pstore wmi_bmof hid_multitouch mc bluetooth snd_seq drm_kms_helper snd_seq_device ecdh_generic cfg80211 ecc snd_timer cec rc_core i2c_algo_bit snd fb_sys_fops syscopyarea sysfillrect mhi sysimgblt libarc4 soundcore snd_rn_pci_acp3x snd_pci_acp3x ccp ucsi_acpi typec_ucsi amd_pmc wireless_hotkey mac_hid typec acpi_tad sch_fq_codel msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul thunderbolt nvme i2c_piix4 xhci_pci xhci_pci_renesas nvme_core iosm wmi i2c_hid_acpi video i2c_hid hid + btintel ttm efi_pstore wmi_bmof hid_multitouch mc bluetooth snd_seq drm_kms_helper snd_seq_device ecdh_generic cfg80211 ecc snd_timer cec rc_core i2c_algo_bit snd fb_sys_fops syscopyarea sysfillrect mhi sysimgblt libarc4 soundcore snd_rn_pci_acp3x snd_pci_acp3x ccp ucsi_acpi typec_ucsi amd_pmc wireless_hotkey mac_hid typec acpi_tad sch_fq_codel msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul thunderbolt nvme i2c_piix4 xhci_pci xhci_pci_renesas nvme_core iosm wmi i2c_hid_acpi video i2c_hid hid Workqueue: events_unbound async_run_entry_fn RIP: 0010:dcn31_smu_send_msg_with_param+0xec/0x130 [amdgpu] Code: 00 e8 38 60 fc ff 48 8b 3b 4c 89 ea be 9b 62 01 00 e8 c8 60 fc ff 85 c0 75 40 bf c6 a7 00 00 e8 aa da 0c c6 41 83 ec 01 75 dc <0f> 0b 48 8b 3b b9 80 84 1e 00 44 89 fa 44 89 f6 e8 af 9c fc ff 48 RSP: 0018:b76d03167bc8 EFLAGS: 00010202 RAX: 00ff RBX: 9dc54f492800 RCX: 0008 RDX: RSI: 0001629b RDI: 9dc548bc RBP: b76d03167bf8 R08: 0009 R09: 0320 R10: 0191 R11: 04451a00 R12: 00030b48 R13: c1717d90 R14: 0011 R15: 0001 FS: () GS:9dcc7e80() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 55f79ba89f68 CR3: 00052681 CR4: 00750ee0 PKRU: 5554 Call Trace: - - dcn31_smu_transfer_wm_table_dram_2_smu+0x23/0x30 [amdgpu] - dcn31_notify_wm_ranges+0x145/0x180 [amdgpu] - dcn31_init_hw+0x465/0x8e0 [amdgpu] - dc_set_power_state+0x113/0x160 [amdgpu] - dm_resume+0x2b5/0x610 [amdgpu] - amdgpu_device_ip_resume_phase2+0x58/0xc0 [amdgpu] - amdgpu_device_resume+0xd9/0x210 [amdgpu] - amdgpu_pmops_resume+0x1d/0x40 [amdgpu] - pci_pm_resume+0x5b/0x90 - ? pci_pm_thaw+0x80/0x80 - dpm_run_callback+0x52/0x160 - device_resume+0xdd/0x1e0 - async_resume+0x1f/0x60 - async_run_entry_fn+0x33/0x120 - process_one_work+0x236/0x420 - worker_thread+0x34/0x410 - ? process_one_work+0x420/0x420 - kthread+0x12f/0x150 - ? set_kthread_struct+0x40/0x40 - ret_from_fork+0x22/0x30 - + + dcn31_smu_transfer_wm_table_dram_2_smu+0x23/0x30 [amdgpu] + dcn31_notify_wm_ranges+0x145/0x180 [amdgpu] + dcn31_init_hw+0x465/0x8e0 [amdgpu] + dc_set_power_state+0x113/0x160 [amdgpu] +
[Kernel-packages] [Bug 1961120] [NEW] SFH sensors are not working on some AMD platforms
Public bug reported: [Impact] When amd-sfh is loaded the sensors connected do not change values at all (ALS sensor). Here is the monitor sensors output, which doesn't change. $ sudo monitor-sensor Waiting for iio-sensor-proxy to appear +++ iio-sensor-proxy appeared === No accelerometer === Has ambient light sensor (value: 0.00, unit: lux) [Fix] [Test] [Where problems could occur] ** Affects: hwe-next Importance: Undecided Assignee: Alex Hung (alexhung) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-1959707 ** Tags added: amd oem-priority originate-from-1959707 ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: hwe-next Status: New => In Progress ** Changed in: hwe-next Assignee: (unassigned) => Alex Hung (alexhung) -- 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/1961120 Title: SFH sensors are not working on some AMD platforms Status in HWE Next: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] When amd-sfh is loaded the sensors connected do not change values at all (ALS sensor). Here is the monitor sensors output, which doesn't change. $ sudo monitor-sensor Waiting for iio-sensor-proxy to appear +++ iio-sensor-proxy appeared === No accelerometer === Has ambient light sensor (value: 0.00, unit: lux) [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961120/+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 1961121] [NEW] Not able to enter s2idle state on AMD platforms
Public bug reported: [Impact] AMD Systems don't enter PC6 at runtime and cause failures to enter s2idle. Currently the fix is from kernel driver rather than MP2 firmware, which disable interrupts from kernel driver to fix MP2 firmware blocking CPUOFF. [Fix] [Test] [Where problems could occur] ** Affects: hwe-next Importance: Undecided Assignee: Alex Hung (alexhung) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-1960434 ** Tags added: amd oem-priority originate-from-1960434 ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: hwe-next Assignee: (unassigned) => Alex Hung (alexhung) ** Changed in: hwe-next Status: New => 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/1961121 Title: Not able to enter s2idle state on AMD platforms Status in HWE Next: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] AMD Systems don't enter PC6 at runtime and cause failures to enter s2idle. Currently the fix is from kernel driver rather than MP2 firmware, which disable interrupts from kernel driver to fix MP2 firmware blocking CPUOFF. [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961121/+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 1961119] [NEW] Lower the volume of expected s0i3 WARN_ON
btrtl snd_rawmidi btbcm videodev btintel ttm efi_pstore wmi_bmof hid_multitouch mc bluetooth snd_seq drm_kms_helper snd_seq_device ecdh_generic cfg80211 ecc snd_timer cec rc_core i2c_algo_bit snd fb_sys_fops syscopyarea sysfillrect mhi sysimgblt libarc4 soundcore snd_rn_pci_acp3x snd_pci_acp3x ccp ucsi_acpi typec_ucsi amd_pmc wireless_hotkey mac_hid typec acpi_tad sch_fq_codel msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul thunderbolt nvme i2c_piix4 xhci_pci xhci_pci_renesas nvme_core iosm wmi i2c_hid_acpi video i2c_hid hid Workqueue: events_unbound async_run_entry_fn RIP: 0010:dcn31_smu_send_msg_with_param+0x56/0x130 [amdgpu] Code: 48 8b 3b 4c 89 ea be 9b 62 01 00 e8 64 61 fc ff 85 c0 75 32 bf c6 a7 00 00 89 45 d4 e8 43 db 0c c6 41 83 ec 01 8b 45 d4 75 d6 <0f> 0b 85 c0 ba ff ff ff ff 75 16 48 83 c4 08 89 d0 5b 41 5c 41 5d RSP: 0018:b76d03167b80 EFLAGS: 00010202 RAX: 00ff RBX: 9dc54f492800 RCX: 9dc54dec03b0 RDX: RSI: 0001629b RDI: 9dc548bc RBP: b76d03167bb0 R08: c1614a90 R09: b76d03167bc8 R10: R11: 88875560 R12: 00030d41 R13: c1717d90 R14: 0012 R15: FS: () GS:9dcc7e80() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 55f79ba89f68 CR3: 00052681 CR4: 00750ee0 PKRU: 5554 Call Trace: ? amdgpu_cgs_write_register+0x14/0x20 [amdgpu] dcn31_smu_set_display_idle_optimization+0x2f/0x40 [amdgpu] dcn31_update_clocks+0x2f5/0x340 [amdgpu] ? amdgpu_device_rreg+0x17/0x20 [amdgpu] ? amdgpu_cgs_read_register+0x14/0x20 [amdgpu] ? dm_read_reg_func+0x2f/0x90 [amdgpu] dcn21_exit_optimized_pwr_state+0x1e/0x20 [amdgpu] clk_mgr_exit_optimized_pwr_state+0x91/0x120 [amdgpu] dc_link_detect+0x73/0xc0 [amdgpu] dm_resume+0x34c/0x610 [amdgpu] amdgpu_device_ip_resume_phase2+0x58/0xc0 [amdgpu] amdgpu_device_resume+0xd9/0x210 [amdgpu] amdgpu_pmops_resume+0x1d/0x40 [amdgpu] pci_pm_resume+0x5b/0x90 ? pci_pm_thaw+0x80/0x80 dpm_run_callback+0x52/0x160 device_resume+0xdd/0x1e0 async_resume+0x1f/0x60 async_run_entry_fn+0x33/0x120 process_one_work+0x236/0x420 worker_thread+0x34/0x410 ? process_one_work+0x420/0x420 kthread+0x12f/0x150 ? set_kthread_struct+0x40/0x40 ret_from_fork+0x22/0x30 ---[ end trace 71d329758d0428b3 ]--- ** Affects: hwe-next Importance: Medium Assignee: Alex Hung (alexhung) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Tags: originate-from-1960665 ** Changed in: hwe-next Assignee: (unassigned) => Alex Hung (alexhung) ** Changed in: hwe-next Status: New => In Progress ** Tags added: originate-from-1960665 ** Changed in: hwe-next Importance: Undecided => Medium ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New -- 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/1961119 Title: Lower the volume of expected s0i3 WARN_ON Status in HWE Next: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] AMD has a known BIOS bug right now that leads to the following WARN traceback during s0i3 resume (see below). This doesn't have (measurable) functional impact to the system or GPU, but it is an ugly message to have in place and makes it look like a potentially major problem. AMD is working on fixing this in BIOS, but it may not be ready by the time the first platforms launch. [Fix] [Test] [Where problems could occur] --- WARN_ON messages --- [ cut here ] WARNING: CPU: 8 PID: 60399 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn31/dcn31_smu.c:123 dcn31_smu_send_msg_with_param+0xec/0x130 [amdgpu] Modules linked in: btrfs blake2b_generic xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cpuid michael_mic hid_logitech_hidpp snd_usb_audio snd_usbmidi_lib hid_logitech_dj usbhid cdc_ether usbnet r8152 mii qrtr_mhi joydev intel_rapl_msr intel_rapl_common bnep snd_soc_dmic snd_acp6x_pdm_dma snd_soc_acp6x_mach snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine edac_mce_amd amdgpu snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi nls_iso8859_1 kvm_amd kvm snd_hda_intel qrtr snd_intel_dspcfg ns snd_intel_sdw_acpi snd_hda_codec ath11k_pci crct10dif_pclmul input_leds snd_pci_acp6x ghash_clmulni_intel ath11k snd_hda_core snd_hwdep qmi_helpers aesni_intel snd_pcm
[Kernel-packages] [Bug 1956670] Re: Extend support for runtime power management for AMD's Yellow Carp
** Changed in: hwe-next Status: Fix Committed => Fix Released ** Changed in: linux-oem-5.14 (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/1956670 Title: Extend support for runtime power management for AMD's Yellow Carp Status in HWE Next: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] Some OEM designs may populate the secured USB port without runtime power management supported. [Fix] Adds two IDs for XHCI controllers and enable runtime PM as default. This is from kernel 5.16-rc6. [Test] This is requested by AMD. [Where problems could occur] Low risk. This patch adds two additional hardware IDs and has no impacts on other systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956670/+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 1956373] Re: Fix for rare (~1%) s0ix failures o AMD systems
** Changed in: hwe-next 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/1956373 Title: Fix for rare (~1%) s0ix failures o AMD systems Status in HWE Next: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] A rare (~1%) failure has been reported in the community for a period of time on Renoir platforms with s0ix. This failure was also corroborated once by a Cezanne user. [Fix] In the s0ix entry need retain gfx in the gfxoff state, so skipping setting gfx cgpg in the S0ix suspend-resume process. The fix was cherry-picked from 5.16-rc8. [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD systems that support s0ix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956373/+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 1941660] Re: Fix incorrect keyboard backlight behaviours
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Invalid ** Changed in: hwe-next Status: New => Invalid ** Changed in: linux (Ubuntu) Assignee: Alex Hung (alexhung) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941660 Title: Fix incorrect keyboard backlight behaviours Status in HWE Next: Invalid Status in linux package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Invalid Bug description: [Impact] The keyboard backlight was turning on when entering suspend and turning off when exiting (the opposite of how it should be). [Fix] Swaps the on / off commands. The fix commit is in 5.14-rc7. [Test] This is requested by AMD. [Where problems could occur] This fixes the incorrect LED on/off behaviours in 5dbf50997578, and the risk is very slow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1941660/+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 1956373] Re: Fix for rare (~1%) s0ix failures o AMD systems
** Changed in: hwe-next Status: New => Fix Committed ** Changed in: hwe-next Status: Fix Committed => 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/1956373 Title: Fix for rare (~1%) s0ix failures o AMD systems Status in HWE Next: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] A rare (~1%) failure has been reported in the community for a period of time on Renoir platforms with s0ix. This failure was also corroborated once by a Cezanne user. [Fix] In the s0ix entry need retain gfx in the gfxoff state, so skipping setting gfx cgpg in the S0ix suspend-resume process. The fix was cherry-picked from 5.16-rc8. [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD systems that support s0ix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956373/+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 1956670] Re: Extend support for runtime power management for AMD's Yellow Carp
** Changed in: hwe-next Status: New => 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/1956670 Title: Extend support for runtime power management for AMD's Yellow Carp Status in HWE Next: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] Some OEM designs may populate the secured USB port without runtime power management supported. [Fix] Adds two IDs for XHCI controllers and enable runtime PM as default. This is from kernel 5.16-rc6. [Test] This is requested by AMD. [Where problems could occur] Low risk. This patch adds two additional hardware IDs and has no impacts on other systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956670/+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 1956373] Re: Fix for rare (~1%) s0ix failures o AMD systems
** Tags removed: verification-needed-focal ** 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/1956373 Title: Fix for rare (~1%) s0ix failures o AMD systems Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] A rare (~1%) failure has been reported in the community for a period of time on Renoir platforms with s0ix. This failure was also corroborated once by a Cezanne user. [Fix] In the s0ix entry need retain gfx in the gfxoff state, so skipping setting gfx cgpg in the S0ix suspend-resume process. The fix was cherry-picked from 5.16-rc8. [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD systems that support s0ix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956373/+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 1956373] Re: Fix for rare (~1%) s0ix failures o AMD systems
** Changed in: linux-oem-5.14 (Ubuntu) Assignee: Alex Hung (alexhung) => (unassigned) -- 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/1956373 Title: Fix for rare (~1%) s0ix failures o AMD systems Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] A rare (~1%) failure has been reported in the community for a period of time on Renoir platforms with s0ix. This failure was also corroborated once by a Cezanne user. [Fix] In the s0ix entry need retain gfx in the gfxoff state, so skipping setting gfx cgpg in the S0ix suspend-resume process. The fix was cherry-picked from 5.16-rc8. [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD systems that support s0ix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956373/+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 1956373] Re: Fix for rare (~1%) s0ix failures o AMD systems
** Changed in: hwe-next Assignee: (unassigned) => Alex Hung (alexhung) -- 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/1956373 Title: Fix for rare (~1%) s0ix failures o AMD systems Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] A rare (~1%) failure has been reported in the community for a period of time on Renoir platforms with s0ix. This failure was also corroborated once by a Cezanne user. [Fix] In the s0ix entry need retain gfx in the gfxoff state, so skipping setting gfx cgpg in the S0ix suspend-resume process. The fix was cherry-picked from 5.16-rc8. [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD systems that support s0ix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956373/+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 1945361] Re: [Yellow Carp] USB4 interdomain communication problems
** Changed in: amd Importance: Undecided => 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/1945361 Title: [Yellow Carp] USB4 interdomain communication problems Status in amd: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] Yellow carp w/ SW CM bi-directional interdomain communication may have some problems that the response packets are lost sometimes within the stipulated time. [Fix] Enable the retry by increasing retry count from 1 to 4. The patch is in linux-next (tag next-20211007) and can be found @ https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/thunderbolt/ctl.c?id=641cdbea7635be3a177dbdf81356ccb16f3769e3 [Test] This is requested and tested by AMD. [Where problems could occur] Low risk. This only affects small number of AMD systems that would excess the time. Systems without problems won't be affected. = Original Description AMD internal team has found that for Yellow carp w/ SW CM bi- directional interdomain communication may have some problems. It's been aligned upstream to increase number of retries to account for these issues. https://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git/commit/?h=next=641cdbea7635be3a177dbdf81356ccb16f3769e3 Can Canonical team please include this in future 5.14-OEM? To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1945361/+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 1956670] [NEW] Extend support for runtime power management for AMD's Yellow Carp
Public bug reported: [Impact] Some OEM designs may populate the secured USB port without runtime power management supported. [Fix] Adds two IDs for XHCI controllers and enable runtime PM as default. This is from kernel 5.16-rc6. [Test] This is requested by AMD. [Where problems could occur] Low risk. This patch adds two additional hardware IDs and has no impacts on other systems. ** Affects: hwe-next Importance: Undecided Assignee: Alex Hung (alexhung) Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-1956471 ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => In Progress ** Tags added: amd oem-priority originate-from-1956471 ** Changed in: hwe-next Assignee: (unassigned) => Alex Hung (alexhung) -- 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/1956670 Title: Extend support for runtime power management for AMD's Yellow Carp Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: In Progress Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] Some OEM designs may populate the secured USB port without runtime power management supported. [Fix] Adds two IDs for XHCI controllers and enable runtime PM as default. This is from kernel 5.16-rc6. [Test] This is requested by AMD. [Where problems could occur] Low risk. This patch adds two additional hardware IDs and has no impacts on other systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956670/+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 1945361] Re: [Yellow Carp] USB4 interdomain communication problems
** Changed in: amd Status: Fix Released => 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/1945361 Title: [Yellow Carp] USB4 interdomain communication problems Status in amd: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] Yellow carp w/ SW CM bi-directional interdomain communication may have some problems that the response packets are lost sometimes within the stipulated time. [Fix] Enable the retry by increasing retry count from 1 to 4. The patch is in linux-next (tag next-20211007) and can be found @ https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/thunderbolt/ctl.c?id=641cdbea7635be3a177dbdf81356ccb16f3769e3 [Test] This is requested and tested by AMD. [Where problems could occur] Low risk. This only affects small number of AMD systems that would excess the time. Systems without problems won't be affected. = Original Description AMD internal team has found that for Yellow carp w/ SW CM bi- directional interdomain communication may have some problems. It's been aligned upstream to increase number of retries to account for these issues. https://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git/commit/?h=next=641cdbea7635be3a177dbdf81356ccb16f3769e3 Can Canonical team please include this in future 5.14-OEM? To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1945361/+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 1949245] Re: AMD ACP 6.x DMIC Supports
** Changed in: hwe-next Status: Fix Released => 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/1949245 Title: AMD ACP 6.x DMIC Supports Status in HWE Next: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) which will not work with existing ACP drivers. [Fix] Backport the new driver that is now in linux-next (to be in 5.16) [Test] This is requested by AMD. [Where problems could occur] Low risk. This is a stand-alone driver that does not affect others devices and platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949245/+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 1941893] Re: Improve performance and idle power consumption
** Changed in: amd Status: Fix Released => 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/1941893 Title: Improve performance and idle power consumption Status in amd: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] This can improve AMD performance for all Zen or newer CPU which support C3 shares cache. [Fix] Its not necessary to flush the caches in software before entering C3. Empirical measurements show: 40-45% improvement in speedometer score. ~15% improvement in idle power. The patch is in linux-next (tag next-20211007) and can be found @ https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/arch/x86/kernel/acpi/cstate.c?id=a8fb40966f19ff81520d9ccf8f7e2b95201368b8 [Test] This is requested by AMD. [Where problems could occur] Low risk. This only works on AMD Zen CPUs that supports this features. AMD tested it and provided estimated measurement results. Original descriptions A patch queued for 5.15 to change the C3 entry will improve AMD performance. https://lore.kernel.org/patchwork/patch/1478776/ Empirical measurements show: 40-45% improvement in speedometer score. ~15% improvement in idle power. Can you please include in 5.13-oem and 5.14-oem kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1941893/+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 1956373] [NEW] Fix for rare (~1%) s0ix failures o AMD systems
Public bug reported: [Impact] A rare (~1%) failure has been reported in the community for a period of time on Renoir platforms with s0ix. This failure was also corroborated once by a Cezanne user. [Fix] In the s0ix entry need retain gfx in the gfxoff state, so skipping setting gfx cgpg in the S0ix suspend-resume process. The fix was cherry-picked from 5.16-rc8. [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD systems that support s0ix. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Assignee: Alex Hung (alexhung) Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-1956259 ** Information type changed from Proprietary to Public ** Changed in: amd Assignee: (unassigned) => Alex Hung (alexhung) ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: amd ** Changed in: linux-oem-5.14 (Ubuntu) Assignee: (unassigned) => Alex Hung (alexhung) ** Tags added: amd oem-priority originate-from-1956259 -- 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/1956373 Title: Fix for rare (~1%) s0ix failures o AMD systems Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] A rare (~1%) failure has been reported in the community for a period of time on Renoir platforms with s0ix. This failure was also corroborated once by a Cezanne user. [Fix] In the s0ix entry need retain gfx in the gfxoff state, so skipping setting gfx cgpg in the S0ix suspend-resume process. The fix was cherry-picked from 5.16-rc8. [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD systems that support s0ix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956373/+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 1928482] Re: [Castle Peak]: pull in CPPC fixes
** Changed in: amd 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.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928482 Title: [Castle Peak]: pull in CPPC fixes Status in amd: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Bug description: Recently a CPPC fix was accepted for fixing CPPC on many AMD platforms. https://github.com/torvalds/linux/commit/3743d55b289c203d8f77b7cd47c24926b9d186ae It's CC'ed to stable, so it will eventually flow in, but to give best performance on customer systems, can you please pull this into all sustaining OEM trees? To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928482/+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 1928694] Re: [Cezanne/Renoire]: Replace some fixes from linux-oem-5.10 with those landing upstream
** Changed in: amd 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.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928694 Title: [Cezanne/Renoire]: Replace some fixes from linux-oem-5.10 with those landing upstream Status in amd: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Invalid Bug description: The following patches are accepted into upstream for 5.14 and should displace the existing patches carried in OEM tree. * "ACPI: processor idle: Fix up C-state latency if not ordered" replaces the hack to hardcode latency values for HP's RN systems. * "ACPI: PM: s2idle: Add missing LPS0 functions for AMD" has been accepted To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928694/+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 1945348] Re: Yellow Carp S0i3 stability fix
** Changed in: amd 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/1945348 Title: Yellow Carp S0i3 stability fix Status in amd: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] Below errors are reported with S0i3 on Yellow carp where under stress testing with 5.14.0 through 5.14.8. [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 amdgpu :04:00.0: amdgpu: amdgpu_device_ip_resume failed (-110). PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110 amdgpu :04:00.0: PM: failed to resume async: error -110 [Fix] The patch fixes this by forcing exit gfxoff for sdma resume. The patch is in 5.15-rc4 (https://github.com/torvalds/linux/commit/26db706a6d77b9e184feb11725e97e53b7a89519) [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD platforms with s0ix supports. The changes repeat what is (should be) done in firmware. = original descriptions = A problem is identified with S0i3 on Yellow carp where under stress testing with 5.14.0 through 5.14.8 sometimes there will be failures. It will manifest as: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 amdgpu :04:00.0: amdgpu: amdgpu_device_ip_resume failed (-110). PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110 amdgpu :04:00.0: PM: failed to resume async: error -110 The fix for this will be going into 5.15-rcX and also to 5.14.y. Just want to give a pointer to Canonical team that if this comes up where to expect the fix for OEM kernel. The patch going into 5.15-rcX and 5.14.y is: https://lists.freedesktop.org/archives/amd-gfx/2021-September/069451.html To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1945348/+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 1953540] Re: Fix power button wakeup with shared IRQs on AMD platforms
** Changed in: linux-oem-5.14 (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/1953540 Title: Fix power button wakeup with shared IRQs on AMD platforms Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button presses. [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1953540/+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 1953540] Re: Fix power button wakeup with shared IRQs on AMD platforms
** Tags removed: verification-needed-focal ** 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/1953540 Title: Fix power button wakeup with shared IRQs on AMD platforms Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Bug description: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button presses. [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1953540/+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 1953540] Re: Fix power button wakeup with shared IRQs on AMD platforms
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: hwe-next Importance: Undecided => Medium ** Package changed: linux (Ubuntu Focal) => linux-oem-5.14 (Ubuntu Focal) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Invalid => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953540 Title: Fix power button wakeup with shared IRQs on AMD platforms Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Bug description: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button presses. [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1953540/+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 1953540] Re: Fix power button wakeup with shared IRQs on AMD platforms
** Tags added: amd oem-priority originate-from-1950332 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953540 Title: Fix power button wakeup with shared IRQs on AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: In Progress Bug description: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button presses. [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1953540/+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 1953540] Re: Fix power button wakeup with shared IRQs on AMD platforms
** Description changed: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to - the the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO + the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. - [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. ** Description changed: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] - This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button + This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button presses. [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953540 Title: Fix power button wakeup with shared IRQs on AMD platforms Status in linux package in Ubuntu: In Progress Bug description: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button presses. [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953540/+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 1953540] [NEW] Fix power button wakeup with shared IRQs on AMD platforms
Public bug reported: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Alex Hung (alexhung) Status: In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Alex Hung (alexhung) ** Changed in: linux (Ubuntu) Status: New => Fix Committed ** Changed in: linux (Ubuntu) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953540 Title: Fix power button wakeup with shared IRQs on AMD platforms Status in linux package in Ubuntu: In Progress Bug description: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953540/+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 1949245] Re: AMD ACP 6.x DMIC Supports
** Changed in: hwe-next 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/1949245 Title: AMD ACP 6.x DMIC Supports Status in HWE Next: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) which will not work with existing ACP drivers. [Fix] Backport the new driver that is now in linux-next (to be in 5.16) [Test] This is requested by AMD. [Where problems could occur] Low risk. This is a stand-alone driver that does not affect others devices and platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949245/+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 1950013] Re: Add s0i3 RTC wake up for AMD systems
** Changed in: hwe-next Status: New => 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/1950013 Title: Add s0i3 RTC wake up for AMD systems Status in HWE Next: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] RTC based wakeup is not supported natively by the hardware for s0i3. [Fix] A firmware and driver updates were implemented. The driver passes wakeup time to SMU to to enable RTC from S0i3. Note this s0i3 RTC wake up also requires new firmware. The first patch is the prerequisite actual fix (patch 2 and 3). [Test] This is requested by AMD and tested by an AMD developer as below: Testing a suspend run with RTC for 15 seconds and then 30 seconds: ``` $ sudo rtcwake --seconds 15 -m mem rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:31:45 2021 $ sudo rtcwake --seconds 30 -m mem rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:33:13 2021 $ sudo cat /sys/kernel/debug/amd_pmc/s0ix_stats === S0ix statistics === S0ix Entry Time: 4793618285 S0ix Exit Time: 6209036738 Residency Time: 29487884 ``` Residency divided by 100 is 29.4 seconds. Reading idle mask works fine too. [Where problems could occur] Low risk. First patch only exports Idlemask value. The actual fix only affects a specific AMD CPU (CZN). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950013/+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 1952356] [NEW] [EHL][TGL][ADL] PMU support
Public bug reported: [Impact] The patches enable PMU support [Fix] Intel provides a list of patches to provide Linux perf supports [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel ElkhartLake/TigerLake/AdlerLake. Further testing will be required. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Alex Hung (alexhung) Status: Triaged ** Tags: intel oem-priority originate-from-1943541 ** Tags added: intel oem-priority originate-from-1943541 ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Alex Hung (alexhung) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952356 Title: [EHL][TGL][ADL] PMU support Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] The patches enable PMU support [Fix] Intel provides a list of patches to provide Linux perf supports [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel ElkhartLake/TigerLake/AdlerLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952356/+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 1952153] [NEW] [EHL][TGL][ADL] power management controller driver enabling
Public bug reported: [Impact] The patches enable power management controller supports. [Fix] The driver is the Kernel gateway to the PMC hardware for Intel processors and it provides debug hooks to developers and end-users to quickly figure out why their platform is not entering a deeper idle state such as S0ix. [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel ElkhartLake / TigerLake / AlderLake. Further testing will be required. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel oem-priority originate-from-1943538 ** Tags added: intel oem-priority originate-from-1943538 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952153 Title: [EHL][TGL][ADL] power management controller driver enabling Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Impact] The patches enable power management controller supports. [Fix] The driver is the Kernel gateway to the PMC hardware for Intel processors and it provides debug hooks to developers and end-users to quickly figure out why their platform is not entering a deeper idle state such as S0ix. [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel ElkhartLake / TigerLake / AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952153/+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 1952132] Re: [ADL] Thermal Support
** Tags added: intel oem-priority originate-from-1943522 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952132 Title: [ADL] Thermal Support Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The patches enable thermal supports. [Fix] Intel provides a list of patches to add new PCI driver which register a thermal zone and allows to get notification [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952132/+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 1952132] [NEW] [ADL] Thermal Support
Public bug reported: [Impact] The patches enable thermal supports. [Fix] Intel provides a list of patches to add new PCI driver which register a thermal zone and allows to get notification [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952132 Title: [ADL] Thermal Support Status in linux package in Ubuntu: New Bug description: [Impact] The patches enable thermal supports. [Fix] Intel provides a list of patches to add new PCI driver which register a thermal zone and allows to get notification [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952132/+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 1952018] [NEW] [ADL] Thunderbolt patches
Public bug reported: [Impact] The patches enable discrete thunderbolt supports. [Fix] Intel provides a list of patches to enable discrete thunderbolt [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel oem-priority originate-from-1943511 ** Tags added: intel oem-priority originate-from-1943511 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952018 Title: [ADL] Thunderbolt patches Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Impact] The patches enable discrete thunderbolt supports. [Fix] Intel provides a list of patches to enable discrete thunderbolt [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952018/+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 1952006] Re: [TGL][ADL] ACRN hypervisor support
** Description changed: [Impact] The driver enables the host to run ACRN hypervisor which is a flexible, lightweight reference hypervisor, built with real-time and safety- criticality in mind, optimized to streamline embedded development through an open-source platform. https://projectacrn.org/ [Fix] - Intel provides a list of patches to enable Tiger Lake ROP CET. + Intel provides a list of patches to enable ACRN hypervisor [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel TigerLake/AlderLake. Further testing will be required. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952006 Title: [TGL][ADL] ACRN hypervisor support Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The driver enables the host to run ACRN hypervisor which is a flexible, lightweight reference hypervisor, built with real-time and safety-criticality in mind, optimized to streamline embedded development through an open-source platform. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable ACRN hypervisor [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel TigerLake/AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952006/+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 1952007] [NEW] [ADL] ITBM support for Hybrid platforms
Public bug reported: [Impact] Need ITBM support for Hybrid platforms. Need to change the scheduling order from Core, HT, ATOM to Core, ATOM, HT. When using ITBM on systems that has a mixture of CPUs supporting Hyper-Threading and others not supporting it (even offlining HT siblings may cause the issue to be reproducible). Hybrid topologies meet the aforementioned condition. In such cases, threads will be consolidated on CPUs of high priority using got HT siblings, while CPUs of medium priority will remain idle. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable AlderLake [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel oem-priority originate-from-1943549 ** Tags added: intel oem-priority originate-from-1943549 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952007 Title: [ADL] ITBM support for Hybrid platforms Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Impact] Need ITBM support for Hybrid platforms. Need to change the scheduling order from Core, HT, ATOM to Core, ATOM, HT. When using ITBM on systems that has a mixture of CPUs supporting Hyper-Threading and others not supporting it (even offlining HT siblings may cause the issue to be reproducible). Hybrid topologies meet the aforementioned condition. In such cases, threads will be consolidated on CPUs of high priority using got HT siblings, while CPUs of medium priority will remain idle. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable AlderLake [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952007/+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 1952006] [NEW] [TGL][ADL] ACRN hypervisor support
Public bug reported: [Impact] The driver enables the host to run ACRN hypervisor which is a flexible, lightweight reference hypervisor, built with real-time and safety- criticality in mind, optimized to streamline embedded development through an open-source platform. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable Tiger Lake ROP CET. [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel TigerLake/AlderLake. Further testing will be required. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel oem-priority originate-from-1943552 ** Tags added: intel oem-priority originate-from-1943552 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952006 Title: [TGL][ADL] ACRN hypervisor support Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Impact] The driver enables the host to run ACRN hypervisor which is a flexible, lightweight reference hypervisor, built with real-time and safety-criticality in mind, optimized to streamline embedded development through an open-source platform. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable Tiger Lake ROP CET. [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel TigerLake/AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952006/+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 1949245] Re: AMD ACP 6.x DMIC Supports
** Tags removed: verification-needed-focal ** 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/1949245 Title: AMD ACP 6.x DMIC Supports Status in HWE Next: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) which will not work with existing ACP drivers. [Fix] Backport the new driver that is now in linux-next (to be in 5.16) [Test] This is requested by AMD. [Where problems could occur] Low risk. This is a stand-alone driver that does not affect others devices and platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949245/+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 1950013] Re: Add s0i3 RTC wake up for AMD systems
** Tags removed: verification-needed-focal ** 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/1950013 Title: Add s0i3 RTC wake up for AMD systems Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] RTC based wakeup is not supported natively by the hardware for s0i3. [Fix] A firmware and driver updates were implemented. The driver passes wakeup time to SMU to to enable RTC from S0i3. Note this s0i3 RTC wake up also requires new firmware. The first patch is the prerequisite actual fix (patch 2 and 3). [Test] This is requested by AMD and tested by an AMD developer as below: Testing a suspend run with RTC for 15 seconds and then 30 seconds: ``` $ sudo rtcwake --seconds 15 -m mem rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:31:45 2021 $ sudo rtcwake --seconds 30 -m mem rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:33:13 2021 $ sudo cat /sys/kernel/debug/amd_pmc/s0ix_stats === S0ix statistics === S0ix Entry Time: 4793618285 S0ix Exit Time: 6209036738 Residency Time: 29487884 ``` Residency divided by 100 is 29.4 seconds. Reading idle mask works fine too. [Where problems could occur] Low risk. First patch only exports Idlemask value. The actual fix only affects a specific AMD CPU (CZN). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950013/+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 1941893] Re: Improve performance and idle power consumption
** Changed in: amd 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/1941893 Title: Improve performance and idle power consumption Status in amd: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] This can improve AMD performance for all Zen or newer CPU which support C3 shares cache. [Fix] Its not necessary to flush the caches in software before entering C3. Empirical measurements show: 40-45% improvement in speedometer score. ~15% improvement in idle power. The patch is in linux-next (tag next-20211007) and can be found @ https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/arch/x86/kernel/acpi/cstate.c?id=a8fb40966f19ff81520d9ccf8f7e2b95201368b8 [Test] This is requested by AMD. [Where problems could occur] Low risk. This only works on AMD Zen CPUs that supports this features. AMD tested it and provided estimated measurement results. Original descriptions A patch queued for 5.15 to change the C3 entry will improve AMD performance. https://lore.kernel.org/patchwork/patch/1478776/ Empirical measurements show: 40-45% improvement in speedometer score. ~15% improvement in idle power. Can you please include in 5.13-oem and 5.14-oem kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1941893/+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 1945361] Re: [Yellow Carp] USB4 interdomain communication problems
** Changed in: amd 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/1945361 Title: [Yellow Carp] USB4 interdomain communication problems Status in amd: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] Yellow carp w/ SW CM bi-directional interdomain communication may have some problems that the response packets are lost sometimes within the stipulated time. [Fix] Enable the retry by increasing retry count from 1 to 4. The patch is in linux-next (tag next-20211007) and can be found @ https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/thunderbolt/ctl.c?id=641cdbea7635be3a177dbdf81356ccb16f3769e3 [Test] This is requested and tested by AMD. [Where problems could occur] Low risk. This only affects small number of AMD systems that would excess the time. Systems without problems won't be affected. = Original Description AMD internal team has found that for Yellow carp w/ SW CM bi- directional interdomain communication may have some problems. It's been aligned upstream to increase number of retries to account for these issues. https://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git/commit/?h=next=641cdbea7635be3a177dbdf81356ccb16f3769e3 Can Canonical team please include this in future 5.14-OEM? To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1945361/+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 1950013] Re: Add s0i3 RTC wake up for AMD systems
https://lists.ubuntu.com/archives/kernel-team/2021-November/125521.html -- 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/1950013 Title: Add s0i3 RTC wake up for AMD systems Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] RTC based wakeup is not supported natively by the hardware for s0i3. [Fix] A firmware and driver updates were implemented. The driver passes wakeup time to SMU to to enable RTC from S0i3. Note this s0i3 RTC wake up also requires new firmware. The first patch is the prerequisite actual fix (patch 2 and 3). [Test] This is requested by AMD and tested by an AMD developer as below: Testing a suspend run with RTC for 15 seconds and then 30 seconds: ``` $ sudo rtcwake --seconds 15 -m mem rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:31:45 2021 $ sudo rtcwake --seconds 30 -m mem rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:33:13 2021 $ sudo cat /sys/kernel/debug/amd_pmc/s0ix_stats === S0ix statistics === S0ix Entry Time: 4793618285 S0ix Exit Time: 6209036738 Residency Time: 29487884 ``` Residency divided by 100 is 29.4 seconds. Reading idle mask works fine too. [Where problems could occur] Low risk. First patch only exports Idlemask value. The actual fix only affects a specific AMD CPU (CZN). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950013/+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 1950013] [NEW] Add s0i3 RTC wake up for AMD systems
Public bug reported: [Impact] RTC based wakeup is not supported natively by the hardware for s0i3. [Fix] A firmware and driver updates were implemented. The driver passes wakeup time to SMU to to enable RTC from S0i3. Note this s0i3 RTC wake up also requires new firmware. The first patch is the prerequisite actual fix (patch 2 and 3). [Test] This is requested by AMD and tested by an AMD developer as below: Testing a suspend run with RTC for 15 seconds and then 30 seconds: ``` $ sudo rtcwake --seconds 15 -m mem rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:31:45 2021 $ sudo rtcwake --seconds 30 -m mem rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:33:13 2021 $ sudo cat /sys/kernel/debug/amd_pmc/s0ix_stats === S0ix statistics === S0ix Entry Time: 4793618285 S0ix Exit Time: 6209036738 Residency Time: 29487884 ``` Residency divided by 100 is 29.4 seconds. Reading idle mask works fine too. [Where problems could occur] Low risk. First patch only exports Idlemask value. The actual fix only affects a specific AMD CPU (CZN). ** Affects: hwe-next Importance: Undecided Assignee: Alex Hung (alexhung) Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-1947889 ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Description changed: [Impact] - RTC based wakeup is not supported natively by the hardware for s0i3. + RTC based wakeup is not supported natively by the hardware for s0i3. [Fix] - A firmware and driver updates were implemented. The driver passes + A firmware and driver updates were implemented. The driver passes wakeup time to SMU to to enable RTC from S0i3. - Note this s0i3 RTC wake up also requires new firmware. + Note this s0i3 RTC wake up also requires new firmware. - The first patch is the prerequisite actual fix (patch 2 and 3). + The first patch is the prerequisite actual fix (patch 2 and 3). [Test] - This is requested by AMD and tested by an AMD developer as below: + This is requested by AMD and tested by an AMD developer as below: - Testing a suspend run with RTC for 15 seconds and then 30 seconds: - ``` - $ sudo rtcwake --seconds 15 -m mem - rtcwake: assuming RTC uses UTC ... - rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:31:45 2021 - $ sudo rtcwake --seconds 30 -m mem - rtcwake: assuming RTC uses UTC ... - rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:33:13 2021 - $ sudo cat /sys/kernel/debug/amd_pmc/s0ix_stats - === S0ix statistics === - S0ix Entry Time: 4793618285 - S0ix Exit Time: 6209036738 - Residency Time: 29487884 - ``` - Residency divided by 100 is 29.4 seconds. + Testing a suspend run with RTC for 15 seconds and then 30 seconds: + ``` + $ sudo rtcwake --seconds 15 -m mem + rtcwake: assuming RTC uses UTC ... + rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:31:45 2021 + $ sudo rtcwake --seconds 30 -m mem + rtcwake: assuming RTC uses UTC ... + rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:33:13 2021 + $ sudo cat /sys/kernel/debug/amd_pmc/s0ix_stats + === S0ix statistics === + S0ix Entry Time: 4793618285 + S0ix Exit Time: 6209036738 + Residency Time: 29487884 + ``` + Residency divided by 100 is 29.4 seconds. - Reading idle mask works fine too. + Reading idle mask works fine too. [Where problems could occur] - Low risk. + Low risk. - First patch only exports Idlemask value. - The actual fix only affects a specific AMD CPU (CZN). + First patch only exports Idlemask value. + The actual fix only affects a specific AMD CPU (CZN). ** Tags added: amd oem-priority originate-from-1947889 ** Changed in: hwe-next Assignee: (unassigned) => Alex Hung (alexhung) -- 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/1950013 Title: Add s0i3 RTC wake up for AMD systems Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] RTC based wakeup is not supported natively by the hardware for s0i3. [Fix] A firmware and driver updates were implemented. The driver passes wakeup time to SMU to to enable RTC from S0i3. Note this s0i3 RTC wake up also requires ne
[Kernel-packages] [Bug 1949245] Re: AMD ACP 6.x DMIC Supports
SRU sent for review: https://lists.ubuntu.com/archives/kernel- team/2021-November/125381.html -- 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/1949245 Title: AMD ACP 6.x DMIC Supports Status in HWE Next: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) which will not work with existing ACP drivers. [Fix] Backport the new driver that is now in linux-next (to be in 5.16) [Test] This is requested by AMD. [Where problems could occur] Low risk. This is a stand-alone driver that does not affect others devices and platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949245/+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 1949245] Re: AMD ACP 6.x DMIC Supports
** Changed in: hwe-next Assignee: (unassigned) => Alex Hung (alexhung) ** Changed in: linux-oem-5.14 (Ubuntu) Assignee: Alex Hung (alexhung) => (unassigned) ** Description changed: [Impact] - AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) - which will not work with existing ACP drivers. + AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) + which will not work with existing ACP drivers. [Fix] - Backport the new driver that is now in linux-next (to be in 5.16) + Backport the new driver that is now in linux-next (to be in 5.16) [Test] - This is requested by AMD. + This is requested by AMD. [Where problems could occur] - Low risk. This is a stand-alone driver that does not affect others devices - and platforms. + Low risk. This is a stand-alone driver that does not affect others + devices and platforms. ** Changed in: hwe-next Status: New => 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/1949245 Title: AMD ACP 6.x DMIC Supports Status in HWE Next: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) which will not work with existing ACP drivers. [Fix] Backport the new driver that is now in linux-next (to be in 5.16) [Test] This is requested by AMD. [Where problems could occur] Low risk. This is a stand-alone driver that does not affect others devices and platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949245/+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 1949245] Re: AMD ACP 6.x DMIC Supports
** Tags added: amd oem-priority originate-from-1943460 -- 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/1949245 Title: AMD ACP 6.x DMIC Supports Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) which will not work with existing ACP drivers. [Fix] Backport the new driver that is now in linux-next (to be in 5.16) [Test] This is requested by AMD. [Where problems could occur] Low risk. This is a stand-alone driver that does not affect others devices and platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949245/+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 1945348] Re: Yellow Carp S0i3 stability fix
** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu) Status: Fix Committed => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => 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/1945348 Title: Yellow Carp S0i3 stability fix Status in amd: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] Below errors are reported with S0i3 on Yellow carp where under stress testing with 5.14.0 through 5.14.8. [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 amdgpu :04:00.0: amdgpu: amdgpu_device_ip_resume failed (-110). PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110 amdgpu :04:00.0: PM: failed to resume async: error -110 [Fix] The patch fixes this by forcing exit gfxoff for sdma resume. The patch is in 5.15-rc4 (https://github.com/torvalds/linux/commit/26db706a6d77b9e184feb11725e97e53b7a89519) [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD platforms with s0ix supports. The changes repeat what is (should be) done in firmware. = original descriptions = A problem is identified with S0i3 on Yellow carp where under stress testing with 5.14.0 through 5.14.8 sometimes there will be failures. It will manifest as: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 amdgpu :04:00.0: amdgpu: amdgpu_device_ip_resume failed (-110). PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110 amdgpu :04:00.0: PM: failed to resume async: error -110 The fix for this will be going into 5.15-rcX and also to 5.14.y. Just want to give a pointer to Canonical team that if this comes up where to expect the fix for OEM kernel. The patch going into 5.15-rcX and 5.14.y is: https://lists.freedesktop.org/archives/amd-gfx/2021-September/069451.html To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1945348/+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 1949245] [NEW] AMD ACP 6.x DMIC Supports
Public bug reported: [Impact] AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) which will not work with existing ACP drivers. [Fix] Backport the new driver that is now in linux-next (to be in 5.16) [Test] This is requested by AMD. [Where problems could occur] Low risk. This is a stand-alone driver that does not affect others devices and platforms. ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Assignee: Alex Hung (alexhung) Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: amd Assignee: (unassigned) => Alex Hung (alexhung) ** Information type changed from Proprietary to Public ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** No longer affects: amd ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu) Assignee: (unassigned) => Alex Hung (alexhung) -- 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/1949245 Title: AMD ACP 6.x DMIC Supports Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) which will not work with existing ACP drivers. [Fix] Backport the new driver that is now in linux-next (to be in 5.16) [Test] This is requested by AMD. [Where problems could occur] Low risk. This is a stand-alone driver that does not affect others devices and platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1949245/+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 1945348] Re: Yellow Carp S0i3 stability fix
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => 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/1945348 Title: Yellow Carp S0i3 stability fix Status in amd: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Fix Committed Bug description: [Impact] Below errors are reported with S0i3 on Yellow carp where under stress testing with 5.14.0 through 5.14.8. [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 amdgpu :04:00.0: amdgpu: amdgpu_device_ip_resume failed (-110). PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110 amdgpu :04:00.0: PM: failed to resume async: error -110 [Fix] The patch fixes this by forcing exit gfxoff for sdma resume. The patch is in 5.15-rc4 (https://github.com/torvalds/linux/commit/26db706a6d77b9e184feb11725e97e53b7a89519) [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD platforms with s0ix supports. The changes repeat what is (should be) done in firmware. = original descriptions = A problem is identified with S0i3 on Yellow carp where under stress testing with 5.14.0 through 5.14.8 sometimes there will be failures. It will manifest as: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 amdgpu :04:00.0: amdgpu: amdgpu_device_ip_resume failed (-110). PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110 amdgpu :04:00.0: PM: failed to resume async: error -110 The fix for this will be going into 5.15-rcX and also to 5.14.y. Just want to give a pointer to Canonical team that if this comes up where to expect the fix for OEM kernel. The patch going into 5.15-rcX and 5.14.y is: https://lists.freedesktop.org/archives/amd-gfx/2021-September/069451.html To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1945348/+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 1945361] Re: [Yellow Carp] USB4 interdomain communication problems
** Changed in: amd Status: New => 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/1945361 Title: [Yellow Carp] USB4 interdomain communication problems Status in amd: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] Yellow carp w/ SW CM bi-directional interdomain communication may have some problems that the response packets are lost sometimes within the stipulated time. [Fix] Enable the retry by increasing retry count from 1 to 4. The patch is in linux-next (tag next-20211007) and can be found @ https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/thunderbolt/ctl.c?id=641cdbea7635be3a177dbdf81356ccb16f3769e3 [Test] This is requested and tested by AMD. [Where problems could occur] Low risk. This only affects small number of AMD systems that would excess the time. Systems without problems won't be affected. = Original Description AMD internal team has found that for Yellow carp w/ SW CM bi- directional interdomain communication may have some problems. It's been aligned upstream to increase number of retries to account for these issues. https://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git/commit/?h=next=641cdbea7635be3a177dbdf81356ccb16f3769e3 Can Canonical team please include this in future 5.14-OEM? To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1945361/+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 1941893] Re: Improve performance and idle power consumption
** Tags removed: verification-needed-focal ** 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/1941893 Title: Improve performance and idle power consumption Status in amd: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] This can improve AMD performance for all Zen or newer CPU which support C3 shares cache. [Fix] Its not necessary to flush the caches in software before entering C3. Empirical measurements show: 40-45% improvement in speedometer score. ~15% improvement in idle power. The patch is in linux-next (tag next-20211007) and can be found @ https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/arch/x86/kernel/acpi/cstate.c?id=a8fb40966f19ff81520d9ccf8f7e2b95201368b8 [Test] This is requested by AMD. [Where problems could occur] Low risk. This only works on AMD Zen CPUs that supports this features. AMD tested it and provided estimated measurement results. Original descriptions A patch queued for 5.15 to change the C3 entry will improve AMD performance. https://lore.kernel.org/patchwork/patch/1478776/ Empirical measurements show: 40-45% improvement in speedometer score. ~15% improvement in idle power. Can you please include in 5.13-oem and 5.14-oem kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1941893/+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 1945361] Re: [Yellow Carp] USB4 interdomain communication problems
** Tags removed: verification-needed-focal ** 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/1945361 Title: [Yellow Carp] USB4 interdomain communication problems Status in amd: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] Yellow carp w/ SW CM bi-directional interdomain communication may have some problems that the response packets are lost sometimes within the stipulated time. [Fix] Enable the retry by increasing retry count from 1 to 4. The patch is in linux-next (tag next-20211007) and can be found @ https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/thunderbolt/ctl.c?id=641cdbea7635be3a177dbdf81356ccb16f3769e3 [Test] This is requested and tested by AMD. [Where problems could occur] Low risk. This only affects small number of AMD systems that would excess the time. Systems without problems won't be affected. = Original Description AMD internal team has found that for Yellow carp w/ SW CM bi- directional interdomain communication may have some problems. It's been aligned upstream to increase number of retries to account for these issues. https://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git/commit/?h=next=641cdbea7635be3a177dbdf81356ccb16f3769e3 Can Canonical team please include this in future 5.14-OEM? To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1945361/+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 1917203] Re: AMD-Vi: Unable to read/write to IOMMU perf counter
** Changed in: linux (Ubuntu) Assignee: Alex Hung (alexhung) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917203 Title: AMD-Vi: Unable to read/write to IOMMU perf counter Status in linux package in Ubuntu: In Progress Bug description: This boot warning (concealed by grub not taking over the fbcon console on a solo installation but always present on a multi-boot) has been bothering Linux users of AMD Ryzen machines for some time. The problem is currently under discussion at kernel level <https://bugzilla.kernel.org/show_bug.cgi?id=201753>. One solution proposed by Suravee Suthikulpanit <https://lkml.org/lkml/2021/2/8/486> works but inserts a boot-up delay of (at least) 100 msec. A second option by Alexander Monakov <https://bugzilla.kernel.org/show_bug.cgi?id=201753> also works but inserts no delay and more-or-less just moves one line of code. I've tried both solutions with kernel rebuilds for both Breezy kernel 5.8.18 and Hirsute kernel 5.10.11 and both work on my AMD Ryzen 2400G. Could I encourage your kernel experts to evaluate the situation (I think SuSE folk already are). My suggestion (as a humble user :-) ) would be to fold Alex's simple patch into your own list of kernel tweeks and get the correction out with the upcoming Hirsute release. Best regards and all respect! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917203/+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 1943185] Re: Fix AMD GPIO-based power button
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1943185 Title: Fix AMD GPIO-based power button Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] Power button or other wake up sources connected to GPIO may not wake up idle AMD systems. [Fix] Enable and disable power management wakeup mode, which is disabled by default, accordingly. The patch series can be found @ https://lore.kernel.org/linux- gpio/20210831120613.1514899-1-basavaraj.nati...@amd.com/ [Test] This is requested by AMD. [Where problems could occur] Only AMD systems that require GPIOs as wake sources will be affected, i.e. amd_gpio_irq_set_wake with "on != 0", but this is intended behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1943185/+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 1912033] Re: Thinkpad - add palm sensor support needed for WWAN
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1912033 Title: Thinkpad - add palm sensor support needed for WWAN Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Bug description: [Impact] Add new palm sensor supports to Lenovo Thinkpad systems [Fix] thinkpad_acpi is updated to check palm sensor presence and its events [Test] Tested on Thinkpad systems [Where problems could occur] Low risks. Only thinkpad systems are affected. Also thinkpad systems without palm sensor and without TP_HKEY_EV_PALM_DETECTED & TP_HKEY_EV_PALM_UNDETECTED events won't be affected either. There can an issue as discussed in commit log of "thinkpad_acpi: Add palm sensor support" Note: On some platforms, because of an issue in the HW implementation, the palm sensor presence may be incorrectly advertised as always enabled even if a palm sensor is not present. The palm sensor is intended for WWAN transmission power control and should be available and correct on all WWAN enabled systems. It is not recommended to use this interface for other use cases. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1912033/+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 1943624] Re: Driver r8169 causes very slow download speed due to ASPM
It seems a SRU was sent to Ubuntu kernel and the status is available @ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946433 So it seems a fix will land in impish later. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943624 Title: Driver r8169 causes very slow download speed due to ASPM Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu Server 21.04 (kernel 5.11.0-34-generic) and have run into a serious network issue where the internet download speed is around 25Mbps on a 150Mbps connection! My setup: Lenovo Ideapad 300S with a wired Ethernet connection. Running Ubuntu Server 21.04 (kernel version 5.11.0-34-generic). Wired Ethernet connection with RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (r8169) driver. My contract with the ISP is for a 150Mbps download speed. My problem: The download speed is extremely low, around 25Mbps whereas my upload speed is 'normal' around 80-90Mbps. I use 'speedtest-cli' for measuring the bandwidth, by the way. This problem does not happen on an Acer Aspire One laptop running the same kernel and connected to the same router. After scouring through countless articles, I noticed that there were lot of issues with the r8169 driver and the RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller subsystem. What eventually fixed the issue for me was setting the "pcie_aspm=off" kernel parameter during boot. But I strongly feel that is a 'workaround' and not a solution to the real problem, which is the r8169 driver has regression with newer kernels, hence filing this bug. Thanks in advance for all your support! I'm a big fan of Ubuntu!!! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.11.0-34-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass Date: Tue Sep 14 12:17:49 2021 InstallationDate: Installed on 2021-09-05 (9 days ago) InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Release amd64 (20210421) MachineType: LENOVO 80Q4 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=b3938b06-c0f7-4342-b99c-94888f030a99 ro pcie_aspm=off RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2018 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: D3CN39WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 300S-14ISK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 300S-14ISK dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvrD3CN39WW:bd06/26/2018:br1.39:efr1.26:svnLENOVO:pn80Q4:pvrLenovoideapad300S-14ISK:skuLENOVO_MT_80Q4_BU_idea_FM_Lenovoideapad300S-14ISK:rvnLENOVO:rnLenovoideapad300S-14ISK:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad300S-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80Q4 dmi.product.sku: LENOVO_MT_80Q4_BU_idea_FM_Lenovo ideapad 300S-14ISK dmi.product.version: Lenovo ideapad 300S-14ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943624/+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 1944019] Re: Most of the computer's memory rendered unavailable in Linux after updating BIOS
Thanks for updating it was fixed by running BIOS diagnostic test. It likely forced BIOS to update the memory configuration which corrected memory maps reported to OS. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1944019 Title: Most of the computer's memory rendered unavailable in Linux after updating BIOS Status in linux package in Ubuntu: Invalid Bug description: I have got a HP HP ZBook Studio G5 laptop. After updating BIOS from "BIOS Q71 Ver. 01.15.00 12/28/2020" to version "BIOS Q71 Ver. 01.16.00 04/22/2021" most of the memory got unavailable in Linux. The system has 16 GiB of memory, but now free -h shows only total of 1.5 GiB. In Windows all memory seems available. No other indication of the problem in /proc/meminfo and /proc/iomem (will attach) is shown except that the total memory is 1.5 GiB. No large area is shown as reserved in /proc/iomem. But there is now an error message in dmesg that didn't use to be there: "kernel: efi: memattr: Failed to map EFI Memory Attributes table @ 0x72f69018". Also that EFI MEMATTR address seems to have changed after the BIOS update. I will also attach an earlier dmesg prior to update and a one after the update, since I updated the BIOS two weeks ago, and after that the kernel has also got updated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-84-generic 5.4.0-84.94 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jttoivon 2725 F pipewire-media- /dev/snd/controlC0: jttoivon 2725 F pipewire-media- /dev/snd/seq:jttoivon 2724 F pipewire CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Sep 18 08:53:18 2021 InstallationDate: Installed on 2020-01-23 (603 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP ZBook Studio G5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-84-generic root=UUID=c6b19f0f-68ff-4d8c-985a-c3ed88345389 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-84-generic N/A linux-backports-modules-5.4.0-84-generic N/A linux-firmware1.187.16 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.16.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.4C.00 dmi.chassis.asset.tag: 5CD9495R4G dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.16.00:bd04/22/2021:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.4C.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2ZC51EA#AK8 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944019/+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 1944511] Re: Touchpad is not present
** Summary changed: - Touch-pad is not present + Touchpad is not present -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1944511 Title: Touchpad is not present Status in linux package in Ubuntu: Confirmed Bug description: Touch-pad is not working on Ubuntu 20.04.3LTS, ThinkPad Lenovo, AMD® Pro a6-9500b r5 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-86-generic 5.4.0-86.97 ProcVersionSignature: Ubuntu 5.4.0-86.97-generic 5.4.133 Uname: Linux 5.4.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kostia 1542 F pulseaudio /dev/snd/pcmC1D0p: kostia 1542 F...m pulseaudio /dev/snd/controlC0: kostia 1542 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 23:09:36 2021 InstallationDate: Installed on 2019-02-17 (948 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20H8000HUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-86-generic root=/dev/mapper/User Name--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-86-generic N/A linux-backports-modules-5.4.0-86-generic N/A linux-firmware1.187.16 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-10-02 (354 days ago) dmi.bios.date: 09/22/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R0EET34W (1.08 ) dmi.board.asset.tag: Not Available dmi.board.name: 20H8000HUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0EET34W(1.08):bd09/22/2016:svnLENOVO:pn20H8000HUS:pvrThinkPadE575:rvnLENOVO:rn20H8000HUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E575 dmi.product.name: 20H8000HUS dmi.product.sku: LENOVO_MT_20H8_BU_Think_FM_ThinkPad E575 dmi.product.version: ThinkPad E575 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944511/+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 1946576] Re: my Network adapter stopped working suddenly
You can unload and reload the driver by the following commands, where r8169 is the name of ethernet device: sudo modprobe -r r8169 && sudo modprobe r8169 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946576 Title: my Network adapter stopped working suddenly Status in linux package in Ubuntu: Confirmed Bug description: My network adapter stop suddenly in the middle of a browsing session, i need solution to bring it back on ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-88-generic 5.4.0-88.99 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lakecombs 1803 F pulseaudio /dev/snd/pcmC1D0p: lakecombs 1803 F...m pulseaudio /dev/snd/controlC0: lakecombs 1803 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 9 22:15:08 2021 InstallationDate: Installed on 2021-08-19 (51 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP Pavilion TS 15 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=ac9719d9-9c90-40df-bbaf-71276af1d13e ro quiet splash i8042.nomux i8024.noloop vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-08-25 (45 days ago) dmi.bios.date: 03/20/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.63 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2163 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.42 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.63:bd03/20/2014:svnHewlett-Packard:pnHPPavilionTS15NotebookPC:pvr098411001440410620182:rvnHewlett-Packard:rn2163:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion TS 15 Notebook PC dmi.product.sku: F5W51UAR#ABA dmi.product.version: 098411001440410620182 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946576/+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 1929889] Re: [TGL][ADL] Enable CET(Control-flow Enforcement Technology)
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929889 Title: [TGL][ADL] Enable CET(Control-flow Enforcement Technology) Status in intel: New Status in linux-intel package in Ubuntu: Triaged Status in linux-intel source package in Focal: New Bug description: Description Enable Tiger Lake ROP CET(Control-flow Enforcement Technology) An upcoming Intel® processor family feature that counters return/jump-oriented programming (ROP) attacks Hardware: Tiger Lake & Alder Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929889/+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 1945462] Re: EHL graphics support for sprint 2
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945462 Title: EHL graphics support for sprint 2 Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Tracking bug, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945462/+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 1944382] Re: Enable runtime power management for yellow carp XHCI
** Changed in: amd Status: New => 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/1944382 Title: Enable runtime power management for yellow carp XHCI Status in amd: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: Alex Hung 7:01 PM (1 minute ago) to kernel-team BugLink: https://bugs.launchpad.net/bugs/1944382 [Impact] XHCI controllers of yellow carp by default will not use runtime PM [Fix] Add PCI Device IDs to enable runtime PM The patch can be found @ https://patchwork.kernel.org/project/linux- usb/patch/20210920154100.3195683-1-nehal-bakulchandra.s...@amd.com/ [Test] This is requested and tested by AMD as described in LP:1944382 [Where problems could occur] Low risk. This only affects devices of AMD's Yellow Carp. == original descriptions == Like all XHCI controllers yellow carp XHCI by default will not use runtime PM and needs to be added to an allow list. AMD has validated that XHCI runtime PM is safe. Please include https://lore.kernel.org/linux- usb/20210920154100.3195683-1-nehal-bakulchandra.s...@amd.com/T/#u in OEM-5.14 kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1944382/+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 1929889] Re: [TGL] Enable Tiger Lake ROP CET(Control-flow Enforcement Technology)
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929889 Title: [TGL] Enable Tiger Lake ROP CET(Control-flow Enforcement Technology) Status in intel: New Status in linux-intel package in Ubuntu: Triaged Bug description: Description Enable Tiger Lake ROP CET(Control-flow Enforcement Technology) An upcoming Intel® processor family feature that counters return/jump-oriented programming (ROP) attacks Hardware: Tiger Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929889/+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 1942952] Re: Kernel Call Trace on Secure Boot
The slow CPU (N5000 CPU @ 1.10GHz) may play a role in the watchdog soft lockup. You can increase the watchdog time and check whether the messages will go away and pop up less frequently: $ echo 20 | sudo tee /proc/sys/kernel/watchdog_thresh The above command will change the default (10) to 20 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942952 Title: Kernel Call Trace on Secure Boot Status in linux package in Ubuntu: Incomplete Bug description: Could the call traces in dmesg be related to UEFI secure boot? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js1 948 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Sep 7 21:05:54 2021 InstallationDate: Installed on 2021-09-06 (1 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 480M |__ Port 8: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-34-generic root=/dev/mapper/vgkubuntu-root ro ipv6.disable=1 elevator=deadline splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 15.63 dmi.bios.vendor: Insyde dmi.bios.version: F.63 dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 76.32 dmi.modalias: dmi:bvnInsyde:bvrF.63:bd03/25/2021:br15.63:efr76.32:svnHP:pn:pvr:sku:rvnHP:rn84B6:rvrKBCVersion76.32:cvnHP:ct10:cvrChassisVersion: dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942952/+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 1943185] Re: Fix AMD GPIO-based power button
** Description changed: [Impact] - Power button or other wake up sources connected to GPIO may not wake up + Power button or other wake up sources connected to GPIO may not wake up idle AMD systems. [Fix] - Enable and disable power management wakeup mode, which is disabled by - default, accordingly + Enable and disable power management wakeup mode, which is disabled by + default, accordingly. + + The patch series can be found @ https://lore.kernel.org/linux- + gpio/20210831120613.1514899-1-basavaraj.nati...@amd.com/ [Test] - This is requested by AMD. + This is requested by AMD. [Where problems could occur] - Only AMD systems that require GPIOs as wake sources will be affected, + Only AMD systems that require GPIOs as wake sources will be affected, i.e. amd_gpio_irq_set_wake with "on != 0", but this is intended - behaviours. + behaviour. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943185 Title: Fix AMD GPIO-based power button Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Power button or other wake up sources connected to GPIO may not wake up idle AMD systems. [Fix] Enable and disable power management wakeup mode, which is disabled by default, accordingly. The patch series can be found @ https://lore.kernel.org/linux- gpio/20210831120613.1514899-1-basavaraj.nati...@amd.com/ [Test] This is requested by AMD. [Where problems could occur] Only AMD systems that require GPIOs as wake sources will be affected, i.e. amd_gpio_irq_set_wake with "on != 0", but this is intended behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1943185/+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 1943185] Re: Fix AMD GPIO-based power button
** Tags added: amd oem-priority originate-from-1942219 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943185 Title: Fix AMD GPIO-based power button Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Power button or other wake up sources connected to GPIO may not wake up idle AMD systems. [Fix] Enable and disable power management wakeup mode, which is disabled by default, accordingly. The patch series can be found @ https://lore.kernel.org/linux- gpio/20210831120613.1514899-1-basavaraj.nati...@amd.com/ [Test] This is requested by AMD. [Where problems could occur] Only AMD systems that require GPIOs as wake sources will be affected, i.e. amd_gpio_irq_set_wake with "on != 0", but this is intended behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1943185/+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 1943185] [NEW] Fix AMD GPIO-based power button
Public bug reported: [Impact] Power button or other wake up sources connected to GPIO may not wake up idle AMD systems. [Fix] Enable and disable power management wakeup mode, which is disabled by default, accordingly [Test] This is requested by AMD. [Where problems could occur] Only AMD systems that require GPIOs as wake sources will be affected, i.e. amd_gpio_irq_set_wake with "on != 0", but this is intended behaviours. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Alex Hung (alexhung) Status: Incomplete ** Tags: amd oem-priority originate-from-1942219 ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Alex Hung (alexhung) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943185 Title: Fix AMD GPIO-based power button Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Power button or other wake up sources connected to GPIO may not wake up idle AMD systems. [Fix] Enable and disable power management wakeup mode, which is disabled by default, accordingly [Test] This is requested by AMD. [Where problems could occur] Only AMD systems that require GPIOs as wake sources will be affected, i.e. amd_gpio_irq_set_wake with "on != 0", but this is intended behaviours. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1943185/+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 1936295] Re: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate
It seems the maintainer has concerns on the patch, and there is no reply from the developer at the moment: https://patchwork.kernel.org/project/linux- input/patch/20210729010940.5752-1-phoe...@emc.com.tw/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936295 Title: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate the FW bug Status in linux package in Ubuntu: Confirmed Bug description: *Problem description:* On Lenovo Thinkpad T14s, X13, A475 (and probably more models) the Elantech Trackpoint firmware is defective. The trackpoint cursor often suddenly jumps to an edge/corner, because the hardware/firmware sometimes reports wrong coordinates / loses sync. Currently, the Trackpoint is barely usable and it's impossible to productively work using it. For a long while, Elantech has not yet put forward (nor confirmed) a firmware update. However, there is a Linux kernel patch mitigating the firmware bug. The kernel bugfix discards the wrongly reported packages by the Elantech hardware. This solves the problem for the user. *Solution:* Please apply existing kernel patch here. https://bugzilla.kernel.org/show_bug.cgi?id=209167 Bug entry in the Linux Kernel.org Bugzilla https://bugzilla.kernel.org/attachment.cgi?id=295733=diff Diff of bugfix *T14s and X13 are Ubuntu certified:* The Lenovo Thinkpad T14s and X13 are Ubuntu certified, but apparently this hardware issue has slipped the Ubuntu certification process! https://ubuntu.com/certified/202006-27978 and https://ubuntu.com/certified/202006-27979 *Further information:* https://forums.lenovo.com/t5/Fedora/T14s-AMD-Trackpoint-almost-unusable/m-p/5064952?page=1 Discussion on the bug in the Lenovo forum. E.g. see comment 18 by Lenovo employee MarkRHPearson *My System:* Lenovo Thinkpad T14s (AMD) 20ujs00k00 Ubuntu 21.04 and 20.04 see entries in kernel.org bugzilla for logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936295/+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 1939543] Re: Power button no longer has any action after applying updates
Please also run "acpi_listen" and "sudo showkey" to check whether power button events are generated by system BIOS and linux kernel correctly. ** Attachment added: "Screenshot-20210830150034.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939543/+attachment/5521717/+files/Screenshot-20210830150034.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939543 Title: Power button no longer has any action after applying updates Status in linux package in Ubuntu: Confirmed Bug description: When using the live iso image or first install, the power button will either prompt to shut down or sleep depending how the user has it configured in the power settings. however after applying updates the power button no longer does anything. Pressing and holding for 10 seconds will perform the hardware power off (as expected). Software wise, nothing happens. I have had this on 3 pc's now and also on your previous version of Ubuntu Budgie so this is not a new issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diddy 1273 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Wed Aug 11 11:27:26 2021 InstallationDate: Installed on 2021-08-09 (1 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5830 Realtek Semiconductor Corp. USB Camera Bus 001 Device 002: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Jumper EZbook ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=6dcedb6d-17fc-4ddc-a907-27b3074282b2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Jumper10x.WP111J.fLHAUGX01.2012039 dmi.board.asset.tag: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 10.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.WP111J.fLHAUGX01.2012039:bd12/29/2020:br5.12:efr10.2:svnJumper:pnEZbook:pvrDefaultstring:rvn:rn:rvrDefaultstring:cvnDefaultstring:ct31:cvrDefaultstring: dmi.product.name: EZbook dmi.product.version: Default string dmi.sys.vendor: Jumper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939543/+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 1939543] Re: Power button no longer has any action after applying updates
Please check whether action for power button is modified. ** Attachment added: "Screenshot-20210830145942.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939543/+attachment/5521716/+files/Screenshot-20210830145942.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939543 Title: Power button no longer has any action after applying updates Status in linux package in Ubuntu: Confirmed Bug description: When using the live iso image or first install, the power button will either prompt to shut down or sleep depending how the user has it configured in the power settings. however after applying updates the power button no longer does anything. Pressing and holding for 10 seconds will perform the hardware power off (as expected). Software wise, nothing happens. I have had this on 3 pc's now and also on your previous version of Ubuntu Budgie so this is not a new issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diddy 1273 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Wed Aug 11 11:27:26 2021 InstallationDate: Installed on 2021-08-09 (1 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5830 Realtek Semiconductor Corp. USB Camera Bus 001 Device 002: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Jumper EZbook ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=6dcedb6d-17fc-4ddc-a907-27b3074282b2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Jumper10x.WP111J.fLHAUGX01.2012039 dmi.board.asset.tag: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 10.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.WP111J.fLHAUGX01.2012039:bd12/29/2020:br5.12:efr10.2:svnJumper:pnEZbook:pvrDefaultstring:rvn:rn:rvrDefaultstring:cvnDefaultstring:ct31:cvrDefaultstring: dmi.product.name: EZbook dmi.product.version: Default string dmi.sys.vendor: Jumper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939543/+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 1941808] Re: AMD desktop fails to suspend
In this case, you can disable USB wakeup if you don't need USB wakeup. A quick search finds an tutorial: http://www.das- werkstatt.com/forum/werkstatt/viewtopic.php?f=7=1985 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941808 Title: AMD desktop fails to suspend Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 5.11.0-31-generic from 5.11.0-25-generic my system is no longer able to enter deep sleep when I choose "Suspend" from the Gnome power menu. The display goes blank for about 3 seconds and then comes back to the login screen. Machine setup: Desktop PC Ubuntu 21.04 Linux version 5.11.0-17-generic AMD Ryzen 3900X Asus X590 PRIME PRO motherboard NVIDIA P400 GPU The following appears in dmesg: [ 193.035190] PM: suspend entry (deep) [ 193.043644] Filesystems sync: 0.008 seconds [ 193.221385] rfkill: input handler enabled [ 193.223342] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 193.225169] OOM killer disabled. [ 193.225170] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 193.226377] printk: Suspending console(s) (use no_console_suspend to debug) [ 193.227086] serial 00:04: disabled [ 193.236938] PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 [ 193.236948] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16 [ 193.236955] PM: Device :0b:00.3 failed to suspend async: error -16 [ 193.433850] PM: Some devices failed to suspend, or early wake event detected [ 193.434781] serial 00:04: activated [ 193.439638] nvme nvme1: Shutdown timeout set to 8 seconds [ 193.441267] nvme nvme0: 32/0/0 default/read/poll queues [ 193.467431] nvme nvme1: 32/0/0 default/read/poll queues [ 193.729944] usb 5-2.3: reset high-speed USB device number 3 using xhci_hcd [ 193.746614] ata1: SATA link down (SStatus 0 SControl 300) [ 193.746619] ata2: SATA link down (SStatus 0 SControl 300) [ 193.864008] OOM killer enabled. [ 193.864009] Restarting tasks ... done. [ 193.865012] PM: suspend exit [ 193.865069] PM: suspend entry (s2idle) [ 193.869519] Filesystems sync: 0.004 seconds [ 193.907792] Freezing user space processes ... (elapsed 0.007 seconds) done. [ 193.915352] OOM killer disabled. [ 193.915353] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 193.916464] printk: Suspending console(s) (use no_console_suspend to debug) [ 193.917046] serial 00:04: disabled [ 193.925345] PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 [ 193.925355] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16 [ 193.925362] PM: Device :0b:00.3 failed to suspend async: error -16 [ 194.118212] PM: Some devices failed to suspend, or early wake event detected [ 194.119120] serial 00:04: activated [ 194.123827] nvme nvme1: Shutdown timeout set to 8 seconds [ 194.126322] nvme nvme0: 32/0/0 default/read/poll queues [ 194.150499] nvme nvme1: 32/0/0 default/read/poll queues [ 194.413459] usb 5-2.3: reset high-speed USB device number 3 using xhci_hcd [ 194.434238] ata2: SATA link down (SStatus 0 SControl 300) [ 194.434256] ata1: SATA link down (SStatus 0 SControl 300) [ 194.547373] OOM killer enabled. [ 194.547374] Restarting tasks ... done. [ 194.548195] PM: suspend exit [ 194.694550] rfkill: input handler disabled I see pci device mentioned is: 0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-31-generic 5.11.0-31.33 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacob 2034 F pulseaudio /dev/snd/controlC0: jacob 2034 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 16:57:09 2021 InstallationDate: Installed on 2020-10-28 (302 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp5s0no wireless extensions. docker0 no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=f721d5df-ceec-434a-919a-0680ee380996 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware
[Kernel-packages] [Bug 1936295] Re: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate
Linux kernel 5.14 was released and 5.15 merge window should be open soon followed by rc1. If we don't see the patch lands in mainline we can consider alternatives such as submit the SRU as a sauce patch instead. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936295 Title: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate the FW bug Status in linux package in Ubuntu: Confirmed Bug description: *Problem description:* On Lenovo Thinkpad T14s, X13, A475 (and probably more models) the Elantech Trackpoint firmware is defective. The trackpoint cursor often suddenly jumps to an edge/corner, because the hardware/firmware sometimes reports wrong coordinates / loses sync. Currently, the Trackpoint is barely usable and it's impossible to productively work using it. For a long while, Elantech has not yet put forward (nor confirmed) a firmware update. However, there is a Linux kernel patch mitigating the firmware bug. The kernel bugfix discards the wrongly reported packages by the Elantech hardware. This solves the problem for the user. *Solution:* Please apply existing kernel patch here. https://bugzilla.kernel.org/show_bug.cgi?id=209167 Bug entry in the Linux Kernel.org Bugzilla https://bugzilla.kernel.org/attachment.cgi?id=295733=diff Diff of bugfix *T14s and X13 are Ubuntu certified:* The Lenovo Thinkpad T14s and X13 are Ubuntu certified, but apparently this hardware issue has slipped the Ubuntu certification process! https://ubuntu.com/certified/202006-27978 and https://ubuntu.com/certified/202006-27979 *Further information:* https://forums.lenovo.com/t5/Fedora/T14s-AMD-Trackpoint-almost-unusable/m-p/5064952?page=1 Discussion on the bug in the Lenovo forum. E.g. see comment 18 by Lenovo employee MarkRHPearson *My System:* Lenovo Thinkpad T14s (AMD) 20ujs00k00 Ubuntu 21.04 and 20.04 see entries in kernel.org bugzilla for logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936295/+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 1941010] Re: add AMD DID for s2idle
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Alex Hung (alexhung) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941010 Title: add AMD DID for s2idle Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] An DID AMDI007 is added to support s2idle. [Fix] Below commit adds the ID. https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=f0c6225531e4a9e43e51c5f7b02089bdd725c734 [Test] We didn't receive h/w yet, and this is requested by AMD. [Where problems could occur] The changes are specific to the new ID and will not impact original behaviors. Mario Limonciello (1): ACPI: PM: Add support for upcoming AMD uPEP HID AMDI007 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1941010/+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 1941660] [NEW] Fix incorrect keyboard backlight behaviours
Public bug reported: [Impact] The keyboard backlight was turning on when entering suspend and turning off when exiting (the opposite of how it should be). [Fix] Swaps the on / off commands. The fix commit is in 5.14-rc7. [Test] This is requested by AMD. [Where problems could occur] This fixes the incorrect LED on/off behaviours in 5dbf50997578, and the risk is very slow. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Alex Hung (alexhung) Status: Incomplete ** Tags: amd oem-priority originate-from-1939606 ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Alex Hung (alexhung) ** Tags added: amd oem-priority originate-from-1939606 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941660 Title: Fix incorrect keyboard backlight behaviours Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The keyboard backlight was turning on when entering suspend and turning off when exiting (the opposite of how it should be). [Fix] Swaps the on / off commands. The fix commit is in 5.14-rc7. [Test] This is requested by AMD. [Where problems could occur] This fixes the incorrect LED on/off behaviours in 5dbf50997578, and the risk is very slow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1941660/+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 1941010] [NEW] add AMD DID for s2idle
Public bug reported: [Impact] An DID AMDI007 is added to support s2idle. [Fix] Below commit adds the ID. https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=f0c6225531e4a9e43e51c5f7b02089bdd725c734 [Test] We didn't receive h/w yet, and this is requested by AMD. [Where problems could occur] The changes are specific to the new ID and will not impact original behaviors. Mario Limonciello (1): ACPI: PM: Add support for upcoming AMD uPEP HID AMDI007 ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-1938052 ** Tags added: amd oem-priority originate-from-1938052 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941010 Title: add AMD DID for s2idle Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Impact] An DID AMDI007 is added to support s2idle. [Fix] Below commit adds the ID. https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=f0c6225531e4a9e43e51c5f7b02089bdd725c734 [Test] We didn't receive h/w yet, and this is requested by AMD. [Where problems could occur] The changes are specific to the new ID and will not impact original behaviors. Mario Limonciello (1): ACPI: PM: Add support for upcoming AMD uPEP HID AMDI007 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1941010/+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 1934014] Re: [SRU] Update amdgpu/renoir firmware
** Tags added: amd oem-priority -- 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/1934014 Title: [SRU] Update amdgpu/renoir firmware Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Bug description: [Impact] Renoir based systems can't resume from s2idle. [Fix] Update firmware for renoir into 21.10 or 21.20 release in linux-firmware.git Accompanying kernel driver updates are distributed with linux-oem-5.10. [Test] Verify s2idle on OEM system. [Where problems could occur] The firmware update is specific to Renoir systems, which are relative new so the impact is limited. We also have direct involvement with AMD, in case any regression happens. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1934014/+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 1940778] Re: Touchpad does not work on Linux Ubuntu 20.04 LTS, but it does work on Windows 10
You may want to try HWE kernel which supports newer hardware sudo apt install linux-generic-hwe-20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940778 Title: Touchpad does not work on Linux Ubuntu 20.04 LTS, but it does work on Windows 10 Status in linux package in Ubuntu: Confirmed Bug description: Lenovo Legion Y540-15IRH, model name 81SX, MTM: 81SX00A3RK. Touchpad works on Windows 10, but does not work on Linux Ubuntu Budgie 20.04.2 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: raylend1659 F pulseaudio /dev/snd/controlC0: raylend1659 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Sun Aug 22 20:41:40 2021 InstallationDate: Installed on 2020-05-17 (462 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81SX ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=4f63cec8-75a6-45ed-b628-e808c54fe158 ro quiet splash acpi_osi= vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN41WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-15IRH dmi.modalias: dmi:bvnLENOVO:bvrBHCN41WW:bd11/30/2020:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionY540-15IRH: dmi.product.family: Legion Y540-15IRH dmi.product.name: 81SX dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH dmi.product.version: Legion Y540-15IRH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940778/+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 1940876] Re: System freezes after logging-in for an hour
** Summary changed: - bug + System freezes after logging-in for an hour -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940876 Title: System freezes after logging-in for an hour Status in linux package in Ubuntu: Incomplete Bug description: when i log in after an hour it freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940876/+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 1935846] Re: Sony Dualshock 4 usb dongle crashes the whole system
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935846 Title: Sony Dualshock 4 usb dongle crashes the whole system Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Won't Fix Bug description: [Impact] Sony Dualshock 4 controller crashes systems. This is the result of a divide by zero when the driver processes requests from Steam and returns invalid data. More details are in the patch description. [Fix] Check whether data is valid and retry up to 3 times if needed. [Test Case] Tested by the bug reporter of LP:1935846. No more crashes after applying this patch. [Where problems could occur] None. The patch checks whether data is valid and retry 3 times before return -EILSEQ if it still fails. == Original descriptions == The hid-sony driver has custom DS4 connect/disconnect logic for the DS4 dongle, which is a USB dongle acting as a proxy to Bluetooth connected DS4. The connect/disconnect logic works fine generally, however not in conjunction with Steam. Steam implements its own DS4 driver using hidraw. Both hid-sony and Steam are issuing their own HID requests and are racing each other during DS4 dongle connect/disconnect resulting in a kernel crash in hid-sony. The problem is that upon a DS4 connect to the dongle, hid-sony kicks of 'ds4_get_calibration_data' from within its dongle hotplug code. The calibration code issues raw HID feature report for reportID 0x02. When Steam is running, it issues a feature report for reportID 0x12 typically just prior to hid-sony requesting feature reportID 0x02. The result is that 'ds4_get_calibration_data' receives the data Steam requested as that's the HID report returing first. Currently this results in it processing invalid data, which ultimately results in a divide by zero upon a future 'dualshock4_parse_report'. The solution for now is to check within 'ds4_get_calibration_data' to check if we received data for the feature report we issued and if not retry. Please consider to add this patch to Ubuntu LTS kernels. Commit: https://github.com/torvalds/linux/commit/f5dc93b7875bcb8be77baa792cc9432aaf65365b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935846/+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 1937978] Re: New device IDs for Intel ADL-M
The following new ID commit is an good addition introduced in v5.14-rc4 to be included in linux-oem-5.13 commit a59c7b6c6ff6d5437f293709e766f939d7107266 Author: Ping Bao Date: Wed Jul 21 15:56:15 2021 -0700 platform/x86: intel-hid: add Alder Lake ACPI device ID Alder Lake has a new ACPI ID for Intel HID event filter device. Signed-off-by: Ping Bao Link: https://lore.kernel.org/r/20210721225615.20575-1-ping.a@intel.com Signed-off-by: Hans de Goede -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937978 Title: New device IDs for Intel ADL-M Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937978/+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 1939045] Re: Extend ANDROID_BINDER_DEVICES
You may want to send emails to Ubuntu kernel team (see https://lists.ubuntu.com/mailman/listinfo/kernel-team) for discussions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939045 Title: Extend ANDROID_BINDER_DEVICES Status in linux package in Ubuntu: New Bug description: Would it be possible to extend ANDROID_BINDER_DEVICES to 'binder,hwbinder,vndbinder,anbox-binder,anbox-hwbinder,anbox- vndbinder' for Waydroid (a new alternative to Anbox) to work OOTB on Ubuntu without having to recompile the kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939045/+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 1939046] Re: Enable CONFIG_SW_SYNC_USER
You may want to send emails to Ubuntu kernel team (see https://lists.ubuntu.com/mailman/listinfo/kernel-team) for discussions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939046 Title: Enable CONFIG_SW_SYNC_USER Status in linux package in Ubuntu: New Bug description: Would it be possible to enable SYNC_USER for Waydroid (a new alternative to Anbox) to work OOTB on Ubuntu without having to recompile the kernel? Related to #1939045. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939046/+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 1939052] Re: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2
Hi Cameron, Thanks for sharing your work. For patches to be merged into Ubuntu kernel, patches need to be backport by sending SRU to ubuntu kernel team: kernel-team at lists.ubuntu.com with specific format. This allows reviews from broader audiences. An example will be like https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938689 Cover letter: https://lists.ubuntu.com/archives/kernel-team/2021-August/122890.html Patch: https://lists.ubuntu.com/archives/kernel-team/2021-August/122891.html Note: subject's "UBUNTU: SAUCE:" is needed for patches aren't in mainline kernel, and bug link should be included in both cover letter and patch description. Details can be found @ https://wiki.ubuntu.com/StableReleaseUpdates#Procedure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939052 Title: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2 Status in linux package in Ubuntu: New Bug description: All 3 models need the appropriate HDA verbs sent to properly initialize the sound hardware. Additionally, the Legion 15IMHG05 needs automute disabled otherwise speaker output will not return after removing headphones. The good news is that I have working patches for all 3. However, the 13s Gen2 reportedly has some weirdness on the volume control. I don't have this model of laptop so there's not a lot I can do. It seems tuning the volume up and down using the keys on the keyboard can jump the volume up and down in large increments. Volume adjustments via a GUI do not have this issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hiryu 7243 F pulseaudio /dev/snd/controlC0: hiryu 7243 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 5 10:17:57 2021 InstallationDate: Installed on 2021-04-23 (104 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82K6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 bluetooth.disable_ertm acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2021 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: H1CN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ITHg6 dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrH1CN33WW:bd07/18/2021:br1.33:efr1.33:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6: dmi.product.family: Legion 7 16ITHg6 dmi.product.name: 82K6 dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6 dmi.product.version: Legion 7 16ITHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939052/+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 1938693] Re: Flameshot doesn't work anymore after linux upgrade to 21.04
falmeshot's wayland supports may not be ready yet. A bug was reported on flameshot's github: https://github.com/flameshot- org/flameshot/issues/675 ** Bug watch added: github.com/flameshot-org/flameshot/issues #675 https://github.com/flameshot-org/flameshot/issues/675 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938693 Title: Flameshot doesn't work anymore after linux upgrade to 21.04 Status in linux package in Ubuntu: New Bug description: After the linux upgrade to 21.04, the package flameshot is not working anymore. I click to take a screenshot but nothing happens. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kaio 1676 F pulseaudio /dev/snd/controlC1: kaio 1676 F pulseaudio CasperMD5CheckResult: unknown Date: Mon Aug 2 08:59:19 2021 InstallationDate: Installed on 2020-12-13 (231 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Acer Aspire VX5-591G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=e4a2a124-2896-4512-af5d-204bf0f6096b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-07-31 (1 days ago) dmi.bios.date: 07/07/2017 dmi.bios.release: 1.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Wish_KLS dmi.board.vendor: KBL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:br1.6:efr1.3:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire VX 15 dmi.product.name: Aspire VX5-591G dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938693/+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 1936678] Re: Samsung Laptop support module doesn't load
** Changed in: linux (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936678 Title: Samsung Laptop support module doesn't load Status in linux package in Ubuntu: Won't Fix Bug description: This is identical to bug # 1170885, which was filed 2013-04-20. The last comment on that bug was by Kai-Heng Feng (kaihengfeng), who requested a new bug report. This is a Samsung laptop NP730QCJ. $ sudo modprobe samsung-laptop modprobe: ERROR: could not insert 'samsung_laptop': No such device About my system: $ sudo dmidecode | grep -A 2 -i 'base board' Base Board Information Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: NP730QCJ-K01US $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS" $ cat /proc/version_signature Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 $ file /sys/firmware/efi/ /sys/firmware/efi/: directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936678/+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 1936295] Re: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate
Thanks for reporting this. The patch does not yet land in mainline kernel (5.14rc3), and the patch was submitted for review on July 29 (https://patchwork.kernel.org/project/linux- input/patch/20210729010940.5752-1-phoe...@emc.com.tw/) Once the patch lands in mainline it can be backport to Ubuntu kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936295 Title: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate the FW bug Status in linux package in Ubuntu: Confirmed Bug description: *Problem description:* On Lenovo Thinkpad T14s, X13, A475 (and probably more models) the Elantech Trackpoint firmware is defective. The trackpoint cursor often suddenly jumps to an edge/corner, because the hardware/firmware sometimes reports wrong coordinates / loses sync. Currently, the Trackpoint is barely usable and it's impossible to productively work using it. For a long while, Elantech has not yet put forward (nor confirmed) a firmware update. However, there is a Linux kernel patch mitigating the firmware bug. The kernel bugfix discards the wrongly reported packages by the Elantech hardware. This solves the problem for the user. *Solution:* Please apply existing kernel patch here. https://bugzilla.kernel.org/show_bug.cgi?id=209167 Bug entry in the Linux Kernel.org Bugzilla https://bugzilla.kernel.org/attachment.cgi?id=295733=diff Diff of bugfix *T14s and X13 are Ubuntu certified:* The Lenovo Thinkpad T14s and X13 are Ubuntu certified, but apparently this hardware issue has slipped the Ubuntu certification process! https://ubuntu.com/certified/202006-27978 and https://ubuntu.com/certified/202006-27979 *Further information:* https://forums.lenovo.com/t5/Fedora/T14s-AMD-Trackpoint-almost-unusable/m-p/5064952?page=1 Discussion on the bug in the Lenovo forum. E.g. see comment 18 by Lenovo employee MarkRHPearson *My System:* Lenovo Thinkpad T14s (AMD) 20ujs00k00 Ubuntu 21.04 and 20.04 see entries in kernel.org bugzilla for logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936295/+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