[Kernel-packages] [Bug 2049569] Re: Enable the mic-mute led on Dell MTL laptops
MR for jammy/mantic/noble. The MR contains the required tplg binary and the patch file. https://code.launchpad.net/~mschiu77/ubuntu/+source/firmware-sof/+git/firmware-sof/+merge/461948 https://code.launchpad.net/~mschiu77/ubuntu/+source/firmware-sof/+git/firmware-sof/+merge/461950 https://code.launchpad.net/~mschiu77/ubuntu/+source/firmware-sof/+git/firmware-sof/+merge/461951 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049569 Title: Enable the mic-mute led on Dell MTL laptops Status in HWE Next: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in firmware-sof source package in Noble: New Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justifications] == kernels == [Impact] On Dell's Precision 3550, Intel MTL platform, the MIC-Mute function is working but the LED(on F4) state is not changed accordingly. [Fix] There's no problem on the same series on RPL platform. It needs MTL specific SoF driver and controls to support the registered mixer switch. It requires the patches in https://lore.kernel.org/all/20230919103115.30783-1-peter.ujfal...@linux.intel.com/ and https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. 2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled. [Where problems could occur] It's only required for new sof-audio-pci-intel-mtl driver. The impact should be restricting. == firmware-sof == [Impact] The mic-mute led not working on Intel MTL powered laptops. [Fix] For firmware-sof, it required the upstream commit fdc884baa4b3 ("Add sof-ipc4-v2.8.1/mtl/, intel-signed + community") and the sof-hda-generic-2ch.tplg from v2.8.1 to make sure the ipc4 topology and control matches with the updated driver. [Test Case] 1. enable -proposed pocket and install firmware-sof-signed 2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. [Where problems could occur] The updated sof-mtl.ri and the sof-hda-generic-2ch.tplg are shared by all Intel MTL platforms. Need to verify audio function on MTL enpowered machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049569/+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 2056317] Re: package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problemas de dependência - deixando desconfigurado
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2056317 Title: package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problemas de dependência - deixando desconfigurado Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I can not install the gpu driver without an error. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-driver-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: google-chrome-stable:amd64: Install libde265-0:amd64: Install zotero:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Mar 5 20:09:23 2024 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2024-02-02 (32 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2056317/+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 2056373] Re: Multiple issues found on Ubuntu 20.04 against HVCS
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => (unassigned) ** Changed in: ubuntu-power-systems Importance: Undecided => High -- 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/2056373 Title: Multiple issues found on Ubuntu 20.04 against HVCS Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Issues with HVCS and hotplugging issues. When working on Canonical bug 2023243, it was discovered that mkvterm was not working for multiple reasons. This bug will cover the issues found in HVCS, and hotplugging issues found when drmgr writes the slot information to .../add_slot. When mkvterm is ran, it ultimately fails because it calls pvmutil which fails. pvmutil calls drmgr, and drmgr is adding a slot correctly. However, when drmgr writes the slot information to ?/add_slot, the return is -ENODEV. This leads to HVCS never having probe() called. In addition, HVCS is missing patches, and is broken without them. 8 kernel patches have been identified to fix these issues. ---uname output--- Linux neop91.pok.stglabs.ibm.com 5.4.0-173-generic #191-Ubuntu SMP Fri Feb 2 13:54:35 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux ---Steps to Reproduce--- Run mkvterm with an id. mkvterm will fail because /dev/hvcs* device nodes are missing. See https://bugs.launchpad.net/ubuntu/+source/powerpc-utils/+bug/2023243 for more information. 2 commits made to arch/powerpc/platforms/pseries/of_helpers.c are needed. These commits fix the hotplugging issue seen when drmgr goes to write the slot information to /sys/bus/pci/slots/control/add_slot. This is also why the HVCS device nodes were not being created, as mentioned in the previous bug. The issue lies in rpadlpar_io and rpaphp calling an of helper function of_read_drc_info_cell(). Without these commits, the value stored drc_index_start is incorrect. This ultimately results in the entire SLOT string being incorrect, and rpaphp never finding the newly added slot by drmgr. rpadlpar then returns -ENODEV. Therefore, HVCS is never probed, and the device nodes are never created. Ideally - HVCS, rpadlpar_io, and rpaphp should not even need to be loaded prior to drmgr adding a vio slot. If rpadlpar_io and rpaphp are not loaded, drmgr will load them. In addition, if rpadlpar_io and rpaphp register the new slot correctly, rpadlpar_io will call dlpar_add_vio_slot(), which calls vio_register_device_node() with the device node. This is what tells the driver core to init and probe HVCS (which is needed to create the device nodes). In addition to the 2 commits mentioned above, 6 HVCS commits are needed. HVCS is essentially broken without them. Issues include race conditions, hotplug remove issues, as well as memory leaks. These commits have been added to other distros after multiple issues were seen. Without these commits, 20.04 will experience the same issues. IBM plans on stress testing these changes after an updated kernel is provided in focal-proposed. --- 2 commits that make changes to arch/powerpc/platforms/pseries/of_helpers.c: powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=57409d4fb12c185b2c0689e0496878c8f6bb5b58 powerpc/pseries: Fix of_read_drc_info_cell() to point at next record https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c5e76fa05b2df519b9f08571cc57e623c1569faa HVCS commits: hvcs: Fix hvcs port reference counting https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a9a733edd46732e906d976dc21a42dd361e53cc hvcs: Use dev_groups to manage hvcs device attributes https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=760aa5e81f33e0da82512c4288489739a6d1c556 hvcs: Use driver groups to manage driver attributes https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=503a90dd619d52dcac2cc68bd742aa914c7cd47a hvcs: Get reference to tty in remove https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3a8d3b366ce47024bf274eac783f8af5df2780f5 hvcs: Use vhangup in hotplug remove https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d432228bc7b1b3f0ed06510278ff5a77b3749fe6 hvcs: Synchronize hotplug remove with port free
[Kernel-packages] [Bug 2055866] Re: Simplify kcontrol naming on Intel MTL platforms
** Description changed: [Impact] - We found some laptops from Dell and HP with Intel MTL platform suffer the same MIC-Mute led not working problem just like lp:2049569. + We found some laptops from Lenovo and HP with Intel MTL platform suffer the same MIC-Mute led not working problem just like lp:2049569. [Fix] - lp:2049569 adds switch/enum type of control on IPC4 to communicate correctly with MTL SoF FW. However, It requires the additional patches from https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/ to fix the kcontrol naming problem to align with the MTL SoF FW. + lp:2049569 adds switch/enum type of control on IPC4 to communicate correctly with MTL SoF FW. However, Lenovo and HP machines requires the additional patches from https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/ to fix the kcontrol naming problem to align with the MTL SoF FW. [Test Case] 1. Make sure the latest firmware-sof is installed. 2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. 3. The mic-mute led should be ON when mic-mute enabled, OFF when disabled. [Where problems could occur] It's only required for new sof-audio-pci-intel-mtl driver. The impact should be restricting. We may need more MTL machines to make sure the behavior is the aligned. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2055866 Title: Simplify kcontrol naming on Intel MTL platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: New Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: New Bug description: [Impact] We found some laptops from Lenovo and HP with Intel MTL platform suffer the same MIC-Mute led not working problem just like lp:2049569. [Fix] lp:2049569 adds switch/enum type of control on IPC4 to communicate correctly with MTL SoF FW. However, Lenovo and HP machines requires the additional patches from https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/ to fix the kcontrol naming problem to align with the MTL SoF FW. [Test Case] 1. Make sure the latest firmware-sof is installed. 2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. 3. The mic-mute led should be ON when mic-mute enabled, OFF when disabled. [Where problems could occur] It's only required for new sof-audio-pci-intel-mtl driver. The impact should be restricting. We may need more MTL machines to make sure the behavior is the aligned. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055866/+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 2056419] [NEW] [Ubuntu 24.04] Observed: ACPI Error: Aborting method \_SB.PMI0._GHL due to previous error (AE_NOT_EXIST) (20230628/psparse-529).
Private bug reported: On DELL PowerEdge system when Ubuntu 24.04 OS is Installed Observed ACPI Error: Aborting method \_SB.PMI0._GHL due to previous error (AE_NOT_EXIST) (20230628/psparse-529) in dmesg logs. Steps to Reproduce: - 1. Install Ubuntu 24.04 OS. 2. Boot to Ubuntu 24.04 OS and check for dmesg logs. 3. Observed "ACPI Error: Aborting method \_SB.PMI0._GHL due to previous error (AE_NOT_EXIST) (20230628/psparse-529)" in dmesg logs. Expected Results: - The error message should not be observed in dmesg logs. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- 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/2056419 Title: [Ubuntu 24.04] Observed: ACPI Error: Aborting method \_SB.PMI0._GHL due to previous error (AE_NOT_EXIST) (20230628/psparse-529). Status in linux package in Ubuntu: New Bug description: On DELL PowerEdge system when Ubuntu 24.04 OS is Installed Observed ACPI Error: Aborting method \_SB.PMI0._GHL due to previous error (AE_NOT_EXIST) (20230628/psparse-529) in dmesg logs. Steps to Reproduce: - 1. Install Ubuntu 24.04 OS. 2. Boot to Ubuntu 24.04 OS and check for dmesg logs. 3. Observed "ACPI Error: Aborting method \_SB.PMI0._GHL due to previous error (AE_NOT_EXIST) (20230628/psparse-529)" in dmesg logs. Expected Results: - The error message should not be observed in dmesg logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056419/+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 2056418] [NEW] Fix headphone mic detection issue on ALC897
Public bug reported: [Impact] Headphone mic is lost after resume from S3 or reboot with plugin. [Fix] Restore the headphone mic detect logic for ALC897 after lost power. [Test] Tested on hardware, the headphone mic appears as plugin after boot or resume from S3, and works fine. [Where problems could occur] It may break ALC897 sound input. ** Affects: hwe-next Importance: High Assignee: AaronMa (mapengyu) Status: New ** Affects: linux (Ubuntu) Importance: High Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: High Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: High Status: In Progress ** Affects: linux (Ubuntu Mantic) Importance: High Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: High Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-2049858 sutton ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Tags added: oem-priority originate-from-2049858 sutton ** Changed in: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) ** Changed in: hwe-next Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2056418 Title: Fix headphone mic detection issue on ALC897 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Headphone mic is lost after resume from S3 or reboot with plugin. [Fix] Restore the headphone mic detect logic for ALC897 after lost power. [Test] Tested on hardware, the headphone mic appears as plugin after boot or resume from S3, and works fine. [Where problems could occur] It may break ALC897 sound input. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2056418/+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 2056417] [NEW] [Ubuntu 24.04]Observed:ACPI BIOS Error (bug): Could not resolve symbol [\_SB.SCK3.C165], AE_NOT_FOUND (20230628/dswload2-162)
Private bug reported: On Dell PowerEdge system when Ubuntu 24.04 OS is Installed observed "ACPI BIOS Error (bug): Could not resolve symbol [\_SB.SCK3.C165], AE_NOT_FOUND (20230628/dswload2-162)" in dmesg logs. Steps to Reproduce: - 1. Install Ubuntu 24.04 OS. 2. Boot to Ubuntu 24.04 OS and check for dmesg logs. 3. Observed "ACPI BIOS Error (bug): Could not resolve symbol [\_SB.SCK3.C165], AE_NOT_FOUND (20230628/dswload2-162)" error messages in dmesg logs. Expected Results: - The error message should not be observed in dmesg logs. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- 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/2056417 Title: [Ubuntu 24.04]Observed:ACPI BIOS Error (bug): Could not resolve symbol [\_SB.SCK3.C165], AE_NOT_FOUND (20230628/dswload2-162) Status in linux package in Ubuntu: New Bug description: On Dell PowerEdge system when Ubuntu 24.04 OS is Installed observed "ACPI BIOS Error (bug): Could not resolve symbol [\_SB.SCK3.C165], AE_NOT_FOUND (20230628/dswload2-162)" in dmesg logs. Steps to Reproduce: - 1. Install Ubuntu 24.04 OS. 2. Boot to Ubuntu 24.04 OS and check for dmesg logs. 3. Observed "ACPI BIOS Error (bug): Could not resolve symbol [\_SB.SCK3.C165], AE_NOT_FOUND (20230628/dswload2-162)" error messages in dmesg logs. Expected Results: - The error message should not be observed in dmesg logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056417/+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 2056403] Re: Mantic update: upstream stable patchset 2024-03-07
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Portia Stephens (portias) ** Description changed: 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: upstream stable patchset 2024-03-07 + + Ported from the following upstream stable releases: + v6.1.75, v6.6.14 + from git://git.kernel.org/ + + x86/lib: Fix overflow when counting digits + x86/mce/inject: Clear test status value + EDAC/thunderx: Fix possible out-of-bounds string access + powerpc: add crtsavres.o to always-y instead of extra-y + powerpc/44x: select I2C for CURRITUCK + powerpc/pseries/memhp: Fix access beyond end of drmem array + selftests/powerpc: Fix error handling in FPU/VMX preemption tests + powerpc/powernv: Add a null pointer check to scom_debug_init_one() + powerpc/powernv: Add a null pointer check in opal_event_init() + powerpc/powernv: Add a null pointer check in opal_powercap_init() + powerpc/imc-pmu: Add a null pointer check in update_events_in_group() + spi: spi-zynqmp-gqspi: fix driver kconfig dependencies + mtd: rawnand: Increment IFC_TIMEOUT_MSECS for nand controller response + ACPI: video: check for error while searching for backlight device parent + ACPI: LPIT: Avoid u32 multiplication overflow + platform/x86/intel/vsec: Fix xa_alloc memory leak + cpufreq: scmi: process the result of devm_of_clk_add_hw_provider() + calipso: fix memory leak in netlbl_calipso_add_pass() + efivarfs: force RO when remounting if SetVariable is not supported + spi: sh-msiof: Enforce fixed DTDL for R-Car H3 + ACPI: LPSS: Fix the fractional clock divider flags + ACPI: extlog: Clear Extended Error Log status when RAS_CEC handled the error + kunit: debugfs: Fix unchecked dereference in debugfs_print_results() + mtd: Fix gluebi NULL pointer dereference caused by ftl notifier + selinux: Fix error priority for bind with AF_UNSPEC on PF_INET6 socket + crypto: virtio - Handle dataq logic with tasklet + crypto: sa2ul - Return crypto_aead_setkey to transfer the error + crypto: ccp - fix memleak in ccp_init_dm_workarea + crypto: af_alg - Disallow multiple in-flight AIO requests + crypto: safexcel - Add error handling for dma_map_sg() calls + crypto: sahara - remove FLAGS_NEW_KEY logic + crypto: sahara - fix cbc selftest failure + crypto: sahara - fix ahash selftest failure + crypto: sahara - fix processing requests with cryptlen < sg->length + crypto: sahara - fix error handling in sahara_hw_descriptor_create() + crypto: hisilicon/qm - save capability registers in qm init process + crypto: hisilicon/zip - add zip comp high perf mode configuration + crypto: hisilicon/qm - add a function to set qm algs + crypto: hisilicon/hpre - save capability registers in probe process + crypto: hisilicon/sec2 - save capability registers in probe process + crypto: hisilicon/zip - save capability registers in probe process + pstore: ram_core: fix possible overflow in persistent_ram_init_ecc() + erofs: fix memory leak on short-lived bounced pages + fs: indicate request originates from old mount API + gfs2: Fix kernel NULL pointer dereference in gfs2_rgrp_dump + crypto: virtio - Wait for tasklet to complete on device remove + crypto: sahara - avoid skcipher fallback code duplication + crypto: sahara - handle zero-length aes requests + crypto: sahara - fix ahash reqsize + crypto: sahara - fix wait_for_completion_timeout() error handling + crypto: sahara - improve error handling in sahara_sha_process() + crypto: sahara - fix processing hash requests with req->nbytes < sg->length + crypto: sahara - do not resize req->src when doing hash operations + crypto: scomp - fix req->dst buffer overflow + csky: fix arch_jump_label_transform_static override + blocklayoutdriver: Fix reference leak of pnfs_device_node + NFSv4.1/pnfs: Ensure we handle the error NFS4ERR_RETURNCONFLICT + SUNRPC: fix _xprt_switch_find_current_entry logic + pNFS: Fix the pnfs block driver's calculation of layoutget size + wifi: plfxlc: check for allocation failure in plfxlc_usb_wreq_async() + wifi: rtw88: fix RX filter in FIF_ALLMULTI flag + bpf, lpm: Fix check prefixlen before walking trie + bpf: Add crosstask check to __bpf_get_stack + wifi: ath11k: Defer on rproc_get failure + wifi: libertas: stop selecting wext + ARM: dts: qcom: apq8064: correct XOADC register address + net/ncsi: Fix netlink major/minor version
[Kernel-packages] [Bug 2056403] [NEW] Mantic update: upstream stable patchset 2024-03-07
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: upstream stable patchset 2024-03-07 Ported from the following upstream stable releases: v6.1.75, v6.6.14 from git://git.kernel.org/ x86/lib: Fix overflow when counting digits x86/mce/inject: Clear test status value EDAC/thunderx: Fix possible out-of-bounds string access powerpc: add crtsavres.o to always-y instead of extra-y powerpc/44x: select I2C for CURRITUCK powerpc/pseries/memhp: Fix access beyond end of drmem array selftests/powerpc: Fix error handling in FPU/VMX preemption tests powerpc/powernv: Add a null pointer check to scom_debug_init_one() powerpc/powernv: Add a null pointer check in opal_event_init() powerpc/powernv: Add a null pointer check in opal_powercap_init() powerpc/imc-pmu: Add a null pointer check in update_events_in_group() spi: spi-zynqmp-gqspi: fix driver kconfig dependencies mtd: rawnand: Increment IFC_TIMEOUT_MSECS for nand controller response ACPI: video: check for error while searching for backlight device parent ACPI: LPIT: Avoid u32 multiplication overflow platform/x86/intel/vsec: Fix xa_alloc memory leak cpufreq: scmi: process the result of devm_of_clk_add_hw_provider() calipso: fix memory leak in netlbl_calipso_add_pass() efivarfs: force RO when remounting if SetVariable is not supported spi: sh-msiof: Enforce fixed DTDL for R-Car H3 ACPI: LPSS: Fix the fractional clock divider flags ACPI: extlog: Clear Extended Error Log status when RAS_CEC handled the error kunit: debugfs: Fix unchecked dereference in debugfs_print_results() mtd: Fix gluebi NULL pointer dereference caused by ftl notifier selinux: Fix error priority for bind with AF_UNSPEC on PF_INET6 socket crypto: virtio - Handle dataq logic with tasklet crypto: sa2ul - Return crypto_aead_setkey to transfer the error crypto: ccp - fix memleak in ccp_init_dm_workarea crypto: af_alg - Disallow multiple in-flight AIO requests crypto: safexcel - Add error handling for dma_map_sg() calls crypto: sahara - remove FLAGS_NEW_KEY logic crypto: sahara - fix cbc selftest failure crypto: sahara - fix ahash selftest failure crypto: sahara - fix processing requests with cryptlen < sg->length crypto: sahara - fix error handling in sahara_hw_descriptor_create() crypto: hisilicon/qm - save capability registers in qm init process crypto: hisilicon/zip - add zip comp high perf mode configuration crypto: hisilicon/qm - add a function to set qm algs crypto: hisilicon/hpre - save capability registers in probe process crypto: hisilicon/sec2 - save capability registers in probe process crypto: hisilicon/zip - save capability registers in probe process pstore: ram_core: fix possible overflow in persistent_ram_init_ecc() erofs: fix memory leak on short-lived bounced pages fs: indicate request originates from old mount API gfs2: Fix kernel NULL pointer dereference in gfs2_rgrp_dump crypto: virtio - Wait for tasklet to complete on device remove crypto: sahara - avoid skcipher fallback code duplication crypto: sahara - handle zero-length aes requests crypto: sahara - fix ahash reqsize crypto: sahara - fix wait_for_completion_timeout() error handling crypto: sahara - improve error handling in sahara_sha_process() crypto: sahara - fix processing hash requests with req->nbytes < sg->length crypto: sahara - do not resize req->src when doing hash operations crypto: scomp - fix req->dst buffer overflow csky: fix arch_jump_label_transform_static override blocklayoutdriver: Fix reference leak of pnfs_device_node NFSv4.1/pnfs: Ensure we handle the error NFS4ERR_RETURNCONFLICT SUNRPC: fix _xprt_switch_find_current_entry logic pNFS: Fix the pnfs block driver's calculation of layoutget size wifi: plfxlc: check for allocation failure in plfxlc_usb_wreq_async() wifi: rtw88: fix RX filter in FIF_ALLMULTI flag bpf, lpm: Fix check prefixlen before walking trie bpf: Add crosstask check to __bpf_get_stack wifi: ath11k: Defer on rproc_get failure wifi: libertas: stop selecting wext ARM: dts: qcom: apq8064: correct XOADC register address net/ncsi: Fix netlink major/minor version numbers firmware: ti_sci: Fix an off-by-one in ti_sci_debugfs_create() wifi: rtlwifi: rtl8821ae: phy: fix an undefined bitwise shift behavior arm64: dts: ti: k3-am62a-main: Fix GPIO pin count in DT nodes arm64: dts: ti: k3-am65-main: Fix DSS irq trigger type selftests/bpf: Fix erroneous bitmask operation md: synchronize flush io with array reconfiguration bpf: enforce precision of R0 on callback return ARM: dts: qcom: sdx65: correct SPMI node name arm64: dts: qcom: sc7180:
[Kernel-packages] [Bug 2054487] Re: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms
** Tags removed: verification-needed-jammy-linux-oem-6.1 ** Tags added: verification-done-jammy-linux-oem-6.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2054487 Title: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] While playing audio with headset plugged, the sound play from both headset and internal speaker. [Fix] The commit from v6.5-rc5 fixes the issue fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform [Test Case] 1. play an audio file. 2. plug 3.5mm headset. 3. select "headset". 4. sound will play only from headset [Where problems could occur] It simply added 2 IDs to the table, should have no impact to the existing machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054487/+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 2051068] Re: GUI crashed after installed proposed package libegl-mesa0
** Information type changed from Public Security to Private Security ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Released Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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 2056387] Re: Fail to suspend/resume for the second time
Random pointers although I'm not sure those are identical to my issue: https://www.reddit.com/r/archlinux/comments/199am0a/thinkpad_t14_suspend_broken_in_kernel_670/ https://discussion.fedoraproject.org/t/random-resume-after-suspend-issue-on-thinkpad-t14s-amd-gen3-radeon-680m-ryzen-7/103452 -- 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/2056387 Title: Fail to suspend/resume for the second time Status in linux package in Ubuntu: New Bug description: I had a similar issue before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718 However, I haven't seen the issue with later kernels until getting 6.8.0-11.11+1 recently. * 6.8.0-11 - fails to suspend/resume for the second time although the first suspend/resume works * 6.6.0-14 - no issue in terms of suspend/resume One thing worth noting is that connecting an external monitor or not might be a key to trigger this issue. I cannot reproduce it when an external monitor (through USB-C to HDMI) is not connected. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 11:17:31 2024 InstallationDate: Installed on 2024-01-08 (59 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104) MachineType: LENOVO 21CFCTO1WW ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv 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-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2023 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET73W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 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.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET73W(1.49):bd11/30/2023:br1.49:efr1.32:svnLENOVO:pn21CFCTO1WW:pvrThinkPadT14Gen3:rvnLENOVO:rn21CFCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CFCTO1WW dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056387/+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 2056387] Re: Fail to suspend/resume for the second time
Multiple suspends in a row worked without an external monitor connected, but after connecting it the machine failed to suspend/resume. ** Attachment added: "failed_on_suspend_after_connecting_monitor.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056387/+attachment/5753543/+files/failed_on_suspend_after_connecting_monitor.log -- 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/2056387 Title: Fail to suspend/resume for the second time Status in linux package in Ubuntu: New Bug description: I had a similar issue before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718 However, I haven't seen the issue with later kernels until getting 6.8.0-11.11+1 recently. * 6.8.0-11 - fails to suspend/resume for the second time although the first suspend/resume works * 6.6.0-14 - no issue in terms of suspend/resume One thing worth noting is that connecting an external monitor or not might be a key to trigger this issue. I cannot reproduce it when an external monitor (through USB-C to HDMI) is not connected. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 11:17:31 2024 InstallationDate: Installed on 2024-01-08 (59 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104) MachineType: LENOVO 21CFCTO1WW ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv 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-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2023 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET73W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 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.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET73W(1.49):bd11/30/2023:br1.49:efr1.32:svnLENOVO:pn21CFCTO1WW:pvrThinkPadT14Gen3:rvnLENOVO:rn21CFCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CFCTO1WW dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056387/+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 2056387] [NEW] Fail to suspend/resume for the second time
Public bug reported: I had a similar issue before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718 However, I haven't seen the issue with later kernels until getting 6.8.0-11.11+1 recently. * 6.8.0-11 - fails to suspend/resume for the second time although the first suspend/resume works * 6.6.0-14 - no issue in terms of suspend/resume One thing worth noting is that connecting an external monitor or not might be a key to trigger this issue. I cannot reproduce it when an external monitor (through USB-C to HDMI) is not connected. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 11:17:31 2024 InstallationDate: Installed on 2024-01-08 (59 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104) MachineType: LENOVO 21CFCTO1WW ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv 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-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2023 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET73W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 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.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET73W(1.49):bd11/30/2023:br1.49:efr1.32:svnLENOVO:pn21CFCTO1WW:pvrThinkPadT14Gen3:rvnLENOVO:rn21CFCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CFCTO1WW dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- 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/2056387 Title: Fail to suspend/resume for the second time Status in linux package in Ubuntu: New Bug description: I had a similar issue before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718 However, I haven't seen the issue with later kernels until getting 6.8.0-11.11+1 recently. * 6.8.0-11 - fails to suspend/resume for the second time although the first suspend/resume works * 6.6.0-14 - no issue in terms of suspend/resume One thing worth noting is that connecting an external monitor or not might be a key to trigger this issue. I cannot reproduce it when an external monitor (through USB-C to HDMI) is not connected. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 11:17:31 2024 InstallationDate: Installed on 2024-01-08 (59 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104) MachineType: LENOVO 21CFCTO1WW ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv 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-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2023 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET73W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag:
[Kernel-packages] [Bug 2056387] Re: Fail to suspend/resume for the second time
kernel log when trying suspend/resume twice in a row. The machine got frozen while the power LED is still on in the second suspend and there is no second "PM: suspend entry (s2idle)" in the kernel log. ** Attachment added: "failed_on_second_suspend.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056387/+attachment/5753542/+files/failed_on_second_suspend.log -- 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/2056387 Title: Fail to suspend/resume for the second time Status in linux package in Ubuntu: New Bug description: I had a similar issue before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718 However, I haven't seen the issue with later kernels until getting 6.8.0-11.11+1 recently. * 6.8.0-11 - fails to suspend/resume for the second time although the first suspend/resume works * 6.6.0-14 - no issue in terms of suspend/resume One thing worth noting is that connecting an external monitor or not might be a key to trigger this issue. I cannot reproduce it when an external monitor (through USB-C to HDMI) is not connected. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 11:17:31 2024 InstallationDate: Installed on 2024-01-08 (59 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104) MachineType: LENOVO 21CFCTO1WW ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv 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-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2023 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET73W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 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.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET73W(1.49):bd11/30/2023:br1.49:efr1.32:svnLENOVO:pn21CFCTO1WW:pvrThinkPadT14Gen3:rvnLENOVO:rn21CFCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CFCTO1WW dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056387/+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 2056373] [NEW] Multiple issues found on Ubuntu 20.04 against HVCS
Public bug reported: ---Problem Description--- Issues with HVCS and hotplugging issues. When working on Canonical bug 2023243, it was discovered that mkvterm was not working for multiple reasons. This bug will cover the issues found in HVCS, and hotplugging issues found when drmgr writes the slot information to .../add_slot. When mkvterm is ran, it ultimately fails because it calls pvmutil which fails. pvmutil calls drmgr, and drmgr is adding a slot correctly. However, when drmgr writes the slot information to ?/add_slot, the return is -ENODEV. This leads to HVCS never having probe() called. In addition, HVCS is missing patches, and is broken without them. 8 kernel patches have been identified to fix these issues. ---uname output--- Linux neop91.pok.stglabs.ibm.com 5.4.0-173-generic #191-Ubuntu SMP Fri Feb 2 13:54:35 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux ---Steps to Reproduce--- Run mkvterm with an id. mkvterm will fail because /dev/hvcs* device nodes are missing. See https://bugs.launchpad.net/ubuntu/+source/powerpc-utils/+bug/2023243 for more information. 2 commits made to arch/powerpc/platforms/pseries/of_helpers.c are needed. These commits fix the hotplugging issue seen when drmgr goes to write the slot information to /sys/bus/pci/slots/control/add_slot. This is also why the HVCS device nodes were not being created, as mentioned in the previous bug. The issue lies in rpadlpar_io and rpaphp calling an of helper function of_read_drc_info_cell(). Without these commits, the value stored drc_index_start is incorrect. This ultimately results in the entire SLOT string being incorrect, and rpaphp never finding the newly added slot by drmgr. rpadlpar then returns -ENODEV. Therefore, HVCS is never probed, and the device nodes are never created. Ideally - HVCS, rpadlpar_io, and rpaphp should not even need to be loaded prior to drmgr adding a vio slot. If rpadlpar_io and rpaphp are not loaded, drmgr will load them. In addition, if rpadlpar_io and rpaphp register the new slot correctly, rpadlpar_io will call dlpar_add_vio_slot(), which calls vio_register_device_node() with the device node. This is what tells the driver core to init and probe HVCS (which is needed to create the device nodes). In addition to the 2 commits mentioned above, 6 HVCS commits are needed. HVCS is essentially broken without them. Issues include race conditions, hotplug remove issues, as well as memory leaks. These commits have been added to other distros after multiple issues were seen. Without these commits, 20.04 will experience the same issues. IBM plans on stress testing these changes after an updated kernel is provided in focal- proposed. --- 2 commits that make changes to arch/powerpc/platforms/pseries/of_helpers.c: powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=57409d4fb12c185b2c0689e0496878c8f6bb5b58 powerpc/pseries: Fix of_read_drc_info_cell() to point at next record https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c5e76fa05b2df519b9f08571cc57e623c1569faa HVCS commits: hvcs: Fix hvcs port reference counting https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a9a733edd46732e906d976dc21a42dd361e53cc hvcs: Use dev_groups to manage hvcs device attributes https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=760aa5e81f33e0da82512c4288489739a6d1c556 hvcs: Use driver groups to manage driver attributes https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=503a90dd619d52dcac2cc68bd742aa914c7cd47a hvcs: Get reference to tty in remove https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3a8d3b366ce47024bf274eac783f8af5df2780f5 hvcs: Use vhangup in hotplug remove https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d432228bc7b1b3f0ed06510278ff5a77b3749fe6 hvcs: Synchronize hotplug remove with port free https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=28d49f8cbe9c7966f91ee1b5ec2f997f6e55bf9f ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-205798 severity-high targetmilestone-inin2004 ** Tags added: architecture-ppc64le bugnameltc-205798 severity-high targetmilestone-inin2004 ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => linux (Ubuntu) -- 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/2056373 Title: Multiple issues found on Ubuntu 20.04 against HVCS Status in linux package in Ubuntu: New Bug description: ---Problem Description---
[Kernel-packages] [Bug 2056373] [NEW] Multiple issues found on Ubuntu 20.04 against HVCS
You have been subscribed to a public bug: ---Problem Description--- Issues with HVCS and hotplugging issues. When working on Canonical bug 2023243, it was discovered that mkvterm was not working for multiple reasons. This bug will cover the issues found in HVCS, and hotplugging issues found when drmgr writes the slot information to .../add_slot. When mkvterm is ran, it ultimately fails because it calls pvmutil which fails. pvmutil calls drmgr, and drmgr is adding a slot correctly. However, when drmgr writes the slot information to ?/add_slot, the return is -ENODEV. This leads to HVCS never having probe() called. In addition, HVCS is missing patches, and is broken without them. 8 kernel patches have been identified to fix these issues. ---uname output--- Linux neop91.pok.stglabs.ibm.com 5.4.0-173-generic #191-Ubuntu SMP Fri Feb 2 13:54:35 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux ---Steps to Reproduce--- Run mkvterm with an id. mkvterm will fail because /dev/hvcs* device nodes are missing. See https://bugs.launchpad.net/ubuntu/+source/powerpc-utils/+bug/2023243 for more information. 2 commits made to arch/powerpc/platforms/pseries/of_helpers.c are needed. These commits fix the hotplugging issue seen when drmgr goes to write the slot information to /sys/bus/pci/slots/control/add_slot. This is also why the HVCS device nodes were not being created, as mentioned in the previous bug. The issue lies in rpadlpar_io and rpaphp calling an of helper function of_read_drc_info_cell(). Without these commits, the value stored drc_index_start is incorrect. This ultimately results in the entire SLOT string being incorrect, and rpaphp never finding the newly added slot by drmgr. rpadlpar then returns -ENODEV. Therefore, HVCS is never probed, and the device nodes are never created. Ideally - HVCS, rpadlpar_io, and rpaphp should not even need to be loaded prior to drmgr adding a vio slot. If rpadlpar_io and rpaphp are not loaded, drmgr will load them. In addition, if rpadlpar_io and rpaphp register the new slot correctly, rpadlpar_io will call dlpar_add_vio_slot(), which calls vio_register_device_node() with the device node. This is what tells the driver core to init and probe HVCS (which is needed to create the device nodes). In addition to the 2 commits mentioned above, 6 HVCS commits are needed. HVCS is essentially broken without them. Issues include race conditions, hotplug remove issues, as well as memory leaks. These commits have been added to other distros after multiple issues were seen. Without these commits, 20.04 will experience the same issues. IBM plans on stress testing these changes after an updated kernel is provided in focal- proposed. --- 2 commits that make changes to arch/powerpc/platforms/pseries/of_helpers.c: powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=57409d4fb12c185b2c0689e0496878c8f6bb5b58 powerpc/pseries: Fix of_read_drc_info_cell() to point at next record https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c5e76fa05b2df519b9f08571cc57e623c1569faa HVCS commits: hvcs: Fix hvcs port reference counting https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a9a733edd46732e906d976dc21a42dd361e53cc hvcs: Use dev_groups to manage hvcs device attributes https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=760aa5e81f33e0da82512c4288489739a6d1c556 hvcs: Use driver groups to manage driver attributes https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=503a90dd619d52dcac2cc68bd742aa914c7cd47a hvcs: Get reference to tty in remove https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3a8d3b366ce47024bf274eac783f8af5df2780f5 hvcs: Use vhangup in hotplug remove https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d432228bc7b1b3f0ed06510278ff5a77b3749fe6 hvcs: Synchronize hotplug remove with port free https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=28d49f8cbe9c7966f91ee1b5ec2f997f6e55bf9f ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-205798 severity-high targetmilestone-inin2004 -- Multiple issues found on Ubuntu 20.04 against HVCS https://bugs.launchpad.net/bugs/2056373 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
I can confirm the fix after applying latest firmware! ISSUE: I was getting intermittent internet dropping (for 5 to 10 seconds) between my MAC OS and my 22.04 Ubuntu server (no lost of connection from Ubuntu or Mac to internet) HARDWARE: Motherboard: MSI MPG X670E CARBON WIFI (mt7921e wifi) IPV6: I noticed missing ipv6 value after 'ifconfig' command (only local ipv6 - fe80) ENVIRONMENT (after fix): Ubuntu 22.04 (jammy) $ uname -a Linux azyri 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux HOW TO: 1- wget http://security.ubuntu.com/ubuntu/pool/main/l/linux-firmware/linux-firmware_20220329.git681281e4-0ubuntu3.29_all.deb 2- sudo dpkg -i linux-firmware_20220329.git681281e4-0ubuntu3.29_all.deb 3- sudo reboot now After applying fix: $ sudo dmesg | grep mt7921 [7.293748] mt7921e :0d:00.0: enabling device ( -> 0002) [7.298835] mt7921e :0d:00.0: ASIC revision: 79220010 [7.380306] mt7921e :0d:00.0: HW/SW Version: 0x8a108a10, Build Time: 20231120183400a [7.395877] mt7921e :0d:00.0: WM Firmware Version: 00, Build Time: 20231120183441 [8.497052] mt7921e :0d:00.0 wlp13s0: renamed from wlan0 $ ifconfig wlp13s0: flags=4163 mtu 1500 inet 192.168.86.21 netmask 255.255.255.0 broadcast 192.168.86.255 *** inet6 wdw:657f:3de:117:63f:d4ff:fe3f:dgd prefixlen 64 scopeid 0x0 inet6 fe80::5fd:d4ff:gd43:fead prefixlen 64 scopeid 0x20 ether sf:3d:3f:3f:fe:as txqueuelen 1000 (Ethernet) RX packets 13414 bytes 3510061 (3.5 MB) RX errors 0 dropped 5 overruns 0 frame 0 TX packets 7267 bytes 4192805 (4.1 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 * this line was missing before -- 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/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2049220 [Impact] MT7921 - IPv6 no longer working (Not receiving Multicast). [Fix] Update WiFi/Bluetooth firmware to upstream commits: * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi device") * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for mediatek bluetooth chip (MT7921)") [Test Case] 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter and connect it to a Dual-stack network leveraging Router Advertisements for IPv6. 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the following: - IPv6 stateless autoconfiguration works and a public/global address is assigned. - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark. 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the following: - IPv6 only configures link-local address (fe80::) and no public/global address. - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark. [Where problems could occur] Opaque binary. No known dependency to kernel version. [Other Info] Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and Mantic. All the commits are in upstream repository, so Noble should have them after rebased. == original bug report == The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 2056297] Re: Non-flatpak Firefox-based browsers crash with kernel 6.8.0-11-generic in 24.04
*** This bug is a duplicate of bug 2046844 *** https://bugs.launchpad.net/bugs/2046844 Hi cipricus, This is a security feature working as intended. Ubuntu recently decided to disable unprivileged access to user namespaces. You can find more information it about it here: https://ubuntu.com/blog/ubuntu-23-10-restricted-unprivileged-user-namespaces https://discourse.ubuntu.com/t/spec-unprivileged-user-namespace-restrictions-via-apparmor-in-ubuntu-23-10/37626 https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844 It was included (but turned off in 23.10). In 24.04, it has been turned on. We have been adding apparmor profiles for most packaged applications. Saying that, firefox downloaded from tarballs or other places don't come with an apparmor profile, so the mitigation isn't relaxed for them. You can enable user namespaces by either making a apparmor profile for your firefox installs, making sure the directory where firefox is installed is correct in the profile, or by just enabling user namespaces for your system. There is instructions to do this in the first blog link. Thanks, Matthew ** This bug has been marked a duplicate of bug 2046844 AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP -- 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/2056297 Title: Non-flatpak Firefox-based browsers crash with kernel 6.8.0-11-generic in 24.04 Status in linux package in Ubuntu: New Bug description: All details are to be found in my previous bug report (https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2056190). Given that simply reverting to kernel 6.5.0-17-generic fixes the problem, the bug seems to be with the 6.8.0 kernel. Therefore I'm posting this. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Mar 6 09:49:36 2024 InstallationDate: Installed on 2023-10-04 (154 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Sony Corporation VPCSB2P9E ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=0dbb7177-a759-43f8-86d2-53e3253805d5 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-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-03-04 (2 days ago) dmi.bios.date: 11/16/2011 dmi.bios.release: 20.85 dmi.bios.vendor: INSYDE dmi.bios.version: R2085H4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 20.85 dmi.modalias: dmi:bvnINSYDE:bvrR2085H4:bd11/16/2011:br20.85:efr20.85:svnSonyCorporation:pnVPCSB2P9E:pvrC609DJQ5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:skuN/A: dmi.product.family: VAIO dmi.product.name: VPCSB2P9E dmi.product.sku: N/A dmi.product.version: C609DJQ5 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056297/+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 2052840] Re: Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed -62
Is there a way I can track this issue? -- 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/2052840 Title: Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed -62 Status in linux-firmware package in Ubuntu: New Bug description: Hello, I'm facing this issue before few months after software upgrade, Distro: Kubuntu 23.10 Kernel: Linux kernel 6.5.0-17-generic Linux Firmware: 20230919.git3672ccab-0ubuntu2.5 My Specs: CPU: Ryzen 9 7950X RAM: 64GB = 16GB × 4 5200/MT DDR5 GPU: Radeon RX 7900 XTX (Founder Edition from Sapphire) Motherboard: Gigabyte B650M GAMING X AX NOTICE: I can boot after 10-20 tries and sometimes I cannot boot at all there other users faced same issue (look like because linux-firmware): https://ubuntuforums.org/showthread.php?t=2489556 My dmesg logs attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2052840/+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 2051871] Re: mlxbf-tmfifo: Drop Tx network packet when Tx TmFIFO is full
** Tags removed: verification-needed-jammy-linux-bluefield ** Tags added: verification-done-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2051871 Title: mlxbf-tmfifo: Drop Tx network packet when Tx TmFIFO is full Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] This is a cherry-pick fix from upstream to drop Tx network packet when Tx TmFIFO is full. [Fix] Starting from Linux 5.16 kernel, Tx timeout mechanism was added in the virtio_net driver which prints the "Tx timeout" warning message when a packet stays in Tx queue for too long. Below is an example of the reported message: "[494105.316739] virtio_net virtio1 tmfifo_net0: TX timeout on queue: 0, sq: output.0, vq: 0×1, name: output.0, usecs since last trans: 3079892256". This issue could happen when external host driver which drains the FIFO is restared, stopped or upgraded. To avoid such confusing "Tx timeout" messages, this commit adds logic to drop the outstanding Tx packet if it's not able to transmit in two seconds due to Tx FIFO full, which can be considered as congestion or out-of-resource drop. This commit also handles the special case that the packet is half- transmitted into the Tx FIFO. In such case, the packet is discarded with remaining length stored in vring->rem_padding. So paddings with zeros can be sent out when Tx space is available to maintain the integrity of the packet format. The padded packet will be dropped on the receiving side. [Test Case] Same functionality and testing as on BlueField-1/2/3. No functionality change. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2051871/+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 1804481] Re: SecureBoot support for arm64
** Changed in: shim-signed (Ubuntu Cosmic) Status: Triaged => Won't Fix ** Changed in: shim-signed (Ubuntu Bionic) Status: Triaged => Fix Released ** Changed in: linux-signed (Ubuntu Cosmic) Status: Triaged => Won't Fix ** Changed in: linux-meta (Ubuntu Cosmic) Status: Triaged => Won't Fix ** Changed in: linux (Ubuntu Cosmic) Status: Triaged => Won't Fix ** Changed in: linux-signed (Ubuntu Bionic) Status: Triaged => Won't Fix ** Changed in: linux (Ubuntu Bionic) Status: Triaged => Won't Fix ** Changed in: linux-meta (Ubuntu Bionic) Status: Triaged => Won't Fix ** Changed in: linux-signed-hwe-edge (Ubuntu) Status: New => Fix Released ** Changed in: linux-meta (Ubuntu) Status: In Progress => Fix Released -- 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/1804481 Title: SecureBoot support for arm64 Status in linux package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Fix Released Status in linux-signed package in Ubuntu: Fix Released Status in linux-signed-hwe package in Ubuntu: Invalid Status in linux-signed-hwe-edge package in Ubuntu: Fix Released Status in shim package in Ubuntu: Fix Released Status in shim-signed package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-meta source package in Bionic: Won't Fix Status in linux-signed source package in Bionic: Won't Fix Status in linux-signed-hwe source package in Bionic: Fix Released Status in linux-signed-hwe-edge source package in Bionic: Fix Released Status in shim source package in Bionic: Fix Released Status in shim-signed source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Status in linux-meta source package in Cosmic: Won't Fix Status in linux-signed source package in Cosmic: Won't Fix Status in linux-signed-hwe source package in Cosmic: Invalid Status in linux-signed-hwe-edge source package in Cosmic: Invalid Status in shim source package in Cosmic: Fix Released Status in shim-signed source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-meta source package in Disco: Won't Fix Status in linux-signed source package in Disco: Fix Released Status in linux-signed-hwe source package in Disco: Invalid Status in linux-signed-hwe-edge source package in Disco: Invalid Status in shim source package in Disco: Fix Released Status in shim-signed source package in Disco: Fix Released Bug description: [Impact] Ubuntu does not currently support SecureBoot for UEFI systems on arm64 platforms. [Test Case] See: https://wiki.ubuntu.com/UEFI/SecureBoot/Testing [Fix] - Introduce shim-signed for arm64 - Introduce grub-signed for arm64 - Produce signed linux kernels [Regression Risk] We're enabling new signed packages - regressions would most likely fall into packaging issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804481/+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 2056364] [NEW] Add test script for DPLL
Public bug reported: * intro In bug 2053155 "Add DPLL and syncE support" below: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2053155 It requires using a yaml spec file, dpll.yaml, and a python script, cli.py, to verify the correctness. ex: $ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \ --dump device-get We've found that the script and spec file are missing in current repo (Ubuntu-bluefield-5.15.0-1037.39). * how to fix Since the existing Bluefield-5.15 doesn't have the tools/net/ynl directory, the efforts to cherry-pick all individual patches shouldn't be too hard due to no dependencies and most likely no conflict, but there are around 200 patches in tools/net/ynl $ git log --oneline tools/net/ynl/ | wc -l 205 and for Documentation/netlink/genetlink.yaml (a dependent file for dpll.yaml) $ git log --oneline Documentation/netlink/genetlink.yaml | wc -l 15 So we decided to just create a new patch consisting all the required files, shown below: create mode 100644 Documentation/netlink/genetlink.yaml create mode 100644 tools/net/ynl/cli.py create mode 100644 tools/net/ynl/lib/__init__.py create mode 100644 tools/net/ynl/lib/nlspec.py create mode 100644 tools/net/ynl/lib/ynl.py ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2056364 Title: Add test script for DPLL Status in linux-bluefield package in Ubuntu: New Bug description: * intro In bug 2053155 "Add DPLL and syncE support" below: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2053155 It requires using a yaml spec file, dpll.yaml, and a python script, cli.py, to verify the correctness. ex: $ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \ --dump device-get We've found that the script and spec file are missing in current repo (Ubuntu-bluefield-5.15.0-1037.39). * how to fix Since the existing Bluefield-5.15 doesn't have the tools/net/ynl directory, the efforts to cherry-pick all individual patches shouldn't be too hard due to no dependencies and most likely no conflict, but there are around 200 patches in tools/net/ynl $ git log --oneline tools/net/ynl/ | wc -l 205 and for Documentation/netlink/genetlink.yaml (a dependent file for dpll.yaml) $ git log --oneline Documentation/netlink/genetlink.yaml | wc -l 15 So we decided to just create a new patch consisting all the required files, shown below: create mode 100644 Documentation/netlink/genetlink.yaml create mode 100644 tools/net/ynl/cli.py create mode 100644 tools/net/ynl/lib/__init__.py create mode 100644 tools/net/ynl/lib/nlspec.py create mode 100644 tools/net/ynl/lib/ynl.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2056364/+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 1970069] Re: Annoying boot messages interfering with splash screen
AFAICT; these initramfs-tools package changes would cover it: * hooks/framebuffer can be totally removed. * scripts/init-top/framebuffer should probably stay * conf/initramfs.conf needs FRAMEBUFFER=y added to it -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=2 fastboot [ Test Plan ] 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
Plymouth only gets added to the initrd when LUKS is enabled or you mark another reason for needing the framebuffer. So the suggestion I have from comment #49 is to mark needing the framebuffer by default, and then stop including any DRM modules because simpledrm is built into the 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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=2 fastboot [ Test Plan ] 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 2056354] [NEW] qat: Improve error/reset handling
Public bug reported: [Impact] Some improvement are made to qat which makes it more resilient and able to handle reset in a better way. There is an upstream patch set that improve this but it's applied to linux-next and scheduled for 6.9. We should apply the patch set to the Noble 6.8 kernel, so we experience less issues with qat and be more maintainable. [Test case] Use the added mechanism to inject errors and rmmod/modprobe the module to verify that qat recover and log issues properly. [Fix] Apply the following commits (from linux-next): 2ecd43413d76 Documentation: qat: fix auto_reset section 7d42e097607c crypto: qat - resolve race condition during AER recovery c2304e1a0b80 crypto: qat - change SLAs cleanup flow at shutdown 9567d3dc7609 crypto: qat - improve aer error reset handling 750fa7c20e60 crypto: qat - limit heartbeat notifications f5419a4239af crypto: qat - add auto reset on error 2aaa1995a94a crypto: qat - add fatal error notification 4469f9b23468 crypto: qat - re-enable sriov after pf reset ec26f8e6c784 crypto: qat - update PFVF protocol for recovery 758a0087db98 crypto: qat - disable arbitration before reset ae508d7afb75 crypto: qat - add fatal error notify method e2b67859ab6e crypto: qat - add heartbeat error simulator [Regression potential] We may experience qat regression when crashing or restarting the module. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Description changed: [Impact] Some improvement are made to qat which makes it more resilient and able to handle reset in a better way. There is an upstream patch set that improve this but it's applied to linux-next and scheduled for 6.9. - We should apply the patch set to the Noble 6.8 kernel, - so we experience less issue with qat and be more maintainable. + We should apply the patch set to the Noble 6.8 kernel, + so we experience less issues with qat and be more maintainable. [Test case] Use the added mechanism to inject errors and rmmod/modprobe the module to verify that qat recover and log issues properly. [Fix] Apply the following commits (from linux-next): 2ecd43413d76 Documentation: qat: fix auto_reset section 7d42e097607c crypto: qat - resolve race condition during AER recovery c2304e1a0b80 crypto: qat - change SLAs cleanup flow at shutdown 9567d3dc7609 crypto: qat - improve aer error reset handling 750fa7c20e60 crypto: qat - limit heartbeat notifications f5419a4239af crypto: qat - add auto reset on error 2aaa1995a94a crypto: qat - add fatal error notification 4469f9b23468 crypto: qat - re-enable sriov after pf reset ec26f8e6c784 crypto: qat - update PFVF protocol for recovery 758a0087db98 crypto: qat - disable arbitration before reset ae508d7afb75 crypto: qat - add fatal error notify method e2b67859ab6e crypto: qat - add heartbeat error simulator [Regression potential] We may experience qat regression when crashing or restarting the module. -- 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/2056354 Title: qat: Improve error/reset handling Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: [Impact] Some improvement are made to qat which makes it more resilient and able to handle reset in a better way. There is an upstream patch set that improve this but it's applied to linux-next and scheduled for 6.9. We should apply the patch set to the Noble 6.8 kernel, so we experience less issues with qat and be more maintainable. [Test case] Use the added mechanism to inject errors and rmmod/modprobe the module to verify that qat recover and log issues properly. [Fix] Apply the following commits (from linux-next): 2ecd43413d76 Documentation: qat: fix auto_reset section 7d42e097607c crypto: qat - resolve race condition during AER recovery c2304e1a0b80 crypto: qat - change SLAs cleanup flow at shutdown 9567d3dc7609 crypto: qat - improve aer error reset handling 750fa7c20e60 crypto: qat - limit heartbeat notifications f5419a4239af crypto: qat - add auto reset on error 2aaa1995a94a crypto: qat - add fatal error notification 4469f9b23468 crypto: qat - re-enable sriov after pf reset ec26f8e6c784 crypto: qat - update PFVF protocol for recovery 758a0087db98 crypto: qat - disable arbitration before reset ae508d7afb75 crypto: qat - add fatal error notify method e2b67859ab6e crypto: qat - add heartbeat error simulator [Regression potential] We may experience qat regression when crashing or restarting the module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056354/+subscriptions --
[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
It's a bit unclear to me what change we need now to take advantage of simpledrm? Comment #49 state getting plymouth in the initrd but that should already be the case today or luks encryption wouldn't be working no? what change would trigger the include of extra drm modules? -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=2 fastboot [ Test Plan ] 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 2054928] Re: kernel UCSI fail
There is no 'kernel-package' in Ubuntu 22.04 so moving... ** Package changed: kernel-package (Ubuntu) => linux-meta-hwe-6.5 (Ubuntu) ** Tags added: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2054928 Title: kernel UCSI fail Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: This only happens to me when I connect my USB-C docking station to my laptop. The laptop doesn't really turn off and goes crazy. To solve this I have seen that disconnecting the battery from the BIOS settings solves the problem. If I don't do this the laptop never really turns off and drains the battery. But when I start Ubuntu and restart it a couple of times it happens again. Dock: Thinkpad dock station Universal usb-c (upgraded the firmware to the last version for see this fix the problem) Laptop: Thinkpad E490 (bios upgraded to the last version) Run Ubuntu 22.04 (All upgraded !!!) kernel: 6.5.0-21-generic (with the kernel 6.5.0-18-generic same thing happens) On the same hardware configuration settings run Ubuntu 20.04 and i dont have problems. Regards!!! Belog my kernel logs ``` matias@matias-ThinkPad-E490:~$ cat /var/log/syslog | grep ucsi Feb 25 13:34:09 matias-ThinkPad-E490 kernel: [6.997101] ucsi_acpi USBC000:00: con1: failed to register partner alt modes (-34) Feb 25 15:05:56 matias-ThinkPad-E490 kernel: [7.077472] ucsi_acpi USBC000:00: con1: failed to register partner alt modes (-34) Feb 25 15:18:51 matias-ThinkPad-E490 kernel: [7.017315] ucsi_acpi USBC000:00: con1: failed to register partner alt modes (-34) Feb 25 15:21:56 matias-ThinkPad-E490 kernel: [7.253151] ucsi_acpi USBC000:00: con1: failed to register partner alt modes (-34) Feb 25 15:21:56 matias-ThinkPad-E490 kernel: [7.898290] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5) Feb 25 15:24:07 matias-ThinkPad-E490 kernel: [7.298691] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:07 matias-ThinkPad-E490 kernel: [7.298842] ucsi_acpi USBC000:00: con2: failed to get status Feb 25 15:24:08 matias-ThinkPad-E490 kernel: [8.789347] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:08 matias-ThinkPad-E490 kernel: [8.789519] ucsi_acpi USBC000:00: con3: failed to get status Feb 25 15:24:10 matias-ThinkPad-E490 kernel: [ 10.297429] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:10 matias-ThinkPad-E490 kernel: [ 10.297435] ucsi_acpi USBC000:00: con4: failed to get status Feb 25 15:24:10 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:005 Feb 25 15:24:11 matias-ThinkPad-E490 kernel: [ 11.765348] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:11 matias-ThinkPad-E490 kernel: [ 11.765353] ucsi_acpi USBC000:00: con5: failed to get status Feb 25 15:24:11 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:006 Feb 25 15:24:13 matias-ThinkPad-E490 kernel: [ 13.274527] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:13 matias-ThinkPad-E490 kernel: [ 13.274739] ucsi_acpi USBC000:00: con6: failed to get status Feb 25 15:24:13 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:007 Feb 25 15:24:14 matias-ThinkPad-E490 kernel: [ 14.798619] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:14 matias-ThinkPad-E490 kernel: [ 14.798637] ucsi_acpi USBC000:00: con7: failed to get status Feb 25 15:24:14 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:008 Feb 25 15:24:16 matias-ThinkPad-E490 kernel: [ 16.386801] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:16 matias-ThinkPad-E490 kernel: [ 16.386821] ucsi_acpi USBC000:00: con8: failed to get status Feb 25 15:24:16 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:009 Feb 25 15:24:17 matias-ThinkPad-E490 kernel: [ 18.018808] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:17 matias-ThinkPad-E490 kernel: [ 18.018827] ucsi_acpi USBC000:00: con9: failed to get status Feb 25 15:24:18 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:0010 Feb 25 15:24:19 matias-ThinkPad-E490 kernel: [ 19.621722] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:19 matias-ThinkPad-E490 kernel: [ 19.621729] ucsi_acpi USBC000:00: con10: failed to get status Feb 25 15:24:19
[Kernel-packages] [Bug 2056126] Re: hwmon: (coretemp) Fix core count limitation
** Changed in: linux (Ubuntu Noble) Status: New => Fix Committed -- 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/2056126 Title: hwmon: (coretemp) Fix core count limitation Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: [Impact] In linux 6.8 the coretemp driver supports at most 128 cores per package. Cores higher than 128 will lose their core temperature information. There is an upstream patch set that allows to support more than 128 cores per package, but it's applied to linux-next for now and it's scheduled for 6.9. We should apply the patch set to the Noble 6.8 kernel, so that we can properly support systems with a large amount of cores per package. [Test case] Read temperature info from /sys/class/hwmon on a system with > 128 cores per package (that means we don't have a proper test case to verify the fix at the moment). [Fix] Apply the following commits (from linux-next): 18cb15e9c108 hwmon: (coretemp) Use dynamic allocated memory for core temp_data f0a5f46b0100 hwmon: (coretemp) Remove redundant temp_data->is_pkg_data 16a29729c00c hwmon: (coretemp) Split package temp_data and core temp_data b48fddda2b30 hwmon: (coretemp) Abstract core_temp helpers a30f3dc6e9bf hwmon: (coretemp) Remove redundant pdata->cpu_map[] e416450cb080 hwmon: (coretemp) Replace sensor_device_attribute with device_attribute 46ee134971bb hwmon: (coretemp) Remove unnecessary dependency of array index 9f360b22929c hwmon: (coretemp) Introduce enum for attr index [Regression potential] We may experience hwmon-related regressions, either systems reading incorrect temperature information or even bugs/crashes when accessing data from /sys/class/hwmon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056126/+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 2054928] [NEW] kernel UCSI fail
You have been subscribed to a public bug: This only happens to me when I connect my USB-C docking station to my laptop. The laptop doesn't really turn off and goes crazy. To solve this I have seen that disconnecting the battery from the BIOS settings solves the problem. If I don't do this the laptop never really turns off and drains the battery. But when I start Ubuntu and restart it a couple of times it happens again. Dock: Thinkpad dock station Universal usb-c (upgraded the firmware to the last version for see this fix the problem) Laptop: Thinkpad E490 (bios upgraded to the last version) Run Ubuntu 22.04 (All upgraded !!!) kernel: 6.5.0-21-generic (with the kernel 6.5.0-18-generic same thing happens) On the same hardware configuration settings run Ubuntu 20.04 and i dont have problems. Regards!!! Belog my kernel logs ``` matias@matias-ThinkPad-E490:~$ cat /var/log/syslog | grep ucsi Feb 25 13:34:09 matias-ThinkPad-E490 kernel: [6.997101] ucsi_acpi USBC000:00: con1: failed to register partner alt modes (-34) Feb 25 15:05:56 matias-ThinkPad-E490 kernel: [7.077472] ucsi_acpi USBC000:00: con1: failed to register partner alt modes (-34) Feb 25 15:18:51 matias-ThinkPad-E490 kernel: [7.017315] ucsi_acpi USBC000:00: con1: failed to register partner alt modes (-34) Feb 25 15:21:56 matias-ThinkPad-E490 kernel: [7.253151] ucsi_acpi USBC000:00: con1: failed to register partner alt modes (-34) Feb 25 15:21:56 matias-ThinkPad-E490 kernel: [7.898290] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5) Feb 25 15:24:07 matias-ThinkPad-E490 kernel: [7.298691] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:07 matias-ThinkPad-E490 kernel: [7.298842] ucsi_acpi USBC000:00: con2: failed to get status Feb 25 15:24:08 matias-ThinkPad-E490 kernel: [8.789347] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:08 matias-ThinkPad-E490 kernel: [8.789519] ucsi_acpi USBC000:00: con3: failed to get status Feb 25 15:24:10 matias-ThinkPad-E490 kernel: [ 10.297429] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:10 matias-ThinkPad-E490 kernel: [ 10.297435] ucsi_acpi USBC000:00: con4: failed to get status Feb 25 15:24:10 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:005 Feb 25 15:24:11 matias-ThinkPad-E490 kernel: [ 11.765348] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:11 matias-ThinkPad-E490 kernel: [ 11.765353] ucsi_acpi USBC000:00: con5: failed to get status Feb 25 15:24:11 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:006 Feb 25 15:24:13 matias-ThinkPad-E490 kernel: [ 13.274527] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:13 matias-ThinkPad-E490 kernel: [ 13.274739] ucsi_acpi USBC000:00: con6: failed to get status Feb 25 15:24:13 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:007 Feb 25 15:24:14 matias-ThinkPad-E490 kernel: [ 14.798619] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:14 matias-ThinkPad-E490 kernel: [ 14.798637] ucsi_acpi USBC000:00: con7: failed to get status Feb 25 15:24:14 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:008 Feb 25 15:24:16 matias-ThinkPad-E490 kernel: [ 16.386801] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:16 matias-ThinkPad-E490 kernel: [ 16.386821] ucsi_acpi USBC000:00: con8: failed to get status Feb 25 15:24:16 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:009 Feb 25 15:24:17 matias-ThinkPad-E490 kernel: [ 18.018808] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:17 matias-ThinkPad-E490 kernel: [ 18.018827] ucsi_acpi USBC000:00: con9: failed to get status Feb 25 15:24:18 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:0010 Feb 25 15:24:19 matias-ThinkPad-E490 kernel: [ 19.621722] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:19 matias-ThinkPad-E490 kernel: [ 19.621729] ucsi_acpi USBC000:00: con10: failed to get status Feb 25 15:24:19 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:0011 Feb 25 15:24:20 matias-ThinkPad-E490 kernel: [ 21.147048] ucsi_acpi USBC000:00: possible UCSI driver bug 2 Feb 25 15:24:20 matias-ThinkPad-E490 kernel: [ 21.147071] ucsi_acpi USBC000:00: con11: failed to get status Feb 25 15:24:21 matias-ThinkPad-E490 upowerd[1347]: treated changed event as add on
[Kernel-packages] [Bug 2056297] Re: Non-flatpak Firefox-based browsers crash with kernel 6.8.0-11-generic in 24.04
** Description changed: - All details are to be found in my previous bug report [Tabs of non- - flatpak Firefox (and non-flatpak Firefox-based browsers) crash in - Kubuntu - 24.04](https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2056190). + All details are to be found in my previous bug report + (https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2056190). Given that simply reverting to kernel 6.5.0-17-generic fixes the problem, the bug seems to be with the 6.8.0 kernel. Therefore I'm posting this. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Mar 6 09:49:36 2024 InstallationDate: Installed on 2023-10-04 (154 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Sony Corporation VPCSB2P9E ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=0dbb7177-a759-43f8-86d2-53e3253805d5 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-6.8.0-11-generic N/A - linux-backports-modules-6.8.0-11-generic N/A - linux-firmware20240202.git36777504-0ubuntu1 + linux-restricted-modules-6.8.0-11-generic N/A + linux-backports-modules-6.8.0-11-generic N/A + linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-03-04 (2 days ago) dmi.bios.date: 11/16/2011 dmi.bios.release: 20.85 dmi.bios.vendor: INSYDE dmi.bios.version: R2085H4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 20.85 dmi.modalias: dmi:bvnINSYDE:bvrR2085H4:bd11/16/2011:br20.85:efr20.85:svnSonyCorporation:pnVPCSB2P9E:pvrC609DJQ5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:skuN/A: dmi.product.family: VAIO dmi.product.name: VPCSB2P9E dmi.product.sku: N/A dmi.product.version: C609DJQ5 dmi.sys.vendor: Sony Corporation -- 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/2056297 Title: Non-flatpak Firefox-based browsers crash with kernel 6.8.0-11-generic in 24.04 Status in linux package in Ubuntu: New Bug description: All details are to be found in my previous bug report (https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2056190). Given that simply reverting to kernel 6.5.0-17-generic fixes the problem, the bug seems to be with the 6.8.0 kernel. Therefore I'm posting this. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Mar 6 09:49:36 2024 InstallationDate: Installed on 2023-10-04 (154 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Sony Corporation VPCSB2P9E ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=0dbb7177-a759-43f8-86d2-53e3253805d5 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-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-03-04 (2 days ago) dmi.bios.date: 11/16/2011 dmi.bios.release: 20.85 dmi.bios.vendor: INSYDE dmi.bios.version: R2085H4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 20.85 dmi.modalias: dmi:bvnINSYDE:bvrR2085H4:bd11/16/2011:br20.85:efr20.85:svnSonyCorporation:pnVPCSB2P9E:pvrC609DJQ5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:skuN/A: dmi.product.family: VAIO dmi.product.name: VPCSB2P9E dmi.product.sku: N/A dmi.product.version: C609DJQ5 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to:
[Kernel-packages] [Bug 2056317] [NEW] package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problemas de dependência - deixando desconfigurado
Public bug reported: I can not install the gpu driver without an error. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-driver-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: google-chrome-stable:amd64: Install libde265-0:amd64: Install zotero:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Mar 5 20:09:23 2024 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2024-02-02 (32 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2056317 Title: package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problemas de dependência - deixando desconfigurado Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I can not install the gpu driver without an error. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-driver-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: google-chrome-stable:amd64: Install libde265-0:amd64: Install zotero:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Mar 5 20:09:23 2024 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2024-02-02 (32 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2056317/+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 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64
This bug is awaiting verification that the linux- hwe-6.5/6.5.0-25.25~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.5' to 'verification-done-jammy-linux-hwe-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.5' to 'verification-failed-jammy-linux-hwe-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-hwe-6.5-v2 verification-needed-jammy-linux-hwe-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/1983357 Title: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64 Status in QA Regression Testing: Invalid Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: New Status in linux source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Won't Fix Status in linux-oem-6.1 source package in Lunar: New Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: New Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Bug description: Issue found on 5.19.0-9.9 Kinetic AMD64 systems Test log: Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel: '5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0 SUDO_USER: 'ubuntu') test_021_aslr_dapper_libs (__main__.KernelSecurityTest) ASLR of libs ... (default libs native) (default libs native rekey) (default libs COMPAT) FAIL == FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest) ASLR of libs -- Traceback (most recent call last): File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs self._test_aslr('libs', expected) File "./test-kernel-security.py", line 1727, in _test_aslr self._test_aslr_all(area, expected, "default %s" % area) File "./test-kernel-security.py", line 1720, in _test_aslr_all self._test_aslr_exec(area, expected, target, name) File "./test-kernel-security.py", line 1703, in _test_aslr_exec self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, "--verbose"], msg="%s:\n" % name) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1203, in assertShellExitEquals self.assertEqual(expected, rc, msg + result + report) AssertionError: default libs COMPAT: Got exit code 1, expected 0 Command: './aslr32', 'libs', '--verbose' Output: Checking ASLR of libs: 0xf7c81790 0xf7c81790 0xf7c81790 FAIL: ASLR not functional (libs always at 0xf7c81790) -- Ran 1 test in 0.144s FAILED (failures=1) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+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 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64
This bug is awaiting verification that the linux-azure/6.5.0-1016.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/1983357 Title: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64 Status in QA Regression Testing: Invalid Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: New Status in linux source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Won't Fix Status in linux-oem-6.1 source package in Lunar: New Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: New Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Bug description: Issue found on 5.19.0-9.9 Kinetic AMD64 systems Test log: Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel: '5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0 SUDO_USER: 'ubuntu') test_021_aslr_dapper_libs (__main__.KernelSecurityTest) ASLR of libs ... (default libs native) (default libs native rekey) (default libs COMPAT) FAIL == FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest) ASLR of libs -- Traceback (most recent call last): File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs self._test_aslr('libs', expected) File "./test-kernel-security.py", line 1727, in _test_aslr self._test_aslr_all(area, expected, "default %s" % area) File "./test-kernel-security.py", line 1720, in _test_aslr_all self._test_aslr_exec(area, expected, target, name) File "./test-kernel-security.py", line 1703, in _test_aslr_exec self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, "--verbose"], msg="%s:\n" % name) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1203, in assertShellExitEquals self.assertEqual(expected, rc, msg + result + report) AssertionError: default libs COMPAT: Got exit code 1, expected 0 Command: './aslr32', 'libs', '--verbose' Output: Checking ASLR of libs: 0xf7c81790 0xf7c81790 0xf7c81790 FAIL: ASLR not functional (libs always at 0xf7c81790) -- Ran 1 test in 0.144s FAILED (failures=1) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+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 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64
This bug is awaiting verification that the linux-aws/6.5.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-aws' to 'verification-done-mantic- linux-aws'. If the problem still exists, change the tag 'verification- needed-mantic-linux-aws' to 'verification-failed-mantic-linux-aws'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-aws-v2 verification-needed-mantic-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/1983357 Title: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64 Status in QA Regression Testing: Invalid Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: New Status in linux source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Won't Fix Status in linux-oem-6.1 source package in Lunar: New Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: New Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Bug description: Issue found on 5.19.0-9.9 Kinetic AMD64 systems Test log: Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel: '5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0 SUDO_USER: 'ubuntu') test_021_aslr_dapper_libs (__main__.KernelSecurityTest) ASLR of libs ... (default libs native) (default libs native rekey) (default libs COMPAT) FAIL == FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest) ASLR of libs -- Traceback (most recent call last): File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs self._test_aslr('libs', expected) File "./test-kernel-security.py", line 1727, in _test_aslr self._test_aslr_all(area, expected, "default %s" % area) File "./test-kernel-security.py", line 1720, in _test_aslr_all self._test_aslr_exec(area, expected, target, name) File "./test-kernel-security.py", line 1703, in _test_aslr_exec self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, "--verbose"], msg="%s:\n" % name) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1203, in assertShellExitEquals self.assertEqual(expected, rc, msg + result + report) AssertionError: default libs COMPAT: Got exit code 1, expected 0 Command: './aslr32', 'libs', '--verbose' Output: Checking ASLR of libs: 0xf7c81790 0xf7c81790 0xf7c81790 FAIL: ASLR not functional (libs always at 0xf7c81790) -- Ran 1 test in 0.144s FAILED (failures=1) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+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 2044131] Re: i915 regression introduced with 5.5 kernel
This bug is awaiting verification that the linux-azure/6.5.0-1016.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2044131 Title: i915 regression introduced with 5.5 kernel Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.15 source package in Focal: Triaged Status in linux source package in Jammy: Fix Committed Status in linux-hwe-5.15 source package in Jammy: Invalid Status in linux source package in Mantic: Fix Released Status in linux-hwe-5.15 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-hwe-5.15 source package in Noble: Invalid Bug description: [ Impact ] Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks which have been proven invalid for at least some hardware setups. A user trying to run Focal with HWE 5.15 kernel is not able to get any video output. After going through bisection between 5.4 and 5.5 this commit was identified. Reverting it on top of Focal HWE kernel fixes the issue. The issue has been addressed upstream in DRM tree (20c2dbff342aec13bf93c2f6c951da198916a455) and has been merge into linux-next (e0ef2daa8ca8ce4dbc2fd0959e383b753a87fd7d). dmesg and lspci from the affected configuration are attached to this bug. [ Test Plan ] 1. Boot the affected hardware with Ubuntu desktop running kernel v5.5 or higher. 2. Wait until boot finishes and see the blank screen. Actual result: there is no video output visible. Expected result: normal boot process should be visible (e.g. splash), then GUI should appear. [ Where problem could occur ] This bug was a result of assumptions in the checks that turned out to be not valid for some hardware. The checks were removed from global intel_mode_valid function and moved into connector specific .mode_valid() hooks, entirely skiping BXT/GLK DSI connectors. This should keep the checks where appropriate and skip for hardware that does not comply to them. [ Other info ] Original bug description: There is a regression preventing a user to upgrade from 5.4 kernel to anything that's higher than 5.5. When using such kernel the image orientation is wrong (rotated by 90°C). Also the kernel log contains: wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06 wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 24.8.0, H2C version 12 wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 80x25 wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga console wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory information wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:o> wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v> wrz 15 09:19:49 desktop kernel: wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.> wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]' (full stack trace attached) The video hardware in use is: 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 [8086:3185] (rev 06) (prog-if 00 [VGA controller]) (...) Kernel driver in use: i915 Kernel modules: i915 The user wanted to upgrade from bionic to focal with HWE kernel (they needed it due to some networking hardware they wanted to have supported by the newer kernel). The user was testing mainline stable kernels and noticed that the last working kernel was the 5.4 series, while anything starting from 5.5 and above is BROKEN (symptoms as described in the first paragraph above). Together with the user we have run a bisection between v5.4 and v5.5 on the upstream stable kernel and we were able to identify the
[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out
This bug is awaiting verification that the linux- hwe-6.5/6.5.0-25.25~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.5' to 'verification-done-jammy-linux-hwe-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.5' to 'verification-failed-jammy-linux-hwe-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-hwe-6.5-v2 verification-needed-jammy-linux-hwe-6.5 -- 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/2036239 Title: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: In Progress Bug description: [Impact] * Issue is causing transmit hang on E810 ports with bonding enabled. * Based on the provided logs, TX hang can last for even a couple of minutes, but in most scenarios, the network will be recovered after the ice driver performs a PF reset (TX hang handler routine). * Originally, the issue was observed during Tempest tests on a newly created OpenStack cluster, resulting in a lack of certification. [Fix] * Initially, a workaround has been proposed by Intel engineers to disable LAG initialization [1]. This change has been tested in an environment where reproduction is easily achieved. After multiple iterations, no reproduction has been observed. * Shortly after, Intel proposed a patch [2] to disable LAG initialization if NVM does not expose proper capabilities. [Test Plan] * To reproduce the issue, over a 20-node cluster was used with Ceph-based storage. The problem could sometimes manifest while deploying a cluster or after the cluster was already deployed during the Tempest test run. * The issue could appear on a random node, making reproduction hard to achieve. * Multiple stress tests on single host with similar configuration did not trigger a reproduction. [Where problems could occur] * All ice drivers with ice_lag_event_handler registered can expose the issue. This handler is not implemented in 20.04 * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this capability will be released. Although potentialy issue is caused by using features without proper FW support [2], we want to take a closer look once NVMs with proper support are introduced. [1] - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40 [2] - https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html 4d50fcdc2476eef94c14c6761073af5667bb43b6 [Other Info] * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice driver backported from mainline kernel from before patch [2] was added. * Original description of the case below: I'm having issues with an Intel E810-XXV card on a Dell server under Ubuntu Jammy. Details: - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results. - using a bond over the two ports of the same card, at 25Gbps to two different switches, bond is using LACP with hash layer3+4 and fast timeout. But I believe the bug is not directly related to bonding as the problem seems to be in the interface. - machine installed by maas. No issues during installation, but at that time bond is not formed yet, later when linux is booted, the bond is formed and works without issues for a while - it works for about 2 to 3 hours fine, then the issue starts (may or may not be related to network load, but it seems that it is triggered by some tests that I run after openstack finishes installing) - one of the legs of the bond freezes and everything that would go to that lag is discarded, in and out, ping to random external hosts start losing every second packet - after some time you can see on the kernel log messages about "NETDEV WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack trace - the switch does log that the bond is flapping --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio
[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out
This bug is awaiting verification that the linux-aws/6.5.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-aws' to 'verification-done-mantic- linux-aws'. If the problem still exists, change the tag 'verification- needed-mantic-linux-aws' to 'verification-failed-mantic-linux-aws'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-aws-v2 verification-needed-mantic-linux-aws -- 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/2036239 Title: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: In Progress Bug description: [Impact] * Issue is causing transmit hang on E810 ports with bonding enabled. * Based on the provided logs, TX hang can last for even a couple of minutes, but in most scenarios, the network will be recovered after the ice driver performs a PF reset (TX hang handler routine). * Originally, the issue was observed during Tempest tests on a newly created OpenStack cluster, resulting in a lack of certification. [Fix] * Initially, a workaround has been proposed by Intel engineers to disable LAG initialization [1]. This change has been tested in an environment where reproduction is easily achieved. After multiple iterations, no reproduction has been observed. * Shortly after, Intel proposed a patch [2] to disable LAG initialization if NVM does not expose proper capabilities. [Test Plan] * To reproduce the issue, over a 20-node cluster was used with Ceph-based storage. The problem could sometimes manifest while deploying a cluster or after the cluster was already deployed during the Tempest test run. * The issue could appear on a random node, making reproduction hard to achieve. * Multiple stress tests on single host with similar configuration did not trigger a reproduction. [Where problems could occur] * All ice drivers with ice_lag_event_handler registered can expose the issue. This handler is not implemented in 20.04 * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this capability will be released. Although potentialy issue is caused by using features without proper FW support [2], we want to take a closer look once NVMs with proper support are introduced. [1] - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40 [2] - https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html 4d50fcdc2476eef94c14c6761073af5667bb43b6 [Other Info] * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice driver backported from mainline kernel from before patch [2] was added. * Original description of the case below: I'm having issues with an Intel E810-XXV card on a Dell server under Ubuntu Jammy. Details: - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results. - using a bond over the two ports of the same card, at 25Gbps to two different switches, bond is using LACP with hash layer3+4 and fast timeout. But I believe the bug is not directly related to bonding as the problem seems to be in the interface. - machine installed by maas. No issues during installation, but at that time bond is not formed yet, later when linux is booted, the bond is formed and works without issues for a while - it works for about 2 to 3 hours fine, then the issue starts (may or may not be related to network load, but it seems that it is triggered by some tests that I run after openstack finishes installing) - one of the legs of the bond freezes and everything that would go to that lag is discarded, in and out, ping to random external hosts start losing every second packet - after some time you can see on the kernel log messages about "NETDEV WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack trace - the switch does log that the bond is flapping --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 12 20:05 seq
[Kernel-packages] [Bug 2044131] Re: i915 regression introduced with 5.5 kernel
This bug is awaiting verification that the linux- hwe-6.5/6.5.0-25.25~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.5' to 'verification-done-jammy-linux-hwe-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.5' to 'verification-failed-jammy-linux-hwe-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-hwe-6.5-v2 verification-needed-jammy-linux-hwe-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2044131 Title: i915 regression introduced with 5.5 kernel Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.15 source package in Focal: Triaged Status in linux source package in Jammy: Fix Committed Status in linux-hwe-5.15 source package in Jammy: Invalid Status in linux source package in Mantic: Fix Released Status in linux-hwe-5.15 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-hwe-5.15 source package in Noble: Invalid Bug description: [ Impact ] Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks which have been proven invalid for at least some hardware setups. A user trying to run Focal with HWE 5.15 kernel is not able to get any video output. After going through bisection between 5.4 and 5.5 this commit was identified. Reverting it on top of Focal HWE kernel fixes the issue. The issue has been addressed upstream in DRM tree (20c2dbff342aec13bf93c2f6c951da198916a455) and has been merge into linux-next (e0ef2daa8ca8ce4dbc2fd0959e383b753a87fd7d). dmesg and lspci from the affected configuration are attached to this bug. [ Test Plan ] 1. Boot the affected hardware with Ubuntu desktop running kernel v5.5 or higher. 2. Wait until boot finishes and see the blank screen. Actual result: there is no video output visible. Expected result: normal boot process should be visible (e.g. splash), then GUI should appear. [ Where problem could occur ] This bug was a result of assumptions in the checks that turned out to be not valid for some hardware. The checks were removed from global intel_mode_valid function and moved into connector specific .mode_valid() hooks, entirely skiping BXT/GLK DSI connectors. This should keep the checks where appropriate and skip for hardware that does not comply to them. [ Other info ] Original bug description: There is a regression preventing a user to upgrade from 5.4 kernel to anything that's higher than 5.5. When using such kernel the image orientation is wrong (rotated by 90°C). Also the kernel log contains: wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06 wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 24.8.0, H2C version 12 wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 80x25 wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga console wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory information wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:o> wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v> wrz 15 09:19:49 desktop kernel: wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.> wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]' (full stack trace attached) The video hardware in use is: 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 [8086:3185] (rev 06) (prog-if 00 [VGA controller]) (...) Kernel driver in use: i915 Kernel modules: i915 The user wanted to upgrade from bionic to focal with HWE kernel (they needed it due to some networking hardware they wanted to have supported by the newer kernel). The user was testing mainline stable kernels and noticed that the last working kernel was the 5.4 series, while anything starting from 5.5 and above is BROKEN (symptoms as described in the first paragraph above). Together with the user we have run a bisection between v5.4 and v5.5 on the upstream stable kernel and we were able to
[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out
This bug is awaiting verification that the linux-azure/6.5.0-1016.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- 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/2036239 Title: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: In Progress Bug description: [Impact] * Issue is causing transmit hang on E810 ports with bonding enabled. * Based on the provided logs, TX hang can last for even a couple of minutes, but in most scenarios, the network will be recovered after the ice driver performs a PF reset (TX hang handler routine). * Originally, the issue was observed during Tempest tests on a newly created OpenStack cluster, resulting in a lack of certification. [Fix] * Initially, a workaround has been proposed by Intel engineers to disable LAG initialization [1]. This change has been tested in an environment where reproduction is easily achieved. After multiple iterations, no reproduction has been observed. * Shortly after, Intel proposed a patch [2] to disable LAG initialization if NVM does not expose proper capabilities. [Test Plan] * To reproduce the issue, over a 20-node cluster was used with Ceph-based storage. The problem could sometimes manifest while deploying a cluster or after the cluster was already deployed during the Tempest test run. * The issue could appear on a random node, making reproduction hard to achieve. * Multiple stress tests on single host with similar configuration did not trigger a reproduction. [Where problems could occur] * All ice drivers with ice_lag_event_handler registered can expose the issue. This handler is not implemented in 20.04 * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this capability will be released. Although potentialy issue is caused by using features without proper FW support [2], we want to take a closer look once NVMs with proper support are introduced. [1] - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40 [2] - https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html 4d50fcdc2476eef94c14c6761073af5667bb43b6 [Other Info] * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice driver backported from mainline kernel from before patch [2] was added. * Original description of the case below: I'm having issues with an Intel E810-XXV card on a Dell server under Ubuntu Jammy. Details: - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results. - using a bond over the two ports of the same card, at 25Gbps to two different switches, bond is using LACP with hash layer3+4 and fast timeout. But I believe the bug is not directly related to bonding as the problem seems to be in the interface. - machine installed by maas. No issues during installation, but at that time bond is not formed yet, later when linux is booted, the bond is formed and works without issues for a while - it works for about 2 to 3 hours fine, then the issue starts (may or may not be related to network load, but it seems that it is triggered by some tests that I run after openstack finishes installing) - one of the legs of the bond freezes and everything that would go to that lag is discarded, in and out, ping to random external hosts start losing every second packet - after some time you can see on the kernel log messages about "NETDEV WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack trace - the switch does log that the bond is flapping --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 12
[Kernel-packages] [Bug 2047634] Re: Reject connection when malformed L2CAP signal packet is received
This bug is awaiting verification that the linux- hwe-6.5/6.5.0-25.25~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.5' to 'verification-done-jammy-linux-hwe-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.5' to 'verification-failed-jammy-linux-hwe-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-hwe-6.5-v2 verification-needed-jammy-linux-hwe-6.5 -- 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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Released Bug description: The patch is merged in mainline kernel v6.7-rc7, so Noble kernel already have this fix. And this patch is CCed to sta...@vger.kernel.org, M and L kernel will have this fix with the SRU update sooner or later. For Jammy kernel, an OEM customer is waiting for this patch to be merged to Jammy kernel and OEM kernel, here I submit the review reqeust for Jammy only. [Impact] An OEM customer want to do the bluetooth profile testing suite (PTS) test, and they found if sending 2 commands and one of them is "unknown comands", the bluetooth stack doesn't reply the ack as expected, this broke the customer's PTS test. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. And I also tested the patched kernel with 2 bt headsets, 1 bt keyboard and my mobile phone, all worked as well as before. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. It has possibility to make some bt devices could not work with patched kernel, but this possibility is very low, I tested the patched kernel with 2 bt headsets, 1 bt keyboard and my Android mobile phone, all worked as well as before. [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2044131] Re: i915 regression introduced with 5.5 kernel
This bug is awaiting verification that the linux-aws/6.5.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-aws' to 'verification-done-mantic- linux-aws'. If the problem still exists, change the tag 'verification- needed-mantic-linux-aws' to 'verification-failed-mantic-linux-aws'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-aws-v2 verification-needed-mantic-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2044131 Title: i915 regression introduced with 5.5 kernel Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.15 source package in Focal: Triaged Status in linux source package in Jammy: Fix Committed Status in linux-hwe-5.15 source package in Jammy: Invalid Status in linux source package in Mantic: Fix Released Status in linux-hwe-5.15 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-hwe-5.15 source package in Noble: Invalid Bug description: [ Impact ] Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks which have been proven invalid for at least some hardware setups. A user trying to run Focal with HWE 5.15 kernel is not able to get any video output. After going through bisection between 5.4 and 5.5 this commit was identified. Reverting it on top of Focal HWE kernel fixes the issue. The issue has been addressed upstream in DRM tree (20c2dbff342aec13bf93c2f6c951da198916a455) and has been merge into linux-next (e0ef2daa8ca8ce4dbc2fd0959e383b753a87fd7d). dmesg and lspci from the affected configuration are attached to this bug. [ Test Plan ] 1. Boot the affected hardware with Ubuntu desktop running kernel v5.5 or higher. 2. Wait until boot finishes and see the blank screen. Actual result: there is no video output visible. Expected result: normal boot process should be visible (e.g. splash), then GUI should appear. [ Where problem could occur ] This bug was a result of assumptions in the checks that turned out to be not valid for some hardware. The checks were removed from global intel_mode_valid function and moved into connector specific .mode_valid() hooks, entirely skiping BXT/GLK DSI connectors. This should keep the checks where appropriate and skip for hardware that does not comply to them. [ Other info ] Original bug description: There is a regression preventing a user to upgrade from 5.4 kernel to anything that's higher than 5.5. When using such kernel the image orientation is wrong (rotated by 90°C). Also the kernel log contains: wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06 wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 24.8.0, H2C version 12 wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 80x25 wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga console wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory information wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:o> wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v> wrz 15 09:19:49 desktop kernel: wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.> wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]' (full stack trace attached) The video hardware in use is: 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 [8086:3185] (rev 06) (prog-if 00 [VGA controller]) (...) Kernel driver in use: i915 Kernel modules: i915 The user wanted to upgrade from bionic to focal with HWE kernel (they needed it due to some networking hardware they wanted to have supported by the newer kernel). The user was testing mainline stable kernels and noticed that the last working kernel was the 5.4 series, while anything starting from 5.5 and above is BROKEN (symptoms as described in the first paragraph above). Together with the user we have run a bisection between v5.4 and v5.5 on the upstream stable kernel and we were able to identify the first broken
[Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
This bug is awaiting verification that the linux-azure/6.5.0-1016.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- 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/2045233 Title: [SRU][22.04.04]: mpi3mr driver update Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Confirmed Bug description: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). This has been requested by both Broadcom as the upstream and by one of the larger OEM partners who are going to be selling systems with these storage controllers to customers. This series of patches includes bug fixes and support for current Broadcom controllers. [Fixes] Below are the commit IDs for the latest upstream version (v6.8). The 22.04 LTS point kernel already includes the latest mpi3mr driver version 8.0.0.69.0. Therefore, the listed commit IDs below correspond to the subsequent patches. The commit IDs listed below are in sequential order from bottom to top, indicating the order for applying the patches. linux-next d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0 9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-3 fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-2 c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-1 07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status reply descriptor f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset and Unrecoverable State c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller reset b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs Mainline at 6.6/6.7 82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset 9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0 d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after controller reset e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O 6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28 9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time out [Testing] verify the mpi3mr driver is loaded verify the version string shows 8.5.1.0.0 [Regression Risk] Low. These patches are contained to the mpi3mr driver code itself and are all already accepted upstream. They cleanly pick into our 6.5 kernel tree. Broadcom has tested these and the only concern is the kernel warning below in Comment #7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045233/+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 2047634] Re: Reject connection when malformed L2CAP signal packet is received
This bug is awaiting verification that the linux-azure/6.5.0-1016.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- 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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Released Bug description: The patch is merged in mainline kernel v6.7-rc7, so Noble kernel already have this fix. And this patch is CCed to sta...@vger.kernel.org, M and L kernel will have this fix with the SRU update sooner or later. For Jammy kernel, an OEM customer is waiting for this patch to be merged to Jammy kernel and OEM kernel, here I submit the review reqeust for Jammy only. [Impact] An OEM customer want to do the bluetooth profile testing suite (PTS) test, and they found if sending 2 commands and one of them is "unknown comands", the bluetooth stack doesn't reply the ack as expected, this broke the customer's PTS test. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. And I also tested the patched kernel with 2 bt headsets, 1 bt keyboard and my mobile phone, all worked as well as before. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. It has possibility to make some bt devices could not work with patched kernel, but this possibility is very low, I tested the patched kernel with 2 bt headsets, 1 bt keyboard and my Android mobile phone, all worked as well as before. [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
This bug is awaiting verification that the linux-aws/6.5.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-aws' to 'verification-done-mantic- linux-aws'. If the problem still exists, change the tag 'verification- needed-mantic-linux-aws' to 'verification-failed-mantic-linux-aws'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-aws-v2 verification-needed-mantic-linux-aws -- 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/2045233 Title: [SRU][22.04.04]: mpi3mr driver update Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Confirmed Bug description: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). This has been requested by both Broadcom as the upstream and by one of the larger OEM partners who are going to be selling systems with these storage controllers to customers. This series of patches includes bug fixes and support for current Broadcom controllers. [Fixes] Below are the commit IDs for the latest upstream version (v6.8). The 22.04 LTS point kernel already includes the latest mpi3mr driver version 8.0.0.69.0. Therefore, the listed commit IDs below correspond to the subsequent patches. The commit IDs listed below are in sequential order from bottom to top, indicating the order for applying the patches. linux-next d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0 9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-3 fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-2 c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-1 07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status reply descriptor f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset and Unrecoverable State c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller reset b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs Mainline at 6.6/6.7 82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset 9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0 d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after controller reset e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O 6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28 9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time out [Testing] verify the mpi3mr driver is loaded verify the version string shows 8.5.1.0.0 [Regression Risk] Low. These patches are contained to the mpi3mr driver code itself and are all already accepted upstream. They cleanly pick into our 6.5 kernel tree. Broadcom has tested these and the only concern is the kernel warning below in Comment #7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045233/+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 2047634] Re: Reject connection when malformed L2CAP signal packet is received
This bug is awaiting verification that the linux-aws/6.5.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-aws' to 'verification-done-mantic- linux-aws'. If the problem still exists, change the tag 'verification- needed-mantic-linux-aws' to 'verification-failed-mantic-linux-aws'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-aws-v2 verification-needed-mantic-linux-aws -- 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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Released Bug description: The patch is merged in mainline kernel v6.7-rc7, so Noble kernel already have this fix. And this patch is CCed to sta...@vger.kernel.org, M and L kernel will have this fix with the SRU update sooner or later. For Jammy kernel, an OEM customer is waiting for this patch to be merged to Jammy kernel and OEM kernel, here I submit the review reqeust for Jammy only. [Impact] An OEM customer want to do the bluetooth profile testing suite (PTS) test, and they found if sending 2 commands and one of them is "unknown comands", the bluetooth stack doesn't reply the ack as expected, this broke the customer's PTS test. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. And I also tested the patched kernel with 2 bt headsets, 1 bt keyboard and my mobile phone, all worked as well as before. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. It has possibility to make some bt devices could not work with patched kernel, but this possibility is very low, I tested the patched kernel with 2 bt headsets, 1 bt keyboard and my Android mobile phone, all worked as well as before. [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.
This bug is awaiting verification that the linux- hwe-6.5/6.5.0-25.25~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.5' to 'verification-done-jammy-linux-hwe-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.5' to 'verification-failed-jammy-linux-hwe-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-hwe-6.5-v2 verification-needed-jammy-linux-hwe-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049027 Title: The display becomes frozen after some time when a HDMI device is connected. Status in linux package in Ubuntu: Invalid Status in linux-signed-hwe-6.5 package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Released Status in linux-signed-hwe-6.5 source package in Mantic: Invalid Bug description: SRU Justification: [Impact] Multiple users have reported frozen displays when external HDMI device is connected on systems with intel graphics chipsets. [Fix] * backport 49e0a85ec344: "drm/i915/dmc: Don't enable any pipe DMC events" from 6.6.9 [Test Plan] * Tested on Intel TigerLake with iris Xe Graphics and no issues so far. It seems it affects mostly Alder Lake though, but at least it does not cause any issues on other models. * It has also been tested upstream https://gitlab.freedesktop.org/drm/intel/-/issues/8685 [Where problems could occur] * We could see issues on systems with Intel Graphics when HDMI devices are connected during power state changes. Old description: It is exactly this bug: https://gitlab.freedesktop.org/drm/intel/-/issues/8685 It was fixed with that kernel commit: commit 648d7be8ecf47b0556e32550145c70db153b16fb Author: Ville Syrjälä Date: Mon Dec 11 23:37:47 2023 +0200 drm/i915/dmc: Don't enable any pipe DMC events https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/ which was picked for 6.6.9. I'd like to ask whether it is possible to apply that patch to the current Ubuntu kernel? Best Sönke ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 11 13:11:59 2024 InstallationDate: Installed on 2023-03-01 (316 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049027/+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 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.
This bug is awaiting verification that the linux-aws/6.5.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-aws' to 'verification-done-mantic- linux-aws'. If the problem still exists, change the tag 'verification- needed-mantic-linux-aws' to 'verification-failed-mantic-linux-aws'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-aws-v2 verification-needed-mantic-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049027 Title: The display becomes frozen after some time when a HDMI device is connected. Status in linux package in Ubuntu: Invalid Status in linux-signed-hwe-6.5 package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Released Status in linux-signed-hwe-6.5 source package in Mantic: Invalid Bug description: SRU Justification: [Impact] Multiple users have reported frozen displays when external HDMI device is connected on systems with intel graphics chipsets. [Fix] * backport 49e0a85ec344: "drm/i915/dmc: Don't enable any pipe DMC events" from 6.6.9 [Test Plan] * Tested on Intel TigerLake with iris Xe Graphics and no issues so far. It seems it affects mostly Alder Lake though, but at least it does not cause any issues on other models. * It has also been tested upstream https://gitlab.freedesktop.org/drm/intel/-/issues/8685 [Where problems could occur] * We could see issues on systems with Intel Graphics when HDMI devices are connected during power state changes. Old description: It is exactly this bug: https://gitlab.freedesktop.org/drm/intel/-/issues/8685 It was fixed with that kernel commit: commit 648d7be8ecf47b0556e32550145c70db153b16fb Author: Ville Syrjälä Date: Mon Dec 11 23:37:47 2023 +0200 drm/i915/dmc: Don't enable any pipe DMC events https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/ which was picked for 6.6.9. I'd like to ask whether it is possible to apply that patch to the current Ubuntu kernel? Best Sönke ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 11 13:11:59 2024 InstallationDate: Installed on 2023-03-01 (316 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049027/+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 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.
This bug is awaiting verification that the linux-azure/6.5.0-1016.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049027 Title: The display becomes frozen after some time when a HDMI device is connected. Status in linux package in Ubuntu: Invalid Status in linux-signed-hwe-6.5 package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Released Status in linux-signed-hwe-6.5 source package in Mantic: Invalid Bug description: SRU Justification: [Impact] Multiple users have reported frozen displays when external HDMI device is connected on systems with intel graphics chipsets. [Fix] * backport 49e0a85ec344: "drm/i915/dmc: Don't enable any pipe DMC events" from 6.6.9 [Test Plan] * Tested on Intel TigerLake with iris Xe Graphics and no issues so far. It seems it affects mostly Alder Lake though, but at least it does not cause any issues on other models. * It has also been tested upstream https://gitlab.freedesktop.org/drm/intel/-/issues/8685 [Where problems could occur] * We could see issues on systems with Intel Graphics when HDMI devices are connected during power state changes. Old description: It is exactly this bug: https://gitlab.freedesktop.org/drm/intel/-/issues/8685 It was fixed with that kernel commit: commit 648d7be8ecf47b0556e32550145c70db153b16fb Author: Ville Syrjälä Date: Mon Dec 11 23:37:47 2023 +0200 drm/i915/dmc: Don't enable any pipe DMC events https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/ which was picked for 6.6.9. I'd like to ask whether it is possible to apply that patch to the current Ubuntu kernel? Best Sönke ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 11 13:11:59 2024 InstallationDate: Installed on 2023-03-01 (316 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049027/+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 2049689] Re: partprobe is broken on empty loopback device
This bug is awaiting verification that the linux- hwe-6.5/6.5.0-25.25~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.5' to 'verification-done-jammy-linux-hwe-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.5' to 'verification-failed-jammy-linux-hwe-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-hwe-6.5-v2 verification-needed-jammy-linux-hwe-6.5 -- 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/2049689 Title: partprobe is broken on empty loopback device Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Bug description: SRU Justification: [Impact] * BLKPG_DEL_PARTITION on an empty loopback device used to return ENXIO but now returns EINVAL, breaking partprobe due to commit "block: don't add or resize partition on the disk with GENHD_FL_NO_PART" introduced in mantic 6.5.0-17 and jammy 5.15.0-94. [Fix] * backport commit "block: Move checking GENHD_FL_NO_PART to bdev_add_partition()" [Test Plan] * dd if=/dev/zero of=/tmp/foo bs=1M count=50 * partprobe $(losetup --find --show /tmp/foo) Before the fix this fails. After the fix it should work. [Where problems could occur] * We may see issues on disk partitions operations. Old description: This is with the kernel from jammy-proposed (linux-image-5.15.0-94-generic 5.15.0-94.104). Do this: # dd if=/dev/zero of=/tmp/file bs=1M count=50 # partprobe "$(losetup --show --find /tmp/file)" Notice this very odd error message: Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/loop2 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. That's a result of an ioctl changing its error code in an incompatible way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing partprobe. 5.15.0.91.88: ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or address) 5.15.0.94.91: ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument) This is a userspace API break which impacts GNU parted and util-linux (as confirmed by the util-linux maintainer). This issue was discovered as part of Cockpit CI here: https://github.com/cockpit-project/bots/pull/5793 This issue is being discussed on LKML here (with a patch likely to land soon): https://lkml.org/lkml/2024/1/15/147 lsb_release -rd: Description: Ubuntu 22.04.3 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049689/+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 2049689] Re: partprobe is broken on empty loopback device
This bug is awaiting verification that the linux-azure/6.5.0-1016.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- 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/2049689 Title: partprobe is broken on empty loopback device Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Bug description: SRU Justification: [Impact] * BLKPG_DEL_PARTITION on an empty loopback device used to return ENXIO but now returns EINVAL, breaking partprobe due to commit "block: don't add or resize partition on the disk with GENHD_FL_NO_PART" introduced in mantic 6.5.0-17 and jammy 5.15.0-94. [Fix] * backport commit "block: Move checking GENHD_FL_NO_PART to bdev_add_partition()" [Test Plan] * dd if=/dev/zero of=/tmp/foo bs=1M count=50 * partprobe $(losetup --find --show /tmp/foo) Before the fix this fails. After the fix it should work. [Where problems could occur] * We may see issues on disk partitions operations. Old description: This is with the kernel from jammy-proposed (linux-image-5.15.0-94-generic 5.15.0-94.104). Do this: # dd if=/dev/zero of=/tmp/file bs=1M count=50 # partprobe "$(losetup --show --find /tmp/file)" Notice this very odd error message: Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/loop2 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. That's a result of an ioctl changing its error code in an incompatible way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing partprobe. 5.15.0.91.88: ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or address) 5.15.0.94.91: ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument) This is a userspace API break which impacts GNU parted and util-linux (as confirmed by the util-linux maintainer). This issue was discovered as part of Cockpit CI here: https://github.com/cockpit-project/bots/pull/5793 This issue is being discussed on LKML here (with a patch likely to land soon): https://lkml.org/lkml/2024/1/15/147 lsb_release -rd: Description: Ubuntu 22.04.3 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049689/+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 2049689] Re: partprobe is broken on empty loopback device
This bug is awaiting verification that the linux-aws/6.5.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-aws' to 'verification-done-mantic- linux-aws'. If the problem still exists, change the tag 'verification- needed-mantic-linux-aws' to 'verification-failed-mantic-linux-aws'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-aws-v2 verification-needed-mantic-linux-aws -- 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/2049689 Title: partprobe is broken on empty loopback device Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Bug description: SRU Justification: [Impact] * BLKPG_DEL_PARTITION on an empty loopback device used to return ENXIO but now returns EINVAL, breaking partprobe due to commit "block: don't add or resize partition on the disk with GENHD_FL_NO_PART" introduced in mantic 6.5.0-17 and jammy 5.15.0-94. [Fix] * backport commit "block: Move checking GENHD_FL_NO_PART to bdev_add_partition()" [Test Plan] * dd if=/dev/zero of=/tmp/foo bs=1M count=50 * partprobe $(losetup --find --show /tmp/foo) Before the fix this fails. After the fix it should work. [Where problems could occur] * We may see issues on disk partitions operations. Old description: This is with the kernel from jammy-proposed (linux-image-5.15.0-94-generic 5.15.0-94.104). Do this: # dd if=/dev/zero of=/tmp/file bs=1M count=50 # partprobe "$(losetup --show --find /tmp/file)" Notice this very odd error message: Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/loop2 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. That's a result of an ioctl changing its error code in an incompatible way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing partprobe. 5.15.0.91.88: ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or address) 5.15.0.94.91: ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument) This is a userspace API break which impacts GNU parted and util-linux (as confirmed by the util-linux maintainer). This issue was discovered as part of Cockpit CI here: https://github.com/cockpit-project/bots/pull/5793 This issue is being discussed on LKML here (with a patch likely to land soon): https://lkml.org/lkml/2024/1/15/147 lsb_release -rd: Description: Ubuntu 22.04.3 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049689/+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 2051050] Re: Audio balancing setting doesn't work with the cirrus codec
This bug is awaiting verification that the linux- hwe-6.5/6.5.0-25.25~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.5' to 'verification-done-jammy-linux-hwe-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.5' to 'verification-failed-jammy-linux-hwe-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-hwe-6.5-v2 verification-needed-jammy-linux-hwe-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051050 Title: Audio balancing setting doesn't work with the cirrus codec Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2051050 Currently this patch is in the linux-next, and will be in the mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble kernel, Noble kernel will have this patch automatically. [Impact] In the gnome audio setting, if we adjust balancing setting, it doesn't work at all on a Dell machine with cirrus codec, that is because with the current driver, the exported amixer controls can't be handled by pulseaudio. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booted with the patched kernel, move the bar to the left or right to adjust the balance, we could hear the sound from left channel or right channel accordingly. [Where problems could occur] This change will not create "Master Volume" amixer controls, probably will make the audio control malfunction, that is we couldn't control playback or capture volume correctly, but this regression possibility is very low, we already tested the patch on the machines with cirrus codec, they all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051050/+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 2051176] Re: Update Ubuntu.md
This bug is awaiting verification that the linux-azure/6.5.0-1016.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- 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/2051176 Title: Update Ubuntu.md Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Released Bug description: [ Impact ] * The Ubuntu.md has incorrect Ubuntu release and kernel version information which may impact any tools that use this information to determine the Ubuntu release. [ Test Plan ] * cat Ubuntu.md and check to make sure it is correct [ Where problems could occur ] * There is no functional impact on the kernel.. we could introduce a typo in Ubuntu.md [ Other Info ] * I used the current kernel version of 6.5.10 since it didn't seem to make sense to use the old version we released with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051176/+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 2051341] Re: black screen when wake up from s3 with AMD W7600 gfx
This bug is awaiting verification that the linux-azure/6.5.0-1016.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051341 Title: black screen when wake up from s3 with AMD W7600 gfx Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The display is blank when resumed from s3 with AMD W7600 DGFx and Dell E2422H monitor [Fix] Mario points out the commit in 6.7 may help 3b401e30c249 drm/ttm: Reorder sys manager cleanup step [Test] 1. Build W7600 dGFx + Monitor: E2422H Config and FIDA Ubunutu22.04 OS. 2. Boot OS, put SUT to suspend. 3. Wake up the System from suspend. 4. Right away reboot the system from Ubuntu OS. 5. Put SUT to suspend and wake up the system. 6. After wake up Suspend, SUT should not be black screen. 7. Repetition Step 2~6 30 cycles [Where problems could occur] Handling the system memory manager after the workqueue is destroyed prevents from the pointer beeing used after free. Should be pretty safe to include it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051341/+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 2051176] Re: Update Ubuntu.md
This bug is awaiting verification that the linux-azure/6.5.0-1016.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-aws-v2 verification-needed-mantic-linux-aws -- 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/2051176 Title: Update Ubuntu.md Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Released Bug description: [ Impact ] * The Ubuntu.md has incorrect Ubuntu release and kernel version information which may impact any tools that use this information to determine the Ubuntu release. [ Test Plan ] * cat Ubuntu.md and check to make sure it is correct [ Where problems could occur ] * There is no functional impact on the kernel.. we could introduce a typo in Ubuntu.md [ Other Info ] * I used the current kernel version of 6.5.10 since it didn't seem to make sense to use the old version we released with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051176/+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 2051050] Re: Audio balancing setting doesn't work with the cirrus codec
This bug is awaiting verification that the linux-aws/6.5.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-aws' to 'verification-done-mantic- linux-aws'. If the problem still exists, change the tag 'verification- needed-mantic-linux-aws' to 'verification-failed-mantic-linux-aws'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-aws-v2 verification-needed-mantic-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051050 Title: Audio balancing setting doesn't work with the cirrus codec Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2051050 Currently this patch is in the linux-next, and will be in the mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble kernel, Noble kernel will have this patch automatically. [Impact] In the gnome audio setting, if we adjust balancing setting, it doesn't work at all on a Dell machine with cirrus codec, that is because with the current driver, the exported amixer controls can't be handled by pulseaudio. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booted with the patched kernel, move the bar to the left or right to adjust the balance, we could hear the sound from left channel or right channel accordingly. [Where problems could occur] This change will not create "Master Volume" amixer controls, probably will make the audio control malfunction, that is we couldn't control playback or capture volume correctly, but this regression possibility is very low, we already tested the patch on the machines with cirrus codec, they all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051050/+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 2051050] Re: Audio balancing setting doesn't work with the cirrus codec
This bug is awaiting verification that the linux-azure/6.5.0-1016.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051050 Title: Audio balancing setting doesn't work with the cirrus codec Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2051050 Currently this patch is in the linux-next, and will be in the mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble kernel, Noble kernel will have this patch automatically. [Impact] In the gnome audio setting, if we adjust balancing setting, it doesn't work at all on a Dell machine with cirrus codec, that is because with the current driver, the exported amixer controls can't be handled by pulseaudio. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booted with the patched kernel, move the bar to the left or right to adjust the balance, we could hear the sound from left channel or right channel accordingly. [Where problems could occur] This change will not create "Master Volume" amixer controls, probably will make the audio control malfunction, that is we couldn't control playback or capture volume correctly, but this regression possibility is very low, we already tested the patch on the machines with cirrus codec, they all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051050/+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 2051176] Re: Update Ubuntu.md
This bug is awaiting verification that the linux- hwe-6.5/6.5.0-25.25~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.5' to 'verification-done-jammy-linux-hwe-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.5' to 'verification-failed-jammy-linux-hwe-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-hwe-6.5-v2 verification-needed-jammy-linux-hwe-6.5 -- 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/2051176 Title: Update Ubuntu.md Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Released Bug description: [ Impact ] * The Ubuntu.md has incorrect Ubuntu release and kernel version information which may impact any tools that use this information to determine the Ubuntu release. [ Test Plan ] * cat Ubuntu.md and check to make sure it is correct [ Where problems could occur ] * There is no functional impact on the kernel.. we could introduce a typo in Ubuntu.md [ Other Info ] * I used the current kernel version of 6.5.10 since it didn't seem to make sense to use the old version we released with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051176/+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 2051341] Re: black screen when wake up from s3 with AMD W7600 gfx
This bug is awaiting verification that the linux-aws/6.5.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-aws' to 'verification-done-mantic- linux-aws'. If the problem still exists, change the tag 'verification- needed-mantic-linux-aws' to 'verification-failed-mantic-linux-aws'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-aws-v2 verification-needed-mantic-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051341 Title: black screen when wake up from s3 with AMD W7600 gfx Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The display is blank when resumed from s3 with AMD W7600 DGFx and Dell E2422H monitor [Fix] Mario points out the commit in 6.7 may help 3b401e30c249 drm/ttm: Reorder sys manager cleanup step [Test] 1. Build W7600 dGFx + Monitor: E2422H Config and FIDA Ubunutu22.04 OS. 2. Boot OS, put SUT to suspend. 3. Wake up the System from suspend. 4. Right away reboot the system from Ubuntu OS. 5. Put SUT to suspend and wake up the system. 6. After wake up Suspend, SUT should not be black screen. 7. Repetition Step 2~6 30 cycles [Where problems could occur] Handling the system memory manager after the workqueue is destroyed prevents from the pointer beeing used after free. Should be pretty safe to include it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051341/+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 2051176] Re: Update Ubuntu.md
This bug is awaiting verification that the linux-aws/6.5.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-aws' to 'verification-done-mantic- linux-aws'. If the problem still exists, change the tag 'verification- needed-mantic-linux-aws' to 'verification-failed-mantic-linux-aws'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2051176 Title: Update Ubuntu.md Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Released Bug description: [ Impact ] * The Ubuntu.md has incorrect Ubuntu release and kernel version information which may impact any tools that use this information to determine the Ubuntu release. [ Test Plan ] * cat Ubuntu.md and check to make sure it is correct [ Where problems could occur ] * There is no functional impact on the kernel.. we could introduce a typo in Ubuntu.md [ Other Info ] * I used the current kernel version of 6.5.10 since it didn't seem to make sense to use the old version we released with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051176/+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 2051341] Re: black screen when wake up from s3 with AMD W7600 gfx
This bug is awaiting verification that the linux- hwe-6.5/6.5.0-25.25~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.5' to 'verification-done-jammy-linux-hwe-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.5' to 'verification-failed-jammy-linux-hwe-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-hwe-6.5-v2 verification-needed-jammy-linux-hwe-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051341 Title: black screen when wake up from s3 with AMD W7600 gfx Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The display is blank when resumed from s3 with AMD W7600 DGFx and Dell E2422H monitor [Fix] Mario points out the commit in 6.7 may help 3b401e30c249 drm/ttm: Reorder sys manager cleanup step [Test] 1. Build W7600 dGFx + Monitor: E2422H Config and FIDA Ubunutu22.04 OS. 2. Boot OS, put SUT to suspend. 3. Wake up the System from suspend. 4. Right away reboot the system from Ubuntu OS. 5. Put SUT to suspend and wake up the system. 6. After wake up Suspend, SUT should not be black screen. 7. Repetition Step 2~6 30 cycles [Where problems could occur] Handling the system memory manager after the workqueue is destroyed prevents from the pointer beeing used after free. Should be pretty safe to include it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051341/+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 2052469] Re: Provide an arm64 linux-oracle 64k kernel variant
This bug was fixed in the package linux-oracle - 6.5.0-1018.18 --- linux-oracle (6.5.0-1018.18) mantic; urgency=medium * mantic/linux-oracle: 6.5.0-1018.18 -proposed tracker (LP: #2054120) * Provide an arm64 linux-oracle 64k kernel variant (LP: #2052469) - [Packaging] oracle: Remove amd64 from 64k flavour -- John Cabaj Fri, 16 Feb 2024 11:42:26 -0600 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2052469 Title: Provide an arm64 linux-oracle 64k kernel variant Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle-6.5 package in Ubuntu: Invalid Status in linux-oracle source package in Jammy: Invalid Status in linux-oracle-6.5 source package in Jammy: Fix Released Status in linux-oracle source package in Mantic: Fix Released Status in linux-oracle-6.5 source package in Mantic: Invalid Status in linux-oracle source package in Noble: In Progress Status in linux-oracle-6.5 source package in Noble: Invalid Bug description: [Impact] * Oracle requested 64k page size flavour. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00377602 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2052469/+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 2052469] Re: Provide an arm64 linux-oracle 64k kernel variant
This bug was fixed in the package linux-oracle-6.5 - 6.5.0-1018.18~22.04.1 --- linux-oracle-6.5 (6.5.0-1018.18~22.04.1) jammy; urgency=medium * jammy/linux-oracle-6.5: 6.5.0-1018.18~22.04.1 -proposed tracker (LP: #2054122) [ Ubuntu: 6.5.0-1018.18 ] * mantic/linux-oracle: 6.5.0-1018.18 -proposed tracker (LP: #2054120) * Provide an arm64 linux-oracle 64k kernel variant (LP: #2052469) - [Packaging] oracle: Remove amd64 from 64k flavour -- John Cabaj Fri, 16 Feb 2024 14:56:27 -0600 ** Changed in: linux-oracle-6.5 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: linux-oracle (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2052469 Title: Provide an arm64 linux-oracle 64k kernel variant Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle-6.5 package in Ubuntu: Invalid Status in linux-oracle source package in Jammy: Invalid Status in linux-oracle-6.5 source package in Jammy: Fix Released Status in linux-oracle source package in Mantic: Fix Released Status in linux-oracle-6.5 source package in Mantic: Invalid Status in linux-oracle source package in Noble: In Progress Status in linux-oracle-6.5 source package in Noble: Invalid Bug description: [Impact] * Oracle requested 64k page size flavour. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00377602 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2052469/+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 2049049] Re: Focal update: v5.4.261 upstream stable release
This bug was fixed in the package linux - 5.4.0-173.191 --- linux (5.4.0-173.191) focal; urgency=medium * focal/linux: 5.4.0-173.191 -proposed tracker (LP: #2052135) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2024.02.05) * CVE-2023-0340 - vhost: use kzalloc() instead of kmalloc() followed by memset() * CVE-2023-6915 - ida: Fix crash in ida_free when the bitmap is empty * Focal update: v5.4.265 upstream stable release (LP: #2051644) - afs: Fix refcount underflow from error handling race - net: ipv6: support reporting otherwise unknown prefix flags in RTM_NEWPREFIX - qca_debug: Prevent crash on TX ring changes - qca_debug: Fix ethtool -G iface tx behavior - qca_spi: Fix reset behavior - atm: solos-pci: Fix potential deadlock on _queue_lock - atm: solos-pci: Fix potential deadlock on _queue_lock - atm: Fix Use-After-Free in do_vcc_ioctl - qed: Fix a potential use-after-free in qed_cxt_tables_alloc - net: Remove acked SYN flag from packet in the transmit queue correctly - sign-file: Fix incorrect return values check - vsock/virtio: Fix unsigned integer wrap around in virtio_transport_has_space() - net: stmmac: use dev_err_probe() for reporting mdio bus registration failure - net: stmmac: Handle disabled MDIO busses from devicetree - cred: switch to using atomic_long_t - ALSA: hda/hdmi: add force-connect quirks for ASUSTeK Z170 variants - usb: aqc111: check packet for fixup for true limit - blk-throttle: fix lockdep warning of "cgroup_mutex or RCU read lock required!" - bcache: avoid oversize memory allocation by small stripe_size - bcache: add code comments for bch_btree_node_get() and __bch_btree_node_alloc() - bcache: avoid NULL checking to c->root in run_cache_set() - platform/x86: intel_telemetry: Fix kernel doc descriptions - HID: add ALWAYS_POLL quirk for Apple kb - HID: hid-asus: reset the backlight brightness level on resume - HID: multitouch: Add quirk for HONOR GLO-GXXX touchpad - asm-generic: qspinlock: fix queued_spin_value_unlocked() implementation - net: usb: qmi_wwan: claim interface 4 for ZTE MF290 - HID: hid-asus: add const to read-only outgoing usb buffer - soundwire: stream: fix NULL pointer dereference for multi_link - ext4: prevent the normalized size from exceeding EXT_MAX_BLOCKS - arm64: mm: Always make sw-dirty PTEs hw-dirty in pte_modify - team: Fix use-after-free when an option instance allocation fails - ring-buffer: Fix memory leak of free page - mmc: block: Be sure to wait while busy in CQE error recovery - powerpc/ftrace: Create a dummy stackframe to fix stack unwind - powerpc/ftrace: Fix stack teardown in ftrace_no_trace - Linux 5.4.265 * Focal update: v5.4.264 upstream stable release (LP: #2049935) - hrtimers: Push pending hrtimers away from outgoing CPU earlier - netfilter: ipset: fix race condition between swap/destroy and kernel side add/del/test - tg3: Move the [rt]x_dropped counters to tg3_napi - tg3: Increment tx_dropped in tg3_tso_bug() - kconfig: fix memory leak from range properties - drm/amdgpu: correct chunk_ptr to a pointer to chunk. - of: base: Add of_get_cpu_state_node() to get idle states for a CPU node - ACPI/IORT: Make iort_get_device_domain IRQ domain agnostic - ACPI/IORT: Make iort_msi_map_rid() PCI agnostic - of/iommu: Make of_map_rid() PCI agnostic - of/irq: make of_msi_map_get_device_domain() bus agnostic - of/irq: Make of_msi_map_rid() PCI bus agnostic - of: base: Fix some formatting issues and provide missing descriptions - of: Fix kerneldoc output formatting - of: Add missing 'Return' section in kerneldoc comments - of: dynamic: Fix of_reconfig_get_state_change() return value documentation - ipv6: fix potential NULL deref in fib6_add() - hv_netvsc: rndis_filter needs to select NLS - net: arcnet: Fix RESET flag handling - net: arcnet: com20020 fix error handling - arcnet: restoring support for multiple Sohard Arcnet cards - ipv4: ip_gre: Avoid skb_pull() failure in ipgre_xmit() - net: hns: fix fake link up on xge port - netfilter: xt_owner: Fix for unsafe access of sk->sk_socket - tcp: do not accept ACK of bytes we never sent - bpf: sockmap, updating the sg structure should also update curr - RDMA/bnxt_re: Correct module description string - hwmon: (acpi_power_meter) Fix 4.29 MW bug - ASoC: wm_adsp: fix memleak in wm_adsp_buffer_populate - tracing: Fix a warning when allocating buffered events fails - scsi: be2iscsi: Fix a memleak in beiscsi_init_wrb_handle() - ARM: imx: Check return value of devm_kasprintf in imx_mmdc_perf_init - ARM: dts: imx: make gpt node name generic - ARM: dts: imx7: Declare timers compatible with fsl,imx6dl-gpt - ALSA: pcm: fix
[Kernel-packages] [Bug 2049024] Re: Focal update: v5.4.260 upstream stable release
This bug was fixed in the package linux - 5.4.0-173.191 --- linux (5.4.0-173.191) focal; urgency=medium * focal/linux: 5.4.0-173.191 -proposed tracker (LP: #2052135) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2024.02.05) * CVE-2023-0340 - vhost: use kzalloc() instead of kmalloc() followed by memset() * CVE-2023-6915 - ida: Fix crash in ida_free when the bitmap is empty * Focal update: v5.4.265 upstream stable release (LP: #2051644) - afs: Fix refcount underflow from error handling race - net: ipv6: support reporting otherwise unknown prefix flags in RTM_NEWPREFIX - qca_debug: Prevent crash on TX ring changes - qca_debug: Fix ethtool -G iface tx behavior - qca_spi: Fix reset behavior - atm: solos-pci: Fix potential deadlock on _queue_lock - atm: solos-pci: Fix potential deadlock on _queue_lock - atm: Fix Use-After-Free in do_vcc_ioctl - qed: Fix a potential use-after-free in qed_cxt_tables_alloc - net: Remove acked SYN flag from packet in the transmit queue correctly - sign-file: Fix incorrect return values check - vsock/virtio: Fix unsigned integer wrap around in virtio_transport_has_space() - net: stmmac: use dev_err_probe() for reporting mdio bus registration failure - net: stmmac: Handle disabled MDIO busses from devicetree - cred: switch to using atomic_long_t - ALSA: hda/hdmi: add force-connect quirks for ASUSTeK Z170 variants - usb: aqc111: check packet for fixup for true limit - blk-throttle: fix lockdep warning of "cgroup_mutex or RCU read lock required!" - bcache: avoid oversize memory allocation by small stripe_size - bcache: add code comments for bch_btree_node_get() and __bch_btree_node_alloc() - bcache: avoid NULL checking to c->root in run_cache_set() - platform/x86: intel_telemetry: Fix kernel doc descriptions - HID: add ALWAYS_POLL quirk for Apple kb - HID: hid-asus: reset the backlight brightness level on resume - HID: multitouch: Add quirk for HONOR GLO-GXXX touchpad - asm-generic: qspinlock: fix queued_spin_value_unlocked() implementation - net: usb: qmi_wwan: claim interface 4 for ZTE MF290 - HID: hid-asus: add const to read-only outgoing usb buffer - soundwire: stream: fix NULL pointer dereference for multi_link - ext4: prevent the normalized size from exceeding EXT_MAX_BLOCKS - arm64: mm: Always make sw-dirty PTEs hw-dirty in pte_modify - team: Fix use-after-free when an option instance allocation fails - ring-buffer: Fix memory leak of free page - mmc: block: Be sure to wait while busy in CQE error recovery - powerpc/ftrace: Create a dummy stackframe to fix stack unwind - powerpc/ftrace: Fix stack teardown in ftrace_no_trace - Linux 5.4.265 * Focal update: v5.4.264 upstream stable release (LP: #2049935) - hrtimers: Push pending hrtimers away from outgoing CPU earlier - netfilter: ipset: fix race condition between swap/destroy and kernel side add/del/test - tg3: Move the [rt]x_dropped counters to tg3_napi - tg3: Increment tx_dropped in tg3_tso_bug() - kconfig: fix memory leak from range properties - drm/amdgpu: correct chunk_ptr to a pointer to chunk. - of: base: Add of_get_cpu_state_node() to get idle states for a CPU node - ACPI/IORT: Make iort_get_device_domain IRQ domain agnostic - ACPI/IORT: Make iort_msi_map_rid() PCI agnostic - of/iommu: Make of_map_rid() PCI agnostic - of/irq: make of_msi_map_get_device_domain() bus agnostic - of/irq: Make of_msi_map_rid() PCI bus agnostic - of: base: Fix some formatting issues and provide missing descriptions - of: Fix kerneldoc output formatting - of: Add missing 'Return' section in kerneldoc comments - of: dynamic: Fix of_reconfig_get_state_change() return value documentation - ipv6: fix potential NULL deref in fib6_add() - hv_netvsc: rndis_filter needs to select NLS - net: arcnet: Fix RESET flag handling - net: arcnet: com20020 fix error handling - arcnet: restoring support for multiple Sohard Arcnet cards - ipv4: ip_gre: Avoid skb_pull() failure in ipgre_xmit() - net: hns: fix fake link up on xge port - netfilter: xt_owner: Fix for unsafe access of sk->sk_socket - tcp: do not accept ACK of bytes we never sent - bpf: sockmap, updating the sg structure should also update curr - RDMA/bnxt_re: Correct module description string - hwmon: (acpi_power_meter) Fix 4.29 MW bug - ASoC: wm_adsp: fix memleak in wm_adsp_buffer_populate - tracing: Fix a warning when allocating buffered events fails - scsi: be2iscsi: Fix a memleak in beiscsi_init_wrb_handle() - ARM: imx: Check return value of devm_kasprintf in imx_mmdc_perf_init - ARM: dts: imx: make gpt node name generic - ARM: dts: imx7: Declare timers compatible with fsl,imx6dl-gpt - ALSA: pcm: fix
[Kernel-packages] [Bug 2049069] Re: Focal update: v5.4.262 upstream stable release
This bug was fixed in the package linux - 5.4.0-173.191 --- linux (5.4.0-173.191) focal; urgency=medium * focal/linux: 5.4.0-173.191 -proposed tracker (LP: #2052135) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2024.02.05) * CVE-2023-0340 - vhost: use kzalloc() instead of kmalloc() followed by memset() * CVE-2023-6915 - ida: Fix crash in ida_free when the bitmap is empty * Focal update: v5.4.265 upstream stable release (LP: #2051644) - afs: Fix refcount underflow from error handling race - net: ipv6: support reporting otherwise unknown prefix flags in RTM_NEWPREFIX - qca_debug: Prevent crash on TX ring changes - qca_debug: Fix ethtool -G iface tx behavior - qca_spi: Fix reset behavior - atm: solos-pci: Fix potential deadlock on _queue_lock - atm: solos-pci: Fix potential deadlock on _queue_lock - atm: Fix Use-After-Free in do_vcc_ioctl - qed: Fix a potential use-after-free in qed_cxt_tables_alloc - net: Remove acked SYN flag from packet in the transmit queue correctly - sign-file: Fix incorrect return values check - vsock/virtio: Fix unsigned integer wrap around in virtio_transport_has_space() - net: stmmac: use dev_err_probe() for reporting mdio bus registration failure - net: stmmac: Handle disabled MDIO busses from devicetree - cred: switch to using atomic_long_t - ALSA: hda/hdmi: add force-connect quirks for ASUSTeK Z170 variants - usb: aqc111: check packet for fixup for true limit - blk-throttle: fix lockdep warning of "cgroup_mutex or RCU read lock required!" - bcache: avoid oversize memory allocation by small stripe_size - bcache: add code comments for bch_btree_node_get() and __bch_btree_node_alloc() - bcache: avoid NULL checking to c->root in run_cache_set() - platform/x86: intel_telemetry: Fix kernel doc descriptions - HID: add ALWAYS_POLL quirk for Apple kb - HID: hid-asus: reset the backlight brightness level on resume - HID: multitouch: Add quirk for HONOR GLO-GXXX touchpad - asm-generic: qspinlock: fix queued_spin_value_unlocked() implementation - net: usb: qmi_wwan: claim interface 4 for ZTE MF290 - HID: hid-asus: add const to read-only outgoing usb buffer - soundwire: stream: fix NULL pointer dereference for multi_link - ext4: prevent the normalized size from exceeding EXT_MAX_BLOCKS - arm64: mm: Always make sw-dirty PTEs hw-dirty in pte_modify - team: Fix use-after-free when an option instance allocation fails - ring-buffer: Fix memory leak of free page - mmc: block: Be sure to wait while busy in CQE error recovery - powerpc/ftrace: Create a dummy stackframe to fix stack unwind - powerpc/ftrace: Fix stack teardown in ftrace_no_trace - Linux 5.4.265 * Focal update: v5.4.264 upstream stable release (LP: #2049935) - hrtimers: Push pending hrtimers away from outgoing CPU earlier - netfilter: ipset: fix race condition between swap/destroy and kernel side add/del/test - tg3: Move the [rt]x_dropped counters to tg3_napi - tg3: Increment tx_dropped in tg3_tso_bug() - kconfig: fix memory leak from range properties - drm/amdgpu: correct chunk_ptr to a pointer to chunk. - of: base: Add of_get_cpu_state_node() to get idle states for a CPU node - ACPI/IORT: Make iort_get_device_domain IRQ domain agnostic - ACPI/IORT: Make iort_msi_map_rid() PCI agnostic - of/iommu: Make of_map_rid() PCI agnostic - of/irq: make of_msi_map_get_device_domain() bus agnostic - of/irq: Make of_msi_map_rid() PCI bus agnostic - of: base: Fix some formatting issues and provide missing descriptions - of: Fix kerneldoc output formatting - of: Add missing 'Return' section in kerneldoc comments - of: dynamic: Fix of_reconfig_get_state_change() return value documentation - ipv6: fix potential NULL deref in fib6_add() - hv_netvsc: rndis_filter needs to select NLS - net: arcnet: Fix RESET flag handling - net: arcnet: com20020 fix error handling - arcnet: restoring support for multiple Sohard Arcnet cards - ipv4: ip_gre: Avoid skb_pull() failure in ipgre_xmit() - net: hns: fix fake link up on xge port - netfilter: xt_owner: Fix for unsafe access of sk->sk_socket - tcp: do not accept ACK of bytes we never sent - bpf: sockmap, updating the sg structure should also update curr - RDMA/bnxt_re: Correct module description string - hwmon: (acpi_power_meter) Fix 4.29 MW bug - ASoC: wm_adsp: fix memleak in wm_adsp_buffer_populate - tracing: Fix a warning when allocating buffered events fails - scsi: be2iscsi: Fix a memleak in beiscsi_init_wrb_handle() - ARM: imx: Check return value of devm_kasprintf in imx_mmdc_perf_init - ARM: dts: imx: make gpt node name generic - ARM: dts: imx7: Declare timers compatible with fsl,imx6dl-gpt - ALSA: pcm: fix
[Kernel-packages] [Bug 2051644] Re: Focal update: v5.4.265 upstream stable release
This bug was fixed in the package linux - 5.4.0-173.191 --- linux (5.4.0-173.191) focal; urgency=medium * focal/linux: 5.4.0-173.191 -proposed tracker (LP: #2052135) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2024.02.05) * CVE-2023-0340 - vhost: use kzalloc() instead of kmalloc() followed by memset() * CVE-2023-6915 - ida: Fix crash in ida_free when the bitmap is empty * Focal update: v5.4.265 upstream stable release (LP: #2051644) - afs: Fix refcount underflow from error handling race - net: ipv6: support reporting otherwise unknown prefix flags in RTM_NEWPREFIX - qca_debug: Prevent crash on TX ring changes - qca_debug: Fix ethtool -G iface tx behavior - qca_spi: Fix reset behavior - atm: solos-pci: Fix potential deadlock on _queue_lock - atm: solos-pci: Fix potential deadlock on _queue_lock - atm: Fix Use-After-Free in do_vcc_ioctl - qed: Fix a potential use-after-free in qed_cxt_tables_alloc - net: Remove acked SYN flag from packet in the transmit queue correctly - sign-file: Fix incorrect return values check - vsock/virtio: Fix unsigned integer wrap around in virtio_transport_has_space() - net: stmmac: use dev_err_probe() for reporting mdio bus registration failure - net: stmmac: Handle disabled MDIO busses from devicetree - cred: switch to using atomic_long_t - ALSA: hda/hdmi: add force-connect quirks for ASUSTeK Z170 variants - usb: aqc111: check packet for fixup for true limit - blk-throttle: fix lockdep warning of "cgroup_mutex or RCU read lock required!" - bcache: avoid oversize memory allocation by small stripe_size - bcache: add code comments for bch_btree_node_get() and __bch_btree_node_alloc() - bcache: avoid NULL checking to c->root in run_cache_set() - platform/x86: intel_telemetry: Fix kernel doc descriptions - HID: add ALWAYS_POLL quirk for Apple kb - HID: hid-asus: reset the backlight brightness level on resume - HID: multitouch: Add quirk for HONOR GLO-GXXX touchpad - asm-generic: qspinlock: fix queued_spin_value_unlocked() implementation - net: usb: qmi_wwan: claim interface 4 for ZTE MF290 - HID: hid-asus: add const to read-only outgoing usb buffer - soundwire: stream: fix NULL pointer dereference for multi_link - ext4: prevent the normalized size from exceeding EXT_MAX_BLOCKS - arm64: mm: Always make sw-dirty PTEs hw-dirty in pte_modify - team: Fix use-after-free when an option instance allocation fails - ring-buffer: Fix memory leak of free page - mmc: block: Be sure to wait while busy in CQE error recovery - powerpc/ftrace: Create a dummy stackframe to fix stack unwind - powerpc/ftrace: Fix stack teardown in ftrace_no_trace - Linux 5.4.265 * Focal update: v5.4.264 upstream stable release (LP: #2049935) - hrtimers: Push pending hrtimers away from outgoing CPU earlier - netfilter: ipset: fix race condition between swap/destroy and kernel side add/del/test - tg3: Move the [rt]x_dropped counters to tg3_napi - tg3: Increment tx_dropped in tg3_tso_bug() - kconfig: fix memory leak from range properties - drm/amdgpu: correct chunk_ptr to a pointer to chunk. - of: base: Add of_get_cpu_state_node() to get idle states for a CPU node - ACPI/IORT: Make iort_get_device_domain IRQ domain agnostic - ACPI/IORT: Make iort_msi_map_rid() PCI agnostic - of/iommu: Make of_map_rid() PCI agnostic - of/irq: make of_msi_map_get_device_domain() bus agnostic - of/irq: Make of_msi_map_rid() PCI bus agnostic - of: base: Fix some formatting issues and provide missing descriptions - of: Fix kerneldoc output formatting - of: Add missing 'Return' section in kerneldoc comments - of: dynamic: Fix of_reconfig_get_state_change() return value documentation - ipv6: fix potential NULL deref in fib6_add() - hv_netvsc: rndis_filter needs to select NLS - net: arcnet: Fix RESET flag handling - net: arcnet: com20020 fix error handling - arcnet: restoring support for multiple Sohard Arcnet cards - ipv4: ip_gre: Avoid skb_pull() failure in ipgre_xmit() - net: hns: fix fake link up on xge port - netfilter: xt_owner: Fix for unsafe access of sk->sk_socket - tcp: do not accept ACK of bytes we never sent - bpf: sockmap, updating the sg structure should also update curr - RDMA/bnxt_re: Correct module description string - hwmon: (acpi_power_meter) Fix 4.29 MW bug - ASoC: wm_adsp: fix memleak in wm_adsp_buffer_populate - tracing: Fix a warning when allocating buffered events fails - scsi: be2iscsi: Fix a memleak in beiscsi_init_wrb_handle() - ARM: imx: Check return value of devm_kasprintf in imx_mmdc_perf_init - ARM: dts: imx: make gpt node name generic - ARM: dts: imx7: Declare timers compatible with fsl,imx6dl-gpt - ALSA: pcm: fix
[Kernel-packages] [Bug 2049084] Re: Focal update: v5.4.263 upstream stable release
This bug was fixed in the package linux - 5.4.0-173.191 --- linux (5.4.0-173.191) focal; urgency=medium * focal/linux: 5.4.0-173.191 -proposed tracker (LP: #2052135) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2024.02.05) * CVE-2023-0340 - vhost: use kzalloc() instead of kmalloc() followed by memset() * CVE-2023-6915 - ida: Fix crash in ida_free when the bitmap is empty * Focal update: v5.4.265 upstream stable release (LP: #2051644) - afs: Fix refcount underflow from error handling race - net: ipv6: support reporting otherwise unknown prefix flags in RTM_NEWPREFIX - qca_debug: Prevent crash on TX ring changes - qca_debug: Fix ethtool -G iface tx behavior - qca_spi: Fix reset behavior - atm: solos-pci: Fix potential deadlock on _queue_lock - atm: solos-pci: Fix potential deadlock on _queue_lock - atm: Fix Use-After-Free in do_vcc_ioctl - qed: Fix a potential use-after-free in qed_cxt_tables_alloc - net: Remove acked SYN flag from packet in the transmit queue correctly - sign-file: Fix incorrect return values check - vsock/virtio: Fix unsigned integer wrap around in virtio_transport_has_space() - net: stmmac: use dev_err_probe() for reporting mdio bus registration failure - net: stmmac: Handle disabled MDIO busses from devicetree - cred: switch to using atomic_long_t - ALSA: hda/hdmi: add force-connect quirks for ASUSTeK Z170 variants - usb: aqc111: check packet for fixup for true limit - blk-throttle: fix lockdep warning of "cgroup_mutex or RCU read lock required!" - bcache: avoid oversize memory allocation by small stripe_size - bcache: add code comments for bch_btree_node_get() and __bch_btree_node_alloc() - bcache: avoid NULL checking to c->root in run_cache_set() - platform/x86: intel_telemetry: Fix kernel doc descriptions - HID: add ALWAYS_POLL quirk for Apple kb - HID: hid-asus: reset the backlight brightness level on resume - HID: multitouch: Add quirk for HONOR GLO-GXXX touchpad - asm-generic: qspinlock: fix queued_spin_value_unlocked() implementation - net: usb: qmi_wwan: claim interface 4 for ZTE MF290 - HID: hid-asus: add const to read-only outgoing usb buffer - soundwire: stream: fix NULL pointer dereference for multi_link - ext4: prevent the normalized size from exceeding EXT_MAX_BLOCKS - arm64: mm: Always make sw-dirty PTEs hw-dirty in pte_modify - team: Fix use-after-free when an option instance allocation fails - ring-buffer: Fix memory leak of free page - mmc: block: Be sure to wait while busy in CQE error recovery - powerpc/ftrace: Create a dummy stackframe to fix stack unwind - powerpc/ftrace: Fix stack teardown in ftrace_no_trace - Linux 5.4.265 * Focal update: v5.4.264 upstream stable release (LP: #2049935) - hrtimers: Push pending hrtimers away from outgoing CPU earlier - netfilter: ipset: fix race condition between swap/destroy and kernel side add/del/test - tg3: Move the [rt]x_dropped counters to tg3_napi - tg3: Increment tx_dropped in tg3_tso_bug() - kconfig: fix memory leak from range properties - drm/amdgpu: correct chunk_ptr to a pointer to chunk. - of: base: Add of_get_cpu_state_node() to get idle states for a CPU node - ACPI/IORT: Make iort_get_device_domain IRQ domain agnostic - ACPI/IORT: Make iort_msi_map_rid() PCI agnostic - of/iommu: Make of_map_rid() PCI agnostic - of/irq: make of_msi_map_get_device_domain() bus agnostic - of/irq: Make of_msi_map_rid() PCI bus agnostic - of: base: Fix some formatting issues and provide missing descriptions - of: Fix kerneldoc output formatting - of: Add missing 'Return' section in kerneldoc comments - of: dynamic: Fix of_reconfig_get_state_change() return value documentation - ipv6: fix potential NULL deref in fib6_add() - hv_netvsc: rndis_filter needs to select NLS - net: arcnet: Fix RESET flag handling - net: arcnet: com20020 fix error handling - arcnet: restoring support for multiple Sohard Arcnet cards - ipv4: ip_gre: Avoid skb_pull() failure in ipgre_xmit() - net: hns: fix fake link up on xge port - netfilter: xt_owner: Fix for unsafe access of sk->sk_socket - tcp: do not accept ACK of bytes we never sent - bpf: sockmap, updating the sg structure should also update curr - RDMA/bnxt_re: Correct module description string - hwmon: (acpi_power_meter) Fix 4.29 MW bug - ASoC: wm_adsp: fix memleak in wm_adsp_buffer_populate - tracing: Fix a warning when allocating buffered events fails - scsi: be2iscsi: Fix a memleak in beiscsi_init_wrb_handle() - ARM: imx: Check return value of devm_kasprintf in imx_mmdc_perf_init - ARM: dts: imx: make gpt node name generic - ARM: dts: imx7: Declare timers compatible with fsl,imx6dl-gpt - ALSA: pcm: fix
[Kernel-packages] [Bug 2049935] Re: Focal update: v5.4.264 upstream stable release
This bug was fixed in the package linux - 5.4.0-173.191 --- linux (5.4.0-173.191) focal; urgency=medium * focal/linux: 5.4.0-173.191 -proposed tracker (LP: #2052135) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2024.02.05) * CVE-2023-0340 - vhost: use kzalloc() instead of kmalloc() followed by memset() * CVE-2023-6915 - ida: Fix crash in ida_free when the bitmap is empty * Focal update: v5.4.265 upstream stable release (LP: #2051644) - afs: Fix refcount underflow from error handling race - net: ipv6: support reporting otherwise unknown prefix flags in RTM_NEWPREFIX - qca_debug: Prevent crash on TX ring changes - qca_debug: Fix ethtool -G iface tx behavior - qca_spi: Fix reset behavior - atm: solos-pci: Fix potential deadlock on _queue_lock - atm: solos-pci: Fix potential deadlock on _queue_lock - atm: Fix Use-After-Free in do_vcc_ioctl - qed: Fix a potential use-after-free in qed_cxt_tables_alloc - net: Remove acked SYN flag from packet in the transmit queue correctly - sign-file: Fix incorrect return values check - vsock/virtio: Fix unsigned integer wrap around in virtio_transport_has_space() - net: stmmac: use dev_err_probe() for reporting mdio bus registration failure - net: stmmac: Handle disabled MDIO busses from devicetree - cred: switch to using atomic_long_t - ALSA: hda/hdmi: add force-connect quirks for ASUSTeK Z170 variants - usb: aqc111: check packet for fixup for true limit - blk-throttle: fix lockdep warning of "cgroup_mutex or RCU read lock required!" - bcache: avoid oversize memory allocation by small stripe_size - bcache: add code comments for bch_btree_node_get() and __bch_btree_node_alloc() - bcache: avoid NULL checking to c->root in run_cache_set() - platform/x86: intel_telemetry: Fix kernel doc descriptions - HID: add ALWAYS_POLL quirk for Apple kb - HID: hid-asus: reset the backlight brightness level on resume - HID: multitouch: Add quirk for HONOR GLO-GXXX touchpad - asm-generic: qspinlock: fix queued_spin_value_unlocked() implementation - net: usb: qmi_wwan: claim interface 4 for ZTE MF290 - HID: hid-asus: add const to read-only outgoing usb buffer - soundwire: stream: fix NULL pointer dereference for multi_link - ext4: prevent the normalized size from exceeding EXT_MAX_BLOCKS - arm64: mm: Always make sw-dirty PTEs hw-dirty in pte_modify - team: Fix use-after-free when an option instance allocation fails - ring-buffer: Fix memory leak of free page - mmc: block: Be sure to wait while busy in CQE error recovery - powerpc/ftrace: Create a dummy stackframe to fix stack unwind - powerpc/ftrace: Fix stack teardown in ftrace_no_trace - Linux 5.4.265 * Focal update: v5.4.264 upstream stable release (LP: #2049935) - hrtimers: Push pending hrtimers away from outgoing CPU earlier - netfilter: ipset: fix race condition between swap/destroy and kernel side add/del/test - tg3: Move the [rt]x_dropped counters to tg3_napi - tg3: Increment tx_dropped in tg3_tso_bug() - kconfig: fix memory leak from range properties - drm/amdgpu: correct chunk_ptr to a pointer to chunk. - of: base: Add of_get_cpu_state_node() to get idle states for a CPU node - ACPI/IORT: Make iort_get_device_domain IRQ domain agnostic - ACPI/IORT: Make iort_msi_map_rid() PCI agnostic - of/iommu: Make of_map_rid() PCI agnostic - of/irq: make of_msi_map_get_device_domain() bus agnostic - of/irq: Make of_msi_map_rid() PCI bus agnostic - of: base: Fix some formatting issues and provide missing descriptions - of: Fix kerneldoc output formatting - of: Add missing 'Return' section in kerneldoc comments - of: dynamic: Fix of_reconfig_get_state_change() return value documentation - ipv6: fix potential NULL deref in fib6_add() - hv_netvsc: rndis_filter needs to select NLS - net: arcnet: Fix RESET flag handling - net: arcnet: com20020 fix error handling - arcnet: restoring support for multiple Sohard Arcnet cards - ipv4: ip_gre: Avoid skb_pull() failure in ipgre_xmit() - net: hns: fix fake link up on xge port - netfilter: xt_owner: Fix for unsafe access of sk->sk_socket - tcp: do not accept ACK of bytes we never sent - bpf: sockmap, updating the sg structure should also update curr - RDMA/bnxt_re: Correct module description string - hwmon: (acpi_power_meter) Fix 4.29 MW bug - ASoC: wm_adsp: fix memleak in wm_adsp_buffer_populate - tracing: Fix a warning when allocating buffered events fails - scsi: be2iscsi: Fix a memleak in beiscsi_init_wrb_handle() - ARM: imx: Check return value of devm_kasprintf in imx_mmdc_perf_init - ARM: dts: imx: make gpt node name generic - ARM: dts: imx7: Declare timers compatible with fsl,imx6dl-gpt - ALSA: pcm: fix
[Kernel-packages] [Bug 1902519] Re: [nvidia] KDE shows bad pixels after hibernate
This bug is very old, if it is still an issue please update the bug with information from a supported release. ** Changed in: kwin (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1902519 Title: [nvidia] KDE shows bad pixels after hibernate Status in kwin package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Opinion Bug description: After hibernation to disk kde shows bad pixels on home screen (look at attached screenshot) sometimes there are also graphics related bugs in other applications when I logout and login again or I do a reboot it works like before maybe it has something to do with the nvidia graphics card? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Nov 2 13:03:10 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-52-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 630 [1558:850a] Subsystem: CLEVO/KAPOK Computer GP107M [GeForce GTX 1050 Mobile] [1558:850a] MachineType: XMG N85_N87,HJ,HJ1,HK1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=UUID=ef695d35-e2d0-422a-bb31-ef1dec2df0e0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.19 dmi.board.asset.tag: Tag 12345 dmi.board.name: N85_N87,HJ,HJ1,HK1 dmi.board.vendor: XMG dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: XMG dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.19:bd12/02/2017:svnXMG:pnN85_N87,HJ,HJ1,HK1:pvrNotApplicable:rvnXMG:rnN85_N87,HJ,HJ1,HK1:rvrNotApplicable:cvnXMG:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N85_N87,HJ,HJ1,HK1 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: XMG version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1902519/+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 2052961] Re: Error: OCI runtime error: crun: chmod : Operation not supported
** Package changed: crun (Ubuntu) => linux-meta-hwe-6.5 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2052961 Title: Error: OCI runtime error: crun: chmod : Operation not supported Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Bug description: There appears to be a regression due to a "change in the kernel" in which, as of "commit 5d1f903f75a80daa4dfb3d84e114ec8ecbf29956 in the kernel, present in a release since Linux 6.6 doesn't allow anymore to change the mode of a symlink, so just ignore the failure." Quote source: https://github.com/containers/crun/pull/1309#issue-1908555328 A fix for crun was committed as of v1.9.1, and I believe should be backported: https://github.com/containers/crun/commit/be16ee75ff8574698250352302e9d5496d888d69 I am attaching the apt/history.log file, which I believe reveals the kernel update that happened since February 8th that triggered the regression. This has been reproducible for me by using podman in combination with the "kind" tool (https://github.com/kubernetes- sigs/kind/releases/tag/v0.21.0 in this case) to attempt to start a Kubernetes cluster within a container. By running "kind create cluster" it is using the container image "kindest/node:v1.29.1" which triggers the error: "Error: OCI runtime error: crun: chmod `run/shm`: Operation not supported" ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: crun 1.8.5-1 ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 12 12:07:09 2024 InstallationDate: Installed on 2022-09-19 (511 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=screen-256color XDG_RUNTIME_DIR= SourcePackage: crun UpgradeStatus: Upgraded to mantic on 2023-11-07 (98 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2052961/+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 2052961] [NEW] Error: OCI runtime error: crun: chmod : Operation not supported
You have been subscribed to a public bug: There appears to be a regression due to a "change in the kernel" in which, as of "commit 5d1f903f75a80daa4dfb3d84e114ec8ecbf29956 in the kernel, present in a release since Linux 6.6 doesn't allow anymore to change the mode of a symlink, so just ignore the failure." Quote source: https://github.com/containers/crun/pull/1309#issue-1908555328 A fix for crun was committed as of v1.9.1, and I believe should be backported: https://github.com/containers/crun/commit/be16ee75ff8574698250352302e9d5496d888d69 I am attaching the apt/history.log file, which I believe reveals the kernel update that happened since February 8th that triggered the regression. This has been reproducible for me by using podman in combination with the "kind" tool (https://github.com/kubernetes- sigs/kind/releases/tag/v0.21.0 in this case) to attempt to start a Kubernetes cluster within a container. By running "kind create cluster" it is using the container image "kindest/node:v1.29.1" which triggers the error: "Error: OCI runtime error: crun: chmod `run/shm`: Operation not supported" ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: crun 1.8.5-1 ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 12 12:07:09 2024 InstallationDate: Installed on 2022-09-19 (511 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=screen-256color XDG_RUNTIME_DIR= SourcePackage: crun UpgradeStatus: Upgraded to mantic on 2023-11-07 (98 days ago) ** Affects: linux-meta-hwe-6.5 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug mantic patch wayland-session -- Error: OCI runtime error: crun: chmod : Operation not supported https://bugs.launchpad.net/bugs/2052961 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. -- 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 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
This bug is very old, if it is still an issue please update the bug with information from a supported release. ** Changed in: kwin (Ubuntu) Status: Confirmed => Incomplete ** No longer affects: plasma-desktop (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver Status in kwin package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: This is a well investigated bug by me. Problem: a black screen freeze occurs by suspend-resume process Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17 Kernel version: default 5.3.10 or the mainline 5.4.0rc3 xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works well This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is enabled in Plasma settings. Xrender is OK however I don't like screen tearing. On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the Gnome's compositor is enabled. (I don't know what is the default one there but I haven't disabled it) I think this is a Kwin / amdgpu driver related bug because of the differentiation. These can be fixed even in Kwin/opengl compositor not just in the amdgpu driver or in kernel. One possible solution: disable opengl compositor by suspend and re- enable it after login. Use fe.: Xrender before login / before the system restored from suspend. For Ubuntu's maintainers: Couldn't be this problem solved by a downstream solution? Maybe a proper script could be enough by resume and by suspend. There are a lot of bugs like this reported in freedesktop bugreport and the developers haven't got enough time for fix them fast enough. Syslog: Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 00 00 Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 00010002 Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 0202 RCX: 046a Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 0202 RDI: 0002 Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: R09: 94da76b2d170 Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: b7b54274b70c R12: 94da76b2d000 Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 94da758d25d0 R15: 94da270d1400 Oct 21 10:57:26 pc kernel: [ 9475.308861] FS: 7f2a1b9bea80() GS:94da87c4() knlGS: Oct 21 10:57:26 pc kernel: [ 9475.308863] CS: 0010 DS: ES: CR0: 80050033 Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 00012c11 CR4: 003406e0 Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace: Oct 21 10:57:26 pc kernel: [ 9475.308977] amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.308991] commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309000] ? commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309009] drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309115] amdgpu_dm_atomic_commit+0x95/0xa0 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309135] drm_atomic_commit+0x4a/0x50 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309144] drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309159] drm_mode_setcrtc+0x1cd/0x7a0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309234] ? amdgpu_cs_wait_ioctl+0xd6/0x150 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309249] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309262] drm_ioctl_kernel+0xae/0xf0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309276] drm_ioctl+0x234/0x3d0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309290] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309370] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309376] do_vfs_ioctl+0x407/0x670 Oct 21 10:57:26 pc kernel: [ 9475.309379] ? do_futex+0x10f/0x1e0 Oct 21 10:57:26 pc kernel: [ 9475.309382] ksys_ioctl+0x67/0x90 Oct 21 10:57:26 pc kernel: [ 9475.309384] __x64_sys_ioctl+0x1a/0x20 Oct 21 10:57:26 pc kernel: [ 9475.309388] do_syscall_64+0x57/0x190 Oct 21 10:57:26 pc kernel: [ 9475.309392]
[Kernel-packages] [Bug 2054456] Re: Possible regression: Some wireless Logitech devices fail to be detected
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: mantic -- 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/2054456 Title: Possible regression: Some wireless Logitech devices fail to be detected Status in linux package in Ubuntu: New Bug description: I'm on Ubuntu 23.10. Kernel 6.5.0-17-generic. I believe I am experiencing this bug, which appears to have been fixed once, some years ago: https://bugzilla.kernel.org/show_bug.cgi?id=208935 Here's what happens in my syslog while pairing my Logitech T650: 2024-02-20T19:29:06.503725+01:00 maccoyii kernel: [ 2426.061743] logitech-djreceiver 0003:046D:C52B.000E: device of type eQUAD step 4 DJ (0x04) connected on slot 1 2024-02-20T19:29:06.507763+01:00 maccoyii kernel: [ 2426.061917] logitech-hidpp-device 0003:046D:4101.001E: item fetching failed at offset 0/0 2024-02-20T19:29:06.507769+01:00 maccoyii kernel: [ 2426.061930] logitech-hidpp-device 0003:046D:4101.001E: hidpp_probe:parse failed 2024-02-20T19:29:06.507769+01:00 maccoyii kernel: [ 2426.061936] logitech-hidpp-device: probe of 0003:046D:4101.001E failed with error -22 Result is that the T650 touchpad doesn't work. I'm using the splendid solaar application to do the actual pairing. Funny thing is that the pairing clearly works. Solaar recognises and lists the newly connected device, with battery status and all. But Ubuntu fails to register the touchpad as an input device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054456/+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 2056303] Re: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c
buntu 6.5.0-21.21~22.04.1-generic 6.5.8 ** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+attachment/5753222/+files/version.log ** Description changed: On one Lenovo machine, using a hwe-22.04 kernel, I get several messages from UBSAN while booting. Previously, on the non-hwe kernel for Jammy, the screen went black shortly after logging in, and that doesn't seem to happen any more, so there is improvement, but it seems still something is going wrong. Attached are the dmesg (where the UBSAN errors are listed), and the output from lspci and the version. + + In the dmesg there is this line, + + [ 19.151801] kfd kfd: amdgpu: STONEY not supported in kfd + + which somewhere was indicated that it would be improved in the hwe + kernel (that's why I tried it). Apparently the issue isn't fully fixex, + but the error seems to be handled better. (Source: + https://forums.linuxmint.com/viewtopic.php?t=410244 ) -- 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/2056303 Title: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c Status in linux package in Ubuntu: New Bug description: On one Lenovo machine, using a hwe-22.04 kernel, I get several messages from UBSAN while booting. Previously, on the non-hwe kernel for Jammy, the screen went black shortly after logging in, and that doesn't seem to happen any more, so there is improvement, but it seems still something is going wrong. Attached are the dmesg (where the UBSAN errors are listed), and the output from lspci and the version. In the dmesg there is this line, [ 19.151801] kfd kfd: amdgpu: STONEY not supported in kfd which somewhere was indicated that it would be improved in the hwe kernel (that's why I tried it). Apparently the issue isn't fully fixex, but the error seems to be handled better. (Source: https://forums.linuxmint.com/viewtopic.php?t=410244 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+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 2056303] Re: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+attachment/5753221/+files/lspci-vnvn.log -- 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/2056303 Title: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c Status in linux package in Ubuntu: New Bug description: On one Lenovo machine, using a hwe-22.04 kernel, I get several messages from UBSAN while booting. Previously, on the non-hwe kernel for Jammy, the screen went black shortly after logging in, and that doesn't seem to happen any more, so there is improvement, but it seems still something is going wrong. Attached are the dmesg (where the UBSAN errors are listed), and the output from lspci and the version. In the dmesg there is this line, [ 19.151801] kfd kfd: amdgpu: STONEY not supported in kfd which somewhere was indicated that it would be improved in the hwe kernel (that's why I tried it). Apparently the issue isn't fully fixex, but the error seems to be handled better. (Source: https://forums.linuxmint.com/viewtopic.php?t=410244 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+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 2056303] [NEW] several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c
Public bug reported: On one Lenovo machine, using a hwe-22.04 kernel, I get several messages from UBSAN while booting. Previously, on the non-hwe kernel for Jammy, the screen went black shortly after logging in, and that doesn't seem to happen any more, so there is improvement, but it seems still something is going wrong. Attached are the dmesg (where the UBSAN errors are listed), and the output from lspci and the version. In the dmesg there is this line, [ 19.151801] kfd kfd: amdgpu: STONEY not supported in kfd which somewhere was indicated that it would be improved in the hwe kernel (that's why I tried it). Apparently the issue isn't fully fixex, but the error seems to be handled better. (Source: https://forums.linuxmint.com/viewtopic.php?t=410244 ) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/2056303/+attachment/5753220/+files/dmesg -- 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/2056303 Title: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c Status in linux package in Ubuntu: New Bug description: On one Lenovo machine, using a hwe-22.04 kernel, I get several messages from UBSAN while booting. Previously, on the non-hwe kernel for Jammy, the screen went black shortly after logging in, and that doesn't seem to happen any more, so there is improvement, but it seems still something is going wrong. Attached are the dmesg (where the UBSAN errors are listed), and the output from lspci and the version. In the dmesg there is this line, [ 19.151801] kfd kfd: amdgpu: STONEY not supported in kfd which somewhere was indicated that it would be improved in the hwe kernel (that's why I tried it). Apparently the issue isn't fully fixex, but the error seems to be handled better. (Source: https://forums.linuxmint.com/viewtopic.php?t=410244 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+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 2054456] [NEW] Possible regression: Some wireless Logitech devices fail to be detected
You have been subscribed to a public bug: I'm on Ubuntu 23.10. Kernel 6.5.0-17-generic. I believe I am experiencing this bug, which appears to have been fixed once, some years ago: https://bugzilla.kernel.org/show_bug.cgi?id=208935 Here's what happens in my syslog while pairing my Logitech T650: 2024-02-20T19:29:06.503725+01:00 maccoyii kernel: [ 2426.061743] logitech-djreceiver 0003:046D:C52B.000E: device of type eQUAD step 4 DJ (0x04) connected on slot 1 2024-02-20T19:29:06.507763+01:00 maccoyii kernel: [ 2426.061917] logitech-hidpp-device 0003:046D:4101.001E: item fetching failed at offset 0/0 2024-02-20T19:29:06.507769+01:00 maccoyii kernel: [ 2426.061930] logitech-hidpp-device 0003:046D:4101.001E: hidpp_probe:parse failed 2024-02-20T19:29:06.507769+01:00 maccoyii kernel: [ 2426.061936] logitech-hidpp-device: probe of 0003:046D:4101.001E failed with error -22 Result is that the T650 touchpad doesn't work. I'm using the splendid solaar application to do the actual pairing. Funny thing is that the pairing clearly works. Solaar recognises and lists the newly connected device, with battery status and all. But Ubuntu fails to register the touchpad as an input device. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Possible regression: Some wireless Logitech devices fail to be detected https://bugs.launchpad.net/bugs/2054456 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 2056297] [NEW] Non-flatpak Firefox-based browsers crash with kernel 6.8.0-11-generic in 24.04
Public bug reported: All details are to be found in my previous bug report [Tabs of non- flatpak Firefox (and non-flatpak Firefox-based browsers) crash in Kubuntu 24.04](https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2056190). Given that simply reverting to kernel 6.5.0-17-generic fixes the problem, the bug seems to be with the 6.8.0 kernel. Therefore I'm posting this. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Mar 6 09:49:36 2024 InstallationDate: Installed on 2023-10-04 (154 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Sony Corporation VPCSB2P9E ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=0dbb7177-a759-43f8-86d2-53e3253805d5 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-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-03-04 (2 days ago) dmi.bios.date: 11/16/2011 dmi.bios.release: 20.85 dmi.bios.vendor: INSYDE dmi.bios.version: R2085H4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 20.85 dmi.modalias: dmi:bvnINSYDE:bvrR2085H4:bd11/16/2011:br20.85:efr20.85:svnSonyCorporation:pnVPCSB2P9E:pvrC609DJQ5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:skuN/A: dmi.product.family: VAIO dmi.product.name: VPCSB2P9E dmi.product.sku: N/A dmi.product.version: C609DJQ5 dmi.sys.vendor: Sony Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- 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/2056297 Title: Non-flatpak Firefox-based browsers crash with kernel 6.8.0-11-generic in 24.04 Status in linux package in Ubuntu: New Bug description: All details are to be found in my previous bug report [Tabs of non- flatpak Firefox (and non-flatpak Firefox-based browsers) crash in Kubuntu 24.04](https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2056190). Given that simply reverting to kernel 6.5.0-17-generic fixes the problem, the bug seems to be with the 6.8.0 kernel. Therefore I'm posting this. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Mar 6 09:49:36 2024 InstallationDate: Installed on 2023-10-04 (154 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Sony Corporation VPCSB2P9E ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=0dbb7177-a759-43f8-86d2-53e3253805d5 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-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-03-04 (2 days ago) dmi.bios.date: 11/16/2011 dmi.bios.release: 20.85 dmi.bios.vendor: INSYDE dmi.bios.version: R2085H4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 20.85 dmi.modalias: dmi:bvnINSYDE:bvrR2085H4:bd11/16/2011:br20.85:efr20.85:svnSonyCorporation:pnVPCSB2P9E:pvrC609DJQ5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:skuN/A: dmi.product.family: VAIO dmi.product.name: VPCSB2P9E dmi.product.sku: N/A dmi.product.version: C609DJQ5 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 2014231] Re: gcc produces DWARF5, gdb requires DWARF4
Accidentally changed status whilst examining status list - currently unable to revert the change! ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/2014231 Title: gcc produces DWARF5, gdb requires DWARF4 Status in linux package in Ubuntu: Fix Released Bug description: On Ubuntu 22.04.2 LTS using fully updated gcc and gdb, I find that by default gcc produces DWARF5 debug files which gdb cannot read, with the following error: Dwarf Error: DW_FORM_line_strp used without required section If I add the flags `-gdwarf-4 -gstrict-dwarf` to `gcc` then it produces output which gdb can read. I would have expected the created and required versions of DWARF to match between these two programs when everything is up-to-date, within the same distro. (I found the following two issues which appear to be people also suffering from gcc newly producing DWARF5, in different contexts: https://github.com/golang/vscode-go/issues/1914 https://github.com/haikuports/haikuports/issues/4987 ; as mentioned however, the mismatch between what gcc produces and what gdb accepts seems to be a specific problem, which I suppose may be likely to break e.g. existing working debug instructions, etc.) --- Package: gcc Version: 4:11.2.0-1ubuntu1 $ gcc --version gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0 Package: gdb Version: 12.1-0ubuntu1~22.04 $ gdb --version GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1 Using default gcc output (i.e. with no flags specifying DWARF version): (gdb) add-symbol-file {...}/shimx64.efi.debug 0x0561B000 -s .data 0x05681000 add symbol table from file "{...}/shimx64.efi.debug" at .text_addr = 0x561b000 .data_addr = 0x5681000 (y or n) y Reading symbols from {...}/shimx64.efi.debug... Dwarf Error: DW_FORM_line_strp used without required section (No debugging symbols found in {...}/shimx64.efi.debug) (gdb) After adding `-gdwarf-4 -gstrict-dwarf` to gcc compile flags: (gdb) add-symbol-file {...}/shimx64.efi.debug 0x0561B000 -s .data 0x05681000 add symbol table from file "{...}/shimx64.efi.debug" at .text_addr = 0x561b000 .data_addr = 0x5681000 (y or n) y Reading symbols from {...}/shimx64.efi.debug... (gdb) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014231/+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