[Kernel-packages] [Bug 2081874] [NEW] NVIDIA: SAUCE: acpi/prmt: find block with specific type
Public bug reported:
[Description]
PRMT needs to find the correct type of block to
translate the PA-VA mapping for EFI runtime services.
The issue arises because the PRMT is finding a block of type
EFI_CONVENTIONAL_MEMORY, which is not appropriate for runtime services
as described in Section 2.2.2 (Runtime Services) of the UEFI
Specification [1]. Since the PRM handler is a type of runtime service,
this causes an exception when the PRM handler is called.
[Firmware Bug]: Unable to handle paging request in EFI runtime service
WARNING: CPU: 22 PID: 4330 at drivers/firmware/efi/runtime-wrappers.c:341
__efi_queue_work+0x11c/0x170
Call trace:
__efi_queue_work+0x11c/0x170
efi_call_acpi_prm_handler+0x68/0xd0
acpi_platformrt_space_handler+0x198/0x258
acpi_ev_address_space_dispatch+0x144/0x388
acpi_ex_access_region+0x9c/0x118
acpi_ex_write_serial_bus+0xc4/0x218
acpi_ex_write_data_to_field+0x168/0x218
acpi_ex_store_object_to_node+0x1a8/0x258
acpi_ex_store+0xec/0x330
acpi_ex_opcode_1A_1T_1R+0x15c/0x618
acpi_ds_exec_end_op+0x274/0x548
acpi_ps_parse_loop+0x10c/0x6b8
acpi_ps_parse_aml+0x140/0x3b0
acpi_ps_execute_method+0x12c/0x2a0
acpi_ns_evaluate+0x210/0x310
acpi_evaluate_object+0x178/0x358
acpi_proc_write+0x1a8/0x8a0 [acpi_call]
proc_reg_write+0xcc/0x150
vfs_write+0xd8/0x380
ksys_write+0x70/0x120
__arm64_sys_write+0x24/0x48
invoke_syscall.constprop.0+0x80/0xf8
do_el0_svc+0x50/0x110
el0_svc+0x48/0x1d0
el0t_64_sync_handler+0x15c/0x178
el0t_64_sync+0x1a8/0x1b0
Find a block with specific type to fix this.
prmt find a block with EFI_RUNTIME_SERVICES_DATA for prm handler and find a
block with EFI_RUNTIME_SERVICES_CODE for prm context. If no suitable block is
found, a warning message will be prompted but the procedue continues to manage
the next prm handler. However, if the prm handler is actullay called without
proper allocation, it would result in a failure during error handling.
By using the correct memory types for runtime services, Ensure that the PRM
handler and the context are
properly mapped in the virtual address space during runtime, preventing the
paging request error.
[1]
https://uefi.org/sites/default/files/resources/UEFI_Spec_2_10_Aug29.pdf
Fixes: cefc7ca ("ACPI: PRM: implement OperationRegion handler for the
PlatformRtMechanism subtype")
[backported from
https://patchwork.kernel.org/project/linux-acpi/patch/20240911155536.3900579-1-ko...@nvidia.com/]
Reviewed-by: Matthew R. Ochs mo...@nvidia.com
Tested-by: Andrew Adriance aadria...@nvidia.com
[Test Plan]
1. With SBIOS 2.3.1, there's a PRM callback in sbios.
2. boot into shell
3. check the result
```
modprobe acpi-call
echo '\_SB.CPER._DSM {0x43, 0x19, 0x1F, 0xF1, 0x02, 0x5B, 0x1B, 0x4B, 0xAC,
0x54, 0xFC, 0x6D, 0xB4, 0x21, 0xC5, 0x5B} 0 0' > /proc/acpi/call
cat /proc/acpi/call
```
[[Where problems could occur]]
Low, w/o target sbios, would not get the callback from sbios.
** Affects: linux-nvidia (Ubuntu)
Importance: Undecided
Assignee: koba (kobako)
Status: In Progress
** Changed in: linux-nvidia (Ubuntu)
Status: New => In Progress
** Changed in: linux-nvidia (Ubuntu)
Assignee: (unassigned) => koba (kobako)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia in Ubuntu.
https://bugs.launchpad.net/bugs/2081874
Title:
NVIDIA: SAUCE: acpi/prmt: find block with specific type
Status in linux-nvidia package in Ubuntu:
In Progress
Bug description:
[Description]
PRMT needs to find the correct type of block to
translate the PA-VA mapping for EFI runtime services.
The issue arises because the PRMT is finding a block of type
EFI_CONVENTIONAL_MEMORY, which is not appropriate for runtime services
as described in Section 2.2.2 (Runtime Services) of the UEFI
Specification [1]. Since the PRM handler is a type of runtime service,
this causes an exception when the PRM handler is called.
[Firmware Bug]: Unable to handle paging request in EFI runtime service
WARNING: CPU: 22 PID: 4330 at drivers/firmware/efi/runtime-wrappers.c:341
__efi_queue_work+0x11c/0x170
Call trace:
__efi_queue_work+0x11c/0x170
efi_call_acpi_prm_handler+0x68/0xd0
acpi_platformrt_space_handler+0x198/0x258
acpi_ev_address_space_dispatch+0x144/0x388
acpi_ex_access_region+0x9c/0x118
acpi_ex_write_serial_bus+0xc4/0x218
acpi_ex_write_data_to_field+0x168/0x218
acpi_ex_store_object_to_node+0x1a8/0x258
acpi_ex_store+0xec/0x330
acpi_ex_opcode_1A_1T_1R+0x15c/0x618
acpi_ds_exec_end_op+0x274/0x548
acpi_ps_parse_loop+0x10c/0x6b8
acpi_ps_parse_aml+0x140/0x3b0
acpi_ps_execute_method+0x12c/0x2a0
acpi_ns_evaluate+0x210/0x310
acpi_evaluate_object+0x178/0x358
acpi_proc_write+0x1a8/0x8a0 [acpi_call]
proc_reg_write+0xcc/0x150
vfs_write+0xd8/0x380
ksys_write+0x70/0x120
__arm64_sys_write+0x24/0x48
in
[Kernel-packages] [Bug 2003161] Re: Fix speaker mute hotkey doesn't work on Dell G16 series
@James, in the developing days, Dell told about the issue of realtek hda. So only EC takes care the mic and speaker related events. Seems the realtek hda driver is updated and have a workaround? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2003161 Title: Fix speaker mute hotkey doesn't work on Dell G16 series Status in HWE Next: New Status in HWE Next lunar series: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: Won't Fix Status in linux source package in Lunar: Won't Fix Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Speaker mute and Mic mute hotkey no function on the G16. [Fix] speaker mute event is sent by EC then dell-wmi can't recognize it. Add a new keymap for KEY_MUTE. Send for OEM kernels first then will SRU for generic kernel once the patch is merged. [Test Case] 1. boot-up with the kernel applied the fix. 2. Play video/audio. 3. Press the speak-mute hotkey 4. can't hear any sounds. [Where problems could occur] Low, only add a keymap the affect would be very limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2003161/+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 2003161] Re: Fix speaker mute hotkey doesn't work on Dell G16 series
@James, could you please also enable dynamic debug for dell-wmi-base.c, then do these 1. press mic-mute key 2. press speaker-mute key. then provide dmesg, dmesg should have some information like these ~~~ 2803.272234] dell_wmi: Received WMI event (02 00 10 00 50 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00) [ 2803.272241] dell_wmi: Process buffer (02 00 10 00 50 01) [ 2803.272244] dell_wmi: Key with type 0x0010 and code 0x0150 pressed ~~~ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2003161 Title: Fix speaker mute hotkey doesn't work on Dell G16 series Status in HWE Next: New Status in HWE Next lunar series: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: Won't Fix Status in linux source package in Lunar: Won't Fix Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Speaker mute and Mic mute hotkey no function on the G16. [Fix] speaker mute event is sent by EC then dell-wmi can't recognize it. Add a new keymap for KEY_MUTE. Send for OEM kernels first then will SRU for generic kernel once the patch is merged. [Test Case] 1. boot-up with the kernel applied the fix. 2. Play video/audio. 3. Press the speak-mute hotkey 4. can't hear any sounds. [Where problems could occur] Low, only add a keymap the affect would be very limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2003161/+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 2003161] Re: Fix speaker mute hotkey doesn't work on Dell G16 series
@james, please revert hwdb to original. could you confirm this 1. revert 83bcf3e52e9cfc727df33f1055ef0618c91719d0, is the issue observed? the code is 0x109 in this patch, yours is 0x113. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2003161 Title: Fix speaker mute hotkey doesn't work on Dell G16 series Status in HWE Next: New Status in HWE Next lunar series: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: Won't Fix Status in linux source package in Lunar: Won't Fix Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Speaker mute and Mic mute hotkey no function on the G16. [Fix] speaker mute event is sent by EC then dell-wmi can't recognize it. Add a new keymap for KEY_MUTE. Send for OEM kernels first then will SRU for generic kernel once the patch is merged. [Test Case] 1. boot-up with the kernel applied the fix. 2. Play video/audio. 3. Press the speak-mute hotkey 4. can't hear any sounds. [Where problems could occur] Low, only add a keymap the affect would be very limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2003161/+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 2003161] Re: Fix speaker mute hotkey doesn't work on Dell G16 series
@James, please update your 60-keyboard.hwdb ubuntu's path is /usr/lib/udev/hwdb.d/60.keyboard.hwdb ~~~ evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnDellG16*:* KEYBOARD_KEY_100113=mute ~~~ then update hwdb, ~~~ sudo udevadm hwdb -u ~~~ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2003161 Title: Fix speaker mute hotkey doesn't work on Dell G16 series Status in HWE Next: New Status in HWE Next lunar series: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: Won't Fix Status in linux source package in Lunar: Won't Fix Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Speaker mute and Mic mute hotkey no function on the G16. [Fix] speaker mute event is sent by EC then dell-wmi can't recognize it. Add a new keymap for KEY_MUTE. Send for OEM kernels first then will SRU for generic kernel once the patch is merged. [Test Case] 1. boot-up with the kernel applied the fix. 2. Play video/audio. 3. Press the speak-mute hotkey 4. can't hear any sounds. [Where problems could occur] Low, only add a keymap the affect would be very limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2003161/+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 2003161] Re: Fix speaker mute hotkey doesn't work on Dell G16 series
@James, could you find mic-mute button on your g16? could you sniffer events for auido-mute and mic-mute? ~~~ sudo libinput debug-events ~~~ the patch [0] is a feature to mute the mic not audio. seems the codes are mixed. [0] 83bcf3e52e9cf) platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2003161 Title: Fix speaker mute hotkey doesn't work on Dell G16 series Status in HWE Next: New Status in HWE Next lunar series: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: Won't Fix Status in linux source package in Lunar: Won't Fix Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Speaker mute and Mic mute hotkey no function on the G16. [Fix] speaker mute event is sent by EC then dell-wmi can't recognize it. Add a new keymap for KEY_MUTE. Send for OEM kernels first then will SRU for generic kernel once the patch is merged. [Test Case] 1. boot-up with the kernel applied the fix. 2. Play video/audio. 3. Press the speak-mute hotkey 4. can't hear any sounds. [Where problems could occur] Low, only add a keymap the affect would be very limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2003161/+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 2003161] Re: Fix speaker mute hotkey doesn't work on Dell G16 series
@James, could you also list and did you change the hwdb by yourself? thanks 1. sudo apt policy systemd-hwe-hwdb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2003161 Title: Fix speaker mute hotkey doesn't work on Dell G16 series Status in HWE Next: New Status in HWE Next lunar series: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: Won't Fix Status in linux source package in Lunar: Won't Fix Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Speaker mute and Mic mute hotkey no function on the G16. [Fix] speaker mute event is sent by EC then dell-wmi can't recognize it. Add a new keymap for KEY_MUTE. Send for OEM kernels first then will SRU for generic kernel once the patch is merged. [Test Case] 1. boot-up with the kernel applied the fix. 2. Play video/audio. 3. Press the speak-mute hotkey 4. can't hear any sounds. [Where problems could occur] Low, only add a keymap the affect would be very limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2003161/+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 2056125] [NEW] Intel CNL: audio device disappear during suspend then resume
Public bug reported: [Description] On CNL platform, after suspend&resume, the audio device is disappleared. $sudo rtcwake -m mem -s 5 or $systemctl suspend it happens with the latest 6.5.0-lowtency and doesn't be observed with 6.2.0-1017-lowlatency. get some errors in dmesg ~~~ 1719 [ 61.041002] sof-audio-pci-intel-cnl :00:1f.3: ipc tx error for 0x6001 (msg/reply size: 108/20): -22 1720 [ 61.041009] sof-audio-pci-intel-cnl :00:1f.3: HW params ipc failed for stream 1 1721 [ 61.041011] sof-audio-pci-intel-cnl :00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on :00:1f.3: -22 1722 [ 61.045196] sof-audio-pci-intel-cnl :00:1f.3: ipc tx error for 0x6001 (msg/reply size: 108/20): -22 1723 [ 61.045205] sof-audio-pci-intel-cnl :00:1f.3: HW params ipc failed for stream 1 1724 [ 61.045208] sof-audio-pci-intel-cnl :00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on :00:1f.3: -22 1725 [ 61.049050] sof-audio-pci-intel-cnl :00:1f.3: ipc tx error for 0x6001 (msg/reply size: 108/20): -22 1726 [ 61.049066] sof-audio-pci-intel-cnl :00:1f.3: HW params ipc failed for stream 1 1727 [ 61.049068] sof-audio-pci-intel-cnl :00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on :00:1f.3: -22 1728 [ 61.052840] sof-audio-pci-intel-cnl :00:1f.3: ipc tx error for 0x6001 (msg/reply size: 108/20): -22 1729 [ 61.052848] sof-audio-pci-intel-cnl :00:1f.3: HW params ipc failed for stream 1 1730 [ 61.052850] sof-audio-pci-intel-cnl :00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on :00:1f.3: -22 1731 [ 61.056868] sof-audio-pci-intel-cnl :00:1f.3: ipc tx error for 0x6001 (msg/reply size: 108/20): -22 1732 [ 61.056876] sof-audio-pci-intel-cnl :00:1f.3: HW params ipc failed for stream 1 1733 [ 61.056878] sof-audio-pci-intel-cnl :00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on :00:1f.3: -22 ~~~ the culprit is 82b18242ae68) ASoC: SOF: pcm: do not free widgets during suspend trigger. it landed since v6.3. the version of sof-bin is ~~~ $ sudo apt policy firmware-sof-signed firmware-sof-signed: Installed: 2.0-1ubuntu4.5 Candidate: 2.0-1ubuntu4.5 ~~~ after upgrade the sof-bin to upstream-sof-bin-2023.12, the issue is gone. ** Affects: firmware-sof (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg_upstreamKernel202403040039" https://bugs.launchpad.net/bugs/2056125/+attachment/5752774/+files/dmesg_upstreamKernel202403040039 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/2056125 Title: Intel CNL: audio device disappear during suspend then resume Status in firmware-sof package in Ubuntu: New Bug description: [Description] On CNL platform, after suspend&resume, the audio device is disappleared. $sudo rtcwake -m mem -s 5 or $systemctl suspend it happens with the latest 6.5.0-lowtency and doesn't be observed with 6.2.0-1017-lowlatency. get some errors in dmesg ~~~ 1719 [ 61.041002] sof-audio-pci-intel-cnl :00:1f.3: ipc tx error for 0x6001 (msg/reply size: 108/20): -22 1720 [ 61.041009] sof-audio-pci-intel-cnl :00:1f.3: HW params ipc failed for stream 1 1721 [ 61.041011] sof-audio-pci-intel-cnl :00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on :00:1f.3: -22 1722 [ 61.045196] sof-audio-pci-intel-cnl :00:1f.3: ipc tx error for 0x6001 (msg/reply size: 108/20): -22 1723 [ 61.045205] sof-audio-pci-intel-cnl :00:1f.3: HW params ipc failed for stream 1 1724 [ 61.045208] sof-audio-pci-intel-cnl :00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on :00:1f.3: -22 1725 [ 61.049050] sof-audio-pci-intel-cnl :00:1f.3: ipc tx error for 0x6001 (msg/reply size: 108/20): -22 1726 [ 61.049066] sof-audio-pci-intel-cnl :00:1f.3: HW params ipc failed for stream 1 1727 [ 61.049068] sof-audio-pci-intel-cnl :00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on :00:1f.3: -22 1728 [ 61.052840] sof-audio-pci-intel-cnl :00:1f.3: ipc tx error for 0x6001 (msg/reply size: 108/20): -22 1729 [ 61.052848] sof-audio-pci-intel-cnl :00:1f.3: HW params ipc failed for stream 1 1730 [ 61.052850] sof-audio-pci-intel-cnl :00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on :00:1f.3: -22 1731 [ 61.056868] sof-audio-pci-intel-cnl :00:1f.3: ipc tx error for 0x6001 (msg/reply size: 108/20): -22 1732 [ 61.056876] sof-audio-pci-intel-cnl :00:1f.3: HW params ipc failed for stream 1 1733 [ 61.056878] sof-audio-pci-intel-cnl :00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on :00:1f.3: -22 ~~~ the culprit is 82b18242ae68) ASoC: SOF: pcm: do not free widgets during suspend trigger. it landed since v6.3. the version of so
[Kernel-packages] [Bug 2011768] Re: Fix NVME storage with RAID ON disappeared under Dell factory WINPE environment
Landed on Jammy via https://bugs.launchpad.net/bugs/2032689. (a86273ff8123-PCI: vmd: Reset VMD config register between soft reboots) Landed on Lunar via https://bugs.launchpad.net/bugs/2034469 (22a014208c21-PCI: vmd: Reset VMD config register between soft reboots) ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2011768 Title: Fix NVME storage with RAID ON disappeared under Dell factory WINPE environment Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] NVME storage disappeared under Dell factory WINPE environment with RAID ON mode when this WINPE boot entry touched by efibootmgr [Fix] Reset the VMD msi remapping during shutdown. [Test Case] 1. Install Ubuntu 2. Then, system will reboot to WINPE to do some cleanup work. 3. in WINPE, the NVME storage could be listed. [Where problems could occur] Low, the issue may be observed on VMD MSI remapping. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2011768/+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 2027957] Re: Fix AMDGPU: the screen freeze with W7500
** Also affects: linux (Ubuntu Noble) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Also affects: linux-oem-6.1 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Mantic) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2027957 Title: Fix AMDGPU: the screen freeze with W7500 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Bug description: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. Solution is, - Detect Intel x86 systems that don't support dynamic switching - Override the input caps to maximum supported for that system - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] low, this could lead issue when setting higher speeds than supported. [Misc] 1. jammy, amdgpu isn't loaded on this platform with 5.15-73-generic. 2. kinetic, amdgpu failed to probe the vga controller with 5.19-46-generic. 3. Passed cbd build against Mantic&Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027957/+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 2027957] Re: Fix AMDGPU: the screen freeze with W7500
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2027957 Title: Fix AMDGPU: the screen freeze with W7500 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Bug description: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. Solution is, - Detect Intel x86 systems that don't support dynamic switching - Override the input caps to maximum supported for that system - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] low, this could lead issue when setting higher speeds than supported. [Misc] 1. jammy, amdgpu isn't loaded on this platform with 5.15-73-generic. 2. kinetic, amdgpu failed to probe the vga controller with 5.19-46-generic. 3. Passed cbd build against Mantic&Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027957/+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 1981525] Re: Add support for Raptor Lake CPUs
** Changed in: thermald (Ubuntu Focal) Status: Triaged => Invalid ** Changed in: thermald (Ubuntu Focal) Assignee: koba (kobako) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981525 Title: Add support for Raptor Lake CPUs Status in OEM Priority Project: Fix Committed Status in OEM Priority Project focal series: Fix Committed Status in thermald package in Ubuntu: Invalid Status in thermald source package in Focal: Invalid Status in thermald source package in Jammy: Fix Released Bug description: [Impact] * Support thermald on Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/354 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981525/+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 2037254] Re: Restore proper ASPM L1ss setting on system resume
*** This bug is a duplicate of bug 2035307 *** https://bugs.launchpad.net/bugs/2035307 ** This bug has been marked a duplicate of private bug 2035307 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2037254 Title: Restore proper ASPM L1ss setting on system resume Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Confirmed Bug description: [Impact] Realtek cardreader drops from PCIe bus after system resume, because L1ss became different. [Fix] Restore ASPM L1ss setting so the ASPM assumption made by driver can be kept. [Test] The cardreader in question keeps working after S3 because the L1ss remains the same after resume. [Where problems could occur] Drivers may already made "workaround" to circumvent the current L1ss situation. So restoring the L1ss might break some drivers. That means we should test this in OEM kernel for some cycles before let it land to generic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2037254/+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 2042385] Re: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on
SRUed for Unstable, https://lists.ubuntu.com/archives/kernel-team/2023-November/147039.html ** Description changed: [Impact] RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on. [Fix] Realtek r8168h/r8111's ASPM is blocked due to users report the regression on their platform[0]. Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep deeper. [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814 [where the issue could happen] Medium, may have the regression but the risk is limited in some Dell platforms. we will ask Realtek's effort once the regression is observed. + + [Misc] + For Unstable, built with mantic configuration + ~~~ + $ git push m_cbd + remote: *** kernel-cbd * + remote: * Queueing builds (your 'ubuntu_unstable_next'); ok to interrupt + remote: * For results: ssh cbd ls kobako-mantic-c281d2b48f02-DyYx + remote: * 1/9 workers busy, 0 builds queued + remote: 2023-11-20 16:19:03 kobako-mantic-c281d2b48f02-DyYx/amd64/BUILD-OK + remote: 2023-11-20 16:21:38 kobako-mantic-c281d2b48f02-DyYx/arm64/BUILD-OK + remote: 2023-11-20 16:18:54 kobako-mantic-c281d2b48f02-DyYx/armhf/BUILD-OK + remote: 2023-11-20 16:22:08 kobako-mantic-c281d2b48f02-DyYx/ppc64el/BUILD-OK + remote: 2023-11-20 16:14:16 kobako-mantic-c281d2b48f02-DyYx/s390x/BUILD-OK + remote: + To cbd.kernel:mantic.git + * [new branch]ubuntu_unstable_next -> ubuntu_unstable_next + ~~~ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042385 Title: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on. [Fix] Realtek r8168h/r8111's ASPM is blocked due to users report the regression on their platform[0]. Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep deeper. [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814 [where the issue could happen] Medium, may have the regression but the risk is limited in some Dell platforms. we will ask Realtek's effort once the regression is observed. [Misc] For Unstable, built with mantic configuration ~~~ $ git push m_cbd remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_unstable_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-mantic-c281d2b48f02-DyYx remote: * 1/9 workers busy, 0 builds queued remote: 2023-11-20 16:19:03 kobako-mantic-c281d2b48f02-DyYx/amd64/BUILD-OK remote: 2023-11-20 16:21:38 kobako-mantic-c281d2b48f02-DyYx/arm64/BUILD-OK remote: 2023-11-20 16:18:54 kobako-mantic-c281d2b48f02-DyYx/armhf/BUILD-OK remote: 2023-11-20 16:22:08 kobako-mantic-c281d2b48f02-DyYx/ppc64el/BUILD-OK remote: 2023-11-20 16:14:16 kobako-mantic-c281d2b48f02-DyYx/s390x/BUILD-OK remote: To cbd.kernel:mantic.git * [new branch]ubuntu_unstable_next -> ubuntu_unstable_next ~~~ To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042385/+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 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
** Description changed: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec&package_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. [Misc] Because the board_ahci_mobile is still not modified to board_ahci_low_power on Jammy, provide a single patch for Jammy. For generic J/M, passed the all arch compilations on cbd, Jammy, ~~~ $ git push j_cbd Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_jammy_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-f5146c67dd2d-XWAJ remote: * 0/1 workers busy, 0 builds queued remote: 2023-11-17 19:50:25 kobako-jammy-f5146c67dd2d-XWAJ/amd64/BUILD-OK remote: 2023-11-17 20:18:29 kobako-jammy-f5146c67dd2d-XWAJ/arm64/BUILD-OK remote: 2023-11-17 20:01:41 kobako-jammy-f5146c67dd2d-XWAJ/armhf/BUILD-OK remote: 2023-11-17 20:31:51 kobako-jammy-f5146c67dd2d-XWAJ/ppc64el/BUILD-OK remote: 2023-11-17 20:37:25 kobako-jammy-f5146c67dd2d-XWAJ/s390x/BUILD-OK remote: To cbd.kernel:jammy.git * [new branch]ubuntu_jammy_next -> ubuntu_jammy_next ~~~ + + Lunar, + $ git push l_cbd + Enumerating objects: 9, done. + Counting objects: 100% (9/9), done. + Delta compression using up to 8 threads + Compressing objects: 100% (5/5), done. + Writing objects: 100% (5/5), 784 bytes | 65.00 KiB/s, done. + Total 5 (delta 4), reused 0 (delta 0), pack-reused 0 + remote: *** kernel-cbd * + remote: * Queueing builds (your 'ubuntu_lunar_next'); ok to interrupt + remote: * For results: ssh cbd ls kobako-lunar-915de03d6ecf-V1nm + remote: * 9/9 workers busy, 0 builds queued + remote: 2023-11-20 16:00:11 kobako-lunar-915de03d6ecf-V1nm/amd64/BUILD-OK + remote: 2023-11-20 15:59:57 kobako-lunar-915de03d6ecf-V1nm/arm64/BUILD-OK + remote: 2023-11-20 15:55:14 kobako-lunar-915de03d6ecf-V1nm/armhf/BUILD-OK + remote: 2023-11-20 15:55:26 kobako-lunar-915de03d6ecf-V1nm/ppc64el/BUILD-OK + remote: 2023-11-20 15:47:17 kobako-lunar-915de03d6ecf-V1nm/s390x/BUILD-OK + remote: + To cbd.kernel:lunar.git + * [new branch]ubuntu_lunar_next -> ubuntu_lunar_next + Mantic, ~~~ $ git push m_cbd Enumerating objects: 102, done. Counting objects: 100% (102/102), done. Delta compression using up to 8 threads Compressing objects: 100% (17/17), done. Writing objects: 100% (61/61), 252.10 KiB | 2.23 MiB/s, done. Total 61 (delta 46), reused 54 (delta 41), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_mantic_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-mantic-e489d3bb608c-9LiJ remote: * 0/1 workers busy, 0 builds queued remote: 2023-11-17 20:58:33 kobako-mantic-e489d3bb608c-9LiJ/amd64/BUILD-OK remote: 2023-11-17 21:30:32 kobako-mantic-e489d3bb608c-9LiJ/arm64/BUILD-OK remote: 2023-11-17 21:09:18 kobako-mantic-e489d3bb608c-9LiJ/armhf/BUILD-OK remote: 2023-11-17 21:45:50 kobako-mantic-e489d3bb608c-9LiJ/ppc64el/BUILD-OK remote: 2023-11-17 21:54:30 kobako-mantic-e489d3bb608c-9LiJ/s390x/BUILD-OK remote: To cbd.kernel:mantic.git * [new branch]ubuntu_mantic_next -> ubuntu_mantic_next ~~~ For Unstable, successfully compiled with the Mantic configuration and without dkms. ~~~ Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 remote: *** kernel-cbd **
[Kernel-packages] [Bug 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
** Changed in: linux (Ubuntu Lunar) Status: Invalid => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2037493 Title: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec&package_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. [Misc] Because the board_ahci_mobile is still not modified to board_ahci_low_power on Jammy, provide a single patch for Jammy. For generic J/M, passed the all arch compilations on cbd, Jammy, ~~~ $ git push j_cbd Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_jammy_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-f5146c67dd2d-XWAJ remote: * 0/1 workers busy, 0 builds queued remote: 2023-11-17 19:50:25 kobako-jammy-f5146c67dd2d-XWAJ/amd64/BUILD-OK remote: 2023-11-17 20:18:29 kobako-jammy-f5146c67dd2d-XWAJ/arm64/BUILD-OK remote: 2023-11-17 20:01:41 kobako-jammy-f5146c67dd2d-XWAJ/armhf/BUILD-OK remote: 2023-11-17 20:31:51 kobako-jammy-f5146c67dd2d-XWAJ/ppc64el/BUILD-OK remote: 2023-11-17 20:37:25 kobako-jammy-f5146c67dd2d-XWAJ/s390x/BUILD-OK remote: To cbd.kernel:jammy.git * [new branch]ubuntu_jammy_next -> ubuntu_jammy_next ~~~ Mantic, ~~~ $ git push m_cbd Enumerating objects: 102, done. Counting objects: 100% (102/102), done. Delta compression using up to 8 threads Compressing objects: 100% (17/17), done. Writing objects: 100% (61/61), 252.10 KiB | 2.23 MiB/s, done. Total 61 (delta 46), reused 54 (delta 41), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_mantic_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-mantic-e489d3bb608c-9LiJ remote: * 0/1 workers busy, 0 builds queued remote: 2023-11-17 20:58:33 kobako-mantic-e489d3bb608c-9LiJ/amd64/BUILD-OK remote: 2023-11-17 21:30:32 kobako-mantic-e489d3bb608c-9LiJ/arm64/BUILD-OK remote: 2023-11-17 21:09:18 kobako-mantic-e489d3bb608c-9LiJ/armhf/BUILD-OK remote: 2023-11-17 21:45:50 kobako-mantic-e489d3bb608c-9LiJ/ppc64el/BUILD-OK remote: 2023-11-17 21:54:30 kobako-mantic-e489d3bb608c-9LiJ/s390x/BUILD-OK remote: To cbd.kernel:mantic.git * [new branch]ubuntu_mantic_next -> ubuntu_mantic_next ~~~ For Unstable, su
[Kernel-packages] [Bug 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
SRUed for generic J/M/U, https://lists.ubuntu.com/archives/kernel-team/2023-November/147011.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2037493 Title: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec&package_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. [Misc] Because the board_ahci_mobile is still not modified to board_ahci_low_power on Jammy, provide a single patch for Jammy. For generic J/M, passed the all arch compilations on cbd, Jammy, ~~~ $ git push j_cbd Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_jammy_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-f5146c67dd2d-XWAJ remote: * 0/1 workers busy, 0 builds queued remote: 2023-11-17 19:50:25 kobako-jammy-f5146c67dd2d-XWAJ/amd64/BUILD-OK remote: 2023-11-17 20:18:29 kobako-jammy-f5146c67dd2d-XWAJ/arm64/BUILD-OK remote: 2023-11-17 20:01:41 kobako-jammy-f5146c67dd2d-XWAJ/armhf/BUILD-OK remote: 2023-11-17 20:31:51 kobako-jammy-f5146c67dd2d-XWAJ/ppc64el/BUILD-OK remote: 2023-11-17 20:37:25 kobako-jammy-f5146c67dd2d-XWAJ/s390x/BUILD-OK remote: To cbd.kernel:jammy.git * [new branch]ubuntu_jammy_next -> ubuntu_jammy_next ~~~ Mantic, ~~~ $ git push m_cbd Enumerating objects: 102, done. Counting objects: 100% (102/102), done. Delta compression using up to 8 threads Compressing objects: 100% (17/17), done. Writing objects: 100% (61/61), 252.10 KiB | 2.23 MiB/s, done. Total 61 (delta 46), reused 54 (delta 41), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_mantic_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-mantic-e489d3bb608c-9LiJ remote: * 0/1 workers busy, 0 builds queued remote: 2023-11-17 20:58:33 kobako-mantic-e489d3bb608c-9LiJ/amd64/BUILD-OK remote: 2023-11-17 21:30:32 kobako-mantic-e489d3bb608c-9LiJ/arm64/BUILD-OK remote: 2023-11-17 21:09:18 kobako-mantic-e489d3bb608c-9LiJ/armhf/BUILD-OK remote: 2023-11-17 21:45:50 kobako-mantic-e489d3bb608c-9LiJ/ppc64el/BUILD-OK remote: 2023-11-17 21:54:30 kobako-mantic-e489d3bb608c-9LiJ/s390x/BUILD-OK remote: To cbd.kernel:mantic.git * [new branch]ubuntu_mantic_next -> ubuntu_mantic_next ~~~ For Unstable, successfully compiled with the Mantic configuration and without dkms. ~~~ Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
[Kernel-packages] [Bug 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
** Description changed: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec&package_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. + + [Misc] + For generic J/M, passed the all arch compilations on cbd, + Jammy, + ~~~ + $ git push j_cbd + Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 + remote: *** kernel-cbd * + remote: * Queueing builds (your 'ubuntu_jammy_next'); ok to interrupt + remote: * For results: ssh cbd ls kobako-jammy-f5146c67dd2d-XWAJ + remote: * 0/1 workers busy, 0 builds queued + remote: 2023-11-17 19:50:25 kobako-jammy-f5146c67dd2d-XWAJ/amd64/BUILD-OK + remote: 2023-11-17 20:18:29 kobako-jammy-f5146c67dd2d-XWAJ/arm64/BUILD-OK + remote: 2023-11-17 20:01:41 kobako-jammy-f5146c67dd2d-XWAJ/armhf/BUILD-OK + remote: 2023-11-17 20:31:51 kobako-jammy-f5146c67dd2d-XWAJ/ppc64el/BUILD-OK + remote: 2023-11-17 20:37:25 kobako-jammy-f5146c67dd2d-XWAJ/s390x/BUILD-OK + remote: + To cbd.kernel:jammy.git + * [new branch]ubuntu_jammy_next -> ubuntu_jammy_next + ~~~ + Mantic, + ~~~ + $ git push m_cbd + Enumerating objects: 102, done. + Counting objects: 100% (102/102), done. + Delta compression using up to 8 threads + Compressing objects: 100% (17/17), done. + Writing objects: 100% (61/61), 252.10 KiB | 2.23 MiB/s, done. + Total 61 (delta 46), reused 54 (delta 41), pack-reused 0 + remote: *** kernel-cbd * + remote: * Queueing builds (your 'ubuntu_mantic_next'); ok to interrupt + remote: * For results: ssh cbd ls kobako-mantic-e489d3bb608c-9LiJ + remote: * 0/1 workers busy, 0 builds queued + remote: 2023-11-17 20:58:33 kobako-mantic-e489d3bb608c-9LiJ/amd64/BUILD-OK + remote: 2023-11-17 21:30:32 kobako-mantic-e489d3bb608c-9LiJ/arm64/BUILD-OK + remote: 2023-11-17 21:09:18 kobako-mantic-e489d3bb608c-9LiJ/armhf/BUILD-OK + remote: 2023-11-17 21:45:50 kobako-mantic-e489d3bb608c-9LiJ/ppc64el/BUILD-OK + remote: 2023-11-17 21:54:30 kobako-mantic-e489d3bb608c-9LiJ/s390x/BUILD-OK + remote: + To cbd.kernel:mantic.git + * [new branch]ubuntu_mantic_next -> ubuntu_mantic_next + ~~~ + + For Unstable, successfully compiled with the Mantic configuration and without dkms. + ~~~ + Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 + remote: *** kernel-cbd * + remote: * Queueing builds (your 'ubuntu_unstable_next'); ok to interrupt + remote: * For results: ssh cbd ls kobako-mantic-dc0405f4bd4c-VZvy + remote: * 0/1 workers busy, 0 builds queued + remote: 2023-11-18 22:35:41 kobako-mantic-dc0405f4bd4c-VZvy/amd64/BUILD-OK + remote: 2023-11-18 23:03:15 kobako-mantic-dc0405f4bd4c-VZvy/arm64/BUILD-OK + remote: 2023-11-18 22:46:15 kobako-mantic-dc0405f4bd4c-VZvy/armhf/BUILD-OK + remote: 2023-11-18 23:16:02 kobako-mantic-dc0405f4bd4c-VZvy/ppc64el/BUILD-OK + remote: 2023-11-18 23:22:02 kobako-mantic-dc0405f4bd4c-VZvy/s390x/BUILD-OK + remote: + To cbd.kernel:mantic.git + * [new branch]ubuntu_unstable_next -> ubuntu_unstable_next + ~~~ ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: In Progress ** Also affects: linux-oem-6.1 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Lunar)
[Kernel-packages] [Bug 2042385] Re: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on
Verified with CID:202309-32128, ~~~ $ uname -a Linux 6.5.0-1008-oem #8-Ubuntu SMP PREEMPT_DYNAMIC Fri Nov 10 13:08:33 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ~~~ $ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec 0 $ sudo rtcwake -m mem -s 5 $ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec 4017704 ~~~ ** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042385 Title: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on. [Fix] Realtek r8168h/r8111's ASPM is blocked due to users report the regression on their platform[0]. Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep deeper. [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814 [where the issue could happen] Medium, may have the regression but the risk is limited in some Dell platforms. we will ask Realtek's effort once the regression is observed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042385/+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 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
** Changed in: linux (Ubuntu) Assignee: koba (kobako) => (unassigned) ** Changed in: linux (Ubuntu Jammy) Status: Invalid => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2037493 Title: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec&package_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037493/+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 2042385] Re: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on
** Changed in: linux (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042385 Title: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on. [Fix] Realtek r8168h/r8111's ASPM is blocked due to users report the regression on their platform[0]. Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep deeper. [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814 [where the issue could happen] Medium, may have the regression but the risk is limited in some Dell platforms. we will ask Realtek's effort once the regression is observed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042385/+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 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => koba (kobako)
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => koba (kobako)
** Changed in: linux-oem-6.1 (Ubuntu Mantic)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Noble)
Status: New => Invalid
** Changed in: linux-oem-6.5 (Ubuntu Mantic)
Status: New => Invalid
** Changed in: linux-oem-6.5 (Ubuntu Noble)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042500
Title:
Fix after-suspend-mediacard/sdhc-insert test failed
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-6.1 source package in Jammy:
In Progress
Status in linux-oem-6.5 source package in Jammy:
Fix Committed
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.1 source package in Noble:
Invalid
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
due to a regression that caused resume from suspend to fail on certain
systems. However, we never added this capability back and this is now
causing systems fail to enter low power CPU states, drawing more power
from the battery.
The original revert mentioned that we restore L1 PM substate configuration
even though ASPM L1 may already be enabled. This is due the fact that
the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
more closely by:
1) Do not restore ASPM configuration in pci_restore_pcie_state() but
do that after PCIe capability is restored in pci_restore_aspm_state()
following PCIe r6.0, sec 5.5.4.
2) ASPM is first enabled on the upstream component and then downstream
(this is already forced by the parent-child ordering of Linux
Device Power Management framework).
3) Program ASPM L1 PM substate configuration before L1 enables.
4) Program ASPM L1 PM substate enables last after rest of the fields
in the capability are programmed.
5) Add denylist that skips restoring on the ASUS and TUXEDO systems
where these regressions happened, just in case. For the TUXEDO case
we only skip restore if the BIOS is involved in system suspend
(that's forcing "mem_sleep=deep" in the command line). This is to
avoid possible power regression when the default suspend to idle is
used, and at the same time make sure the devices continue working
after resume when the BIOS is involved.
[Test Case]
1. suspend and resume.
2. check if the error appears in dmesg
~~~
pcieport :00:1c.0: pciehp: Slot(5): Card not present
rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
~~~
[where the issue could happen]
low, the patch works well on the reported malfunctioned ASUS platform too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042500/+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 2038288] Re: Failed to start thermald.service
＠madigal, could you upload the whole thermald lod? and systemctl status thermald.service -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2038288 Title: Failed to start thermald.service Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: In Progress Bug description: Get lot of thermald errors logged with that Mate session on Mantic dbus-broker-launch[775]: Invalid group-name in /usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power" systemd[1]: Starting thermald.service - Thermal Daemon Service... thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[892]: sensor id 10 : No temp sysfs for reading raw temp thermald[892]: sensor id 10 : No temp sysfs for reading raw temp thermald[892]: sensor id 10 : No temp sysfs for reading raw temp thermald[892]: *** stack smashing detected ***: terminated systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT systemd[1]: thermald.service: Failed with result 'signal'. systemd[1]: Failed to start thermald.service - Thermal Daemon Service. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[982]: *** stack smashing detected ***: terminated systemd[1]: Started thermald.service - Thermal Daemon Service. thermald[982]: sensor id 10 : No temp sysfs for reading raw temp thermald[982]: sensor id 10 : No temp sysfs for reading raw temp thermald[982]: sensor id 10 : No temp sysfs for reading raw temp systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT systemd[1]: thermald.service: Failed with result 'signal'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp thermald[1049]: *** stack smashing detected ***: terminated systemd[1]: Started thermald.service - Thermal Daemon Service. systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: thermald.service: Failed with result 'core-dump'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... systemd[1]: Started thermald.service - Thermal Daemon Service. thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp thermald[1117]: *** stack smashing detected ***: terminated systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: thermald.service: Failed with result 'core-dump'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... systemd[1]: Started thermald.service - Thermal Daemon Service. thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp thermald[1180]: *** stack smashing detected ***: terminated systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: thermald.service: Failed with result 'core-dump'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: thermald.service: Start request repeated too quickly. systemd[1]: thermald.service: Failed with result 'core-dump'. systemd[1]: Failed to start thermald.service - Thermal Daemo
[Kernel-packages] [Bug 2038288] Re: Failed to start thermald.service
@Anaggh, thanks, I'm surprised by this and thought it doesn't matter the xml isn't there. btw, there's a dependency issue of thermald. i will check further, thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2038288 Title: Failed to start thermald.service Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: In Progress Bug description: Get lot of thermald errors logged with that Mate session on Mantic dbus-broker-launch[775]: Invalid group-name in /usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power" systemd[1]: Starting thermald.service - Thermal Daemon Service... thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[892]: sensor id 10 : No temp sysfs for reading raw temp thermald[892]: sensor id 10 : No temp sysfs for reading raw temp thermald[892]: sensor id 10 : No temp sysfs for reading raw temp thermald[892]: *** stack smashing detected ***: terminated systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT systemd[1]: thermald.service: Failed with result 'signal'. systemd[1]: Failed to start thermald.service - Thermal Daemon Service. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[982]: *** stack smashing detected ***: terminated systemd[1]: Started thermald.service - Thermal Daemon Service. thermald[982]: sensor id 10 : No temp sysfs for reading raw temp thermald[982]: sensor id 10 : No temp sysfs for reading raw temp thermald[982]: sensor id 10 : No temp sysfs for reading raw temp systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT systemd[1]: thermald.service: Failed with result 'signal'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp thermald[1049]: *** stack smashing detected ***: terminated systemd[1]: Started thermald.service - Thermal Daemon Service. systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: thermald.service: Failed with result 'core-dump'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... systemd[1]: Started thermald.service - Thermal Daemon Service. thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp thermald[1117]: *** stack smashing detected ***: terminated systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: thermald.service: Failed with result 'core-dump'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... systemd[1]: Started thermald.service - Thermal Daemon Service. thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp thermald[1180]: *** stack smashing detected ***: terminated systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: thermald.service: Failed with result 'core-dump'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: thermald.service: Start request repeated too quickly. systemd[1]: thermald.service: Failed with result
Re: [Kernel-packages] [Bug 2038288] Re: Failed to start thermald.service
hi, would you mind to help on checking, if upstream thermald also happens? #git clone https://github.com/intel/thermal_daemon.git #As per README.md, #./autogen prefix=/ #make Before run the upstream thermald, stop the original daemon #systemctl stop thermald.service #sudo ./thermald --no-daemon --adaptive -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2038288 Title: Failed to start thermald.service Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: In Progress Bug description: Get lot of thermald errors logged with that Mate session on Mantic dbus-broker-launch[775]: Invalid group-name in /usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power" systemd[1]: Starting thermald.service - Thermal Daemon Service... thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[892]: sensor id 10 : No temp sysfs for reading raw temp thermald[892]: sensor id 10 : No temp sysfs for reading raw temp thermald[892]: sensor id 10 : No temp sysfs for reading raw temp thermald[892]: *** stack smashing detected ***: terminated systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT systemd[1]: thermald.service: Failed with result 'signal'. systemd[1]: Failed to start thermald.service - Thermal Daemon Service. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[982]: *** stack smashing detected ***: terminated systemd[1]: Started thermald.service - Thermal Daemon Service. thermald[982]: sensor id 10 : No temp sysfs for reading raw temp thermald[982]: sensor id 10 : No temp sysfs for reading raw temp thermald[982]: sensor id 10 : No temp sysfs for reading raw temp systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT systemd[1]: thermald.service: Failed with result 'signal'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp thermald[1049]: *** stack smashing detected ***: terminated systemd[1]: Started thermald.service - Thermal Daemon Service. systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: thermald.service: Failed with result 'core-dump'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... systemd[1]: Started thermald.service - Thermal Daemon Service. thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp thermald[1117]: *** stack smashing detected ***: terminated systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: thermald.service: Failed with result 'core-dump'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... systemd[1]: Started thermald.service - Thermal Daemon Service. thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp thermald[1180]: *** stack smashing detected ***: terminated systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: thermald.service: Failed with result 'core-dump'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5. systemd[1]: Stopped thermald.service
[Kernel-packages] [Bug 2042385] Re: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042385 Title: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: New Bug description: [Impact] RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on. [Fix] Realtek r8168h/r8111's ASPM is blocked due to users report the regression on their platform[0]. Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep deeper. [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814 [where the issue could happen] Medium, may have the regression but the risk is limited in some Dell platforms. we will ask Realtek's effort once the regression is observed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042385/+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 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
** Description changed:
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
+ Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
+ for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
+ due to a regression that caused resume from suspend to fail on certain
+ systems. However, we never added this capability back and this is now
+ causing systems fail to enter low power CPU states, drawing more power
+ from the battery.
+
+ The original revert mentioned that we restore L1 PM substate configuration
+ even though ASPM L1 may already be enabled. This is due the fact that
+ the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
+
+ Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
+ more closely by:
+
+ 1) Do not restore ASPM configuration in pci_restore_pcie_state() but
+do that after PCIe capability is restored in pci_restore_aspm_state()
+following PCIe r6.0, sec 5.5.4.
+
+ 2) ASPM is first enabled on the upstream component and then downstream
+(this is already forced by the parent-child ordering of Linux
+Device Power Management framework).
+
+ 3) Program ASPM L1 PM substate configuration before L1 enables.
+
+ 4) Program ASPM L1 PM substate enables last after rest of the fields
+in the capability are programmed.
+
+ 5) Add denylist that skips restoring on the ASUS and TUXEDO systems
+where these regressions happened, just in case. For the TUXEDO case
+we only skip restore if the BIOS is involved in system suspend
+(that's forcing "mem_sleep=deep" in the command line). This is to
+avoid possible power regression when the default suspend to idle is
+used, and at the same time make sure the devices continue working
+after resume when the BIOS is involved.
+ [Test Case]
+ 1. suspend and resume.
+ 2. check if the error appears in dmesg
+ ~~~
+ pcieport :00:1c.0: pciehp: Slot(5): Card not present
+ rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
+ rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
+ ~~~
[where the issue could happen]
- low,
+ low, the patch works well on the reported malfunctioned ASUS platform too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042500
Title:
Fix after-suspend-mediacard/sdhc-insert test failed
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
New
Status in linux-oem-6.5 package in Ubuntu:
New
Status in linux source package in Jammy:
New
Status in linux-oem-6.1 source package in Jammy:
In Progress
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.1 source package in Noble:
New
Status in linux-oem-6.5 source package in Noble:
New
Bug description:
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
due to a regression that caused resume from suspend to fail on certain
systems. However, we never added this capability back and this is now
causing systems fail to enter low power CPU states, drawing more power
from the battery.
The original revert mentioned that we restore L1 PM substate configuration
even though ASPM L1 may already be enabled. This is due the fact that
the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
more closely by:
1) Do not restore ASPM configuration in pci_restore_pcie_state() but
do that after PCIe capability is restored in pci_restore_aspm_state()
following PCIe r6.0, sec 5.5.4.
2) ASPM is first enabled on the upstream component and then downstream
(this is already forced by the parent-child ordering of Linux
Device Power Management framework).
3) Program ASPM L1 PM substate configuration before L1 enables.
4) Program ASPM L1 PM substate enables last after rest of the fields
in the capability are programmed.
5) Add denylist that skips restoring on the ASUS and TUXEDO systems
where these regressions happened, just in case. For the TUXEDO case
we only skip restore if the BIOS is involved in system suspend
(that's forcing "mem_sleep=deep" in the command line). This is to
avoid possible power regression when the default suspend to idle is
used, and at the same time make sure the devices continue working
after resume when the BIOS is involved.
[Test Case]
1. suspend and
[Kernel-packages] [Bug 2042500] [NEW] Fix after-suspend-mediacard/sdhc-insert test failed
Public bug reported: [Impact] checkbox test case, after-suspend-mediacard/sdhc-insert, failed. [Fix] [where the issue could happen] low, ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Noble) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2035307 stella ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Tags added: oem-priority originate-from-2035307 stella -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042500 Title: Fix after-suspend-mediacard/sdhc-insert test failed Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: New Status in linux-oem-6.5 source package in Noble: New Bug description: [Impact] checkbox test case, after-suspend-mediacard/sdhc-insert, failed. [Fix] [where the issue could happen] low, To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042500/+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 2042385] Re: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on
** Description changed: [Impact] RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on. [Fix] Realtek r8168h/r8111's ASPM is blocked due to users report the regression on their platform[0]. Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep deeper. + [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814 + [where the issue could happen] Medium, may have the regression but the risk is limited in some Dell platforms. we will ask Realtek's effort once the regression is observed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042385 Title: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: In Progress Bug description: [Impact] RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on. [Fix] Realtek r8168h/r8111's ASPM is blocked due to users report the regression on their platform[0]. Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep deeper. [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814 [where the issue could happen] Medium, may have the regression but the risk is limited in some Dell platforms. we will ask Realtek's effort once the regression is observed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042385/+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 2042385] Re: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on
** Summary changed: - Fix CPU C-state alway keep at C3 when system run PHM with idle screen on + Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on ** Description changed: [Impact] + RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on. [Fix] + Realtek r8168h/r8111's ASPM is blocked due to users report the regression [where the issue could happen] Medium, ** Description changed: [Impact] RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on. [Fix] - Realtek r8168h/r8111's ASPM is blocked due to users report the regression + Realtek r8168h/r8111's ASPM is blocked due to users report the regression on their platform[0]. + Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep deeper. [where the issue could happen] - Medium, + Medium, may have the regression but the risk is limited in some Dell platforms. + we will ask Realtek's effort once the regression is observed. ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Tags added: oem-priority originate-from-2038398 somerville -- 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/2042385 Title: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: In Progress Bug description: [Impact] RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on. [Fix] Realtek r8168h/r8111's ASPM is blocked due to users report the regression on their platform[0]. Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep deeper. [where the issue could happen] Medium, may have the regression but the risk is limited in some Dell platforms. we will ask Realtek's effort once the regression is observed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042385/+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 2042385] Re: Fix CPU C-state alway keep at C3 when system run PHM with idle screen on
** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) 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/2042385 Title: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Bug description: [Impact] RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on. [Fix] Realtek r8168h/r8111's ASPM is blocked due to users report the regression [where the issue could happen] Medium, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042385/+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 2042385] [NEW] Fix CPU C-state alway keep at C3 when system run PHM with idle screen on
Public bug reported: [Impact] [Fix] [where the issue could happen] Medium, ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Jammy) 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/2042385 Title: Fix CPU C-state alway keep at C3 when system run PHM with idle screen on Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Bug description: [Impact] [Fix] [where the issue could happen] Medium, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042385/+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 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
Reply #2 ~~~ $ uname -a Linux 6.5.0-1005-oem #5-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 6 12:13:41 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec 0 $ sudo rtcwake -m mem -s 5 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Oct 13 11:09:41 2023 $ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec 4127220 ~~~ Reply #1 ~~~ $ uname -a Linux 6.1.0-1024-oem #24-Ubuntu SMP PREEMPT_DYNAMIC Wed Oct 4 10:18:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec [sudo] password for u: 4127220 $ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec 4127220 $ sudo rtcwake -m mem -s 5 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Oct 13 11:27:32 2023 $ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec 4800390 ~~~ ** Tags removed: verification-needed-jammy-linux-oem-6.1 ** Tags added: verification-done-jammy-linux-oem-6.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2037493 Title: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec&package_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037493/+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 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
Reply #2 ~~~ u@u-OptiPlex-SFF-7010:~$ uname -a Linux u-OptiPlex-SFF-7010 6.5.0-1005-oem #5-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 6 12:13:41 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux u@u-OptiPlex-SFF-7010:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec 0 u@u-OptiPlex-SFF-7010:~$ sudo rtcwake -m mem -s 5 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Oct 13 11:09:41 2023 u@u-OptiPlex-SFF-7010:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec 4127220 ~~~ ** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2037493 Title: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec&package_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037493/+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 2028830] Re: [mpt3sas, UBSAN] ]linux 6.5-rc give error messages at boot
@Keeley, please check the comments from here https://lore.kernel.org/lkml/202310101748.5E39C3A@keescook/ -- 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/2028830 Title: [mpt3sas, UBSAN] ]linux 6.5-rc give error messages at boot Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu release: sune@jekaterina:~/src/deb$ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 sune@jekaterina:~/src/deb$ Package: linux-image- unsigned-6.5.0-060500rc1-generic_6.5.0-060500rc1.202307232333_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline (rc2 and rc3 also affected) Expectation: System boots normally Actual results: See below On the request of Koba Ko on the kernel-t...@lists.ubuntu.com mailing list, I hereby submit the following: Do note that two "types" are mentioned, and that I am willing the assist in testing, as, obviously, I have a system with a controller covered by the mpt3sas driver. This is output from attempted boot of 6.5-rc3 from kernel-ppa, but it is similar to rcs 1 and 2: UBSAN: array-index-out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/npt3sas/mpt3sas_scsih.c:4667:12 index 1 is out of range for type ’MPI12_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih-c:4023:12 index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6810:36 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6598:38 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6602:36 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux-drivers/scsi/mpt3sas/mpt3sas_scsih.c:6619:7 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c::21 index 1 is out of range for type ’MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7649:32 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index-out-of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7651:23 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7655:12 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [EDIT] the next error, repeating for ~1½ hours before finishing boot, was unrelated to mpt2sas and UBSAN. That error was "Timed out for waiting the udey queue being empty." Bug subject altered to reflect this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028830/+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 2038288] Re: Failed to start thermald.service
** Changed in: thermald (Ubuntu) Status: New => In Progress ** Changed in: thermald (Ubuntu) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2038288 Title: Failed to start thermald.service Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: In Progress Bug description: Get lot of thermald errors logged with that Mate session on Mantic dbus-broker-launch[775]: Invalid group-name in /usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power" systemd[1]: Starting thermald.service - Thermal Daemon Service... thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[892]: sensor id 10 : No temp sysfs for reading raw temp thermald[892]: sensor id 10 : No temp sysfs for reading raw temp thermald[892]: sensor id 10 : No temp sysfs for reading raw temp thermald[892]: *** stack smashing detected ***: terminated systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT systemd[1]: thermald.service: Failed with result 'signal'. systemd[1]: Failed to start thermald.service - Thermal Daemon Service. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[982]: *** stack smashing detected ***: terminated systemd[1]: Started thermald.service - Thermal Daemon Service. thermald[982]: sensor id 10 : No temp sysfs for reading raw temp thermald[982]: sensor id 10 : No temp sysfs for reading raw temp thermald[982]: sensor id 10 : No temp sysfs for reading raw temp systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT systemd[1]: thermald.service: Failed with result 'signal'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp thermald[1049]: *** stack smashing detected ***: terminated systemd[1]: Started thermald.service - Thermal Daemon Service. systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: thermald.service: Failed with result 'core-dump'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... systemd[1]: Started thermald.service - Thermal Daemon Service. thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp thermald[1117]: *** stack smashing detected ***: terminated systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: thermald.service: Failed with result 'core-dump'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... systemd[1]: Started thermald.service - Thermal Daemon Service. thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp thermald[1180]: *** stack smashing detected ***: terminated systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: thermald.service: Failed with result 'core-dump'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: thermald.service: Start request repeated too quic
[Kernel-packages] [Bug 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
** Description changed: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. - 3. suspend then check slp_s0_residency_usec + 3. suspend then check slp_s0_residency_usec&package_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. -- 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/2037493 Title: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.5 source package in Lunar: New Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: New Bug description: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec&package_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037493/+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 2037493] [NEW] Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
Public bug reported: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Lunar) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Tags: flying-fox oem-priority originate-from-2025203 originate-from-2027772 ** Description changed: [Impact] - System can't enter suspend on AHCI mode, - the CPU FAN and System FAN is running, PSU LED is on. + System can't enter suspend on AHCI mode, + the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... - rtcwake: wakeup from "mem" using /dev/rtc0 at Wed Jul 19 05:13:56 2023 + rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. ** Tags added: flying-fox oem-priority originate-from-2025203 ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Tags added: originate-from-2027772 ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because yo
[Kernel-packages] [Bug 2028830] Re: [mpt3sas, UBSAN] ]linux 6.5-rc give error messages at boot
** Changed in: linux (Ubuntu) Status: In Progress => Incomplete -- 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/2028830 Title: [mpt3sas, UBSAN] ]linux 6.5-rc give error messages at boot Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu release: sune@jekaterina:~/src/deb$ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 sune@jekaterina:~/src/deb$ Package: linux-image- unsigned-6.5.0-060500rc1-generic_6.5.0-060500rc1.202307232333_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline (rc2 and rc3 also affected) Expectation: System boots normally Actual results: See below On the request of Koba Ko on the kernel-t...@lists.ubuntu.com mailing list, I hereby submit the following: Do note that two "types" are mentioned, and that I am willing the assist in testing, as, obviously, I have a system with a controller covered by the mpt3sas driver. This is output from attempted boot of 6.5-rc3 from kernel-ppa, but it is similar to rcs 1 and 2: UBSAN: array-index-out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/npt3sas/mpt3sas_scsih.c:4667:12 index 1 is out of range for type ’MPI12_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih-c:4023:12 index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6810:36 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6598:38 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6602:36 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux-drivers/scsi/mpt3sas/mpt3sas_scsih.c:6619:7 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c::21 index 1 is out of range for type ’MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7649:32 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index-out-of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7651:23 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7655:12 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [EDIT] the next error, repeating for ~1½ hours before finishing boot, was unrelated to mpt2sas and UBSAN. That error was "Timed out for waiting the udey queue being empty." Bug subject altered to reflect this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028830/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
@Joseph, please try #5.15 sudo apt install linux-image-generic #6.2 sudo apt install linux-image-generic-hwe-22.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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
@Eli, may i know it it a brand-new notebook? in the logs, there's one entry to limit your cpu. this is came from bios through ACPI. ~~~ 1694076246][INFO]index 2: type:passive temp:9 hyst:1000 zone id:6 sensor id:6 control_type:1 cdev size:4 ~~~ the cpu temperatrue is 93000 that exceed temp:9, so thermald try to cool the cpu, ~~~ [1694076254][DEBUG]pref 0 type 3 temp 91000 trip 9 [1694076254][DEBUG]Passive Trip point applicable [1694076254][DEBUG]Trip point applicable > 2:9 [1694076254][DEBUG]cdev size for this trippoint 4 [1694076254][DEBUG]cdev at index 27:rapl_controller [1694076254][DEBUG]>>thd_cdev_set_state temperature 9:91000 index:27 state:1 :zone:6 trip_id:2 target_state_valid:0 target_value :0 force:0 min_state:0 max_state:0 ~~~ if this's a brand-new notebook, you should contact the vendor first. if not, we need to investigate further. thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: In Progress Bug description: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install un
Re: [Kernel-packages] [Bug 2028217] Re: MTL: Add support for Meteor Lake
Verified, ~~~ $ sudo systemctl status thermald ● thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2023-09-13 17:42:10 CST; 4min 19s ago Main PID: 1053 (thermald) Tasks: 2 (limit: 8916) Memory: 1.0M CPU: 29ms CGroup: /system.slice/thermald.service └─1053 /usr/sbin/thermald --systemd --dbus-enable --adaptive Sep 13 17:42:10 ubuntu thermald[1053]: 32 CPUID levels; family:model:stepping 0x6:aa:2 (6:170:2) Sep 13 17:42:10 ubuntu thermald[1053]: NO RAPL sysfs present Sep 13 17:42:10 ubuntu thermald[1053]: 32 CPUID levels; family:model:stepping 0x6:aa:2 (6:170:2) Sep 13 17:42:10 ubuntu thermald[1053]: sensor id 11 : No temp sysfs for reading raw temp Sep 13 17:42:10 ubuntu thermald[1053]: sensor id 11 : No temp sysfs for reading raw temp Sep 13 17:42:10 ubuntu thermald[1053]: sensor id 11 : No temp sysfs for reading raw temp Sep 13 17:42:10 ubuntu thermald[1053]: Config file /etc/thermald/thermal-conf.xml does not exist Sep 13 17:42:10 ubuntu thermald[1053]: Config file /etc/thermald/thermal-conf.xml does not exist Sep 13 17:42:10 ubuntu thermald[1053]: Config file /etc/thermald/thermal-conf.xml does not exist Sep 13 17:42:10 ubuntu thermald[1053]: Polling mode is enabled: 4 ~~~ $ uname -a Linux ubuntu 6.2.0-34-generic #34~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 7 13:12:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ubuntu:~$ sudo apt policy thermald thermald: Installed: 2.4.9-1ubuntu0.4 Candidate: 2.4.9-1ubuntu0.4 Version table: *** 2.4.9-1ubuntu0.4 500 500 http://tw.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2.4.9-1ubuntu0.3 500 500 http://tw.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 2.4.9-1 500 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ~~~ ** Attachment added: "Screenshot from 2023-09-13 17-46-54.png" https://bugs.launchpad.net/bugs/2028217/+attachment/5700539/+files/Screenshot%20from%202023-09-13%2017-46-54.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2028217 Title: MTL: Add support for Meteor Lake Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Won't Fix Status in thermald source package in Jammy: Fix Committed Status in thermald source package in Kinetic: Won't Fix Status in thermald source package in Lunar: Won't Fix Status in thermald source package in Mantic: Fix Released Bug description: [Impact] * Support thermald on Meteor Lake CPU. [Test Plan] * Use a machine with a Meteor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change adds support for Meteor Lake in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2028217/+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
Re: [Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
@Eli, could you run this scripts and upload the log? thanks ~~~ // could find this repor, https://github.com/intel/thermal_daemon thermal_daemon/test/thermal-debug-dump-ubuntu.sh ~~~ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: In Progress Bug description: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install undervolt==0.3.0) to force particular power limits (the provided values are intentional overkill): 1 │ from undervolt import read_power_limit, set_power_limit, PowerLimit, ADDRESSES 2 │ from pprint import pprint 3 │ 4 │ limits = read_power_limit(ADDRESSES) 5 │ pprint(vars(limits)) # print current values before setting them 6 │ 7 │ POWER_LIMITS = PowerLimit() 8 │ POWER_LIMITS.locked = True # lock means don't allow the value to be reset until a reboot. 9 │ POWER_LIMITS.backup_rest = 281474976776192 # afaik this is just a backup-on-failure setting, it has no effect here. 10 │ POWER_LIMITS.long_term_enabled = Tru
[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
@Eli, re-built with 23.04, would you please have a try, thanks https://drive.google.com/drive/folders/1XmxwqgiUB_vjLRWiIaSpzXc89ilSwItx?usp=sharing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: In Progress Bug description: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install undervolt==0.3.0) to force particular power limits (the provided values are intentional overkill): 1 │ from undervolt import read_power_limit, set_power_limit, PowerLimit, ADDRESSES 2 │ from pprint import pprint 3 │ 4 │ limits = read_power_limit(ADDRESSES) 5 │ pprint(vars(limits)) # print current values before setting them 6 │ 7 │ POWER_LIMITS = PowerLimit() 8 │ POWER_LIMITS.locked = True # lock means don't allow the value to be reset until a reboot. 9 │ POWER_LIMITS.backup_rest = 281474976776192 # afaik this is just a backup-on-failure setting, it has no effect here. 10 │ POWER_LIMITS.long_term_enabled = True 11 │ POWER_LIMITS.long_te
[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
@Eli, are you using 23.04/22.04? I built with 22.04 configuration. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: In Progress Bug description: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install undervolt==0.3.0) to force particular power limits (the provided values are intentional overkill): 1 │ from undervolt import read_power_limit, set_power_limit, PowerLimit, ADDRESSES 2 │ from pprint import pprint 3 │ 4 │ limits = read_power_limit(ADDRESSES) 5 │ pprint(vars(limits)) # print current values before setting them 6 │ 7 │ POWER_LIMITS = PowerLimit() 8 │ POWER_LIMITS.locked = True # lock means don't allow the value to be reset until a reboot. 9 │ POWER_LIMITS.backup_rest = 281474976776192 # afaik this is just a backup-on-failure setting, it has no effect here. 10 │ POWER_LIMITS.long_term_enabled = True 11 │ POWER_LIMITS.long_term_power = 160 # values are intentional overkill 12 │ POWER_LIMITS.long
[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
hi, would you please help me to try vanilla kernel? check if the issue is still here？ https://drive.google.com/drive/folders/1AFgeX8_USkR9omba8E-D-cJsaDuhzKLW?usp=sharing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: In Progress Bug description: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install undervolt==0.3.0) to force particular power limits (the provided values are intentional overkill): 1 │ from undervolt import read_power_limit, set_power_limit, PowerLimit, ADDRESSES 2 │ from pprint import pprint 3 │ 4 │ limits = read_power_limit(ADDRESSES) 5 │ pprint(vars(limits)) # print current values before setting them 6 │ 7 │ POWER_LIMITS = PowerLimit() 8 │ POWER_LIMITS.locked = True # lock means don't allow the value to be reset until a reboot. 9 │ POWER_LIMITS.backup_rest = 281474976776192 # afaik this is just a backup-on-failure setting, it has no effect here. 10 │ POWER_LIMITS.long_term_enabled = True 11
[Kernel-packages] [Bug 2028217] Re: MTL: Add support for Meteor Lake
Verified ~~~ thermald[6941]: 32 CPUID levels; family:model:stepping 0x6:aa:2 (6:170:2) thermald[6941]: NO RAPL sysfs present thermald[6941]: 32 CPUID levels; family:model:stepping 0x6:aa:2 (6:170:2) thermald[6941]: sensor id 11 : No temp sysfs for reading raw temp thermald[6941]: sensor id 11 : No temp sysfs for reading raw temp thermald[6941]: sensor id 11 : No temp sysfs for reading raw temp thermald[6941]: Config file /etc/thermald/thermal-conf.xml does not exist thermald[6941]: Config file /etc/thermald/thermal-conf.xml does not exist thermald[6941]: Config file /etc/thermald/thermal-conf.xml does not exist thermald[6941]: Polling mode is enabled: 4 $ uname -a Linux ubuntu 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ~~~ ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2028217 Title: MTL: Add support for Meteor Lake Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Won't Fix Status in thermald source package in Jammy: Fix Committed Status in thermald source package in Kinetic: Won't Fix Status in thermald source package in Lunar: Won't Fix Status in thermald source package in Mantic: Fix Released Bug description: [Impact] * Support thermald on Meteor Lake CPU. [Test Plan] * Use a machine with a Meteor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change adds support for Meteor Lake in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2028217/+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 2033348] Re: Wireless: Update RTL8852BE wifi driver
@Dave, could you provide the details about issue? [Symptom] [Description for fix] [Reproduced processes] -- 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/2033348 Title: Wireless: Update RTL8852BE wifi driver Status in linux package in Ubuntu: Incomplete Bug description: Firmware 0.27 was added in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002601 but there has been an update submitted by Realtek which resolves crash issues of the driver related to DMA. New firmware file is up in kernel: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/log/rtw89/rtw8852b_fw-1.bin?showmsg=1 Ideally updated for both Lunar and Jammy :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033348/+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 2018236] Re: Fix ADL: System shutdwon automically when run Prime95&stress-ng with i9-12900K
@Andreas, re-ran the test case for 7 hours and system didn't reboot. run stress-ng and mprime simutaneously. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2018236 Title: Fix ADL: System shutdwon automically when run Prime95&stress-ng with i9-12900K Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Description] System shutdown automatically when stressing the machine. [Fix] Need these two to fix the issue. cbdd92b) Parse idsp and trips d385f20) Use PL1 max/min from PPCC when policies match https://github.com/intel/thermal_daemon/commit/d385f20764e1e5477450405be71ec719adc973be [Test Case] 1. Find a unit with i9-12900k CPU and air cooling 2. Install tools #sudo apt install stress-ng s-tui #sudo systemctl stop thermald #sudo thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.txt & #download prime95 linux version: p95v308b15.linux64.tar.gz and decompress 4. Stress test: (you may need to open multiple terminals for the test) #./mprime #sudo stress-ng -a 0 --class cpu,cpu-cache --ignite-cpu -v 5. monitor cpu temperature for 6 hours if you didn’t hit overheat and shutdown issue. #sudo s-tui -c [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018236/+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 1981087] Re: thermald prematurely throttling GPU
put cpu-load and gpu-laod simultaneously 1. cpu-load, phoronix-test-suite benchmark compress-7zip 2. gpu-load, phoronix-test-suite benchmark unigine-super resolution: 2560*, full-screen, ultra quality. use nvidia-smi to monitor gpu temperature, performance and utilization #sudo nvidia-smi -pm 1, watch -n 1 nvidia-smi kernel, ~~~ $ uname -a Linux u 6.0.0-1020-oem #20-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 14 13:12:17 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ~~~ With 2.4.9-1ubuntu0.2, observed the gpu was put into P3(performance state), the max power watt is limited under 30W. the gpu temperature is under 70 and lower. even cpu load is finished, the p state of gpu is still P3 and gpu performance is limited. gpu load is still running after cpu load is finished. With 2.4.9-1ubuntu0.3, didn't observe the throttled symptom during run cpu&gpu load. gpu is keepin in P0 and max power watt, 80w. the gpu temperature is over 70 and higher. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981087 Title: thermald prematurely throttling GPU Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * thermald prematurely throttling GPU [Fix] This fix is removed the code refactoring part and keep the necessary. (patch: 0009-Install-passive-default.patch) 82609c7) Separate Adaptive engine and GDDV [Test Plan] Test1, * Run game on the target machine. * the FPS must not be significantly reduced. Test2, * Run on others platform, ADL/TGL/CML/CFL/KBL. * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine runs normally. [Where problems could occur] * better support for Passive Policy. currently passive policy 1 is supported and it should have a bug if the machine only enable pssive policy 2. ~~~ I got a new game and started playing it It would run at over 100 FPS solidly some of the time and then cyclically dip down to below 20 FPS for a few minutes I determined that it was thermald trying to keep my GPU below 70°C to determine this I sudo systemctl stop thermald The game ran solidly and consistently with the GPU at 75°C This is well below the specs set by the manufacturer and perhaps unreasonably low for a laptop But more importantly I was given no indication this was happening. I had to sleuth it out myself. Perhaps it is impossible to determine good defaults for all hardware, I don't know. However without an indication that this is happening there will be a lot of people with a mysteriously broken experience. This was extremely difficult for me to find and I had several friend who are experts on linux gaming and video drivers trying to track this down. I discovered it by luck and perseverance. This absolutely needs some sort of indication and hopefully a way to remedy it from the GUI. ideally it would set thermal limits that are more in line with what the device is designed for and not a conservative default if at all possible. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thermald 2.4.9-1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Jul 8 16:08:55 2022 InstallationDate: Installed on 2020-10-19 (626 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: thermald UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1981087/+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 2018236] Re: Fix ADL: System shutdwon automically when run Prime95&stress-ng with i9-12900K
@Andreas, as per personal experience, if issue is occurred, it would shutdown less than 10 mins. so is it necessary to run 6 hours? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2018236 Title: Fix ADL: System shutdwon automically when run Prime95&stress-ng with i9-12900K Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Description] System shutdown automatically when stressing the machine. [Fix] Need these two to fix the issue. cbdd92b) Parse idsp and trips d385f20) Use PL1 max/min from PPCC when policies match https://github.com/intel/thermal_daemon/commit/d385f20764e1e5477450405be71ec719adc973be [Test Case] 1. Find a unit with i9-12900k CPU and air cooling 2. Install tools #sudo apt install stress-ng s-tui #sudo systemctl stop thermald #sudo thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.txt & #download prime95 linux version: p95v308b15.linux64.tar.gz and decompress 4. Stress test: (you may need to open multiple terminals for the test) #./mprime #sudo stress-ng -a 0 --class cpu,cpu-cache --ignite-cpu -v 5. monitor cpu temperature for 6 hours if you didn’t hit overheat and shutdown issue. #sudo s-tui -c [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018236/+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 2007579] Re: Raptor Lake Thermald ITMT version 2 support
@Andreas, correct it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2007579 Title: Raptor Lake Thermald ITMT version 2 support Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Bionic: Won't Fix Status in thermald source package in Focal: Won't Fix Status in thermald source package in Jammy: Fix Committed Status in thermald source package in Kinetic: Fix Released Status in thermald source package in Lunar: Fix Released Bug description: == SRU Justification Kinetic == Raptor Lake system uses ITMT v2 instead of V1 for thermal configuration via GDDV. This was observed on Dell XPS 9320 system. Because thermald can't parse V2 table, it is not getting correct thermal threshold temperature and power limits. == The Fix == This is fixed in upstream thermald by the patch: https://github.com/intel/thermal_daemon/commit/90d56bc06cdcf78e7398ea7da389401516591774 This fix is part of Thermald 2.5.2 release. The fix applies cleanly and this is already in Ubuntu Lunar in thermald 2.5.2. The fix checks for illegal ITMT version and handles version 2 as a specific exceptional case. == Regression Risks == For systems that do not used ITMT, no change in behaviour will occur. Systems with versions > 2 (currently not valid) will not have ITMT parsed anymore; this will avoid misinterpreting unsupported ITMT data. Finally, version 2 of ITMT will be now parsed differently and additional fields will be parsed and these will be ignored as intended. == Test Plan == Test against a Dell XPS 9320 system. See if it handles the ITMT correctly. The thermald log should indicate version 2 is being used with the message: "ignore dummy_str: ds d1 d2 d3 " where ds = a string, d1 .. d3 are uint64 values that are parsed and ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2007579/+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 2012260] Re: Add support for Alder Lake N
@Andreas, it also work on generic jammy kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2012260 Title: Add support for Alder Lake N Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Status in thermald source package in Kinetic: Won't Fix Bug description: [Impact] * Support thermald on Alder Lake N CPU. [Test Plan] * Use a machine with a Alder Lake N cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Alder Lake N in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2012260/+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 1981087] Re: thermald prematurely throttling GPU
@Andreas, for the test 1, actually i can't hit the issue on my side so just show the benchmark between the proposded and upstream version. i can ran the previous version to compare. i still need Colette's help to verify but didnt get the reply. for test 2, it just to run thermald and check if the cpu is throttled. please review this in LP#1995606, #25. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981087 Title: thermald prematurely throttling GPU Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * thermald prematurely throttling GPU [Fix] This fix is removed the code refactoring part and keep the necessary. (patch: 0009-Install-passive-default.patch) 82609c7) Separate Adaptive engine and GDDV [Test Plan] Test1, * Run game on the target machine. * the FPS must not be significantly reduced. Test2, * Run on others platform, ADL/TGL/CML/CFL/KBL. * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine runs normally. [Where problems could occur] * better support for Passive Policy. currently passive policy 1 is supported and it should have a bug if the machine only enable pssive policy 2. ~~~ I got a new game and started playing it It would run at over 100 FPS solidly some of the time and then cyclically dip down to below 20 FPS for a few minutes I determined that it was thermald trying to keep my GPU below 70°C to determine this I sudo systemctl stop thermald The game ran solidly and consistently with the GPU at 75°C This is well below the specs set by the manufacturer and perhaps unreasonably low for a laptop But more importantly I was given no indication this was happening. I had to sleuth it out myself. Perhaps it is impossible to determine good defaults for all hardware, I don't know. However without an indication that this is happening there will be a lot of people with a mysteriously broken experience. This was extremely difficult for me to find and I had several friend who are experts on linux gaming and video drivers trying to track this down. I discovered it by luck and perseverance. This absolutely needs some sort of indication and hopefully a way to remedy it from the GUI. ideally it would set thermal limits that are more in line with what the device is designed for and not a conservative default if at all possible. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thermald 2.4.9-1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Jul 8 16:08:55 2022 InstallationDate: Installed on 2020-10-19 (626 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: thermald UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1981087/+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 2028800] Re: Kubuntu 23.04 boots with 6.2.0-24-generic but not 6.2.0-25-generic or 6.2.0-26-generic
maybe you also need linux-modules-extra-6.2.0-25-generic -- 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/2028800 Title: Kubuntu 23.04 boots with 6.2.0-24-generic but not 6.2.0-25-generic or 6.2.0-26-generic Status in linux package in Ubuntu: New Bug description: I can run Kubuntu 23.04 with kernel 6.2.0-24-generic but not 6.2.0-25-generic or 6.2.0-26-generic. I have installed the latest AMD microcode, but that did not help. I am attaching the journalctl report for 6.2.0-24-generic that boots fully and the journalctl report for 6.2.0-26-generic that does not boot fully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028800/+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 2028830] Re: [mpt3sas, UBSAN] ]linux 6.5-rc won't boot
** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => koba (kobako) -- 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/2028830 Title: [mpt3sas, UBSAN] ]linux 6.5-rc won't boot Status in linux package in Ubuntu: In Progress Bug description: Ubuntu release: sune@jekaterina:~/src/deb$ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 sune@jekaterina:~/src/deb$ Package: linux-image- unsigned-6.5.0-060500rc1-generic_6.5.0-060500rc1.202307232333_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline (rc2 and rc3 also affected) Expectation: System boots normally Actual results: See below On the request of Koba Ko on the kernel-t...@lists.ubuntu.com mailing list, I hereby submit the following: Do note that two "types" are mentioned, and that I am willing the assist in testing, as, obviously, I have a system with a controller covered by the mpt3sas driver. This is output from attempted boot of 6.5-rc3 from kernel-ppa, but it is similar to rcs 1 and 2: UBSAN: array-index-out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/npt3sas/mpt3sas_scsih.c:4667:12 index 1 is out of range for type ’MPI12_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih-c:4023:12 index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6810:36 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6598:38 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6602:36 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux-drivers/scsi/mpt3sas/mpt3sas_scsih.c:6619:7 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c::21 index 1 is out of range for type ’MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7649:32 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index-out-of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7651:23 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7655:12 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' Timed out for waiting the udey queue being empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028830/+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 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
@Eli, could you provide the thermald logs? thanks #sudo systemctl stop thermald #sudo thermald --no-daemon --adaptive --loglevel=debug >> thermald_debug_202307270935 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: New Bug description: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install undervolt==0.3.0) to force particular power limits (the provided values are intentional overkill): 1 │ from undervolt import read_power_limit, set_power_limit, PowerLimit, ADDRESSES 2 │ from pprint import pprint 3 │ 4 │ limits = read_power_limit(ADDRESSES) 5 │ pprint(vars(limits)) # print current values before setting them 6 │ 7 │ POWER_LIMITS = PowerLimit() 8 │ POWER_LIMITS.locked = True # lock means don't allow the value to be reset until a reboot. 9 │ POWER_LIMITS.backup_rest = 281474976776192 # afaik this is just a backup-on-failure setting, it has no effect here. 10 │ POWER_LIMITS.long_term_enabled = True 11 │ POWER_LIM
[Kernel-packages] [Bug 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)
@Chris, Sure, this's my regular processes but didn't collect the logs. I will update the logs about this test cases. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: Fix Committed Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1995606/+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 1981525] Re: Add support for Raptor Lake CPUs
** Changed in: thermald (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981525 Title: Add support for Raptor Lake CPUs Status in OEM Priority Project: Fix Committed Status in OEM Priority Project focal series: Fix Committed Status in thermald package in Ubuntu: Invalid Status in thermald source package in Focal: In Progress Status in thermald source package in Jammy: Fix Released Bug description: [Impact] * Support thermald on Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/354 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981525/+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 1989044] Re: RPL: Add INT3400 base path
** Also affects: thermald (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: thermald (Ubuntu Focal) Status: New => In Progress ** Changed in: thermald (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1989044 Title: RPL: Add INT3400 base path Status in thermald package in Ubuntu: New Status in thermald source package in Focal: In Progress Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * Add INT3400 base path for Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * check the thermald log. * Get the base path of INT3400. [Where problems could occur] * This change is to add path in INT3400 for Raptor Lake, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1989044/+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 1981525] Re: Add support for Raptor Lake CPUs
** Also affects: oem-priority/focal Importance: Critical Assignee: Dirk Su (dirksu) Status: Fix Committed ** Changed in: thermald (Ubuntu) Status: Fix Released => Invalid ** Changed in: thermald (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: thermald (Ubuntu) Assignee: koba (kobako) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981525 Title: Add support for Raptor Lake CPUs Status in OEM Priority Project: Fix Committed Status in OEM Priority Project focal series: Fix Committed Status in thermald package in Ubuntu: Invalid Status in thermald source package in Jammy: Fix Released Bug description: [Impact] * Support thermald on Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/354 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981525/+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 2028217] [NEW] MTL: Add support for Mateor Lake
Public bug reported: [Impact] * Support thermald on Mateor Lake CPU. [Test Plan] * Use a machine with a Mateor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Mateor Lake in thermald, which won't impact other hardware. ** Affects: thermald (Ubuntu) Importance: Undecided Status: New ** Affects: thermald (Ubuntu Focal) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: thermald (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: thermald (Ubuntu Kinetic) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: thermald (Ubuntu Lunar) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Also affects: thermald (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: thermald (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: thermald (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: thermald (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: thermald (Ubuntu Focal) Status: New => In Progress ** Changed in: thermald (Ubuntu Jammy) Status: New => In Progress ** Changed in: thermald (Ubuntu Kinetic) Status: New => In Progress ** Changed in: thermald (Ubuntu Lunar) Status: New => In Progress ** Changed in: thermald (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Changed in: thermald (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: thermald (Ubuntu Kinetic) Assignee: (unassigned) => koba (kobako) ** Changed in: thermald (Ubuntu Lunar) Assignee: (unassigned) => koba (kobako) ** Summary changed: - MTL: Add support for Meter Lake + MTL: Add support for Mateor Lake ** Description changed: - [Description] + [Impact] + + * Support thermald on Mateor Lake CPU. + + [Test Plan] + + * Use a machine with a Mateor Lake cpu. + + * systemctl status thermald + + * Status of thermald should be `running` + + [Where problems could occur] + + * This change is to add support for Mateor Lake in thermald, which + won't impact other hardware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2028217 Title: MTL: Add support for Mateor Lake Status in thermald package in Ubuntu: New Status in thermald source package in Focal: In Progress Status in thermald source package in Jammy: In Progress Status in thermald source package in Kinetic: In Progress Status in thermald source package in Lunar: In Progress Bug description: [Impact] * Support thermald on Mateor Lake CPU. [Test Plan] * Use a machine with a Mateor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Mateor Lake in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2028217/+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 2012260] Re: Add support for Alder Lake N
** Changed in: thermald (Ubuntu Kinetic) Status: New => In Progress ** Changed in: thermald (Ubuntu Kinetic) Assignee: (unassigned) => koba (kobako) ** Changed in: thermald (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2012260 Title: Add support for Alder Lake N Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Status in thermald source package in Kinetic: In Progress Bug description: [Impact] * Support thermald on Alder Lake N CPU. [Test Plan] * Use a machine with a Alder Lake N cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Alder Lake N in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2012260/+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 2027957] Re: Fix AMDGPU: the screen freeze with W7500
** Description changed: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. Solution is, - Detect Intel x86 systems that don't support dynamic switching - Override the input caps to maximum supported for that system - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] low, this could lead issue when setting higher speeds than supported. + + [Misc] + 1. jammy, amdgpu isn't loaded on this platform with 5.15-73-generic. + 2. kinetic, amdgpu failed to probe the vga controller with 5.19-46-generic. ** Description changed: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. Solution is, - Detect Intel x86 systems that don't support dynamic switching - Override the input caps to maximum supported for that system - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] low, this could lead issue when setting higher speeds than supported. [Misc] 1. jammy, amdgpu isn't loaded on this platform with 5.15-73-generic. 2. kinetic, amdgpu failed to probe the vga controller with 5.19-46-generic. + 3. Passed cbd build against Mantic&Lunar. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2027957 Title: Fix AMDGPU: the screen freeze with W7500 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: New Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: New Bug description: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. Solution is, - Detect Intel x86 systems that don't support dynamic switching - Override the input caps to maximum supported for that system - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] low, this could lead issue when setting higher speeds than supported. [Misc] 1. jammy, amdgpu isn't loaded on this platform with 5.15-73-generic. 2. kinetic, amdgpu failed to probe the vga controller with 5.19-46-generic. 3. Passed cbd build against Mantic&Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027957/+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 2027957] Re: Fix AMDGPU: the screen freeze with W7500
#Jammy, amdgpu isn't loaded in boot against 5.15.0-73-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2027957 Title: Fix AMDGPU: the screen freeze with W7500 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: New Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: New Bug description: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. Solution is, - Detect Intel x86 systems that don't support dynamic switching - Override the input caps to maximum supported for that system - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] low, this could lead issue when setting higher speeds than supported. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027957/+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 2027957] Re: Fix AMDGPU: the screen freeze with W7500
Failed to probe amdgpu with 5.19.0-46-generic ~~~ $ sudo dmesg | grep -ie amdgpu [5.065150] [drm] amdgpu kernel modesetting enabled. [5.065224] amdgpu: CRAT table not found [5.065226] amdgpu: Virtual CRAT table created for CPU [5.065231] amdgpu: Topology: Add CPU node [5.065349] amdgpu :57:00.0: enabling device (0146 -> 0147) [5.067023] amdgpu :57:00.0: amdgpu: Failed to add dm ip block(DCE_HWIP:0x30201) [5.067025] amdgpu :57:00.0: amdgpu: Fatal error during GPU init [5.067026] amdgpu :57:00.0: amdgpu: amdgpu: finishing device. [5.067206] amdgpu: probe of :57:00.0 failed with error -22 $ uname -a Linux 5.19.0-46-generic #47~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun 21 15:35:31 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ~~~ ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu Jammy) Assignee: koba (kobako) => (unassigned) ** Changed in: linux (Ubuntu Kinetic) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu Kinetic) Assignee: koba (kobako) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2027957 Title: Fix AMDGPU: the screen freeze with W7500 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: New Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: New Bug description: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. Solution is, - Detect Intel x86 systems that don't support dynamic switching - Override the input caps to maximum supported for that system - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] low, this could lead issue when setting higher speeds than supported. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027957/+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 2027957] Re: Fix AMDGPU: the screen freeze with W7500
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => koba (kobako) ** Tags added: oem-priority originate-from-2024460 somerville ** Tags added: originate-from-2026462 -- 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/2027957 Title: Fix AMDGPU: the screen freeze with W7500 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: New Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: New Bug description: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. Solution is, - Detect Intel x86 systems that don't support dynamic switching - Override the input caps to maximum supported for that system - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] low, this could lead issue when setting higher speeds than supported. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027957/+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 2027957] Re: Fix AMDGPU: the screen freeze with W7500
** Description changed: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. - Turn off the dynamic gen/lane switching when platform is Intel. - amdgpu driver would pick the highest gen/lane instead. + - Detect Intel x86 systems that don't support dynamic switching + - Override the input caps to maximum supported for that system + - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] - low, just fix the pci gen/lane. + low, this could lead issue when setting higher speeds than supported. ** Description changed: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. + Solution is, - Detect Intel x86 systems that don't support dynamic switching - Override the input caps to maximum supported for that system - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] low, this could lead issue when setting higher speeds than supported. -- 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/2027957 Title: Fix AMDGPU: the screen freeze with W7500 Status in linux package in Ubuntu: New Bug description: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. Solution is, - Detect Intel x86 systems that don't support dynamic switching - Override the input caps to maximum supported for that system - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] low, this could lead issue when setting higher speeds than supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027957/+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 2027957] Re: Fix AMDGPU: the screen freeze with W7500
** Description changed: [impact] + While booting into OOBE, the screen freeze [AMD W7500 only] [fix] + AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. + Intel CPU may not support the dynamic lane/speed switching. + + Turn off the dynamic gen/lane switching when platform is Intel. + amdgpu driver would pick the highest gen/lane instead. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] + low, just fix the pci gen/lane. -- 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/2027957 Title: Fix AMDGPU: the screen freeze with W7500 Status in linux package in Ubuntu: New Bug description: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. Solution is, - Detect Intel x86 systems that don't support dynamic switching - Override the input caps to maximum supported for that system - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] low, this could lead issue when setting higher speeds than supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027957/+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 2027957] [NEW] Fix AMDGPU: the screen freeze with W7500
Public bug reported: [impact] [fix] [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] ** 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/2027957 Title: Fix AMDGPU: the screen freeze with W7500 Status in linux package in Ubuntu: New Bug description: [impact] [fix] [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027957/+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 1989044] Re: RPL: Add INT3400 base path
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1989044 Title: RPL: Add INT3400 base path Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * Add INT3400 base path for Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * check the thermald log. * Get the base path of INT3400. [Where problems could occur] * This change is to add path in INT3400 for Raptor Lake, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1989044/+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 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)
Verified against thermald-2.4.9-1ubuntu0.3, ~~~ LP#2018275, LP#2018236, LP#2012260, LP#2007579, LP#1989044, LP#1981087 ~~~ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: Fix Committed Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1995606/+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 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: Fix Committed Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1995606/+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 1981087] Re: thermald prematurely throttling GPU
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981087 Title: thermald prematurely throttling GPU Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * thermald prematurely throttling GPU [Fix] This fix is removed the code refactoring part and keep the necessary. (patch: 0009-Install-passive-default.patch) 82609c7) Separate Adaptive engine and GDDV [Test Plan] Test1, * Run game on the target machine. * the FPS must not be significantly reduced. Test2, * Run on others platform, ADL/TGL/CML/CFL/KBL. * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine runs normally. [Where problems could occur] * better support for Passive Policy. currently passive policy 1 is supported and it should have a bug if the machine only enable pssive policy 2. ~~~ I got a new game and started playing it It would run at over 100 FPS solidly some of the time and then cyclically dip down to below 20 FPS for a few minutes I determined that it was thermald trying to keep my GPU below 70°C to determine this I sudo systemctl stop thermald The game ran solidly and consistently with the GPU at 75°C This is well below the specs set by the manufacturer and perhaps unreasonably low for a laptop But more importantly I was given no indication this was happening. I had to sleuth it out myself. Perhaps it is impossible to determine good defaults for all hardware, I don't know. However without an indication that this is happening there will be a lot of people with a mysteriously broken experience. This was extremely difficult for me to find and I had several friend who are experts on linux gaming and video drivers trying to track this down. I discovered it by luck and perseverance. This absolutely needs some sort of indication and hopefully a way to remedy it from the GUI. ideally it would set thermal limits that are more in line with what the device is designed for and not a conservative default if at all possible. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thermald 2.4.9-1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Jul 8 16:08:55 2022 InstallationDate: Installed on 2020-10-19 (626 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: thermald UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1981087/+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 1981087] Re: thermald prematurely throttling GPU
Verified with unigine-super of phoronix-test-suite ~~~ $phoronix-test-suite benchmark unigine-super ~~~ didn't observe the significant difference compared to upstream thermald 2.5.3. ~~~ - thermald-2.4.9_1ubuntu-0.3 > > > > Unigine Superposition 1.0: > pts/unigine-super-1.0.8 [Resolution: 1920 x 1080 - Mode: Fullscreen - Quality: High - Renderer: OpenGL] > Test 1 of 1 > Estimated Trial Run Count:3 > > Estimated Time To Completion: 13 Minutes [03:40 CDT] > Started Run 1 @ 03:28:08 > Started Run 2 @ 03:31:37 > Started Run 3 @ 03:35:03 > > ``` > Resolution: 1920 x 1080 - Mode: Fullscreen - Quality: High - Renderer: OpenGL: > 4.6 > 4.6 > 4.6 > > Average: 4.6 Frames Per Second > Maximum: 5.4 > Deviation: 0.00% > > Comparison of 1,233 OpenBenchmarking.org samples since 14 June 2018; median result: 70.5 Frames Per Second. Box plot of samples: > [ *--!###*##*#*#*---*-*--*-*| * ] > ^ This Result (2nd Percentile): 4.6 > Arc A770 DG2: 101 ^ RTX 3080: 147 ^ RX 6900 XT: 199 ^ > Arc A750 DG2: 96 ^ Gigabyte RX 6800 XT: 177 ^ > RTX 2070 SUPER: 91 ^ RTX 3090: 173 ^ > RX 5700 XT: 81 ^ Gigabyte RX 6800: 163 ^ > ``` > ~~~ - upstream thermald 2.5.3, > Unigine Superposition 1.0: pts/unigine-super-1.0.8 [Resolution: 1920 x 1080 - Mode: Fullscreen - Quality: High - Renderer: OpenGL] Test 1 of 1 Estimated Trial Run Count:3 > > Estimated Time To Completion: 11 Minutes [03:49 CDT] Started Run 1 @ 03:39:42 Started Run 2 @ 03:43:08 Started Run 3 @ 03:46:35 > > Resolution: 1920 x 1080 - Mode: Fullscreen - Quality: High - Renderer: OpenGL: 4.7 4.7 4.7 Average: 4.7 Frames Per Second Maximum: 5.4 Deviation: 0.00% Comparison of 1,233 OpenBenchmarking.org samples since 14 June 2018; median result: 70.5 Frames Per Second. Box plot of samples: [ *--!###*##*#*#*---*-*--*-*| * ] ^ This Result (2nd Percentile): 4.7 Arc A770 DG2: 101 ^ RTX 3080: 147 ^ RX 6900 XT: 199 ^ Arc A750 DG2: 96 ^ Gigabyte RX 6800 XT: 177 ^ RTX 2070 SUPER: 91 ^ RTX 3090: 173 ^ RX 5700 XT: 81 ^ Gigabyte RX 6800: 163 ^ > ~~~ ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981087 Title: thermald prematurely throttling GPU Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * thermald prematurely throttling GPU [Fix] This fix is removed the code refactoring part and keep the necessary. (patch: 0009-Install-passive-default.patch) 82609c7) Separate Adaptive engine and GDDV [Test Plan] Test1, * Run game on the target machine. * the FPS must not be significantly reduced. Test2, * Run on others platform, ADL/TGL/CML/CFL/KBL. * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine runs normally. [Where problems could occur] * better support for Passive Policy. currently passive policy 1 is supported and it should have a bug if the machine only enable pssive policy 2. ~~~ I got a new game and started playing it It would run at over 100 FPS solidly some of the time and then cyclically dip down to below 20 FPS for a few minutes I determined that it was thermald trying to keep my GPU below 70°C to determine this I sudo systemctl stop thermald The game ran solidly and consistently with the GPU at 75°C This is well below the specs set by the manufacturer and perhaps unreasonably low for a laptop But more importantly I was given no indication this was happening. I had to sleuth it out myself. Perhaps it is impossible to determine good defaults for all hardware, I don't know. However without an indication that this is happening there will be a lot of people with a mysteriously broken experience. This was extremely difficult for me to find and I had several friend who are experts on linux gaming and video drivers trying to track this down. I discovered it by luck and perseverance. This absolutely needs some sort of indication and hopefully a way to remedy it from the GUI. ideally it would set thermal limits that are more in line with what the device is designed for and not a conservative default if at all possible. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thermald 2.4.9-1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
[Kernel-packages] [Bug 2021949] Re: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle
Verified, ~~~ $ uname -a Linux u-Precision-5480 5.19.0-47-generic #49-Ubuntu SMP PREEMPT_DYNAMIC Sun Jun 18 20:38:50 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ cat /proc/cpuinfo | head processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 186 model name : 13th Gen Intel(R) CoreT i7-13700H stepping: 2 microcode : 0x4114 cpu MHz : 660.692 cache size : 24576 KB physical id : 0 $ boltctl list ● Dell WD19TB Thunderbolt Dock ├─ type: peripheral ├─ name: WD19TB Thunderbolt Dock ├─ vendor:Dell ├─ uuid: d501-0080-8c1e-0362-0016e0a4d921 ├─ generation:Thunderbolt 3 ├─ status:authorized │ ├─ domain: ca518780-3186-b87d-- │ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ └─ authflags: none ├─ authorized:2023年七月10日 (週一) 01時44分33秒 ├─ connected: 2023年七月10日 (週一) 01時44分33秒 └─ stored:2023年七月10日 (週一) 01時43分54秒 ├─ policy: iommu └─ key:no ~~~ ** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2021949 Title: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Enabling CL1 (Controller Low Power) states during discovery of existing tunnels established by the system firmware can interfere with the operation of those tunnels. The DisplayPort tunnel establishment timeout of 1.5 seconds can be insufficient for some docking stations, leading to blank displays. [Fix] CL1 states are now not enabled during discovery of existing tunnels. The TMU settings also remain unchanged. The timeout is increased to 3 seconds to allow more time for the DisplayPort connection manager handshake, fixing the issue of displays remaining blank. [Test Cases] 1. plug docking station on the host 2. bring up the host and get into desktop. 3. flip docking station's cable. 4. check if the external monitor works well [Where problems could occur] Low, If the handshake actually requires even more than 3 seconds in some cases, the timeout may still need to be increased further. [Misc] Jammy needs more patches to enable the thunderbolt CLx and the SRU will be a huge, so skip Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2021949/+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 2018236] Re: Fix ADL: System shutdwon automically when run Prime95&stress-ng with i9-12900K
Verified with 15 mins and system didn't reboot ~~~ ~$ cat /proc/cpuinfo | head processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 183 model name : 13th Gen Intel(R) Core(TM) i9-13900 stepping: 1 microcode : 0x10e cpu MHz : 2000.000 cache size : 36864 KB physical id : 0 $ uname -a Linux x31-Precision-3260 6.1.0-1014-oem #14-Ubuntu SMP PREEMPT_DYNAMIC Fri May 19 06:02:46 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt policy thermald [sudo] password for x31: thermald: Installed: 2.4.9-1ubuntu0.3 Candidate: 2.4.9-1ubuntu0.3 Version table: *** 2.4.9-1ubuntu0.3 500 500 http://tw.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2.4.9-1ubuntu0.3 500 500 https://ppa.launchpadcontent.net/kobako/exp-thermald/ubuntu jammy/main amd64 Packages 2.4.9-1ubuntu0.2 500 500 http://tw.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 2.4.9-1 500 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ~~~ ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2018236 Title: Fix ADL: System shutdwon automically when run Prime95&stress-ng with i9-12900K Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Description] System shutdown automatically when stressing the machine. [Fix] Need these two to fix the issue. cbdd92b) Parse idsp and trips d385f20) Use PL1 max/min from PPCC when policies match https://github.com/intel/thermal_daemon/commit/d385f20764e1e5477450405be71ec719adc973be [Test Case] 1. Find a unit with i9-12900k CPU and air cooling 2. Install tools #sudo apt install stress-ng s-tui #sudo systemctl stop thermald #sudo thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.txt & #download prime95 linux version: p95v308b15.linux64.tar.gz and decompress 4. Stress test: (you may need to open multiple terminals for the test) #./mprime #sudo stress-ng -a 0 --class cpu,cpu-cache --ignite-cpu -v 5. monitor cpu temperature for 6 hours if you didn’t hit overheat and shutdown issue. #sudo s-tui -c [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018236/+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 2018275] Re: Fix the in-motion function does not work
Verified, ~~~ $ uname -a Linux u-Precision-5480 6.1.0-1016-oem #16-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun 21 08:45:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux #if motion==1, ignore [1688919145][DEBUG]evaluate condition.condition 4 [1688919145][DEBUG]Match motion == 0 :1 [1688919145][DEBUG]evaluate condition set 1 [1688919145][DEBUG]evaluate condition.condition at index 0 ~~~ ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2018275 Title: Fix the in-motion function does not work Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Summary] in-Motion condition doesn't work with adaptive performance policy [Fix] This patch fix the issue, cc0890a59725) Always match motion = 0 [Test cases] 1. Install the Ubuntu 22.04-oem image on BMM4-DVT2-C2X 2. run the thermald applied the fix. #thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.log" and check the log 3. in-motion condition works [Where problems could occur] because motion is always 0, the rules with motion=1 wouldn't be hit. but motion=1 isn't supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018275/+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 2007579] Re: Raptor Lake Thermald ITMT version 2 support
Verified ~~~ $ uname -a Linux u-Precision-5480 6.1.0-1016-oem #16-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun 21 08:45:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ sudo thermald --no-daemon --adaptive --loglevel=debug [1688919145][INFO]thd_read_default_thermal_zones loaded 14 zones [1688919145][INFO]INT3400 Base path is /sys/bus/acpi/devices/INTC10A0:00/physical_node/uuids/ ~~~ ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2007579 Title: Raptor Lake Thermald ITMT version 2 support Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Bionic: Won't Fix Status in thermald source package in Focal: Won't Fix Status in thermald source package in Jammy: Fix Committed Status in thermald source package in Kinetic: Fix Released Status in thermald source package in Lunar: Fix Released Bug description: == SRU Justification Kinetic == Raptor Lake system uses ITMT v2 instead of V1 for thermal configuration via GDDV. This was observed on Dell XPS 9320 system. Because thermald can't parse V2 table, it is not getting correct thermal threshold temperature and power limits. == The Fix == This is fixed in upstream thermald by the patch: https://github.com/intel/thermal_daemon/commit/90d56bc06cdcf78e7398ea7da389401516591774 This fix is part of Thermald 2.5.2 release. The fix applies cleanly and this is already in Ubuntu Lunar in thermald 2.5.2. The fix checks for illegal ITMT version and handles version 2 as a specific exceptional case. == Regression Risks == For systems that do not used ITMT, no change in behaviour will occur. Systems with versions > 2 (currently not valid) will not have ITMT parsed anymore; this will avoid misinterpreting unsupported ITMT data. Finally, version 2 of ITMT will be now parsed differently and additional fields will be parsed and these will be ignored as intended. == Test Plan == Test against a Dell XPS 9320 system. See if it handles the ITMT correctly. The thermald log should indicate version 2 is being used with the message: "ignore dummy_str: ds d1 d2 d3 " where ds = a string, d1 .. d3 are uint64 values that are parsed and ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2007579/+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 1989044] Re: RPL: Add INT3400 base path
Verified, ~~~ $ uname -a Linux u-Precision-5480 6.1.0-1016-oem #16-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun 21 08:45:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ sudo thermald --no-daemon --adaptive --loglevel=debug [1688919145][INFO]thd_read_default_thermal_zones loaded 14 zones [1688919145][INFO]INT3400 Base path is /sys/bus/acpi/devices/INTC10A0:00/physical_node/uuids/ ~~~ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1989044 Title: RPL: Add INT3400 base path Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * Add INT3400 base path for Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * check the thermald log. * Get the base path of INT3400. [Where problems could occur] * This change is to add path in INT3400 for Raptor Lake, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1989044/+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 1981087] Re: thermald prematurely throttling GPU
@Colette, would you please enable the proposed and verfiy against thermald-2.4.9-1ubunt0.3? thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981087 Title: thermald prematurely throttling GPU Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * thermald prematurely throttling GPU [Fix] This fix is removed the code refactoring part and keep the necessary. (patch: 0009-Install-passive-default.patch) 82609c7) Separate Adaptive engine and GDDV [Test Plan] Test1, * Run game on the target machine. * the FPS must not be significantly reduced. Test2, * Run on others platform, ADL/TGL/CML/CFL/KBL. * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine runs normally. [Where problems could occur] * better support for Passive Policy. currently passive policy 1 is supported and it should have a bug if the machine only enable pssive policy 2. ~~~ I got a new game and started playing it It would run at over 100 FPS solidly some of the time and then cyclically dip down to below 20 FPS for a few minutes I determined that it was thermald trying to keep my GPU below 70°C to determine this I sudo systemctl stop thermald The game ran solidly and consistently with the GPU at 75°C This is well below the specs set by the manufacturer and perhaps unreasonably low for a laptop But more importantly I was given no indication this was happening. I had to sleuth it out myself. Perhaps it is impossible to determine good defaults for all hardware, I don't know. However without an indication that this is happening there will be a lot of people with a mysteriously broken experience. This was extremely difficult for me to find and I had several friend who are experts on linux gaming and video drivers trying to track this down. I discovered it by luck and perseverance. This absolutely needs some sort of indication and hopefully a way to remedy it from the GUI. ideally it would set thermal limits that are more in line with what the device is designed for and not a conservative default if at all possible. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thermald 2.4.9-1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Jul 8 16:08:55 2022 InstallationDate: Installed on 2020-10-19 (626 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: thermald UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1981087/+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 2012260] Re: Add support for Alder Lake N
Verified on target machine, ~~~ $ systemctl status thermald.service ● thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2023-07-09 23:28:44 CST; 1s ago Main PID: 1916 (thermald) Tasks: 4 (limit: 9145) Memory: 2.2M CPU: 41ms CGroup: /system.slice/thermald.service └─1916 /usr/sbin/thermald --systemd --dbus-enable --adaptive 七 09 23:28:44 x31-Precision-3260 systemd[1]: Starting Thermal Daemon Service... 七 09 23:28:44 x31-Precision-3260 systemd[1]: Started Thermal Daemon Service. 七 09 23:28:44 x31-Precision-3260 thermald[1916]: 32 CPUID levels; family:model:stepping 0x6:be:0 (6:190:0) 七 09 23:28:44 x31-Precision-3260 thermald[1916]: 32 CPUID levels; family:model:stepping 0x6:be:0 (6:190:0) 七 09 23:28:44 x31-Precision-3260 thermald[1916]: sensor id 8 : No temp sysfs for reading raw temp 七 09 23:28:44 x31-Precision-3260 thermald[1916]: sensor id 8 : No temp sysfs for reading raw temp 七 09 23:28:44 x31-Precision-3260 thermald[1916]: sensor id 8 : No temp sysfs for reading raw temp 七 09 23:28:44 x31-Precision-3260 thermald[1916]: Polling mode is enabled: 4 $ uname -a Linux x31-Precision-3260 6.1.0-1014-oem #14-Ubuntu SMP PREEMPT_DYNAMIC Fri May 19 06:02:46 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ~~~ ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2012260 Title: Add support for Alder Lake N Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Status in thermald source package in Kinetic: New Bug description: [Impact] * Support thermald on Alder Lake N CPU. [Test Plan] * Use a machine with a Alder Lake N cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Alder Lake N in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2012260/+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 2012260] Re: Add support for Alder Lake N
** Tags added: originate-from-2026344 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2012260 Title: Add support for Alder Lake N Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Status in thermald source package in Kinetic: New Bug description: [Impact] * Support thermald on Alder Lake N CPU. [Test Plan] * Use a machine with a Alder Lake N cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Alder Lake N in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2012260/+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 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)
+202307051456, @Raof, @Lucas v3: because the patch, 0004-Fixed-enumeration-of-cpu-thermal-sensors.patch, can't verify on the proper machine, pull it out from patches. ** Patch added: "thermald_jammy_2.4.9-1ubuntu0.3.v3.debdiff" https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+attachment/5683967/+files/thermald_jammy_2.4.9-1ubuntu0.3.v3.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: In Progress Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1995606/+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 2018275] Re: Fix the in-motion function does not work
@Raof, your understandings are correct. Then, "motion=1" isn't supported currently. For apct, the motion variant may not exist in each entries. so extra policy rules maybe hit. if these cause the problem, 1. the apct have the incorrect rules and table needs correction. 2. need fully support in "motion", need to enable the motion variant fully. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2018275 Title: Fix the in-motion function does not work Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: In Progress Bug description: [Summary] in-Motion condition doesn't work with adaptive performance policy [Fix] This patch fix the issue, cc0890a59725) Always match motion = 0 [Test cases] 1. Install the Ubuntu 22.04-oem image on BMM4-DVT2-C2X 2. run the thermald applied the fix. #thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.log" and check the log 3. in-motion condition works [Where problems could occur] because motion is always 0, the rules with motion=1 wouldn't be hit. but motion=1 isn't supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018275/+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 2018275] Re: Fix the in-motion function does not work
** Description changed: [Summary] in-Motion condition doesn't work with adaptive performance policy [Fix] This patch fix the issue, cc0890a59725) Always match motion = 0 [Test cases] 1. Install the Ubuntu 22.04-oem image on BMM4-DVT2-C2X 2. run the thermald applied the fix. #thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.log" and check the log 3. in-motion condition works [Where problems could occur] because motion is always 0, the rules with motion=1 wouldn't be hit. + but motion=1 isn't supported. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2018275 Title: Fix the in-motion function does not work Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: In Progress Bug description: [Summary] in-Motion condition doesn't work with adaptive performance policy [Fix] This patch fix the issue, cc0890a59725) Always match motion = 0 [Test cases] 1. Install the Ubuntu 22.04-oem image on BMM4-DVT2-C2X 2. run the thermald applied the fix. #thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.log" and check the log 3. in-motion condition works [Where problems could occur] because motion is always 0, the rules with motion=1 wouldn't be hit. but motion=1 isn't supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018275/+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 2021949] Re: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle
Verified,
~~~
$ uname -a
Linux u-Precision-5480 6.0.0-1019-oem #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Jun 20
10:50:57 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
$ ubuntu-report show | grep -ie bios -a5
"BIOS": {
"Version": "1.3.0"
},
~~~
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2021949
Title:
Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to
type-C dongle
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
New
Status in linux-oem-6.0 source package in Jammy:
Fix Committed
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Fix Committed
Status in linux-oem-6.0 source package in Lunar:
Invalid
Status in linux-oem-6.1 source package in Lunar:
Invalid
Status in linux source package in Mantic:
Fix Committed
Status in linux-oem-6.0 source package in Mantic:
Invalid
Status in linux-oem-6.1 source package in Mantic:
Invalid
Bug description:
[Impact]
Enabling CL1 (Controller Low Power) states during discovery of existing
tunnels established by the system firmware can interfere with the operation of
those tunnels.
The DisplayPort tunnel establishment timeout of 1.5 seconds can be
insufficient for some docking stations, leading to blank displays.
[Fix]
CL1 states are now not enabled during discovery of existing tunnels. The TMU
settings also remain unchanged.
The timeout is increased to 3 seconds to allow more time for the DisplayPort
connection manager handshake, fixing the issue of displays remaining blank.
[Test Cases]
1. plug docking station on the host
2. bring up the host and get into desktop.
3. flip docking station's cable.
4. check if the external monitor works well
[Where problems could occur]
Low, If the handshake actually requires even more than 3 seconds in some
cases, the timeout may still need to be increased further.
[Misc]
Jammy needs more patches to enable the thunderbolt CLx and the SRU will be a
huge,
so skip Jammy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2021949/+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 2018275] Re: Fix the in-motion function does not work
@Julian, add more explanation in [where problems could occur] ** Description changed: [Summary] in-Motion condition doesn't work with adaptive performance policy [Fix] This patch fix the issue, cc0890a59725) Always match motion = 0 [Test cases] 1. Install the Ubuntu 22.04-oem image on BMM4-DVT2-C2X 2. run the thermald applied the fix. #thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.log" and check the log 3. in-motion condition works [Where problems could occur] - low + because motion is always 0, the rules with motion=1 wouldn't be hit. ** Changed in: thermald (Ubuntu Jammy) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2018275 Title: Fix the in-motion function does not work Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: In Progress Bug description: [Summary] in-Motion condition doesn't work with adaptive performance policy [Fix] This patch fix the issue, cc0890a59725) Always match motion = 0 [Test cases] 1. Install the Ubuntu 22.04-oem image on BMM4-DVT2-C2X 2. run the thermald applied the fix. #thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.log" and check the log 3. in-motion condition works [Where problems could occur] because motion is always 0, the rules with motion=1 wouldn't be hit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018275/+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 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)
** Changed in: thermald (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: In Progress Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1995606/+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 1946433] Re: Fix only reach PC3 when ethernet is plugged r8169
+202306281458, disabled vmd and verified against 6.2.0-25 ~~~ u@u-Latitude-3520:~$ sudo cat /sys/kernel/debug/pmc_core/package_cstate_show Package C2 : 30219360 Package C3 : 18898473 Package C6 : 4122 Package C7 : 5223 Package C8 : 794719 Package C9 : 0 Package C10 : 0 u@u-Latitude-3520:~$ sudo cat /sys/kernel/debug/pmc_core/package_cstate_show Package C2 : 30566777 Package C3 : 19339300 Package C6 : 4381 Package C7 : 5940 Package C8 : 814012 Package C9 : 0 Package C10 : 0 u@u-Latitude-3520:~$ uname -a Linux u-Latitude-3520 6.2.0-25-generic #25-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun 16 17:05:07 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ~~~ ** Tags removed: verification-needed-lunar ** Tags added: verification-done-lunar ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/1946433 Title: Fix only reach PC3 when ethernet is plugged r8169 Status in HWE Next: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Triaged Status in linux-oem-5.13 source package in Kinetic: Invalid Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Committed Status in linux-oem-5.13 source package in Lunar: Invalid Status in linux-oem-5.14 source package in Lunar: Invalid Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-5.13 source package in Mantic: Invalid Status in linux-oem-5.14 source package in Mantic: Invalid Status in linux-oem-5.17 source package in Mantic: Invalid Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] System only can reach PC3, and it affects power consumption alot. [Fix] Kaiheng implemented a dynamic ASPM for r8169, it not only fixes the PC state issue, but also fixes network speed issue. V7: https://patchwork.kernel.org/project/netdevbpf/patch/20211016075442.650311-5-kai.heng.f...@canonical.com/ V6: https://patchwork.ozlabs.org/project/linux-pci/cover/20211007161552.272771-1-kai.heng.f...@canonical.com/ [Test] Verified on 2 different systems which has PC state issue and has network speed issue, these patches fix both issues. [Where problems could occur] It toggles ASPM on and off depends on the network traffic during runtime, I don't think it'll lead to any regressions. Some potential issues have been addressed during the patch submitting. It's v6 now and accepted by upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946433/+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 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)
** Patch added: "thermald_jammy_2.4.9-1ubuntu0.3.v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+attachment/5682352/+files/thermald_jammy_2.4.9-1ubuntu0.3.v2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: Incomplete Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1995606/+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 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)
@Raof * Replied 1st, please check Ref. https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018275/comments/2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: Incomplete Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1995606/+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 2018275] Re: Fix the in-motion function does not work
@Raof, As per Dell and Intel, here're some documents ~~~ 1. Currently, Motion condition is not supported against v2.5.0 release. 2. A patch in WIP branch to have the partial support, Motion = 0: https://github.com/intel/thermal_daemon/commit/cc0890a5972575eee2ab778772b1ee9ae1c75dba 3. Some background of this “motion”: 1) Per Intel document #607821, the Motion variant is to indicate the system put on the desk “Motion=0”, or it is carried on moving or it is put on the lap (Motion=1). 2) For the Dell Latitude laptops, in the adaptive performance condition table (APCT), Motion variant is added for each condition_set. Taking our current POC system for example, as you known, there are totally 8 condition sets, 7 of them are with Motion=0, 1 of them is with Motion=1. If we do not apply above mentioned patch, the system will be working under the “highest power” mode which is defined in the APCT table, but could not switch to other cooler mode. [1660808299][INFO]Falling back to use configuration with the highest power ~~~ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2018275 Title: Fix the in-motion function does not work Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: In Progress Bug description: [Summary] in-Motion condition doesn't work with adaptive performance policy [Fix] This patch fix the issue, cc0890a59725) Always match motion = 0 [Test cases] 1. Install the Ubuntu 22.04-oem image on BMM4-DVT2-C2X 2. run the thermald applied the fix. #thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.log" and check the log 3. in-motion condition works [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018275/+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 2021949] Re: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle
VNP against Lunar,
~~~
u@u-Precision-5480:~$ uname -a
Linux u-Precision-5480 6.2.0-25-generic #25-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun
16 17:05:07 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
u@u-Precision-5480:~$ ubuntu-report show | grep -ie bios -a5
"OEM": {
"Vendor": "Dell Inc.",
"Product": "Precision 5480",
"Family": "Precision"
},
"BIOS": {
"Vendor": "Dell Inc.",
"Version": "1.3.0"
},
"Arch": "amd64",
"HwCap": "x86-64-v3",
~~~
** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2021949
Title:
Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to
type-C dongle
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-6.0 package in Ubuntu:
New
Status in linux-oem-6.1 package in Ubuntu:
New
Status in linux source package in Jammy:
New
Status in linux-oem-6.0 source package in Jammy:
In Progress
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
New
Status in linux-oem-6.1 source package in Kinetic:
New
Status in linux source package in Lunar:
Fix Committed
Status in linux-oem-6.0 source package in Lunar:
New
Status in linux-oem-6.1 source package in Lunar:
New
Status in linux source package in Mantic:
Fix Committed
Status in linux-oem-6.0 source package in Mantic:
New
Status in linux-oem-6.1 source package in Mantic:
New
Bug description:
[Impact]
Enabling CL1 (Controller Low Power) states during discovery of existing
tunnels established by the system firmware can interfere with the operation of
those tunnels.
The DisplayPort tunnel establishment timeout of 1.5 seconds can be
insufficient for some docking stations, leading to blank displays.
[Fix]
CL1 states are now not enabled during discovery of existing tunnels. The TMU
settings also remain unchanged.
The timeout is increased to 3 seconds to allow more time for the DisplayPort
connection manager handshake, fixing the issue of displays remaining blank.
[Test Cases]
1. plug docking station on the host
2. bring up the host and get into desktop.
3. flip docking station's cable.
4. check if the external monitor works well
[Where problems could occur]
Low, If the handshake actually requires even more than 3 seconds in some
cases, the timeout may still need to be increased further.
[Misc]
Jammy needs more patches to enable the thunderbolt CLx and the SRU will be a
huge,
so skip Jammy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2021949/+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 2023004] Re: Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad
VNP against Jammy,
~~~
u@u-Precision-5480:~$ uname -a
Linux u-Precision-5480 6.1.0-1015-oem #15-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun 16
09:51:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
u@u-Precision-5480:~$ ubuntu-report show | grep -ie bios -a5
"Vendor": "Dell Inc.",
"Product": "Precision 5480",
"Family": "Precision",
"DCD":
"canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-gardevoir+X57"
},
"BIOS": {
"Vendor": "Dell Inc.",
"Version": "1.3.0"
},
"Arch": "amd64",
"HwCap": "x86-64-v3",
~~~
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2023004
Title:
Fix Disable thunderbolt clx make edp-monitor garbage while moving the
touchpad
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
New
Status in linux source package in Jammy:
In Progress
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
In Progress
Status in linux-oem-6.1 source package in Kinetic:
New
Status in linux source package in Lunar:
Fix Committed
Status in linux-oem-6.1 source package in Lunar:
New
Status in linux source package in Mantic:
Fix Committed
Status in linux-oem-6.1 source package in Mantic:
New
Bug description:
[impact]
The default sync pulse length for fast wake AUX transactions was changed from
18 to 10, which was causing issues with some eDP panels.
[fix]
Revert the sync pulse length for fast wake AUX transactions back to the
hardware default of 18 (10 precharge + 8 preamble).
[test cases]
1. configure with thunderbolt.clx=0.
2. check edp's behavior and it should work well and there's no garbage.
[where the issue could happen]
low, By reverting this setting back to the default, this commit restores
stability for configurations using fast wake AUX transactions, especially those
involving eDP panels that were incompatible with the shorter sync pulse length.
The longer, hardware-default sync pulse length is compatible with more use
cases.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023004/+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 2023004] Re: Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad
VNP against Lunar,
~~~
u@u-Precision-5480:~$ uname -a
Linux u-Precision-5480 6.2.0-25-generic #25-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun
16 17:05:07 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
u@u-Precision-5480:~$ ubuntu-report show | grep -ie bios -a5
"OEM": {
"Vendor": "Dell Inc.",
"Product": "Precision 5480",
"Family": "Precision"
},
"BIOS": {
"Vendor": "Dell Inc.",
"Version": "1.3.0"
},
"Arch": "amd64",
"HwCap": "x86-64-v3",
~~~
** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2023004
Title:
Fix Disable thunderbolt clx make edp-monitor garbage while moving the
touchpad
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
New
Status in linux source package in Jammy:
In Progress
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
In Progress
Status in linux-oem-6.1 source package in Kinetic:
New
Status in linux source package in Lunar:
Fix Committed
Status in linux-oem-6.1 source package in Lunar:
New
Status in linux source package in Mantic:
Fix Committed
Status in linux-oem-6.1 source package in Mantic:
New
Bug description:
[impact]
The default sync pulse length for fast wake AUX transactions was changed from
18 to 10, which was causing issues with some eDP panels.
[fix]
Revert the sync pulse length for fast wake AUX transactions back to the
hardware default of 18 (10 precharge + 8 preamble).
[test cases]
1. configure with thunderbolt.clx=0.
2. check edp's behavior and it should work well and there's no garbage.
[where the issue could happen]
low, By reverting this setting back to the default, this commit restores
stability for configurations using fast wake AUX transactions, especially those
involving eDP panels that were incompatible with the shorter sync pulse length.
The longer, hardware-default sync pulse length is compatible with more use
cases.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023004/+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 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)
@Raof, as per request, modified the changelog please help to review. ** Patch added: "thermald_jammy_2.4.9-1ubuntu0.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+attachment/5681109/+files/thermald_jammy_2.4.9-1ubuntu0.3.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: Incomplete Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1995606/+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 2023004] Re: Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023004 Title: Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: New Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: New Bug description: [impact] The default sync pulse length for fast wake AUX transactions was changed from 18 to 10, which was causing issues with some eDP panels. [fix] Revert the sync pulse length for fast wake AUX transactions back to the hardware default of 18 (10 precharge + 8 preamble). [test cases] 1. configure with thunderbolt.clx=0. 2. check edp's behavior and it should work well and there's no garbage. [where the issue could happen] low, By reverting this setting back to the default, this commit restores stability for configurations using fast wake AUX transactions, especially those involving eDP panels that were incompatible with the shorter sync pulse length. The longer, hardware-default sync pulse length is compatible with more use cases. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023004/+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 2021949] Re: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle
VNP,
~~~
u@u-Precision-5480:~$ uname -a
Linux u-Precision-5480 6.1.0-1015-oem #15-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun 16
09:51:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
u@u-Precision-5480:~$ ubuntu-report show | grep -ie bios -a5
"Vendor": "Dell Inc.",
"Product": "Precision 5480",
"Family": "Precision",
"DCD":
"canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-gardevoir+X57"
},
"BIOS": {
"Vendor": "Dell Inc.",
"Version": "1.3.0"
},
"Arch": "amd64",
"HwCap": "x86-64-v3",
~~~
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2021949
Title:
Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to
type-C dongle
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-6.0 package in Ubuntu:
New
Status in linux-oem-6.1 package in Ubuntu:
New
Status in linux source package in Jammy:
New
Status in linux-oem-6.0 source package in Jammy:
In Progress
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
New
Status in linux-oem-6.1 source package in Kinetic:
New
Status in linux source package in Lunar:
Fix Committed
Status in linux-oem-6.0 source package in Lunar:
New
Status in linux-oem-6.1 source package in Lunar:
New
Status in linux source package in Mantic:
Fix Committed
Status in linux-oem-6.0 source package in Mantic:
New
Status in linux-oem-6.1 source package in Mantic:
New
Bug description:
[Impact]
Enabling CL1 (Controller Low Power) states during discovery of existing
tunnels established by the system firmware can interfere with the operation of
those tunnels.
The DisplayPort tunnel establishment timeout of 1.5 seconds can be
insufficient for some docking stations, leading to blank displays.
[Fix]
CL1 states are now not enabled during discovery of existing tunnels. The TMU
settings also remain unchanged.
The timeout is increased to 3 seconds to allow more time for the DisplayPort
connection manager handshake, fixing the issue of displays remaining blank.
[Test Cases]
1. plug docking station on the host
2. bring up the host and get into desktop.
3. flip docking station's cable.
4. check if the external monitor works well
[Where problems could occur]
Low, If the handshake actually requires even more than 3 seconds in some
cases, the timeout may still need to be increased further.
[Misc]
Jammy needs more patches to enable the thunderbolt CLx and the SRU will be a
huge,
so skip Jammy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2021949/+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 2002601] Re: Wireless: Enable RTL8852BE wifi driver
** Changed in: linux (Ubuntu Jammy) Status: Invalid => Won't Fix -- 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/2002601 Title: Wireless: Enable RTL8852BE wifi driver Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Justification] Enable Realtek RLT8852BE WIFI. [Test] 1. put rtw8852b_fw.bin in /lib/firmware/rtw89/ 2. boot-up with kernel enabled RTL8852be. 3. Connect to WIFI-AP and test with ping. * ping -I wlp2s0 8.8.8.8 ~~~ PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms ~~~ * Connected to AP ~~~ u@ubuntu:~$ nmcli dev DEVICE TYPE STATE CONNECTION enp3s0 ethernet connected Wired connection 1 wlp2s0 wifi connected Canonical p2p-dev-wlp2s0 wifi-p2p disconnected -- lo loopback unmanaged -- ~~~ * lsmod | grep 8852 ~~~ lsmod | grep 8852 rtw89_8852be 16384 0 rtw89_8852b 368640 1 rtw89_8852be rtw89_pci 61440 1 rtw89_8852be rtw89_core 442368 2 rtw89_8852b,rtw89_pci cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211 ~~~ 4. cbd's built result, Lunar, ~~~ remote: Resolving deltas: 100% (391/391), completed with 118 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-0e58018b43c1-ioeM remote: * 96/480 cores busy (1/5 hosts), 0 builds queued remote: 2023-01-12 03:16:35 kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK remote: 2023-01-12 03:17:47 kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK remote: 2023-01-12 03:11:36 kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK remote: 2023-01-12 03:16:30 kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK remote: 2023-01-12 03:10:24 kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK remote: To cbd:lunar.git ~~~ OEM-6.1, remote: Resolving deltas: 100% (399/399), completed with 121 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-c1002f30ccc3-m65z remote: * 0/192 cores busy (0/2 hosts), 0 builds queued remote: 2023-01-12 05:25:23 kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK remote: To cbd:jammy.git [Where problems could occur] Medium, a new driver so the current driver may have some edge cases didn't consider. [Misc] * For generic Jammy, need more patches to enable RTL8852be so only SRU for OEM-6.1. * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on Lunar, so only SRU for Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002601/+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
