[Kernel-packages] [Bug 1995638] [NEW] Jammy update: v5.15.74 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.74 upstream stable release
from git://git.kernel.org/
nilfs2: fix NULL pointer dereference at nilfs_bmap_lookup_at_level()
nilfs2: fix use-after-free bug of struct nilfs_root
nilfs2: fix leak of nilfs_root in case of writer thread creation failure
nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure
ceph: don't truncate file in atomic_open
random: restore O_NONBLOCK support
random: clamp credited irq bits to maximum mixed
ALSA: hda: Fix position reporting on Poulsbo
efi: Correct Macmini DMI match in uefi cert quirk
USB: serial: qcserial: add new usb-id for Dell branded EM7455
Revert "powerpc/rtas: Implement reentrant rtas call"
Revert "crypto: qat - reduce size of mapped region"
random: avoid reading two cache lines on irq randomness
random: use expired timer rather than wq for mixing fast pool
Input: xpad - add supported devices as contributed on github
Input: xpad - fix wireless 360 controller breaking after suspend
misc: pci_endpoint_test: Aggregate params checking for xfer
misc: pci_endpoint_test: Fix pci_endpoint_test_{copy,write,read}() panic
Linux 5.15.74
UBUNTU: Upstream stable to v5.15.74
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ v5.15.74 upstream stable release
+ from git://git.kernel.org/
-v5.15.74 upstream stable release
-from git://git.kernel.org/
+ nilfs2: fix NULL pointer dereference at nilfs_bmap_lookup_at_level()
+ nilfs2: fix use-after-free bug of struct nilfs_root
+ nilfs2: fix leak of nilfs_root in case of writer thread creation failure
+ nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure
+ ceph: don't truncate file in atomic_open
+ random: restore O_NONBLOCK support
+ random: clamp credited irq bits to maximum mixed
+ ALSA: hda: Fix position reporting on Poulsbo
+ efi: Correct Macmini DMI match in uefi cert quirk
+ USB: serial: qcserial: add new usb-id for Dell branded EM7455
+ Revert "powerpc/rtas: Implement reentrant rtas call"
+ Revert "crypto: qat - reduce size of mapped region"
+ random: avoid reading two cache lines on irq randomness
+ random: use expired timer rather than wq for mixing fast pool
+ Input: xpad - add supported devices as contributed on github
+ Input: xpad - fix wireless 360 controller breaking after suspend
+ misc: pci_endpoint_test: Aggregate params checking for xfer
+ misc: pci_endpoint_test: Fix pci_endpoint_test_{copy,write,read}() panic
+ Linux 5.15.74
+ UBUNTU: Upstream stable to v5.15.74
--
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/1995638
Title:
Jammy update: v5.15.74 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Bug description:
SRU Justification
Impact:
Th
[Kernel-packages] [Bug 1995637] Re: Jammy update: v5.15.73 upstream stable release
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.15.73 upstream stable release + from git://git.kernel.org/ -v5.15.73 upstream stable release -from git://git.kernel.org/ + Makefile.extrawarn: Move -Wcast-function-type-strict to W=1 + docs: update mediator information in CoC docs + xsk: Inherit need_wakeup flag for shared sockets + mm: gup: fix the fast GUP race against THP collapse + powerpc/64s/radix: don't need to broadcast IPI for radix pmd collapse flush + firmware: arm_scmi: Improve checks in the info_get operations + firmware: arm_scmi: Harden accesses to the sensor domains + firmware: arm_scmi: Add SCMI PM driver remove routine + dmaengine: xilinx_dma: Fix devm_platform_ioremap_resource error handling + dmaengine: xilinx_dma: cleanup for fetching xlnx,num-fstores property + dmaengine: xilinx_dma: Report error in case of dma_set_mask_and_coherent API failure + ARM: dts: fix Moxa SDIO 'compatible', remove 'sdhci' misnomer + scsi: qedf: Fix a UAF bug in __qedf_probe() + net/ieee802154: fix uninit value bug in dgram_sendmsg + net: marvell: prestera: add support for for Aldrin2 + ALSA: hda/hdmi: Fix the converter reuse for the silent stream + um: Cleanup syscall_handler_t cast in syscalls_32.h + um: Cleanup compiler warning in arch/x86/um/tls_32.c + arch: um: Mark the stack non-executable to fix a binutils warning + net: atlantic: fix potential memory leak in aq_ndev_close() + drm/amd/display: Fix double cursor on non-video RGB MPO + drm/amd/display: Assume an LTTPR is always present on fixed_vs links + drm/amd/display: update gamut remap if plane has changed + drm/amd/display: skip audio setup when audio stream is enabled + mmc: core: Replace with already defined values for readability + mmc: core: Terminate infinite loop in SD-UHS voltage switch + perf parse-events: Identify broken modifiers + mm/huge_memory: minor cleanup for split_huge_pages_all + mm/huge_memory: use pfn_to_online_page() in split_huge_pages_all() + wifi: cfg80211: fix MCS divisor value + net/mlx5: Disable irq when locking lag_lock + usb: mon: make mmapped memory read only + USB: serial: ftdi_sio: fix 300 bps rate for SIO + rpmsg: qcom: glink: replace strncpy() with strscpy_pad() + Revert "clk: ti: Stop using legacy clkctrl names for omap4 and 5" + Linux 5.15.73 + UBUNTU: Upstream stable to v5.15.73 -- 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/1995637 Title: Jammy update: v5.15.73 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.73 upstream stable release from git://git.kernel.org/ Makefile.extrawarn: Move -Wcast-function-type-strict to W=1 docs: update mediator information in CoC docs xsk: Inherit need_wakeup flag for shared sockets mm: gup: fix the fast GUP race against THP collapse powerpc/64s/radix: don't need to broadcast IPI for radix pmd collapse flush firmware: arm_scmi: Improve checks in the info_get operations firmware: arm_scmi: Harden accesses to the sensor domains firmware: arm_scmi: Add SCMI PM driver remove routine dmaengine: xilinx_dma: Fix devm_platform_ioremap_resource error handling
[Kernel-packages] [Bug 1995637] [NEW] Jammy update: v5.15.73 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.73 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (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/1995637 Title: Jammy update: v5.15.73 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.73 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995637/+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 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
Unfortunately I just hit the same issue this morning: $ dpkg -l | grep linux-firmwar ii linux-firmware 20220329.git681281e4-0ubuntu3.6 all Firmware for Linux kernel drivers So seems that the issue can still occur. -- 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/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: Confirmed Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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 1995607] Re: Laptop wont charge (usb-c) while in suspend
I updated BIOS. No change in behavior. BIOS version: EBTGLMIV.0070.2022.0824.1647 08/24/2022 One thing I forgot to mention is the laptop will continue charging of it is already charging and it goes into suspend (lid gets closed). -- 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/1995607 Title: Laptop wont charge (usb-c) while in suspend Status in linux package in Ubuntu: Confirmed Bug description: My laptop charges fine if on or off but not during suspend. It charges over USB-C. Verified not charging using a charger with an amp reading. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: radec 973 F pipewire radec 976 F wireplumber /dev/snd/seq:radec 973 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 3 06:03:21 2022 InstallationDate: Installed on 2022-11-02 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Intel(R) Client Systems CMCN1CC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=00ba6fe9-0b35-454d-aae5-5adffc88f70e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: EBTGLMIV.0057.2021.0521.2137 dmi.board.name: CM11EBV716W dmi.board.vendor: Intel Corporation dmi.board.version: M15481-301 dmi.chassis.type: 10 dmi.chassis.vendor: Intel(R) Corporation dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.1 dmi.modalias: dmi:bvnIntelCorp.:bvrEBTGLMIV.0057.2021.0521.2137:bd05/21/2021:br5.19:efr3.1:svnIntel(R)ClientSystems:pnCMCN1CC:pvrK95289-402:rvnIntelCorporation:rnCM11EBV716W:rvrM15481-301:cvnIntel(R)Corporation:ct10:cvr1.0:sku: dmi.product.family: CC dmi.product.name: CMCN1CC dmi.product.version: K95289-402 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995607/+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 1766857] Re: [Hyper-V] KVP daemon fails to start
Uups, wrong tagging. This bug does still affect linux (Ubuntu Focal) ** Also affects: focal (Ubuntu) Importance: Undecided Status: New ** No longer affects: focal (Ubuntu) ** No longer affects: focal (Ubuntu Bionic) ** No longer affects: focal (Ubuntu Cosmic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1766857 Title: [Hyper-V] KVP daemon fails to start Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-azure source package in Bionic: Invalid Status in linux source package in Cosmic: Confirmed Status in linux-azure source package in Cosmic: Invalid Bug description: While testing Bionic daily build with kernel 4.15.0-20-generic we saw that there are 2 issues with the KVP daemon: 1. KVP daemon crash after boot. Opened a different bug for this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779640 2. After the KVP daemon is being started the following messages appear: Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dns_info: not found Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dhcp_info: not found The above binaries are present on the system, but the their actual path is /usr/sbin/hv_get_dns_info and /usr/sbin/hv_get_dhcp_info. Either the hv_get_dhcp_info and hv_get_dns_info binaries should be placed in the location where the daemon is looking for (/usr/libexec/hypervkvpd/), or the daemon should be set to search for the binaries in the /usr/sbin directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766857/+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 1995618] Re: It seems not to auto login or get X session after installing Nvidia-driver
** Attachment added: "27810.logs.tar.xz" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1995618/+attachment/5628933/+files/27810.logs.tar.xz ** Summary changed: - It seems not to auto login or get X session after installing Nvidia-driver + It seems to now login automatically or get X session after installing Nvidia-driver ** Summary changed: - It seems to now login automatically or get X session after installing Nvidia-driver + It seems to not login automatically or get X session after installing Nvidia-driver ** Also affects: nvidia-graphics-drivers-520 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1995618 Title: It seems to not login automatically or get X session after installing Nvidia-driver Status in linux-signed-hwe-5.15 package in Ubuntu: New Status in nvidia-graphics-drivers-520 package in Ubuntu: New Bug description: During SRU testing, I found some machines kept failing to run switching graphic card test. According to the output from the test run, those machines seem to not login automatically or can't get X session somehow. Now I can't check the status of machines directly, but my guessing is base on the output from our test case, it showed "Can't open display :0" and "Gtk couldn't be initialized. Use Gtk.init_check() ". I met this issue on there different machine which I can get log from them so far, there are other machines have this issue but I can't get the log. Our testing always use ubuntu-driver install to install nvidia-driver. https://certification.canonical.com/hardware/202004-27810/ https://certification.canonical.com/hardware/202004-27811/ https://certification.canonical.com/hardware/201904-26941/ Kernel version:5.15.0-53-generic Nvidia driver: nvidia-driver-520-open ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 3 10:55:26 2022 InstallationDate: Installed on 2020-08-03 (821 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1995618/+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 1995618] Re: It seems not to auto login or get X session after installing Nvidia-driver
** Attachment added: "26941.logs.tar.xz" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1995618/+attachment/5628932/+files/26941.logs.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1995618 Title: It seems to not login automatically or get X session after installing Nvidia-driver Status in linux-signed-hwe-5.15 package in Ubuntu: New Status in nvidia-graphics-drivers-520 package in Ubuntu: New Bug description: During SRU testing, I found some machines kept failing to run switching graphic card test. According to the output from the test run, those machines seem to not login automatically or can't get X session somehow. Now I can't check the status of machines directly, but my guessing is base on the output from our test case, it showed "Can't open display :0" and "Gtk couldn't be initialized. Use Gtk.init_check() ". I met this issue on there different machine which I can get log from them so far, there are other machines have this issue but I can't get the log. Our testing always use ubuntu-driver install to install nvidia-driver. https://certification.canonical.com/hardware/202004-27810/ https://certification.canonical.com/hardware/202004-27811/ https://certification.canonical.com/hardware/201904-26941/ Kernel version:5.15.0-53-generic Nvidia driver: nvidia-driver-520-open ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 3 10:55:26 2022 InstallationDate: Installed on 2020-08-03 (821 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1995618/+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 1995618] [NEW] It seems to not login automatically or get X session after installing Nvidia-driver
Public bug reported: During SRU testing, I found some machines kept failing to run switching graphic card test. According to the output from the test run, those machines seem to not login automatically or can't get X session somehow. Now I can't check the status of machines directly, but my guessing is base on the output from our test case, it showed "Can't open display :0" and "Gtk couldn't be initialized. Use Gtk.init_check() ". I met this issue on there different machine which I can get log from them so far, there are other machines have this issue but I can't get the log. Our testing always use ubuntu-driver install to install nvidia-driver. https://certification.canonical.com/hardware/202004-27810/ https://certification.canonical.com/hardware/202004-27811/ https://certification.canonical.com/hardware/201904-26941/ Kernel version:5.15.0-53-generic Nvidia driver: nvidia-driver-520-open ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 3 10:55:26 2022 InstallationDate: Installed on 2020-08-03 (821 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.15 (Ubuntu) Importance: High Status: New ** Affects: nvidia-graphics-drivers-520 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal package-from-proposed uec-images ** Attachment added: "27811.logs.tar.xz" https://bugs.launchpad.net/bugs/1995618/+attachment/5628929/+files/27811.logs.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1995618 Title: It seems to not login automatically or get X session after installing Nvidia-driver Status in linux-signed-hwe-5.15 package in Ubuntu: New Status in nvidia-graphics-drivers-520 package in Ubuntu: New Bug description: During SRU testing, I found some machines kept failing to run switching graphic card test. According to the output from the test run, those machines seem to not login automatically or can't get X session somehow. Now I can't check the status of machines directly, but my guessing is base on the output from our test case, it showed "Can't open display :0" and "Gtk couldn't be initialized. Use Gtk.init_check() ". I met this issue on there different machine which I can get log from them so far, there are other machines have this issue but I can't get the log. Our testing always use ubuntu-driver install to install nvidia-driver. https://certification.canonical.com/hardware/202004-27810/ https://certification.canonical.com/hardware/202004-27811/ https://certification.canonical.com/hardware/201904-26941/ Kernel version:5.15.0-53-generic Nvidia driver: nvidia-driver-520-open ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 3 10:55:26 2022 InstallationDate: Installed on 2020-08-03 (821 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1995618/+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 1995465] Re: linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security.
Enable the following configs: PAGE_POISONING_ZERO PAGE_POISONING_NO_SANITY PAGE_POISONING SECURITY_LOCKDOWN_LSM SCHED_STACK_END_CHECK SECURITY_YAMA DEBUG_WX CONFIG_SECURITY_PERF_EVENTS_RESTRICT CONFIG_SECURITY_PERF_EVENTS_RESTRICT FORTIFY_SOURCE HARDENED_USERCOPY SLAB_FREELIST_RANDOM IP_ADVANCED_ROUTER SECURITY_TOMOYO ** Description changed: [SRU Justification] [Impact] - The linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security regression test due to kernel config options. The kernel configs were changed to + The linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security regression test due to kernel config options. The kernel configs were changed to match the Xilinx provided kernel configs which resulted in these configs being disabled. [Fix] - Enable the following configs: - PAGE_POISONING_ZERO - PAGE_POISONING_NO_SANITY - PAGE_POISONING - SECURITY_LOCKDOWN_LSM - SCHED_STACK_END_CHECK - SECURITY_YAMA - DEBUG_WX - CONFIG_SECURITY_PERF_EVENTS_RESTRICT - CONFIG_SECURITY_PERF_EVENTS_RESTRICT - FORTIFY_SOURCE - HARDENED_USERCOPY - SLAB_FREELIST_RANDOM - IP_ADVANCED_ROUTER - SECURITY_TOMOYO - RANDOMIZE_BASE + Enable all configs checked in ubuntu_qrt_kernel_security. + [Testcase] ubuntu_qrt_kernel caught this isuse and will continue to test whether these configs are enabled. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/1995465 Title: linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security. Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: [SRU Justification] [Impact] The linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security regression test due to kernel config options. The kernel configs were changed to match the Xilinx provided kernel configs which resulted in these configs being disabled. [Fix] Enable all configs checked in ubuntu_qrt_kernel_security. [Testcase] ubuntu_qrt_kernel caught this isuse and will continue to test whether these configs are enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/1995465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad
[Kernel-packages] [Bug 1992912] Re: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted
** Description changed: [SRU Justification] [Impact] The focal kernel is failing the ubuntu_ltp:sched:time-schedule01 and ubuntu_ltp:sched:trace_sched01 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. This is due to have having CONFIG_RT_GROUP_SCHED enabled. There are multiple known issues with CONFIG_RT_GROUP_SCHED that are reported in the debian.master/config/annotations file: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665 [Fix] CONFIG_RT_GROUP_SCHED should be disabled. The config was enabled when we copied the Xilinx default config settings and there is not a - justification for this exact config. + justification for this exact config. There may even be a negative + impact, from the kernel.org documentation: + + “The default values for sched_rt_period_us (100 or 1s) and + sched_rt_runtime_us (95 or 0.95s). This gives 0.05s to be used by + SCHED_OTHER (non-RT tasks).” + + This suggests this option will benefit RT systems, but be detrimental to + non-RT systems, [Testcase] + + The annotations file will enforce that CONFIG_RT_GROUP_SCHED is + disabled. ** Description changed: [SRU Justification] [Impact] - The focal kernel is failing the ubuntu_ltp:sched:time-schedule01 and ubuntu_ltp:sched:trace_sched01 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. This is due to have having CONFIG_RT_GROUP_SCHED enabled. + The focal kernel is failing the ubuntu_ltp:sched:time-schedule01, ubuntu_ltp:sched:trace_sched01 and ubuntu_ltp:irq:irqbalance0 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. This is due to have having CONFIG_RT_GROUP_SCHED enabled. Once RT_GROUP_SCHED is enabled it is impossible to schedule realtime tasks for non-root users until you allocate realtime bandwidth for them. There are multiple known issues with CONFIG_RT_GROUP_SCHED that are reported in the debian.master/config/annotations file: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665 [Fix] CONFIG_RT_GROUP_SCHED should be disabled. The config was enabled when we copied the Xilinx default config settings and there is not a justification for this exact config. There may even be a negative impact, from the kernel.org documentation: “The default values for sched_rt_period_us (100 or 1s) and sched_rt_runtime_us (95 or 0.95s). This gives 0.05s to be used by SCHED_OTHER (non-RT tasks).” This suggests this option will benefit RT systems, but be detrimental to non-RT systems, [Testcase] The annotations file will enforce that CONFIG_RT_GROUP_SCHED is disabled. ** Changed in: linux-xilinx-zynqmp (Ubuntu) Assignee: (unassigned) => Portia Stephens (portias) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/1992912 Title: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted Status in ubuntu-kernel-tests: New Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: [SRU Justification] [Impact] The focal kernel is failing the ubuntu_ltp:sched:time-schedule01, ubuntu_ltp:sched:trace_sched01 and ubuntu_ltp:irq:irqbalance0 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. This is due to have having CONFIG_RT_GROUP_SCHED enabled. Once RT_GROUP_SCHED is enabled it is impossible to schedule realtime tasks for non-root users until you allocate realtime bandwidth for them. There are multiple known issues with CONFIG_RT_GROUP_SCHED that are reported in the debian.master/config/annotations file: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665 [Fix] CONFIG_RT_GROUP_SCHED should be disabled. The config was enabled when we copied the Xilinx default config settings and there is not a justification for this exact config. There may even be a negative impact, from the kernel.org documentation: “The default values for sched_rt_period_us (100 or 1s) and sched_rt_runtime_us (95 or 0.95s). This gives 0.05s to be used by SCHED_OTHER (non-RT tasks).” This suggests this option will benefit RT systems, but be detrimental to non-RT systems, [Testcase] The annotations file will enforce that CONFIG_RT_GROUP_SCHED is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1992912/+subscriptions -- Mailing list: https:/
[Kernel-packages] [Bug 1992912] Re: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted
** Description changed: - The focal kernel is failing the ubuntu_ltp:sched:time-schedule01 and - ubuntu_ltp:sched:trace_sched01 regression test due to sched_setscheduler - being unable to a task class to SCHED_FIFO. + [SRU Justification] + + [Impact] + The focal kernel is failing the ubuntu_ltp:sched:time-schedule01 and ubuntu_ltp:sched:trace_sched01 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. This is due to have having CONFIG_RT_GROUP_SCHED enabled. There are multiple known issues with CONFIG_RT_GROUP_SCHED that are reported in the debian.master/config/annotations file: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665 - We do not have a good reason to enable this , I see no processes using realtime scheduling. We should disable this setting to match the upstream Ubuntu focal arm64 kernel. The following tests are failing with this error: - * ubuntu_ltp:sched:time-schedule01 - * ubuntu_ltp:sched:trace_sched01 - * ubuntu_qrt_apparmor:test-apparmor + [Fix] + + CONFIG_RT_GROUP_SCHED should be disabled. The config was enabled when we + copied the Xilinx default config settings and there is not a + justification for this exact config. + + [Testcase] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/1992912 Title: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted Status in ubuntu-kernel-tests: New Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: [SRU Justification] [Impact] The focal kernel is failing the ubuntu_ltp:sched:time-schedule01 and ubuntu_ltp:sched:trace_sched01 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. This is due to have having CONFIG_RT_GROUP_SCHED enabled. There are multiple known issues with CONFIG_RT_GROUP_SCHED that are reported in the debian.master/config/annotations file: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665 [Fix] CONFIG_RT_GROUP_SCHED should be disabled. The config was enabled when we copied the Xilinx default config settings and there is not a justification for this exact config. There may even be a negative impact, from the kernel.org documentation: “The default values for sched_rt_period_us (100 or 1s) and sched_rt_runtime_us (95 or 0.95s). This gives 0.05s to be used by SCHED_OTHER (non-RT tasks).” This suggests this option will benefit RT systems, but be detrimental to non-RT systems, [Testcase] The annotations file will enforce that CONFIG_RT_GROUP_SCHED is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1992912/+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 1995607] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1995607 Title: Laptop wont charge (usb-c) while in suspend Status in linux package in Ubuntu: Confirmed Bug description: My laptop charges fine if on or off but not during suspend. It charges over USB-C. Verified not charging using a charger with an amp reading. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: radec 973 F pipewire radec 976 F wireplumber /dev/snd/seq:radec 973 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 3 06:03:21 2022 InstallationDate: Installed on 2022-11-02 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Intel(R) Client Systems CMCN1CC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=00ba6fe9-0b35-454d-aae5-5adffc88f70e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: EBTGLMIV.0057.2021.0521.2137 dmi.board.name: CM11EBV716W dmi.board.vendor: Intel Corporation dmi.board.version: M15481-301 dmi.chassis.type: 10 dmi.chassis.vendor: Intel(R) Corporation dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.1 dmi.modalias: dmi:bvnIntelCorp.:bvrEBTGLMIV.0057.2021.0521.2137:bd05/21/2021:br5.19:efr3.1:svnIntel(R)ClientSystems:pnCMCN1CC:pvrK95289-402:rvnIntelCorporation:rnCM11EBV716W:rvrM15481-301:cvnIntel(R)Corporation:ct10:cvr1.0:sku: dmi.product.family: CC dmi.product.name: CMCN1CC dmi.product.version: K95289-402 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995607/+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
** Description changed: [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. - Currently, just use a stressing tools and monitor status manually(e.g. s-tui). - Use stress-ng to stress the machine and observe the temperature/frequency/power. + Currently, just use stress-ng and observe the temperature/frequency/power manually(e.g. s-tui). The whole test cases are the followings and run on the platforms, RPL/ADL/TGL/CML/CFL/KBL. 1. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. 2. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. 3. 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. a. rapl.sh b. intel_pstate.sh c. powerclamp.sh d. processor.sh 4. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 5. check if system would be throttled even the temperature is under the thrip-poits. -- 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 Status in thermald package in Ubuntu: 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. Currently, just use stress-ng and observe the temperature/frequency/power manually(e.g. s-tui). The whole test cases are the followings and run on the platforms, RPL/ADL/TGL/CML/CFL/KBL. 1. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. 2. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. 3. 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. a. rapl.sh b. intel_pstate.sh c. powerclamp.sh d. processor.sh 4. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 5. check if system would be throttled even the temperature is under the thrip-poits. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+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 1992912] Re: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted
** Summary changed: - linux-xilinx-zynqmp: main(): sched_setscheduler(): Operation not permitted + linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/1992912 Title: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted Status in ubuntu-kernel-tests: New Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: The focal kernel is failing the ubuntu_ltp:sched:time-schedule01 and ubuntu_ltp:sched:trace_sched01 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. There are multiple known issues with CONFIG_RT_GROUP_SCHED that are reported in the debian.master/config/annotations file: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665 We do not have a good reason to enable this , I see no processes using realtime scheduling. We should disable this setting to match the upstream Ubuntu focal arm64 kernel. The following tests are failing with this error: * ubuntu_ltp:sched:time-schedule01 * ubuntu_ltp:sched:trace_sched01 * ubuntu_qrt_apparmor:test-apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1992912/+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 1995491] Comment bridged from LTC Bugzilla
--- Comment From boris.m...@de.ibm.com 2022-11-03 09:09 EDT--- Hi Pedro, The dumps should be available in Ecurep at SW:/ecurep/sw/5/9/5900-A6A/5.4.0/26/2022-10-19/* Thanks -- 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/1995491 Title: [UBUNTU 20.04] "kauditd: hold queue overflow " and node failure Status in linux package in Ubuntu: New Bug description: ---Problem Description--- This is an issue being reported on a node that went down. Had a chance to look at the currently available logs, which doesn't provide me sufficient indication of a potential issue beyond an issue w.r.t "kauditd: hold queue overflow " (~790 number of messages ) Would be great to have your review on the dump file to see , whether there is anything significant that caused the node down. Contact Information = Kishore Kumar G/kishore.pil...@in.ibm.com ---uname output--- I will come back with the uname output , as I couldn't get that info from the logs Machine Type = z15 -GT2 lpar ---Debugger--- A debugger is not configured Stack trace output: no Oops output: no System Dump Location: [18:in07100f@ecurep]:/ecurep/toibm/linux $ ls 2022_09_26_18_18_51_tor2-qz1-sr1-rk085-s03_192.168.85.7_5.4.0-121-generic_dumpfile 2022_09_26_18_18_51_tor2-qz1-sr1-rk085-s03_192.168.85.7_5.4.0-121-generic_locDmsg *Additional Instructions for Kishore Kumar G/kishore.pil...@in.ibm.com: -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995491/+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 1995465] Re: linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security.
** Description changed: - The linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security - regression test due to kernel config options. The following tests are - failing: + [SRU Justification] - KernelSecurityConfigTest.test_010_kaslr_config - KernelSecurityConfigTest.test_100_config_security_tomoyo - KernelSecurityConfigTest.test_230_config_security_ipsec - KernelSecurityConfigTest.test_240_SLAB_freelist_randomization - KernelSecurityConfigTest.test_290_config_hardened_usercopy - KernelSecurityConfigTest.test_300_config_kernel_fortify - KernelSecurityConfigTest.test_310_config_security_perf_events_restrict - KernelSecurityConfigTest.test_320_config_arm_pan - KernelSecurityConfigTest.test_330_config_debug_wx - KernelSecurityConfigTest.test_360_config_security_yama - KernelSecurityConfigTest.test_380_config_sched_stack_end_check - KernelSecurityConfigTest.test_410_config_lock_down_kernel - KernelSecurityConfigTest.test_420_config_page_poisoning - KernelSecurityConfigTest.test_421_config_page_poisoning_no_sanity - KernelSecurityConfigTest.test_421_config_page_poisoning_zero - KernelSecurityConfigTest.test_430_config_module_sign - KernelSecurityConfigTest.test_440_config_module_sign_all + [Impact] + + The linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security regression test due to kernel config options. The kernel configs were changed to + match the Xilinx provided kernel configs which resulted in these configs being disabled. + + [Fix] + + Enable the following configs: + PAGE_POISONING_ZERO + PAGE_POISONING_NO_SANITY + PAGE_POISONING + SECURITY_LOCKDOWN_LSM + SCHED_STACK_END_CHECK + SECURITY_YAMA
[Kernel-packages] [Bug 1995606] Re: Upgrade thermald to 2.5.1
** Description changed: [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. Currently, just use a stressing tools and monitor status manually(e.g. s-tui). Use stress-ng to stress the machine and observe the temperature/frequency/power. - The whole test cases are the followings, + The whole test cases are the followings and run on the platforms, RPL/ADL/TGL/CML/CFL/KBL. 1. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. 2. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. 3. 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. a. rapl.sh b. intel_pstate.sh c. powerclamp.sh d. processor.sh 4. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 5. check if system would be throttled even the temperature is under the thrip-poits. ** Changed in: thermald (Ubuntu) Assignee: (unassigned) => koba (kobako) ** Changed in: thermald (Ubuntu) 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 Status in thermald package in Ubuntu: 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. Currently, just use a stressing tools and monitor status manually(e.g. s-tui). Use stress-ng to stress the machine and observe the temperature/frequency/power. The whole test cases are the followings and run on the platforms, RPL/ADL/TGL/CML/CFL/KBL. 1. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. 2. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. 3. 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. a. rapl.sh b. intel_pstate.sh c. powerclamp.sh d. processor.sh 4. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 5. check if system would be throttled even the temperature is under the thrip-poits. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+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 1995607] [NEW] Laptop wont charge (usb-c) while in suspend
Public bug reported: My laptop charges fine if on or off but not during suspend. It charges over USB-C. Verified not charging using a charger with an amp reading. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: radec 973 F pipewire radec 976 F wireplumber /dev/snd/seq:radec 973 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 3 06:03:21 2022 InstallationDate: Installed on 2022-11-02 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Intel(R) Client Systems CMCN1CC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=00ba6fe9-0b35-454d-aae5-5adffc88f70e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: EBTGLMIV.0057.2021.0521.2137 dmi.board.name: CM11EBV716W dmi.board.vendor: Intel Corporation dmi.board.version: M15481-301 dmi.chassis.type: 10 dmi.chassis.vendor: Intel(R) Corporation dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.1 dmi.modalias: dmi:bvnIntelCorp.:bvrEBTGLMIV.0057.2021.0521.2137:bd05/21/2021:br5.19:efr3.1:svnIntel(R)ClientSystems:pnCMCN1CC:pvrK95289-402:rvnIntelCorporation:rnCM11EBV716W:rvrM15481-301:cvnIntel(R)Corporation:ct10:cvr1.0:sku: dmi.product.family: CC dmi.product.name: CMCN1CC dmi.product.version: K95289-402 dmi.sys.vendor: Intel(R) Client Systems ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/1995607 Title: Laptop wont charge (usb-c) while in suspend Status in linux package in Ubuntu: New Bug description: My laptop charges fine if on or off but not during suspend. It charges over USB-C. Verified not charging using a charger with an amp reading. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: radec 973 F pipewire radec 976 F wireplumber /dev/snd/seq:radec 973 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 3 06:03:21 2022 InstallationDate: Installed on 2022-11-02 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Intel(R) Client Systems CMCN1CC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=00ba6fe9-0b35-454d-aae5-5adffc88f70e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: EBTGLMIV.0057.2021.0521.2137 dmi.board.name: CM11EBV716W dmi.board.vendor: Intel Corporation dmi.board.version: M15481-301 dmi.chassis.type: 10 dmi.chassis.vendor: Intel(R) Corporation dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.1 dmi.modalias: dmi:bvnIntelCorp.:bvrEBTGLMIV.0057.2021.0521.2137:bd05/21/2021:br5.19:efr3.1:svnIntel(R)ClientSystems:pnCMCN1CC:pvrK95289-402:rvnIntelCorporation:rnCM11EBV716W:rvrM15481-301:cvnIntel(R)Corporation:ct10:cvr1.0:sku: dmi.product.family: CC dmi.product.name: CMCN1CC dmi.product.version: K95289-402 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995607/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpa
[Kernel-packages] [Bug 1995580] Re: load of value 8 is not a valid value for type '_Bool'
where did you get this kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995580 Title: load of value 8 is not a valid value for type '_Bool' Status in linux-oem-5.17 package in Ubuntu: New Bug description: Getting a call trace below with the 5.17.0-1003-oem OEM kernel. HW: Lenovo 21D4000HUS WNIC: 04:00.0 Network controller: Qualcomm QCNFA765 Wireless Network Adapter (rev 01) ~$ uname -r 5.17.0-1003-oem ноя 03 10:22:47 dz16 kernel: wlp4s0: send auth to aa:46:8d:38:07:9d (try 1/3) ноя 03 10:22:47 dz16 kernel: ноя 03 10:22:47 dz16 kernel: UBSAN: invalid-load in /build/linux-oem-5.17-vTcPy2/linux-oem-5.17-5.17.0/net/mac80211/status.c:1164:21 ноя 03 10:22:47 dz16 kernel: load of value 8 is not a valid value for type '_Bool' ноя 03 10:22:47 dz16 kernel: CPU: 9 PID: 0 Comm: swapper/9 Not tainted 5.17.0-1003-oem #3-Ubuntu ноя 03 10:22:47 dz16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS N3GET42W (1.22 ) 09/06/2022 ноя 03 10:22:47 dz16 kernel: Call Trace: ноя 03 10:22:47 dz16 kernel: ноя 03 10:22:47 dz16 kernel: show_stack+0x52/0x58 ноя 03 10:22:47 dz16 kernel: dump_stack_lvl+0x4c/0x63 ноя 03 10:22:47 dz16 kernel: dump_stack+0x10/0x12 ноя 03 10:22:47 dz16 kernel: ubsan_epilogue+0x9/0x45 ноя 03 10:22:47 dz16 kernel: __ubsan_handle_load_invalid_value.cold+0x44/0x49 ноя 03 10:22:47 dz16 kernel: ieee80211_tx_status_ext.cold+0x4e/0x5f [mac80211] ноя 03 10:22:47 dz16 kernel: ieee80211_tx_status+0x7d/0xa0 [mac80211] ноя 03 10:22:47 dz16 kernel: ieee80211_tasklet_handler+0xa2/0xd0 [mac80211] ноя 03 10:22:47 dz16 kernel: tasklet_action_common.constprop.0+0xc0/0xf0 ноя 03 10:22:47 dz16 kernel: tasklet_action+0x22/0x30 ноя 03 10:22:47 dz16 kernel: __do_softirq+0xd9/0x315 ноя 03 10:22:47 dz16 kernel: __irq_exit_rcu+0x87/0xb0 ноя 03 10:22:47 dz16 kernel: irq_exit_rcu+0xe/0x10 ноя 03 10:22:47 dz16 kernel: common_interrupt+0x8a/0xa0 ноя 03 10:22:47 dz16 kernel: ноя 03 10:22:47 dz16 kernel: ноя 03 10:22:47 dz16 kernel: asm_common_interrupt+0x1e/0x40 ноя 03 10:22:47 dz16 kernel: RIP: 0010:cpuidle_enter_state+0xec/0x630 ноя 03 10:22:47 dz16 kernel: Code: ff e8 a8 ee 6a ff 80 7d d0 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 3c 03 00 00 31 ff e8 3b c4 72 ff fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 73 01 00 00 4d 63 ee 49 8> ноя 03 10:22:47 dz16 kernel: RSP: 0018:a571001ffe28 EFLAGS: 0246 ноя 03 10:22:47 dz16 kernel: RAX: 94e422071340 RBX: 94dddb0e8400 RCX: 0005a1d2ec47 ноя 03 10:22:47 dz16 kernel: RDX: 0005a20ff50b RSI: 0005a1d2ec47 RDI: ноя 03 10:22:47 dz16 kernel: RBP: a571001ffe78 R08: 0005a1d2f24e R09: 000aae60 ноя 03 10:22:47 dz16 kernel: R10: 0004 R11: 071c71c71c71c71c R12: a60f6020 ноя 03 10:22:47 dz16 kernel: R13: 0003 R14: 0003 R15: 0005a1d2f24e ноя 03 10:22:47 dz16 kernel: ? cpuidle_enter_state+0xc8/0x630 ноя 03 10:22:47 dz16 kernel: cpuidle_enter+0x2e/0x40 ноя 03 10:22:47 dz16 kernel: cpuidle_idle_call+0x13e/0x1d0 ноя 03 10:22:47 dz16 kernel: do_idle+0x83/0xf0 ноя 03 10:22:47 dz16 kernel: cpu_startup_entry+0x20/0x30 ноя 03 10:22:47 dz16 kernel: start_secondary+0x12a/0x180 ноя 03 10:22:47 dz16 kernel: secondary_startup_64_no_verify+0xd5/0xdb ноя 03 10:22:47 dz16 kernel: ноя 03 10:22:47 dz16 kernel: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1995580/+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] [NEW] Upgrade thermald to 2.5.1
Public bug reported: [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. Currently, just use a stressing tools and monitor status manually(e.g. s-tui). Use stress-ng to stress the machine and observe the temperature/frequency/power. The whole test cases are the followings, 1. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. 2. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. 3. 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. a. rapl.sh b. intel_pstate.sh c. powerclamp.sh d. processor.sh 4. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 5. check if system would be throttled even the temperature is under the thrip-poits. ** Affects: thermald (Ubuntu) Importance: Undecided Status: New ** Description changed: [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. Currently, just use a stressing tools and monitor status manually(e.g. s-tui). Use stress-ng to stress the machine and observe the temperature/frequency/power. The whole test cases are the followings, 1. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. 2. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. 3. 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. a. rapl.sh b. intel_pstate.sh c. powerclamp.sh d. processor.sh 4. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 5. check if system would be throttled even the temperature is under the thrip-poits. - /dev/acpi_thermal_rel -- 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 Status in thermald package in Ubuntu: New 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. Currently, just use a stressing tools and monitor status manually(e.g. s-tui). Use stress-ng to stress the machine and observe the temperature/frequency/power. The whole test cases are the followings, 1. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. 2. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. 3. 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. a. rapl.sh b. intel_pstate.sh c. powerclamp.sh d. processor.sh 4. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 5. check if system would be throttled even the temperature is under the thrip-poits. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+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 1981366] Re: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam
The reason blocking pings prevents the IP address change is because a lot of DHCP servers ping the IP before they (re)allocate the address. If the device responds to the ping then the DHCP server abandons the IP and leases a new one. For this reason the network stack should; in my opinion ignore IPv4 ICMP echo requests during the DHCP part of the roam process. Indeed I believe that this was the behaviour previously. Blocking IPv4 pings isnt impacting any other functionality for me. -- 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/1981366 Title: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle of WiFi roam events which is causing the IP address to change every time it roams on the WiFi network. This is a huge problem for me because I install WiFi networks for a living but in general it causes every TCP connection over IPv4 to die every time the laptop roams to a new wifi cell. 00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20) I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18. Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE elem, Disable HE Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0110] device (wlp0s20f3): supplicant interface state: completed -> authenticating Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> authenticating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (wlp0s20f3): ip:dhcp4: restarting Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): canceled DHCP transaction Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): state changed no lease Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0113] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 MHz) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0463] device (wlp0s20f3): supplicant interface state: authenticating -> associating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0464] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (wlp0s20f3): supplicant interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0799] device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0800] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: WPA: Key negotiation completed with 86:2a:a8:8b:05:cb [PTK=CCMP GTK=CCMP] Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-CONNECTED - Connection to 86:2a:a8:8b:05:cb completed [id=0 id_str=] Jul 11 20:11:15 littlebrat discord_discord.desktop[4119]: [2022-07-11 20:11:15.091] [4119] (discord.cpp:551): JS console: ["%c[GatewaySocket]","Performing an expedited heartbeat reason: network detected online."] Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise= txrate=26000 Jul 11 20:11:15 littlebrat Networ
[Kernel-packages] [Bug 1994126] Re: NULL pointer dereference in power_supply_get_property
I'm experiencing the same problem. My equipment is a Lenovo P53 laptop, the kernel panic happens when connected to the Lenovo USB-C Dock and booting to the 5.19 kernel. -- 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/1994126 Title: NULL pointer dereference in power_supply_get_property Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 final release boot via usb thumb drive on thinkpad T480 (containing nvidia gpu) reproducible kernel panic during boot backtrace via OCR from picture of kernel panic: Started Periodic ext4 Online Hetadata Check for All Filesystems. Started Discard unused blocks once a week. Started Refresh fuupd metadate regularly. Started Daily rotation of log files. Started Daily man-db regeneration. Started Message of the Day. Started Daily Cleanup of Temporary Directories. Started Ubuntu Advantage Timer for running repeated jobs. Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation Socket. 1 Listening on CUPS Scheduler. 1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation for snappy deeson... Listening on UUID deemon activation socket. 1 Listening on Socket activation for snappy daemon. Reached target Socket Units. 1 Reached target Basic System. 20.300662) BUG: Kernel NULL pointer dereference, address: 20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 WPF: error code (0x0010) - not-present page 20.302458) PGD O P40 0 20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579) CPU: 4 PID: 1 Comm: systemd Tainted: P 0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 20L5000BGE/20L5000BGE, BIOS N24ET7ON (1.45) 07/22/2022 20.304190) 20.304774) RIP: 0010:0N0 20.305376) Code: Unable to access opcode bytes at RIP Oxffd6. 20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202 20.3066231 RAX: RBX: 95538288 RCX: 8c43c1d89800 20.307282) RDX: b17180087cdo RSI: 0004 RDI: 8c43c1d89800 20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09: 0 20.308627) R10: R11: R12: 00 20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15: 9553a288 20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000 20.310762) CS: 0010 DS: ES: CRO: 80050033 20.311491) CR2: fffds CRS: 00011eida002 CR4: 003706e0 20.312241) Call Trace: 20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+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 1981366] Re: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam
The only upstream bug that seems potentially related is https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1024 . But that's more about ensuring that WPA auth has completed before starting the DHCP renewal, and it's not clear to me how blocking ICMP could avoid that problem. So it might not actually be related. The fix for that issue went into development version NM 1.39.9, so I may try building and trying an upstream version which includes it, to see if that fixes the problem (but I won't be able to try before next week at the earliest). ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #1024 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1024 -- 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/1981366 Title: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle of WiFi roam events which is causing the IP address to change every time it roams on the WiFi network. This is a huge problem for me because I install WiFi networks for a living but in general it causes every TCP connection over IPv4 to die every time the laptop roams to a new wifi cell. 00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20) I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18. Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE elem, Disable HE Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0110] device (wlp0s20f3): supplicant interface state: completed -> authenticating Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> authenticating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (wlp0s20f3): ip:dhcp4: restarting Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): canceled DHCP transaction Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): state changed no lease Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0113] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 MHz) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0463] device (wlp0s20f3): supplicant interface state: authenticating -> associating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0464] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (wlp0s20f3): supplicant interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0799] device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0800] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: WPA: Key negotiation completed with 86:2a:a8:8b:05:cb [PTK=CCMP GTK=CCMP] Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-CONNECTED - Connection to 86:2a:a8:8b:05:cb completed [id=0 id_str=] Jul 11 20:11:15 littlebrat discord_discord.desktop[4119]: [2022-07-11 20:11:15.091] [4119] (discord.cpp:551): JS console: ["%c[GatewayS
[Kernel-packages] [Bug 1995494] Re: Guest VM freeze after "soft lockup"
Same or similar issue here. Host os: windows 10 enterprise / Version 10.0.19045 Build 19045 VMware® Workstation 16 Pro / 16.2.3 build-19376536 Guest os: Ubuntu 22.04.1 LTS \n \l Linux ubuntu 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux journalctl around time of crash: Nov 03 11:34:10 ubuntu kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 52s! [kworker/1:0:2921] + call trace etc. but on other crashes it was in systemd or systemd-oomd) I can still suspend/resume VM to "unblock" the crashed VM. -- 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/1995494 Title: Guest VM freeze after "soft lockup" Status in linux package in Ubuntu: Confirmed Bug description: Hi, After roughly 15 minutes of execution, any Ubuntu VM (20.04 / 22.04) on the latest and greatest stable kernel throws the following error and is fully frozen and the CPU is at 100%: > dev kernel: [ 920.717075] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [kworker/2:0:28] The only resolution is to restart the VM, I haven't found a way to prevent this from happening. Let me know if I need to attach any more information for this issue. Thanks, Pavel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pavel 1692 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 2 14:09:44 2022 IwConfig: lono wireless extensions. ens33 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=a74339af-1949-49cc-817a-140a3b97e100 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995494/+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 1995491] Re: [UBUNTU 20.04] "kauditd: hold queue overflow " and node failure
Hi Boris (et al). Can you please either share the dump on ECuRep at /fromibm/linux, or sftp it to files.support.canonical.com? Thanks! -- 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/1995491 Title: [UBUNTU 20.04] "kauditd: hold queue overflow " and node failure Status in linux package in Ubuntu: New Bug description: ---Problem Description--- This is an issue being reported on a node that went down. Had a chance to look at the currently available logs, which doesn't provide me sufficient indication of a potential issue beyond an issue w.r.t "kauditd: hold queue overflow " (~790 number of messages ) Would be great to have your review on the dump file to see , whether there is anything significant that caused the node down. Contact Information = Kishore Kumar G/kishore.pil...@in.ibm.com ---uname output--- I will come back with the uname output , as I couldn't get that info from the logs Machine Type = z15 -GT2 lpar ---Debugger--- A debugger is not configured Stack trace output: no Oops output: no System Dump Location: [18:in07100f@ecurep]:/ecurep/toibm/linux $ ls 2022_09_26_18_18_51_tor2-qz1-sr1-rk085-s03_192.168.85.7_5.4.0-121-generic_dumpfile 2022_09_26_18_18_51_tor2-qz1-sr1-rk085-s03_192.168.85.7_5.4.0-121-generic_locDmsg *Additional Instructions for Kishore Kumar G/kishore.pil...@in.ibm.com: -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995491/+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 1981366] Re: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam
I have the same symptoms on Ubuntu 22.04.1 on a 12th-gen Framework laptop with Intel Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) device. Every time wpa-supplicant chooses to associate with a different BSSID (of the same SSID), the interface ends up being given a new IP address by the DHCP server (usually the sequentially next address). I don't have access to the DHCP server or its logs, but I tried the above suggested workaround of setting net.ipv4.icmp_echo_ignore_all=1 and this prevents the problem from occurring. So I expect the root cause is the same. (And as an aside, there is nothing in the client- side logs to indicate that ICMP pings could be in any way related; without this report it would have much more difficult to diagnose and work around the problem.) A different laptop running 18.04 on the same network is able to keep its IP address when roaming, so presumably this is due to a change in NetworkManager behaviour. The problem makes it difficult to work in an enterprise office environment (ie. moving around between desks and meeting rooms), because all TCP connections are lost when the IP address changes, which is especially impactful for ssh connections. -- 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/1981366 Title: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle of WiFi roam events which is causing the IP address to change every time it roams on the WiFi network. This is a huge problem for me because I install WiFi networks for a living but in general it causes every TCP connection over IPv4 to die every time the laptop roams to a new wifi cell. 00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20) I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18. Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE elem, Disable HE Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0110] device (wlp0s20f3): supplicant interface state: completed -> authenticating Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> authenticating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (wlp0s20f3): ip:dhcp4: restarting Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): canceled DHCP transaction Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): state changed no lease Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0113] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 MHz) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0463] device (wlp0s20f3): supplicant interface state: authenticating -> associating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0464] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (wlp0s20f3): supplicant interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0799] device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0800] device (p2p-dev-wlp0s20f3): supplicant management interface sta
[Kernel-packages] [Bug 1944389] Re: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz
** Changed in: thermald (Ubuntu) Status: New => Won't Fix -- 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/1944389 Title: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz Status in thermald package in Ubuntu: Won't Fix Bug description: After update to 1.9.1-1ubuntu0.6 from 1.9.1-1ubuntu0.4 thermald keeps Tigerlake Iris Xe GPU frequency on 400 MHz after reaching some high temperature value. It became impossible to play video games on the laptop. System: Ubuntu 20.04.3 LTS Kernel: 5.10.0-1045-oem Laptop: Dell XPS 9310, CPU: Intel Core i7-1165G7 (Tigerlake), Integrated GPU Iris Xe. BIOS 2.1.1 03/25/2021 Display: 2560x1440 144Hz HDMI USB-C connection Room temperature is 23.5-25.4 degrees Game: Stalker Clear Sky (Wine/Proton Steam) Note: The game itself is very old and loads 100% of one CPU core disregarding of frequency. GPU frequency is monitored by intel-gpu-top GPU frequencies (according to /sys/class/drm/card0/) min/max/boost/efficiency: 100/1300/1300/400 Previous behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. After some time when threshold temperature value (~78 degrees) is reached the GPU frequency decreases to ~660 MHz and FPS to 40-48 FPS. Package temperature decreases to 66-68 degrees. It's possible to play for indefinite amount of time. New behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. But after reaching the threshold temperature (about 81 degrees) GPU frequency decreases to 400 MHz (gt_RP1_freq_mhz -- "efficiency" temperature for the GPU) and stays on this value for the indefinite amount of time. The temperature is maintained on 70-74 degrees. FPS is about 25-30 FPS, it is not possible to play the game anymore. The only way to return the good FPS and frequency is to fold the game window, wait some time and open it again. Also there is a workaround -- limit the CPU frequency to 2001 MHz and disable Intel turbo boost. With such approach package temperature never reaches 80 degrees and it is possible to play game with 500 MHz and 35-40 FPS. Better than nothing. If it is needed I can perform any additional checks, provide CPU frequencies and so on. Most probably regression happened with 1.9.1-1ubuntu0.5, but I tried only versions 0.4 and 0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1944389/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
** Tags added: fr-2934
--
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/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Triaged
Status in grub2-unsigned package in Ubuntu:
Triaged
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to access.
[Other Info]
* Upstream grub2 bug #61058
https://savannah.gnu.org/bugs/index.php?61058
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
* Test grubx64.efi:
https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320
* Test source code: https://github.com/os369510/grub2/tree/lp1842320
* If you built the package, then test grubx64.efi is under
“obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
`/var/cache/pbuilder/build/276481/build/grub2-2.06/obj/monolithic/grub-
efi-amd64/grubx64.e
[Kernel-packages] [Bug 1987595] Re: Support Intel IPU6 MIPI camera
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- 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/1987595 Title: Support Intel IPU6 MIPI camera Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Confirmed Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: Incomplete Status in linux-firmware source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justfication:linux-firmware] [Impact] Need new firmware updates for additional camera senesors. [Fix] Firmware updates for Intel IPU6/VSC drivers, as well as new firmware blobs for hi556/ovti02c1. [Test Case] The driver will prompt for missed firmware blobs for a given platform. [Where problems could occur] There is still no suspend support for the camera driver, and user sessions across system suspend have to be restarted. [Other Info] New sensors are introduced in Jammy oem kernels only, and kinetic is nominated for future hwe migration. = original bug report == This is a follow-up for bug 1964983 but on different platforms that runs linux-oem-5.17 or newer. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987595/+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 1995580] [NEW] load of value 8 is not a valid value for type '_Bool'
Public bug reported: Getting a call trace below with the 5.17.0-1003-oem OEM kernel. HW: Lenovo 21D4000HUS WNIC: 04:00.0 Network controller: Qualcomm QCNFA765 Wireless Network Adapter (rev 01) ~$ uname -r 5.17.0-1003-oem ноя 03 10:22:47 dz16 kernel: wlp4s0: send auth to aa:46:8d:38:07:9d (try 1/3) ноя 03 10:22:47 dz16 kernel: ноя 03 10:22:47 dz16 kernel: UBSAN: invalid-load in /build/linux-oem-5.17-vTcPy2/linux-oem-5.17-5.17.0/net/mac80211/status.c:1164:21 ноя 03 10:22:47 dz16 kernel: load of value 8 is not a valid value for type '_Bool' ноя 03 10:22:47 dz16 kernel: CPU: 9 PID: 0 Comm: swapper/9 Not tainted 5.17.0-1003-oem #3-Ubuntu ноя 03 10:22:47 dz16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS N3GET42W (1.22 ) 09/06/2022 ноя 03 10:22:47 dz16 kernel: Call Trace: ноя 03 10:22:47 dz16 kernel: ноя 03 10:22:47 dz16 kernel: show_stack+0x52/0x58 ноя 03 10:22:47 dz16 kernel: dump_stack_lvl+0x4c/0x63 ноя 03 10:22:47 dz16 kernel: dump_stack+0x10/0x12 ноя 03 10:22:47 dz16 kernel: ubsan_epilogue+0x9/0x45 ноя 03 10:22:47 dz16 kernel: __ubsan_handle_load_invalid_value.cold+0x44/0x49 ноя 03 10:22:47 dz16 kernel: ieee80211_tx_status_ext.cold+0x4e/0x5f [mac80211] ноя 03 10:22:47 dz16 kernel: ieee80211_tx_status+0x7d/0xa0 [mac80211] ноя 03 10:22:47 dz16 kernel: ieee80211_tasklet_handler+0xa2/0xd0 [mac80211] ноя 03 10:22:47 dz16 kernel: tasklet_action_common.constprop.0+0xc0/0xf0 ноя 03 10:22:47 dz16 kernel: tasklet_action+0x22/0x30 ноя 03 10:22:47 dz16 kernel: __do_softirq+0xd9/0x315 ноя 03 10:22:47 dz16 kernel: __irq_exit_rcu+0x87/0xb0 ноя 03 10:22:47 dz16 kernel: irq_exit_rcu+0xe/0x10 ноя 03 10:22:47 dz16 kernel: common_interrupt+0x8a/0xa0 ноя 03 10:22:47 dz16 kernel: ноя 03 10:22:47 dz16 kernel: ноя 03 10:22:47 dz16 kernel: asm_common_interrupt+0x1e/0x40 ноя 03 10:22:47 dz16 kernel: RIP: 0010:cpuidle_enter_state+0xec/0x630 ноя 03 10:22:47 dz16 kernel: Code: ff e8 a8 ee 6a ff 80 7d d0 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 3c 03 00 00 31 ff e8 3b c4 72 ff fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 73 01 00 00 4d 63 ee 49 8> ноя 03 10:22:47 dz16 kernel: RSP: 0018:a571001ffe28 EFLAGS: 0246 ноя 03 10:22:47 dz16 kernel: RAX: 94e422071340 RBX: 94dddb0e8400 RCX: 0005a1d2ec47 ноя 03 10:22:47 dz16 kernel: RDX: 0005a20ff50b RSI: 0005a1d2ec47 RDI: ноя 03 10:22:47 dz16 kernel: RBP: a571001ffe78 R08: 0005a1d2f24e R09: 000aae60 ноя 03 10:22:47 dz16 kernel: R10: 0004 R11: 071c71c71c71c71c R12: a60f6020 ноя 03 10:22:47 dz16 kernel: R13: 0003 R14: 0003 R15: 0005a1d2f24e ноя 03 10:22:47 dz16 kernel: ? cpuidle_enter_state+0xc8/0x630 ноя 03 10:22:47 dz16 kernel: cpuidle_enter+0x2e/0x40 ноя 03 10:22:47 dz16 kernel: cpuidle_idle_call+0x13e/0x1d0 ноя 03 10:22:47 dz16 kernel: do_idle+0x83/0xf0 ноя 03 10:22:47 dz16 kernel: cpu_startup_entry+0x20/0x30 ноя 03 10:22:47 dz16 kernel: start_secondary+0x12a/0x180 ноя 03 10:22:47 dz16 kernel: secondary_startup_64_no_verify+0xd5/0xdb ноя 03 10:22:47 dz16 kernel: ноя 03 10:22:47 dz16 kernel: ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995580 Title: load of value 8 is not a valid value for type '_Bool' Status in linux-oem-5.17 package in Ubuntu: New Bug description: Getting a call trace below with the 5.17.0-1003-oem OEM kernel. HW: Lenovo 21D4000HUS WNIC: 04:00.0 Network controller: Qualcomm QCNFA765 Wireless Network Adapter (rev 01) ~$ uname -r 5.17.0-1003-oem ноя 03 10:22:47 dz16 kernel: wlp4s0: send auth to aa:46:8d:38:07:9d (try 1/3) ноя 03 10:22:47 dz16 kernel: ноя 03 10:22:47 dz16 kernel: UBSAN: invalid-load in /build/linux-oem-5.17-vTcPy2/linux-oem-5.17-5.17.0/net/mac80211/status.c:1164:21 ноя 03 10:22:47 dz16 kernel: load of value 8 is not a valid value for type '_Bool' ноя 03 10:22:47 dz16 kernel: CPU: 9 PID: 0 Comm: swapper/9 Not tainted 5.17.0-1003-oem #3-Ubuntu ноя 03 10:22:47 dz16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS N3GET42W (1.22 ) 09/06/2022 ноя 03 10:22:47 dz16 kernel: Call Trace: ноя 03 10:22:47 dz16 kernel: ноя 03 10:22:47 dz16 kernel: show_stack+0x52/0x58 ноя 03 10:22:47 dz16 kernel: dump_stack_lvl+0x4c/0x63 ноя 03 10:22:47 dz16 kernel: dump_stack+0x10/0x12 ноя 03 10:22:47 dz16 kernel: ubsan_epilogue+0x9/0x45 ноя 03 10:22:47 dz16 kernel: __ubsan_handle_load_invalid_value.cold+0x44/0x49 ноя 03 10:22:47 dz16 kernel: ieee80211_tx_status_ext.cold+0x4e/0x5f [mac80211] ноя 03 10:22:47 dz
[Kernel-packages] [Bug 1995453] Re: Add some ACPI device IDs for Intel HID device
** Tags added: originate-from-1993325 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995453 Title: Add some ACPI device IDs for Intel HID device Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-5.17 source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: New Status in linux source package in Kinetic: New Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] Add the ACPI devices IDs for Intel JasonLake, MeteorLake and RaptorLake [Fix] ACPI devices IDs are add the the related Intel HID devices on these platforms can work. [Test] Verified the Intel HID events can work such as power button for suspend and wake. [Where problems could occur] Add the ACPI device IDs for support Intel HID devices, so chance of problems should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995453/+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] Proposed package upload rejected
An upload of thermald to jammy-proposed has been rejected from the upload queue for the following reason: "Please re-upload with an overall "upgrade to 2.5.1" process bug, detailing the testing to be done to detect regressions across 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/1981087 Title: thermald prematurely throttling GPU Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Incomplete Bug description: [Impact] * thermald prematurely throttling GPU [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 1989044] Proposed package upload rejected
An upload of thermald to jammy-proposed has been rejected from the upload queue for the following reason: "Please re-upload with an overall "upgrade to 2.5.1" process bug, detailing the testing to be done to detect regressions across 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/1989044 Title: RPL: Add INT3400 base path Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: New 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 1989047] Proposed package upload rejected
An upload of thermald to jammy-proposed has been rejected from the upload queue for the following reason: "Please re-upload with an overall "upgrade to 2.5.1" process bug, detailing the testing to be done to detect regressions across 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/1989047 Title: ADL: Fix System hang up when run Prime95 with i9-12900K CPU Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: New Bug description: [Impact] * System hang up when run Prime95 10~15 minutes [Test Plan] 1. Find a unit with i9-12900k CPU and liquid cooling 2. Connect to Internet and install below tools >sudo apt update >sudo apt install stress-ng >sudo apt install 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 #decompressed from p95*.tar.gz >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] * it install Passive Policy as default and use PL1 max/min from PPCC, there may be some edge cases that don't handle well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1989047/+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 1989556] Proposed package upload rejected
An upload of thermald to jammy-proposed has been rejected from the upload queue for the following reason: "Please re-upload with an overall "upgrade to 2.5.1" process bug, detailing the testing to be done to detect regressions across 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/1989556 Title: Add support for Raptor Lake S CPUs Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Released Bug description: [Impact] * Support thermald on Raptor Lake S CPU. [Test Plan] * Use a machine with a Raptor Lake S cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake S in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1989556/+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 1995573] Re: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]
** Tags added: oem-priority originate-from-1990928 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995573 Title: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536] Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Screen cannot turn on after screen is off [Fix] Below commit from v6.0-rc1 fixes the issue c577b2f43e80 drm/mgag200: Enable atomic gamma lut update [Tests] Verified on the machine with Matrox G200eW3 [102b:0536] graphics card. [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995573/+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
This SRU remains blocked on https://lists.ubuntu.com/archives/ubuntu- release/2022-October/005495.html. For a straight backport to Jammy, if that is the conclusion, then the upload also needs an SRU meta-bug really to document the justification and regression risk mitigation for the backport. ** Changed in: thermald (Ubuntu Jammy) Status: In Progress => Incomplete -- 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: Incomplete Bug description: [Impact] * thermald prematurely throttling GPU [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 1995573] Re: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]
** Description changed: [Impact] + Screen cannot turn on after screen is off [Fix] + Below commit from v6.0-rc1 fixes the issue + c577b2f43e80 drm/mgag200: Enable atomic gamma lut update [Tests] + Verified on the machine with Matrox G200eW3 [102b:0536] graphics card. [Where problems could occur] -- 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/1995573 Title: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536] Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Screen cannot turn on after screen is off [Fix] Below commit from v6.0-rc1 fixes the issue c577b2f43e80 drm/mgag200: Enable atomic gamma lut update [Tests] Verified on the machine with Matrox G200eW3 [102b:0536] graphics card. [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995573/+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 1995573] [NEW] Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]
Public bug reported: [Impact] [Fix] [Tests] [Where problems could occur] ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) -- 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/1995573 Title: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536] Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] [Fix] [Tests] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995573/+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 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Tags added: originate-from-1992399
--
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/1990089
Title:
Screen freeze when performing memory stress in Wayland mode
Status in Linux:
New
Status in Mutter:
Fix Released
Status in OEM Priority Project:
Incomplete
Status in linux package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Opinion
Bug description:
[Steps to reproduce]
(disable systemd-oomd or executing over ssh)
(below command allocates a lot of memory to stress kernel page fault)
1. stress-ng --stack 0 --timeout 300
2. check the screen
[Expected result]
Screen will update slowly when performing the stress-test.
but screen needs back to work after stress.
[Actual result]
Screen freeze after stress test.
[Additional information]
kernel version: vmlinuz-5.17.0-1017-oem
kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
Mesa version: 22.0.5-0ubuntu0.1
Mutter version: 42.2-0ubuntu1
Gnome-shell version: 42.2-0ubuntu0.2
* Issue happens in Wayland only
* gnome-shell keeps issuing ioctl()
```
(gdb) bt
#0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at
../sysdeps/unix/sysv/linux/ioctl.c:36
#1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80,
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
#2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=,
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
#3 iris_wait_syncobj (bufmgr=, syncobj=,
timeout_nsec=timeout_nsec@entry=9223372036854775807) at
../src/gallium/drivers/iris/iris_fence.c:215
#4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50,
wait=, query=0x55774159b800, ctx=) at
../src/gallium/drivers/iris/iris_query.c:635
#5 iris_get_query_result (ctx=, query=0x55774159b800,
wait=, result=0x7fffc5404e50) at
../src/gallium/drivers/iris/iris_query.c:601
#6 0x7fcaca405e89 in tc_get_query_result (_pipe=,
query=0x55774159b800, wait=, result=0x7fffc5404e50) at
../src/gallium/auxiliary/util/u_threaded_context.c:881
#7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0,
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at
../src/mesa/main/queryobj.c:266
#8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790,
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
#9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283
"glGetQueryObjecti64v", id=, pname=34918,
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
at ../src/mesa/main/queryobj.c:1174
#10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=,
pname=, params=) at
../src/mesa/main/queryobj.c:1257
#11 0x7fcadfa39b90 in ?? () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#20 0x7fcae0743c24 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fcae0743293 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fcadf8d0849 in meta_context_run_main_loop () from
/lib/x86_64-linux-gnu/libmutter-10.so.0
#24 0x55773f1a4f12 in ?? ()
#25 0x7fcadf429d90 in __libc_start_call_main
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1,
argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70,
argc=1, argv=0x7fffc54053e8, init=, fini=,
rtld_fini=, stack_end=0x7fffc54053d8)
at ../csu/libc-start.c:392
#27 0x55773f1a51b5 in ?? ()
```
Other discussion thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/6851
https://gitlab.gnome.org/GNOME/mutter/-/issues/2431
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter (not installed)
Uname: Linux 5.18.0-rc2+ x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Sep 19 10:39:59 2022
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.c
[Kernel-packages] [Bug 1981366] Re: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1981366 Title: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle of WiFi roam events which is causing the IP address to change every time it roams on the WiFi network. This is a huge problem for me because I install WiFi networks for a living but in general it causes every TCP connection over IPv4 to die every time the laptop roams to a new wifi cell. 00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20) I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18. Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE elem, Disable HE Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0110] device (wlp0s20f3): supplicant interface state: completed -> authenticating Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> authenticating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (wlp0s20f3): ip:dhcp4: restarting Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): canceled DHCP transaction Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): state changed no lease Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0113] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 MHz) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0463] device (wlp0s20f3): supplicant interface state: authenticating -> associating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0464] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (wlp0s20f3): supplicant interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0799] device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0800] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: WPA: Key negotiation completed with 86:2a:a8:8b:05:cb [PTK=CCMP GTK=CCMP] Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-CONNECTED - Connection to 86:2a:a8:8b:05:cb completed [id=0 id_str=] Jul 11 20:11:15 littlebrat discord_discord.desktop[4119]: [2022-07-11 20:11:15.091] [4119] (discord.cpp:551): JS console: ["%c[GatewaySocket]","Performing an expedited heartbeat reason: network detected online."] Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise= txrate=26000 Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0970] device (wlp0s20f3): supplicant interface state: 4way_handshake -> completed Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0975] device (p2p-dev-wlp0s20f3): supplicant management interface state: 4way_handshake -> completed Jul 11 20:11:17 gateway-ycs dhcpd: DHCPDISCOVER from 5c:e4:2a:c
