[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-aws-6.2/6.2.0-1009.9~22.04.2)
All autopkgtests for the newly accepted linux-restricted-modules-aws-6.2 (6.2.0-1009.9~22.04.2) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-525/525.125.06-0ubuntu0.22.04.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-aws-6.2 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028582] [NEW] package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: 无法为 './lib/firmware/qcom/sm8250/adsp.mbn' 拷贝解压的文件至 '/lib/firmware/qcom/sm8250/a
Public bug reported: E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zhangxiaohui 2429 F pulseaudio /dev/snd/controlC1: zhangxiaohui 2429 F pulseaudio CasperMD5CheckResult: unknown Date: Tue Jul 25 09:05:26 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: 无法为 './lib/firmware/qcom/sm8250/adsp.mbn' 拷贝解压的文件至 '/lib/firmware/qcom/sm8250/adsp.mbn.dpkg-new'： 未预期的文件结束或流结束 InstallationDate: Installed on 2023-06-07 (47 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) IwConfig: lono wireless extensions. enp4s0no wireless extensions. enp5s0no wireless extensions. PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-76-generic root=UUID=2bfa1021-936e-4a95-bf37-58e8c878b6bd 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. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: 无法为 './lib/firmware/qcom/sm8250/adsp.mbn' 拷贝解压的文件至 '/lib/firmware/qcom/sm8250/adsp.mbn.dpkg-new'： 未预期的文件结束或流结束 UpgradeStatus: Upgraded to jammy on 2023-06-24 (30 days ago) dmi.bios.date: 09/06/2022 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Default string dmi.board.name: X99-F8D dmi.board.vendor: HUANANZHI dmi.board.version: V2.6 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd09/06/2022:br5.11:svnHUANANZHI:pn:pvrDefaultstring:rvnHUANANZHI:rnX99-F8D:rvrV2.6:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: HUANANZHI ** Affects: linux-firmware (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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2028582 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: 无法为 './lib/firmware/qcom/sm8250/adsp.mbn' 拷贝解压的文件至 '/lib/firmware/qcom/sm8250/adsp.mbn.dpkg-new'： 未预期的文件结束或流结束 Status in linux-firmware package in Ubuntu: New Bug description: E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zhangxiaohui 2429 F pulseaudio /dev/snd/controlC1: zhangxiaohui 2429 F pulseaudio CasperMD5CheckResult: unknown Date: Tue Jul 25 09:05:26 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: 无法为 './lib/firmware/qcom/sm8250/adsp.mbn' 拷贝解压的文件至 '/lib/firmware/qcom/sm8250/adsp.mbn.dpkg-new'： 未预期的文件结束或流结束 InstallationDate: Installed on 2023-06-07 (47 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) IwConfig: lono wireless extensions. enp4s0no wireless extensions. enp5s0no wireless extensions. PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-76-generic root=UUID=2bfa1021-936e-4a95-bf37-58e8c878b6bd 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. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: 无法为 './lib/firmware/qcom/sm8250/adsp.mbn' 拷贝解压的文件至 '/lib/firmware/qcom/sm8250/adsp.mbn.dpkg-new'： 未预期的文件结束或流结束
[Kernel-packages] [Bug 2028580] Re: Lunar update: v6.2.16 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v6.2.16 upstream stable release + from git://git.kernel.org/ -v6.2.16 upstream stable release -from git://git.kernel.org/ + USB: dwc3: gadget: drop dead hibernation code + usb: dwc3: gadget: Execute gadget stop after halting the controller + crypto: ccp - Clear PSP interrupt status register before calling handler + ASoC: codecs: constify static sdw_slave_ops struct + ASoC: codecs: wcd938x: fix accessing regmap on unattached devices + mtd: spi-nor: Add a RWW flag + mtd: spi-nor: spansion: Enable JFFS2 write buffer for Infineon s28hx SEMPER flash + qcom: llcc/edac: Support polling mode for ECC handling + soc: qcom: llcc: Do not create EDAC platform device on SDM845 + mailbox: zynq: Switch to flexible array to simplify code + mailbox: zynqmp: Fix counts of child nodes + mtd: spi-nor: spansion: Enable JFFS2 write buffer for Infineon s25hx SEMPER flash + fs/ntfs3: Fix null-ptr-deref on inode->i_op in ntfs_lookup() + drm/amd/display: Ext displays with dock can't recognized after resume + KVM: x86/mmu: Avoid indirect call for get_cr3 + KVM: x86: Do not unload MMU roots when only toggling CR0.WP with TDP enabled + KVM: x86: Make use of kvm_read_cr*_bits() when testing bits + KVM: VMX: Make CR0.WP a guest owned bit + KVM: x86/mmu: Refresh CR0.WP prior to checking for emulated permission faults + RDMA/rxe: Remove rxe_alloc() + RDMA/rxe: Change rxe_dbg to rxe_dbg_dev + RDMA/rxe: Extend dbg log messages to err and info + ASoC: Intel: soc-acpi-byt: Fix "WM510205" match no longer working + scsi: qedi: Fix use after free bug in qedi_remove() + drm/amd/display: Add missing WA and MCLK validation + drm/amd/display: Return error code on DSC atomic check failure + drm/amd/display: Fixes for dcn32_clk_mgr implementation + drm/amd/display: Reset OUTBOX0 r/w pointer on DMUB reset + drm/amd/display: Do not clear GPINT register when releasing DMUB from reset + drm/amd/display: Update bounding box values for DCN321 + rxrpc: Fix potential data race in rxrpc_wait_to_be_connected() + ixgbe: Fix panic during XDP_TX with > 64 CPUs + octeonxt2-af: mcs: Fix per port bypass config + octeontx2-af: mcs: Write TCAM_DATA and TCAM_MASK registers at once + octeontx2-af: mcs: Config parser to skip 8B header + octeontx2-af: mcs: Fix MCS block interrupt + octeontx2-pf: mcs: Fix NULL pointer dereferences + octeontx2-pf: mcs: Match macsec ethertype along with DMAC + octeontx2-pf: mcs: Clear stats before freeing resource + octeontx2-pf: mcs: Fix shared counters logic + octeontx2-pf: mcs: Do not reset PN while updating secy + net/ncsi: clear Tx enable mode when handling a Config required AEN + tcp: fix skb_copy_ubufs() vs BIG TCP + net/sched: cls_api: remove block_cb from driver_list before freeing + sit: update dev->needed_headroom in ipip6_tunnel_bind_dev() + selftests: srv6: make srv6_end_dt46_l3vpn_test more robust + net: ipv6: fix skb hash for some RST packets + net: dsa: mv88e6xxx: add mv88e6321 rsvd2cpu + writeback: fix call of incorrect macro + block: Skip destroyed blkg when restart in blkg_destroy_all() + watchdog: dw_wdt: Fix the error handling path of dw_wdt_drv_probe() + RISC-V: mm: Enable huge page support to kernel_page_present() function + i2c: tegra: Fix PEC support for SMBUS block read + net/sched: act_mirred: Add carrier check + r8152: fix flow control issue of RTL8156A + r8152: fix the poor throughput for 2.5G devices + r8152: move setting r8153b_rx_agg_chg_indicate() + sfc: Fix module EEPROM reporting for QSFP modules + rxrpc: Fix hard call timeout units + rxrpc: Make it so that a waiting process can be aborted + rxrpc: Fix timeout of a call that hasn't yet been granted a channel + riscv: compat_syscall_table: Fixup compile warning + net: ethernet: mtk_eth_soc: drop generic vlan rx offload, only use DSA untagging + drm/i915/mtl: Add the missing CPU transcoder mask in intel_device_info + selftests: netfilter: fix libmnl pkg-config usage + octeontx2-af: Secure APR table update with the lock + octeontx2-af: Fix start and end bit for scan config +
[Kernel-packages] [Bug 2028580] [NEW] Lunar update: v6.2.16 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.2.16 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Lunar) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/2028580 Title: Lunar update: v6.2.16 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.2.16 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0
Here is from my fresh install of Xubuntu 22.04 LTS ** Attachment added: "dmesg and lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+attachment/5688171/+files/dmesg%20and%20lspci.txt -- 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903920] Re: Warning message about cryptsetup during boot
With today's kernel update (5.19.0-50-generic), I'm still experiencing this issue and none of the above solutions works for me. When I try to update initramfs, I get: update-initramfs: Generating /boot/initrd.img-5.19.0-50-generic Device /dev/sda2 is not a valid LUKS device. -- 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/1903920 Title: Warning message about cryptsetup during boot Status in linux package in Ubuntu: Confirmed Bug description: I have noticed that since upgrade to 20.04.1 (from 18.04), a warning message appears during boot: "cryptsetup: WARNING: Option 'size' missing in crypttab for plain dm-crypt mapping cryptswap1. Please read /usr/share/doc/cryptsetup-initramfs/README.initramfs.gz and add the correct 'size' option to your crypttab(5).". AFAICT, there is no problem however. I use ecryptfs to encrypt my home directory but I don't think it's related (since the message is related to swap). This message used to appear during updates under 18.04 but I never paid attention to it. I probably use the same setup since 16.04. Others have reported the problem (https://askubuntu.com/questions/1109463, https://medium.com/@anirudha/fixing-cryptsetup-wating-for-encrypted- source-device-swapfile-error-on-linux-boot-ubuntu-20-04-5483e0dcf9e9). From what I read: - The answers indicate to edit /etc/crypttab and add a value for size but I don't know what value to use. - It seems that before 20.04, just editing /etc/crypttab was enough but some users say that they need to manually regenerate the initramfs image after each update which is boring. I have asked the question at https://answers.launchpad.net/ubuntu/+question/693615 and @bernard010 suggested to open a bug report. I have found anything worth in dmesg though. As I said everything seems fine (boot proceeds normally, I can use the computer) but I expect that there is a way to permanently make this warning disappear. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-53-generic 5.4.0-53.59 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2322 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 23:02:47 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-06 (1405 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 2570p ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=74d77edf-b4b7-4815-865f-b7602f3396b4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-53-generic N/A linux-backports-modules-5.4.0-53-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-10-04 (38 days ago) dmi.bios.date: 02/01/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ISB Ver. F.40 dmi.board.name: 17DF dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 61.21 dmi.chassis.asset.tag: CNU3229ST9 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ISBVer.F.40:bd02/01/2013:svnHewlett-Packard:pnHPEliteBook2570p:pvrA1029C1102:rvnHewlett-Packard:rn17DF:rvrKBCVersion61.21:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 2570p dmi.product.sku: C9S65EC#ABF dmi.product.version: A1029C1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028471] Re: dmraid modules not properly loaded during installation
What installer did you use to install Ubuntu? If you provide the contents of /var/log/installer/media-info we'll be able to figure it out. -- 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/2028471 Title: dmraid modules not properly loaded during installation Status in linux package in Ubuntu: New Bug description: There are actually 2 problems with this one. First is that although Ubuntu 22 Desktop does indeed see FakeRAID cards, it does a partition probe before dmraid sets up the array. On a system with a LSI Megaraid (older card, fakeraid) card I created the RAID array in the BIOS of the card then booted the desktop install. Then ran Live. At the Live desktop at the terminal prompt /dev/mapper/ddf1_4c534920202020202055000471147111450 was visible however fdisk -l on that device showed an actual disklabel (msdos partition table) existed along with a partition #1 completely filling the disk. Executing partprobe /dev/mapper/ddf1_4c534920202020202055000471147111450 created the /dev/mapper/ddf1_4c534920202020202055000471147111450 /dev/mapper/ddf1_4c534920202020202055000471147111450p1 entries with the p1 entry lined to /dev/dm-1 So I then ran the installer and at the disk screen changed grub install to /dev/mapper/ddf1_4c534920202020202055000471147111450 instead of /dev/sda and then I installed Ubuntu on the now visible first partition However after the install completed the system attempted to boot and errored out at an initramfs prompt with: ALERT! UUID=68ca7f1a-c462-4f7c-9657-05d3ad04e4ee does not exists. Dropping to a shell! I ran the following command and got this output: dmraid -ay 165.190010] device-mapper: table: 253:0: raid: unknown target type ERROR: device-mapper target type "raid" is not in the kernel: RAID set "ddf1_4c534920202020202055000471147111450" was not activated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942260] Re: compress firmware in /lib/firmware
** Tags added: patch -- 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/1942260 Title: compress firmware in /lib/firmware Status in initramfs-tools package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware-raspi2 package in Ubuntu: Confirmed Bug description: -- initramfs-tools [Impact] * linux supports xz compressed linux-firmware which saves disk space. In focal, initramfs-tools only knows how to included uncompressed firmware files (even when kernel supports loading compressed ones). Newer releases of linux-firmware may use compressed firmware files only, in such cases it would be nice for focal's initramfs-tools to support compressed firmware files in case of partial or incomplete upgrades (i.e. linux-firmware force installed or upgraded, without newer initramfs-tools). The proposed changes to initramfs-tools are backwards and forwards compatible, they prefer to include uncompressed firmware files; and if missing, include compressed firmware files in their uncompressed form. Thus maintaining compatibility with any kernels, irrespective of compressed/uncompressed firmware inputs. [Test Plan] * Compress all files shipped by linux-firmware with xz * Rebuild initrd * Check that all the same firmware files are still included in the initramfs, in their uncompressed form as before [Where problems could occur] * This SRU is precautionary to prevent accidental installation of compressed linux-firmware from generating incorrect initramfs. It should be noted that whilst initramfs-tools would create a compatible initramfs with any kernels, pre-v5.3 kernels do not support xz compressed firmware files at runtime. Mixing this new initramfs with compressed firmwares and pre 5.3 kernels may lead to expectations of supporting compressed firmware files with them only working at initrd stage and not at runtime. [Other Info] Original bug report Some facts: - The linux kernel has supported loading xz compressed firmware since 5.3 - The size of /lib/firmware in impish is ~650Mb (and growing) - The compressed size of firmware could be ~230Mb It would be nice to install compressed firmware to save space. Here are the plans from the Fedora project: https://fedoraproject.org/wiki/Changes/CompressKernelFirmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998285] Re: 5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu
5.15.0-78-generic #85-Ubuntu
[1.440676] UBSAN: shift-out-of-bounds in
/build/linux-OC2Jcv/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32
[1.440678] shift exponent 64 is too large for 64-bit type 'long long
unsigned int'
followed by a crash as before.
--
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/1998285
Title:
5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu
Status in linux package in Ubuntu:
Confirmed
Bug description:
from dmesg
1.313665] UBSAN: shift-out-of-bounds in
/build/linux-JjvoxS/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32
[1.313668] shift exponent 64 is too large for 64-bit type 'long long
unsigned int'
there is also a crash but i don't know if it's related.
1.313671] Call Trace:
[1.313672]
[1.313673] show_stack+0x52/0x5c
[1.313676] dump_stack_lvl+0x4a/0x63
[1.313678] dump_stack+0x10/0x16
[1.313679] ubsan_epilogue+0x9/0x49
[1.313680] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
[1.313682] initialize_nocpsch.cold+0x15/0x59 [amdgpu]
[1.313841] device_queue_manager_init+0x208/0x3b0 [amdgpu]
[1.313946] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu]
[1.314079] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu]
[1.314178] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu]
[1.314323] amdgpu_device_init.cold+0x25b/0x7db [amdgpu]
[1.314463] ? do_pci_enable_device+0xdb/0x110
[1.314466] amdgpu_driver_load_kms+0x1e/0x270 [amdgpu]
[1.314556] amdgpu_pci_probe+0x1ce/0x260 [amdgpu]
[1.314642] local_pci_probe+0x48/0x90
[1.314644] pci_device_probe+0x119/0x1f0
[1.314645] really_probe+0x21f/0x420
[1.314647] __driver_probe_device+0x119/0x190
[1.314648] driver_probe_device+0x23/0xc0
[1.314650] __driver_attach+0xbd/0x1f0
[1.314651] ? __device_attach_driver+0x120/0x120
[1.314652] bus_for_each_dev+0x7c/0xd0
[1.314654] driver_attach+0x1e/0x30
[1.314655] bus_add_driver+0x148/0x220
[1.314656] driver_register+0x95/0x100
[1.314657] __pci_register_driver+0x68/0x70
[1.314659] amdgpu_init+0x7c/0x1000 [amdgpu]
[1.314747] ? 0xc0fc
[1.314748] do_one_initcall+0x46/0x1e0
[1.314750] ? kmem_cache_alloc_trace+0x19e/0x2e0
[1.314752] do_init_module+0x52/0x260
[1.314753] load_module+0xb2b/0xbc0
[1.314754] __do_sys_finit_module+0xbf/0x120
[1.314756] __x64_sys_finit_module+0x18/0x20
[1.314757] do_syscall_64+0x59/0xc0
[1.314758] ? ksys_lseek+0x85/0xc0
[1.314759] ? exit_to_user_mode_prepare+0x37/0xb0
[1.314761] ? syscall_exit_to_user_mode+0x27/0x50
[1.314762] ? __x64_sys_lseek+0x18/0x20
[1.314763] ? do_syscall_64+0x69/0xc0
[1.314764] entry_SYSCALL_64_after_hwframe+0x61/0xcb
[1.314766] RIP: 0033:0x7fef87ab8a3d
[1.314767] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48
[1.314768] RSP: 002b:7fffe67aa7c8 EFLAGS: 0246 ORIG_RAX:
0139
[1.314770] RAX: ffda RBX: 55d1d00078a0 RCX:
7fef87ab8a3d
[1.314771] RDX: RSI: 7fef87c4f441 RDI:
0018
[1.314772] RBP: 0002 R08: R09:
0002
[1.314772] R10: 0018 R11: 0246 R12:
7fef87c4f441
[1.314773] R13: 55d1d002ea30 R14: 55d1d0011600 R15:
55d1d002eb10
[1.314774]
[1.314778]
gpu is Amd r 380 tonga 4Gb.
I was adviced to try 6.0 series of kernel and I dont see the ubsan error
there but I would like to get the fixes backported 5.15 series.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarkko 1322 F pulseaudio
/dev/snd/controlC1: jarkko 1322 F pulseaudio
CasperMD5json: {
CurrentDesktop: MATE
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-09-19 (71 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
MachineType: ASUS System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1007-oem
root=UUID=62a471af-17fd-40e2-9304-b3e113e4f47f ro quiet splash
ProcVersionSignature: Ubuntu 6.0.0-1007.7-oem 6.0.3
RelatedPackageVersions:
linux-restricted-modules-6.0.0-1007-oem N/A
linux-backports-modules-6.0.0-1007-oem N/A
linux-firmware
[Kernel-packages] [Bug 1942260] Re: compress firmware in /lib/firmware
All kernels need to support reading the compressed firmware files (even after partial upgrades). See bug #2028550 for the kernel side. linux-firmware needs two patches to correctly produce compressed firmware files: * https://lore.kernel.org/linux-firmware/1addfae3b9a376ebbf39c0d05642394ebcfb9ee9.ca...@canonical.com/T/#u * https://lore.kernel.org/linux-firmware/c151f7d4837d3a07143ee5191d3f5e57bc6ded2c.ca...@canonical.com/T/#u Attached a tested debdiff that could be uploaded once following points are addressed: * support for zstd compressed firmware files in initramfs-tools (should be in 0.142ubuntu8) * support for zstd compressed firmware in all relevant kernels (see bug #2028550) * a "Breaks: initramfs-tools (<< 0.142ubuntu8~)" for the final uploaded version should be added ** Patch added: "linux-firmware_20230629.gitee91452d-0ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1942260/+attachment/5688141/+files/linux-firmware_20230629.gitee91452d-0ubuntu2.debdiff -- 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/1942260 Title: compress firmware in /lib/firmware Status in initramfs-tools package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware-raspi2 package in Ubuntu: Confirmed Bug description: -- initramfs-tools [Impact] * linux supports xz compressed linux-firmware which saves disk space. In focal, initramfs-tools only knows how to included uncompressed firmware files (even when kernel supports loading compressed ones). Newer releases of linux-firmware may use compressed firmware files only, in such cases it would be nice for focal's initramfs-tools to support compressed firmware files in case of partial or incomplete upgrades (i.e. linux-firmware force installed or upgraded, without newer initramfs-tools). The proposed changes to initramfs-tools are backwards and forwards compatible, they prefer to include uncompressed firmware files; and if missing, include compressed firmware files in their uncompressed form. Thus maintaining compatibility with any kernels, irrespective of compressed/uncompressed firmware inputs. [Test Plan] * Compress all files shipped by linux-firmware with xz * Rebuild initrd * Check that all the same firmware files are still included in the initramfs, in their uncompressed form as before [Where problems could occur] * This SRU is precautionary to prevent accidental installation of compressed linux-firmware from generating incorrect initramfs. It should be noted that whilst initramfs-tools would create a compatible initramfs with any kernels, pre-v5.3 kernels do not support xz compressed firmware files at runtime. Mixing this new initramfs with compressed firmwares and pre 5.3 kernels may lead to expectations of supporting compressed firmware files with them only working at initrd stage and not at runtime. [Other Info] Original bug report Some facts: - The linux kernel has supported loading xz compressed firmware since 5.3 - The size of /lib/firmware in impish is ~650Mb (and growing) - The compressed size of firmware could be ~230Mb It would be nice to install compressed firmware to save space. Here are the plans from the Fedora project: https://fedoraproject.org/wiki/Changes/CompressKernelFirmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023952] Re: UNII-4 5.9G Band support request on 8852BE
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023952 Title: UNII-4 5.9G Band support request on 8852BE Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The platform can't connect to AP with Wi-Fi 5.9G capability and wifi function doesn't work properly. [Fix] Realtek has verified the 5.9G function with 8852BE WLAN on WarlockMLK2 Intel platform and submitted upstream. https://lore.kernel.org/linux-wireless/20230508081211.38760-1-pks...@realtek.com/ Included in v6.5-rc e3b77c06c886 wifi: rtw89: support U-NII-4 channels on 5GHz band a002f98123dd wifi: rtw89: regd: judge UNII-4 according to BIOS and chip e897b0bef38a wifi: rtw89: introduce realtek ACPI DSM method [Test] Verified by ODM and can connect to 5.9G AP [Where problems could occur] commit 5 added new callback functions which change the device behavior during suspending/resuming, not sure if this impacts old chips. Other commits looks normal and should not lead to regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025713] Re: Jammy update: v6.1.37 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2025713 Title: Jammy update: v6.1.37 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.37 upstream stable release from git://git.kernel.org/ Linux 6.1.37 xtensa: fix NOMMU build with lock_mm_and_find_vma() conversion csky: fix up lock_mm_and_find_vma() conversion parisc: fix expand_stack() conversion sparc32: fix lock_mm_and_find_vma() conversion Revert "thermal/drivers/mediatek: Use devm_of_iomap to avoid resource leak in mtk_thermal_probe" HID: logitech-hidpp: add HIDPP_QUIRK_DELAYED_INIT for the T651. HID: wacom: Use ktime_t rather than int when dealing with timestamps HID: hidraw: fix data race on device refcount fbdev: fix potential OOB read in fast_imageblit() mm: always expand the stack with the mmap write lock held execve: expand new process stack manually ahead of time mm: make find_extend_vma() fail if write lock not held powerpc/mm: convert coprocessor fault to lock_mm_and_find_vma() mm/fault: convert remaining simple cases to lock_mm_and_find_vma() arm/mm: Convert to using lock_mm_and_find_vma() riscv/mm: Convert to using lock_mm_and_find_vma() mips/mm: Convert to using lock_mm_and_find_vma() powerpc/mm: Convert to using lock_mm_and_find_vma() arm64/mm: Convert to using lock_mm_and_find_vma() mm: make the page fault mmap locking killable mm: introduce new 'lock_mm_and_find_vma()' page fault helper maple_tree: fix potential out-of-bounds access in mas_wr_end_piv() can: isotp: isotp_sendmsg(): fix return error fix on TX path x86/smp: Cure kexec() vs. mwait_play_dead() breakage x86/smp: Use dedicated cache-line for mwait_play_dead() x86/smp: Remove pointless wmb()s from native_stop_other_cpus() x86/smp: Dont access non-existing CPUID leaf x86/smp: Make stop_other_cpus() more robust x86/microcode/AMD: Load late on both threads too mm, hwpoison: when copy-on-write hits poison, take page offline mm, hwpoison: try to recover from copy-on write faults mptcp: ensure listener is unhashed before updating the sk status mm/mmap: Fix error return in do_vmi_align_munmap() mm/mmap: Fix error path in do_vmi_align_munmap() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2025713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025708] Re: Jammy update: v6.1.35 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2025708 Title: Jammy update: v6.1.35 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.35 upstream stable release from git://git.kernel.org/ Linux 6.1.35 kbuild: Update assembler calls to use proper flags and language target MIPS: Prefer cc-option for additions to cflags MIPS: Move '-Wa,-msoft-float' check from as-option to cc-option x86/boot/compressed: prefer cc-option for CFLAGS additions scsi: target: core: Fix error path in target_setup_session() neighbour: delete neigh_lookup_nodev as not used net/sched: act_api: add specific EXT_WARN_MSG for tc action Revert "net/sched: act_api: move TCA_EXT_WARN_MSG to the correct hierarchy" net/sched: act_api: move TCA_EXT_WARN_MSG to the correct hierarchy drm/amdgpu: Don't set struct drm_driver.output_poll_changed rcu/kvfree: Avoid freeing new kfree_rcu() memory after old grace period parisc: Delete redundant register definitions in afs: Fix vlserver probe RTT handling octeon_ep: Add missing check for ioremap selftests/ptp: Fix timestamp printf format for PTP_SYS_OFFSET net: tipc: resize nlattr array to correct size dm: don't lock fs when the map is NULL during suspend or resume sfc: fix XDP queues mode with legacy IRQ net: macsec: fix double free of percpu stats net: lapbether: only support ethernet devices net: dsa: felix: fix taprio guard band overflow at 10Mbps with jumbo frames net/sched: cls_api: Fix lockup on flushing explicitly created chain ext4: drop the call to ext4_error() from ext4_get_group_info() cifs: fix lease break oops in xfstest generic/098 selftests: forwarding: hw_stats_l3: Set addrgenmode in a separate step net/sched: qdisc_destroy() old ingress and clsact Qdiscs before grafting net/sched: Refactor qdisc_graft() for ingress and clsact Qdiscs sched: add new attr TCA_EXT_WARN_MSG to report tc extact message selftests/tc-testing: Fix SFB db test selftests/tc-testing: Fix Error: failed to find target LOG selftests/tc-testing: Fix Error: Specified qdisc kind is unknown. drm/nouveau: add nv_encoder pointer check for NULL drm/nouveau/dp: check for NULL nv_connector->native_mode drm/bridge: ti-sn65dsi86: Avoid possible buffer overflow drm/nouveau: don't detect DSM for non-NVIDIA device net: phylink: use a dedicated helper to parse usgmii control word net: phylink: report correct max speed for QUSGMII igb: fix nvm.ops.read() error handling igc: Fix possible system crash when loading module igc: Clean the TX buffer and TX descriptor ring sctp: fix an error code in sctp_sf_eat_auth() ipvlan: fix bound dev checking for IPv6 l3s mode net: ethtool: correct MAX attribute value for stats IB/isert: Fix incorrect release of isert connection IB/isert: Fix possible list corruption in CMA handler IB/isert: Fix dead lock in ib_isert RDMA/mlx5: Fix affinity assignment IB/uverbs: Fix to consider event queue closing also upon non-blocking mode RDMA/cma: Always set static rate to 0 for RoCE RDMA/mlx5: Create an indirect flow table for steering anchor RDMA/mlx5: Initiate dropless RQ for RAW Ethernet functions octeontx2-af: fix lbk link credits on cn10k octeontx2-af: fixed resource availability check iavf: remove mask from iavf_irq_enable_queues() RDMA/rxe: Fix the use-before-initialization error of resp_pkts RDMA/rxe: Removed unused name from rxe_task struct wifi: mac80211: take lock before setting vif links wifi: cfg80211: fix link del callback to call correct handler wifi: mac80211: fix link activation settings order net/sched: cls_u32: Fix reference counter leak leading to overflow octeontx2-af: Fix promiscuous mode net/sched: act_pedit: Parse L3 Header for L4 offset net/sched: act_pedit: remove extra check for key type net/sched: simplify tcf_pedit_act igb: Fix extts capture value format for 82580/i354/i350 ping6: Fix send to link-local addresses with VRF. net: enetc: correct the indexes of highest and 2nd highest TCs netfilter: nf_tables: incorrect error path handling with NFT_MSG_NEWRULE ice: Fix
[Kernel-packages] [Bug 2025710] Re: Jammy update: v6.1.36 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2025710 Title: Jammy update: v6.1.36 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.36 upstream stable release from git://git.kernel.org/ Linux 6.1.36 smb: move client and server files to common directory fs/smb i2c: imx-lpi2c: fix type char overflow issue when calculating the clock cycle x86/apic: Fix kernel panic when booting with intremap=off and x2apic_phys KVM: arm64: Restore GICv2-on-GICv3 functionality vhost_net: revert upend_idx only on retriable error vhost_vdpa: tell vqs about the negotiated drm/radeon: fix race condition UAF in radeon_gem_set_domain_ioctl drm/exynos: fix race condition UAF in exynos_g2d_exec_ioctl drm/exynos: vidi: fix a wrong error return null_blk: Fix: memory release when memory_backed=1 ARM: dts: Fix erroneous ADS touchscreen polarities i2c: mchp-pci1: Avoid cast to incompatible function type ALSA: hda/realtek: Add "Intel Reference board" and "NUC 13" SSID in the ALC256 ASoC: fsl_sai: Enable BCI bit if SAI works on synchronous mode with BYP asserted s390/purgatory: disable branch profiling gfs2: Don't get stuck writing page onto itself under direct I/O ASoC: amd: yc: Add Thinkpad Neo14 to quirks list for acp6x ASoC: nau8824: Add quirk to active-high jack-detect soundwire: qcom: add proper error paths in qcom_swrm_startup() soundwire: dmi-quirks: add new mapping for HP Spectre x360 ASoC: simple-card: Add missing of_node_put() in case of error ASoC: codecs: wcd938x-sdw: do not set can_multi_write flag spi: lpspi: disable lpspi module irq in DMA mode s390/cio: unregister device when the only path is gone arm64: dts: qcom: sc7280-qcard: drop incorrect dai-cells from WCD938x SDW arm64: dts: qcom: sc7280-idp: drop incorrect dai-cells from WCD938x SDW Input: soc_button_array - add invalid acpi_index DMI quirk handling nvme: improve handling of long keep alives nvme: check IO start time when deciding to defer KA nvme: double KA polling frequency to avoid KATO with TBKAS on usb: gadget: udc: fix NULL dereference in remove() btrfs: fix an uninitialized variable warning in btrfs_log_inode nfcsim.c: Fix error checking for debugfs_create_dir media: cec: core: don't set last_initiator if tx in progress media: cec: core: disable adapter in cec_devnode_unregister smb3: missing null check in SMB2_change_notify arm64: Add missing Set/Way CMO encodings HID: wacom: Add error check to wacom_parse_and_register() scsi: target: iscsi: Prevent login threads from racing between each other gpiolib: Fix irq_domain resource tracking for gpiochip_irqchip_add_domain() gpio: sifive: add missing check for platform_get_irq gpiolib: Fix GPIO chip IRQ initialization restriction arm64: dts: rockchip: fix nEXTRST on SOQuartz arm64: dts: rockchip: Enable GPU on SOQuartz CM4 revert "net: align SO_RCVMARK required privileges with SO_MARK" sch_netem: acquire qdisc lock in netem_change() platform/x86/amd/pmf: Register notify handler only if SPS is enabled selftests: forwarding: Fix race condition in mirror installation io_uring/net: use the correct msghdr union member in io_sendmsg_copy_hdr bpf: Force kprobe multi expected_attach_type for kprobe_multi link bpf/btf: Accept function names that contain dots Revert "net: phy: dp83867: perform soft reset and retain established link" netfilter: nfnetlink_osf: fix module autoload netfilter: nf_tables: disallow updates of anonymous sets netfilter: nf_tables: reject unbound chain set before commit phase netfilter: nf_tables: reject unbound anonymous set before commit phase netfilter: nf_tables: disallow element updates of bound anonymous sets netfilter: nft_set_pipapo: .walk does not deal with generations netfilter: nf_tables: drop map element references from preparation phase netfilter: nf_tables: add NFT_TRANS_PREPARE_ERROR to deal with bound set/chain netfilter: nf_tables: fix chain binding transaction logic be2net: Extend xmit workaround to BE3 chip net: dsa: mt7530: fix handling of LLDP frames net: dsa: mt7530:
[Kernel-packages] [Bug 2026269] Re: Jammy update: v6.1.38 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2026269 Title: Jammy update: v6.1.38 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.38 upstream stable release from git://git.kernel.org/ Linux 6.1.38 drm/amd/display: Ensure vmin and vmax adjust for DCE drm/amdgpu: Validate VM ioctl flags. docs: Set minimal gtags / GNU GLOBAL version to 6.6.5 scripts/tags.sh: Resolve gtags empty index generation perf symbols: Symbol lookup with kcore can fail if multiple segments match stext nubus: Partially revert proc_create_single_data() conversion execve: always mark stack as growing down during early stack setup PCI/ACPI: Call _REG when transitioning D-states PCI/ACPI: Validate acpi_pci_set_power_state() parameter drm/amd/display: Do not update DRR while BW optimizations pending drm/amd/display: Remove optimization for VRR updates xtensa: fix lock_mm_and_find_vma in case VMA not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2026269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026322] Re: Fix non-working MT7921e when pre-boot WiFi is enabled
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2026322 Title: Fix non-working MT7921e when pre-boot WiFi is enabled Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] When "pre-boot WiFi" is enabled in UEFI, MT7921e WiFi doesn't work under Linux. [Fix] Reset the device earlier at the probing process. [Test] With the patch applied, WiFi always works regardless of pre-boot WiFi is toggled or not. [Where problems could occur] Probe routine might fail one some other corner cases. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2026322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026652] Re: Suspend Broken
May or may not be related to this other bug I filed https://bugs.launchpad.net/ubuntu/+bug/2028410. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2026652 Title: Suspend Broken Status in linux-signed-lowlatency package in Ubuntu: New Bug description: When I go to suspend my system via the UI "Suspend" option, the system fails to suspend. Instead it looks like its going to suspend, and then wakes up but with a locked screen. When I use `pm-suspend` from the command line, it suspends the system, but does not lock the screen. I have the Settings -> Privacy -> Screen Lock -> "Lock Screen on Suspend" setting enabled. I am using the Nouveau driver, with Wayland, using GNOME 44.2. This bug only started when I switched away from using any of the NVIDIA drivers, so its probably partially Nouveau related. Switching back to the NVIDIA drivers (I tried them all) isn't an option, because they break: 1. External monitor connectivity 2. VMWare Horizon Debug info: 1. `lsb_release -rd` Description: Ubuntu 23.04 Release: 23.04 2. `uname -srm` Linux 6.2.0-1007-lowlatency x86_64 Please let me know of any other information needed to debug this. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7 ProcVersionSignature: Ubuntu 6.2.0-1007.7-lowlatency 6.2.12 Uname: Linux 6.2.0-1007-lowlatency x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 9 10:26:06 2023 InstallationDate: Installed on 2021-12-18 (567 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: linux-signed-lowlatency UpgradeStatus: Upgraded to lunar on 2023-04-26 (73 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2026652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027773] Re: UBSAN: shift-out-of-bounds in amd_sfh
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2027773
Title:
UBSAN: shift-out-of-bounds in amd_sfh
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.0 source package in Jammy:
Won't Fix
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.0 source package in Lunar:
Invalid
Status in linux-oem-6.1 source package in Lunar:
Invalid
Status in linux source package in Mantic:
Fix Released
Status in linux-oem-6.0 source package in Mantic:
Invalid
Status in linux-oem-6.1 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
UBSAN: shift-out-of-bounds in
drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_desc.c:149:50
[ 7.928631] shift exponent 103 is too large for 64-bit type 'long unsigned
int'
[ 9.877309] Workqueue: events amd_sfh_work_buffer \[amd_sfh]
[ 9.877327] Call Trace:
[ 9.877331] \
[ 9.877335] dump_stack_lvl+0x49/0x63
[ 9.877346] dump_stack+0x10/0x16
[ 9.877348] ubsan_epilogue+0x9/0x36
[ 9.877357] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
[ 9.877363] ? _raw_spin_lock+0x17/0x50
[ 9.877369] ? raw_spin_rq_lock_nested+0x2e/0xa0
[ 9.877378] ? psi_group_change+0x1e2/0x4a0
[ 9.877385] float_to_int.cold+0x18/0xc8 \[amd_sfh]
[ 9.877394] ? get_feature_rep+0xb0/0xb0 \[amd_sfh]
[ 9.877402] get_input_rep+0x219/0x2f0 \[amd_sfh]
[ 9.877409] ? up+0x37/0x70
[ 9.877414] ? hid_input_report+0x104/0x170 \[hid]
[ 9.877428] amd_sfh_work_buffer+0x94/0x150 \[amd_sfh]
[ 9.877436] process_one_work+0x21f/0x3f0
[ 9.877443] worker_thread+0x50/0x3e0
[ 9.877446] ? process_one_work+0x3f0/0x3f0
[ 9.877449] kthread+0xfd/0x130
[ 9.877452] ? kthread_complete_and_exit+0x20/0x20
[ 9.877454] ret_from_fork+0x22/0x30
[ 9.877463] \
[Fix]
Fixes in:
* commit c1685a862a4b ("HID: amd_sfh: Rename the float32 variable")
* commit 878543661764 ("HID: amd_sfh: Fix for shift-out-of-bounds")
[Test Case]
The affected platform should no longer has such error dumped in kernel dmesg
at
boot.
[Where problems could occur]
This renamed a variable and corrected the way shift offset is calculated. No
known side effect.
[Other Info]
The affects kernel >= v6.0 and < v6.5, so Unstable/Mantis/Lunar/OEM-6.1 are
nominated for fix.
== original bug report ==
UBSAN: shift-out-of-bounds in
drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_desc.c:149:50
[ 7.928631] shift exponent 103 is too large for 64-bit type 'long unsigned
int'
[ 9.877309] Workqueue: events amd_sfh_work_buffer [amd_sfh]
[ 9.877327] Call Trace:
[ 9.877331]
[ 9.877335] dump_stack_lvl+0x49/0x63
[ 9.877346] dump_stack+0x10/0x16
[ 9.877348] ubsan_epilogue+0x9/0x36
[ 9.877357] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
[ 9.877363] ? _raw_spin_lock+0x17/0x50
[ 9.877369] ? raw_spin_rq_lock_nested+0x2e/0xa0
[ 9.877378] ? psi_group_change+0x1e2/0x4a0
[ 9.877385] float_to_int.cold+0x18/0xc8 [amd_sfh]
[ 9.877394] ? get_feature_rep+0xb0/0xb0 [amd_sfh]
[ 9.877402] get_input_rep+0x219/0x2f0 [amd_sfh]
[ 9.877409] ? up+0x37/0x70
[ 9.877414] ? hid_input_report+0x104/0x170 [hid]
[ 9.877428] amd_sfh_work_buffer+0x94/0x150 [amd_sfh]
[ 9.877436] process_one_work+0x21f/0x3f0
[ 9.877443] worker_thread+0x50/0x3e0
[ 9.877446] ? process_one_work+0x3f0/0x3f0
[ 9.877449] kthread+0xfd/0x130
[ 9.877452] ? kthread_complete_and_exit+0x20/0x20
[ 9.877454] ret_from_fork+0x22/0x30
[ 9.877463]
Fixes in:
https://github.com/torvalds/linux/commit/c1685a862a4bea863537f06abaa37a123aef493c
https://github.com/torvalds/linux/commit/87854366176403438d01f368b09de3ec2234e0f5
This affects kernel >= v6.0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2027773/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027804] Re: Fix GUI hang in login menu on Intel GPU
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2027804 Title: Fix GUI hang in login menu on Intel GPU Status in HWE Next: In Progress 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: Fix Committed Bug description: [Impact] Intel GPU hang on 6.1 stable kernel in login menu after boot. [Fix] Add missing DC_OFF power domain for GPU. [Test] Tested on Intel RPL iGPU and DG2 GPU. [Where problems could occur] Low risk, the fix is in 6.2-rc1, the issue is only reproduced on oem-6.1 kernel, not reproduced on jammy kernel. So SRU for oem-6.1 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027847] Re: Bump minimum /boot size in ubuntu-release-upgrader
We have a bunch of bugs to decrease initramfs size and to make it faster: * bug #2028567: initramfs-tools: Do not re-compress compressed kernel modules and firmware files * bug #2028568: Ship kernel modules compressed * bug #1942260: compress firmware in /lib/firmware * bug #2028571: klibc-utils contains identical binaries * bug #2028574: Duplicate firmware files in /lib/firmware This started on ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html -- 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/2027847 Title: Bump minimum /boot size in ubuntu-release-upgrader Status in apt package in Ubuntu: Won't Fix Status in dpkg package in Ubuntu: Invalid Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-kernel-headers package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-libc-dev:amd64 linux-libc-dev:i386 linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Is not possible to uninstall any kernel because fails: $ sudo apt purge linux-headers-6.2.0-23 E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reconfigure fails again so some kernel have to be manually removed to free up space: $ sudo rm /boot/initrd.img-6.2.0-23-generic $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new Now you can reconfigure: $ Remove kernels: $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Reboot: $ sudo reboot Upgrade as usual: $ sudo apt update && sudo apt upgrade Before upgrading new kernels I need to check for free space and remove older kernels manually. Fix this so there's only one kernel left. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027957] Re: Fix AMDGPU: the screen freeze with W7500
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2027957 Title: Fix AMDGPU: the screen freeze with W7500 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. Solution is, - Detect Intel x86 systems that don't support dynamic switching - Override the input caps to maximum supported for that system - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] low, this could lead issue when setting higher speeds than supported. [Misc] 1. jammy, amdgpu isn't loaded on this platform with 5.15-73-generic. 2. kinetic, amdgpu failed to probe the vga controller with 5.19-46-generic. 3. Passed cbd build against Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027914] Re: missing nvidia kernel module for generic kernel (linux-objects-nvidia-535-6.2.0-25-generic)
Worked again after I upgraded to 6.2.0-26, which does have the relevant linux-objects-nvidia package available. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2027914 Title: missing nvidia kernel module for generic kernel (linux-objects- nvidia-535-6.2.0-25-generic) Status in linux-restricted-modules package in Ubuntu: Confirmed Bug description: For latest generic kernel for Ubuntu 23.04 there in no package of kernel module. Present is for previous kernel: # aptitude search linux-objects-nvidia-535.*generic i A linux-objects-nvidia-535-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-open-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-open-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) There is no package for 6.2.0-25 kernel. So after upgrade to new kernel - gpu isn't working, as the module is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2027914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028122] Re: Fix unreliable ethernet cable detection on I219 NIC
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2028122 Title: Fix unreliable ethernet cable detection on I219 NIC Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Hotplugging RJ45 ethernet cable only works for one time because ACPI GPE wake doesn't working properly anymore. [Fix] Always use PME poll to read PCI PME to know if there's wake event. [Test] With the patch applied, ethernet cable can always be detected. [Where problems could occur] PME poll mechanism periodically reads the PMCTRL register, so the power consumption can be slightly higher. The increase will be very low, probably won't be noticeable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2028122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028522] Re: the ath9k drivers do not work on arm (raspberry pi)
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: rpi-image ** Tags added: rpi -- 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/2028522 Title: the ath9k drivers do not work on arm (raspberry pi) Status in linux package in Ubuntu: New Bug description: My kernel image is linux-image-5.15.0-1024-raspi The ath9k_* drivers are not present on the system out of the box, from what i can see of the kernel config they should be included (could well be wrong on that front). I have tried building the module from source and although it builds the .ko files just fine when i try to load them i get "could not insert module unknown symbol in module" errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028528] Re: Jammy update: v6.1.39 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2028528 Title: Jammy update: v6.1.39 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.39 upstream stable release from git://git.kernel.org/ Linux 6.1.39 io_uring: Use io_schedule* in cqring wait sh: hd64461: Handle virq offset for offchip IRQ base and HD64461 IRQ sh: mach-dreamcast: Handle virq offset in cascaded IRQ demux sh: mach-highlander: Handle virq offset in cascaded IRL demux sh: mach-r2d: Handle virq offset in cascaded IRL demux block/partition: fix signedness issue for Amiga partitions tty: serial: fsl_lpuart: add earlycon for imx8ulp platform wireguard: netlink: send staged packets when setting initial private key wireguard: queueing: use saner cpu selection wrapping netfilter: nf_tables: prevent OOB access in nft_byteorder_eval netfilter: nf_tables: do not ignore genmask when looking up chain by id netfilter: conntrack: Avoid nf_ct_helper_hash uses after free netfilter: nf_tables: unbind non-anonymous set if rule construction fails mtd: parsers: refer to ARCH_BCMBCA instead of ARCH_BCM4908 drm/i915/tc: Fix system resume MST mode restore for DP-alt sinks drm/i915/tc: Fix TC port link ref init for DP MST during HW readout drm/i915: Fix TypeC mode initialization during system resume mm/mmap: Fix extra maple tree write xfs: fix xfs_inodegc_stop racing with mod_delayed_work xfs: disable reaping in fscounters scrub xfs: check that per-cpu inodegc workers actually run on that cpu xfs: explicitly specify cpu when forcing inodegc delayed work to run immediately fs: no need to check source blktrace: use inline function for blk_trace_remove() while blktrace is disabled leds: trigger: netdev: Recheck NETDEV_LED_MODE_LINKUP on dev rename ARM: orion5x: fix d2net gpio initialization ARM: dts: qcom: ipq4019: fix broken NAND controller properties override regulator: tps65219: Fix matching interrupts for their regulators ASoC: mediatek: mt8173: Fix snd_soc_component_initialize error path ASoC: mediatek: mt8173: Fix irq error path btrfs: do not BUG_ON() on tree mod log failure at __btrfs_cow_block() btrfs: fix extent buffer leak after tree mod log failure at split_node() btrfs: fix race when deleting quota root from the dirty cow roots list btrfs: reinsert BGs failed to reclaim btrfs: add block-group tree to lockdep classes btrfs: bail out reclaim process if filesystem is read-only btrfs: delete unused BGs while reclaiming BGs btrfs: add handling for RAID1C23/DUP to btrfs_reduce_alloc_profile ipvs: increase ip_vs_conn_tab_bits range for 64BIT usb: typec: ucsi: Mark dGPUs as DEVICE scope i2c: nvidia-gpu: Remove ccgx,firmware-build property i2c: nvidia-gpu: Add ACPI property to align with device-tree fs: Lock moved directories fs: Establish locking order for unrelated directories Revert "f2fs: fix potential corruption when moving a directory" ext4: Remove ext4 locking of moved directory fs: avoid empty option when generating legacy mount string jffs2: reduce stack usage in jffs2_build_xattr_subsystem() shmem: use ramfs_kill_sb() for kill_sb method of ramfs-based tmpfs mm/damon/ops-common: atomically test and clear young on ptes and pmds autofs: use flexible array in ioctl structure integrity: Fix possible multiple allocation in integrity_inode_get() um: Use HOST_DIR for mrproper watch_queue: prevent dangling pipe pointer bcache: Fix __bch_btree_node_alloc to make the failure behavior consistent bcache: Remove unnecessary NULL point check in node allocations bcache: fixup btree_cache_wait list damage wifi: mt76: mt7921e: fix init command fail with enabled device wifi: ath10k: Serialize wake_tx_queue ops wifi: cfg80211: fix regulatory disconnect for non-MLO mmc: sdhci: fix DMA configure compatibility issue when 64bit DMA mode is used. mmc: mmci: Set PROBE_PREFER_ASYNCHRONOUS mmc: core: disable TRIM on Micron MTFC4GACAJCN-1M mmc: core: disable TRIM on Kingston EMMC04G-M627 io_uring: wait interruptibly for request completions on exit irqchip/loongson-pch-pic:
[Kernel-packages] [Bug 2028568] Re: Ship kernel modules compressed
** Tags added: patch -- 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/2028568 Title: Ship kernel modules compressed Status in linux package in Ubuntu: New Bug description: To reduce the size of the initramfs and also to speed up the boot (by only decompressing the modules that are needed), please compress the kernel modules. From size and speed perspective, either use zstd or xz. I suggest to go with zstd -19. This change is independent of the initramfs-tools version. Old initramfs-tools versions will decompress the kernel modules before putting them in the initramfs. New initramfs-tools versions will put the compressed kernel modules into an uncompressed cpio archive (see bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028534] Re: Jammy update: v6.1.40 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2028534 Title: Jammy update: v6.1.40 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.40 upstream stable release from git://git.kernel.org/ Linux 6.1.40 net/ncsi: change from ndo_set_mac_address to dev_set_mac_address net/ncsi: make one oem_gma function for all mfr id drm/atomic: Fix potential use-after-free in nonblocking commits net/sched: sch_qfq: reintroduce lmax bound check for MTU swiotlb: mark swiotlb_memblock_alloc() as __init Revert "drm/amd: Disable PSR-SU on Parade 0803 TCON" MIPS: kvm: Fix build error with KVM_MIPS_DEBUG_COP0_COUNTERS enabled scsi: qla2xxx: Fix end of loop test scsi: qla2xxx: Remove unused nvme_ls_waitq wait queue scsi: qla2xxx: Pointer may be dereferenced scsi: qla2xxx: Correct the index of array scsi: qla2xxx: Check valid rport returned by fc_bsg_to_rport() scsi: qla2xxx: Fix potential NULL pointer dereference scsi: qla2xxx: Fix buffer overrun scsi: qla2xxx: Avoid fcport pointer dereference scsi: qla2xxx: Array index may go out of bound scsi: qla2xxx: Fix mem access after free scsi: qla2xxx: Wait for io return on terminate rport scsi: qla2xxx: Fix hang in task management scsi: qla2xxx: Fix task management cmd fail due to unavailable resource scsi: qla2xxx: Fix task management cmd failure scsi: qla2xxx: Multi-que support for TMF tracing/user_events: Fix struct arg size match check tracing/probes: Fix to update dynamic data counter if fetcharg uses it tracing/probes: Fix not to count error code to total length selftests: mptcp: pm_nl_ctl: fix 32-bit support selftests: mptcp: depend on SYN_COOKIES selftests: mptcp: userspace_pm: report errors with 'remove' tests selftests: mptcp: userspace_pm: use correct server port selftests: mptcp: sockopt: return error if wrong mark selftests: mptcp: connect: fail if nft supposed to work tracing: Fix null pointer dereference in tracing_err_log_open() fprobe: Ensure running fprobe_exit_handler() finished before calling rethook_free() fprobe: Release rethook after the ftrace_ops is unregistered pwm: meson: fix handling of period/duty if greater than UINT_MAX pwm: meson: modify and simplify calculation in meson_pwm_get_state PM: QoS: Restore support for default value on frequency QoS perf/x86: Fix lockdep warning in for_each_sibling_event() on SPR xtensa: ISS: fix call to split_if_spec cifs: if deferred close is disabled then close files immediately drm/amd/pm: conditionally disable pcie lane/speed switching for SMU13 drm/amd/pm: share the code around SMU13 pcie parameters update ftrace: Fix possible warning on checking all pages used in ftrace_process_locs() ring-buffer: Fix deadloop issue on reading trace_pipe net: ena: fix shift-out-of-bounds in exponential backoff regmap-irq: Fix out-of-bounds access when allocating config buffers perf: RISC-V: Remove PERF_HES_STOPPED flag checking in riscv_pmu_start() samples: ftrace: Save required argument registers in sample trampolines nvme: don't reject probe due to duplicate IDs for single-ported PCIe devices tracing: Fix memory leak of iter->temp when reading trace_pipe tracing/histograms: Add histograms to hist_vars if they have referenced variables dm: verity-loadpin: Add NULL pointer check for 'bdev' parameter s390/decompressor: fix misaligned symbol build error bus: ixp4xx: fix IXP4XX_EXP_T1_MASK Revert "8250: add support for ASIX devices with a FIFO bug" soundwire: qcom: fix storing port config out-of-bounds opp: Fix use-after-free in lazy_opp_tables after probe deferral meson saradc: fix clock divider mask length xhci: Show ZHAOXIN xHCI root hub speed correctly xhci: Fix TRB prefetch issue of ZHAOXIN hosts xhci: Fix resume issue of some ZHAOXIN hosts ceph: don't let check_caps skip sending responses for revoke msgs ceph: fix blindly expanding the readahead windows ceph: add a dedicated private data for netfs rreq libceph: harden msgr2.1 frame segment length checks firmware: stratix10-svc: Fix a potential resource leak in
[Kernel-packages] [Bug 2028574] [NEW] Duplicate firmware files in /lib/firmware
Public bug reported: linux-firmware ships firmware files that are identical/duplicates: ``` $ fdupes -rm /lib/firmware/ 341 duplicate files (in 195 sets), occupying 37.1 megabytes ``` Please patch the source package and replace the duplicates by symlinks. Alternatively run jdupes during build, but then ensure that the resulting symlinks are stable. This will reduce the initramfs size especially after compressing firmware files (bug #1942260) and putting compressed files in an uncompressed cpio archive (bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html Some upstream discussion: https://lore.kernel.org/linux- firmware/20230331115739.bytw7s35aacgr...@notk.org/ ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1.2 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jul 24 21:18:24 2023 Dependencies: firmware-sof-signed 2.2.4-1 InstallationDate: Installed on 2022-03-20 (491 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. B550I AORUS PRO AX PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-25-generic root=UUID=f9311d7a-cbb8-43f1-b2cd-38c98ae92b9e 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.2.0-25-generic N/A linux-backports-modules-6.2.0-25-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 SourcePackage: linux-firmware UpgradeStatus: Upgraded to lunar on 2023-04-20 (95 days ago) dmi.bios.date: 07/20/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F16e dmi.board.asset.tag: Default string dmi.board.name: B550I AORUS PRO AX dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF16e:bd07/20/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550IAORUSPROAX:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550IAORUSPROAX:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550I AORUS PRO AX dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Summary changed: - Duplicate firmware files + Duplicate firmware files in /lib/firmware -- 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/2028574 Title: Duplicate firmware files in /lib/firmware Status in linux-firmware package in Ubuntu: New Bug description: linux-firmware ships firmware files that are identical/duplicates: ``` $ fdupes -rm /lib/firmware/ 341 duplicate files (in 195 sets), occupying 37.1 megabytes ``` Please patch the source package and replace the duplicates by symlinks. Alternatively run jdupes during build, but then ensure that the resulting symlinks are stable. This will reduce the initramfs size especially after compressing firmware files (bug #1942260) and putting compressed files in an uncompressed cpio archive (bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html Some upstream discussion: https://lore.kernel.org/linux- firmware/20230331115739.bytw7s35aacgr...@notk.org/ ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1.2 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jul 24 21:18:24 2023 Dependencies: firmware-sof-signed 2.2.4-1 InstallationDate: Installed on 2022-03-20 (491 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. B550I AORUS PRO AX PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-25-generic root=UUID=f9311d7a-cbb8-43f1-b2cd-38c98ae92b9e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
[Kernel-packages] [Bug 2028576] [NEW] Pull-request for setting CPU frequency gov to performance
Public bug reported: [issue] CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set so it's using ondemand. We want to be using PERFORMANCE ** Affects: linux-nvidia-6.2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2028576 Title: Pull-request for setting CPU frequency gov to performance Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: [issue] CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set so it's using ondemand. We want to be using PERFORMANCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2028576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028568] Re: Ship kernel modules compressed
Attached a tested patch for zstd -19 compression. ** Patch added: "0001-UBUNTU-Compress-kernel-modules-with-zst-19.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028568/+attachment/5688115/+files/0001-UBUNTU-Compress-kernel-modules-with-zst-19.patch -- 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/2028568 Title: Ship kernel modules compressed Status in linux package in Ubuntu: New Bug description: To reduce the size of the initramfs and also to speed up the boot (by only decompressing the modules that are needed), please compress the kernel modules. From size and speed perspective, either use zstd or xz. I suggest to go with zstd -19. This change is independent of the initramfs-tools version. Old initramfs-tools versions will decompress the kernel modules before putting them in the initramfs. New initramfs-tools versions will put the compressed kernel modules into an uncompressed cpio archive (see bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028568] [NEW] Ship kernel modules compressed
Public bug reported: To reduce the size of the initramfs and also to speed up the boot (by only decompressing the modules that are needed), please compress the kernel modules. From size and speed perspective, either use zstd or xz. I suggest to go with zstd -19. This change is independent of the initramfs-tools version. Old initramfs-tools versions will decompress the kernel modules before putting them in the initramfs. New initramfs-tools versions will put the compressed kernel modules into an uncompressed cpio archive (see bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028568 Title: Ship kernel modules compressed Status in linux package in Ubuntu: New Bug description: To reduce the size of the initramfs and also to speed up the boot (by only decompressing the modules that are needed), please compress the kernel modules. From size and speed perspective, either use zstd or xz. I suggest to go with zstd -19. This change is independent of the initramfs-tools version. Old initramfs-tools versions will decompress the kernel modules before putting them in the initramfs. New initramfs-tools versions will put the compressed kernel modules into an uncompressed cpio archive (see bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020901] Re: io_uring regression in the Ubuntu kernel (deadlock)
Can someone validate this fix, please? The original reporter said that he left the company. 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/2020901 Title: io_uring regression in the Ubuntu kernel (deadlock) Status in linux package in Ubuntu: Triaged Status in linux source package in Kinetic: Fix Committed Bug description: Whenever using io_uring on the Ubuntu 5.15 or 5.19 kernel, one gets: ``` [ 123.226074] BUG: kernel NULL pointer dereference, address: 001d [ 123.226160] #PF: supervisor read access in kernel mode [ 123.226201] #PF: error_code(0x) - not-present page [ 123.226241] PGD 0 P4D 0 [ 123.226272] Oops: [#1] PREEMPT SMP PTI [ 123.226310] CPU: 2 PID: 4326 Comm: qemu-system-x86 Tainted: P O 5.19.0-42-generic #43~22.04.1-Ubuntu [ 123.226381] Hardware name: /D33217GKE, BIOS GKPPT10H.86A.0069.2019.1104.1340 11/04/2019 [ 123.228698] RIP: 0010:__blk_queue_split+0x53/0x1f0 [ 123.231029] Code: 00 00 83 f8 09 0f 84 e7 00 00 00 83 f8 03 0f 84 15 01 00 00 48 89 d1 4c 89 c6 4c 89 ca e8 b5 f2 ff ff 48 89 c3 48 85 db 74 5f <44> 8b 63 28 81 4b 10 00 40 00 00 49 be 00 00 00 00 00 00 00 80 4c [ 123.235909] RSP: 0018:9bb3414779e8 EFLAGS: 00010286 [ 123.238328] RAX: fff5 RBX: fff5 RCX: [ 123.240737] RDX: RSI: RDI: [ 123.243093] RBP: 9bb341477a08 R08: R09: [ 123.245435] R10: R11: R12: 8e095d629ac0 [ 123.247735] R13: 9bb341477a18 R14: 8e0940df2040 R15: 0140 [ 123.250024] FS: 7fa1cff602c0() GS:8e0a5730() knlGS: [ 123.252306] CS: 0010 DS: ES: CR0: 80050033 [ 123.254591] CR2: 001d CR3: 000111ccc006 CR4: 001726e0 [ 123.256899] Call Trace: [ 123.259174] [ 123.261406] blk_mq_submit_bio+0x8c/0x440 [ 123.263626] __submit_bio+0x109/0x1a0 [ 123.265795] __submit_bio_noacct+0x81/0x1f0 [ 123.267922] submit_bio_noacct_nocheck+0x91/0x120 [ 123.270016] ? blk_cgroup_bio_start+0xac/0x130 [ 123.272076] ? recalibrate_cpu_khz+0x10/0x10 [ 123.274114] ? ktime_get+0x46/0xc0 [ 123.276126] submit_bio_noacct+0x209/0x590 [ 123.278132] submit_bio+0x40/0xf0 [ 123.280121] __blkdev_direct_IO_async+0x146/0x1f0 [ 123.282108] blkdev_direct_IO.part.0+0x40/0xa0 [ 123.284097] blkdev_read_iter+0x9f/0x1a0 [ 123.286065] io_read+0xea/0x510 [ 123.288080] ? fget+0x83/0xc0 [ 123.290031] io_issue_sqe+0x61/0x440 [ 123.291960] ? io_init_req+0xfa/0x2f0 [ 123.293847] io_submit_sqes+0x141/0x4a0 [ 123.295703] ? __fget_light+0xb5/0x160 [ 123.297537] __do_sys_io_uring_enter+0x316/0x670 [ 123.299345] ? __secure_computing+0x9b/0x110 [ 123.301153] __x64_sys_io_uring_enter+0x22/0x40 [ 123.302900] do_syscall_64+0x5c/0x90 [ 123.304608] ? do_syscall_64+0x69/0x90 [ 123.306286] ? exit_to_user_mode_prepare+0x3b/0xd0 [ 123.307969] ? syscall_exit_to_user_mode+0x2a/0x50 [ 123.309605] ? do_syscall_64+0x69/0x90 [ 123.311176] ? do_syscall_64+0x69/0x90 [ 123.312717] ? sysvec_reschedule_ipi+0x7b/0x120 [ 123.314252] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 123.315791] RIP: 0033:0x7fa1d28855e1 [ 123.317314] Code: 89 55 e4 89 4d e0 4c 89 45 d8 4c 89 4d d0 44 8b 55 e0 4c 8b 45 d8 4c 8b 4d d0 b8 aa 01 00 00 8b 7d ec 8b 75 e8 8b 55 e4 0f 05 <48> 89 45 f8 48 8b 45 f8 5d c3 55 48 89 e5 48 83 ec 18 89 7d fc 89 [ 123.320664] RSP: 002b:7fa17550ae68 EFLAGS: 0216 ORIG_RAX: 01aa [ 123.322364] RAX: ffda RBX: 5603c0418a28 RCX: 7fa1d28855e1 [ 123.324060] RDX: RSI: 0001 RDI: 002d [ 123.325684] RBP: 7fa17550ae68 R08: R09: 0008 [ 123.327225] R10: R11: 0216 R12: 5603c0418b10 [ 123.328734] R13: 5603bdc48948 R14: 5603bdc48988 R15: [ 123.330247] [ 123.331740] Modules linked in: nft_masq nft_chain_nat zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter nf_tables nfnetlink vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock unix_diag tls bridge stp llc binfmt_misc intel_rapl_msr mei_pxp mei_hdcp intel_rapl_common x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi coretemp snd_hda_intel kvm_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi snd_hda_codec rapl intel_cstate snd_hda_core joydev snd_hwdep input_leds at24 mei_me
[Kernel-packages] [Bug 2023197] Re: Fix speaker volume too low on HP G10 laptops
** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress -- 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/2023197 Title: Fix speaker volume too low on HP G10 laptops Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: New Status in linux source package in Mantic: Incomplete Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [ Impact ] HP G10 laptops need the quirk ALC245_FIXUP_CS35L41_SPI_4_HP_GPIO_LED to enable all amplifiers to output audio with expected level. [ Test Plan ] * Power up the HP G10 series laptops and adjust the output volume to MAX * Verify speaker output volume by ears. [ Where problems could occur ] * The quirk is for Cirrus codec on particular HP series laptops. * The risk of regression should only impact particular models To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023638] Re: Various backlight issues with the 6.0/6.1 kernel
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1017.17 --- linux-oem-6.1 (6.1.0-1017.17) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1017.17 -proposed tracker (LP: #2026459) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper * CVE-2023-3269 - exec: Remove FOLL_FORCE for stack setup - mm: introduce new 'lock_mm_and_find_vma()' page fault helper - mm: make the page fault mmap locking killable - arm64/mm: Convert to using lock_mm_and_find_vma() - powerpc/mm: Convert to using lock_mm_and_find_vma() - mips/mm: Convert to using lock_mm_and_find_vma() - riscv/mm: Convert to using lock_mm_and_find_vma() - arm/mm: Convert to using lock_mm_and_find_vma() - mm/fault: convert remaining simple cases to lock_mm_and_find_vma() - powerpc/mm: convert coprocessor fault to lock_mm_and_find_vma() - mm: make find_extend_vma() fail if write lock not held - execve: expand new process stack manually ahead of time - mm: always expand the stack with the mmap write lock held - [CONFIG]: Set CONFIG_LOCK_MM_AND_FIND_VMA * CVE-2023-3389 - io_uring/poll: serialize poll linked timer start with poll removal * amd_pmf: AMD 7840HS cpufreq locked at 400-544MHz after power unplugged (LP: #2025670) - platform/x86/amd/pmf: Register notify handler only if SPS is enabled * Mute/mic LEDs no function on some HP Platforms (LP: #2025444) - ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on EliteBook * Various backlight issues with the 6.0/6.1 kernel (LP: #2023638) - ACPI: video: Stop trying to use vendor backlight control on laptops from after ~2012 * HDMI output with More than one child device for port B in VBT error (LP: #2025195) - SAUCE: drm/i915/quirks: Add multiple VBT quirk for HP ZBook Power G10 -- You-Sheng Yang Wed, 12 Jul 2023 11:26:03 +0800 ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3269 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3389 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2023638 Title: Various backlight issues with the 6.0/6.1 kernel Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] There are some new patches for new method to decide which backlight driver should be registered introduced since 6.1. And we backport some of them to 6.0-oem kernel which are not enough to solved all backlight issues. 1. dell_laptop created a non-working backlight driver before nvidia is loaded, that leads to the system can't adjust the display brightness. 2. acpi_backlight0 sometimes will be generated together with intel_backlight. [Fix] Below 2 commits from v6.3-rc6 prevent the acpi_backlight from being registered automatically(which have been included into ubuntu kernels through stable update) e506731c8f35 ACPI: video: Make acpi_backlight=video work independent from GPU driver 78dfc9d1d1ab ACPI: video: Add auto_detect arg to __acpi_video_get_backlight_type() Below patch prevents platform driver(dell_laptop) from creating backlight driver after win8. aa8a950a5d6b ACPI: video: Stop trying to use vendor backlight control on laptops from after ~2012 https://patchwork.kernel.org/project/linux-acpi/patch/20230608091258.7963-1-hdego...@redhat.com/ [Test] Verified on the dell platform which reports this issue. [Where problems could occur] The assumption of the not-yet-upstreamed commit regarding backlight control is that, after Windows 8, all laptop backlights are controlled either by ACPI or the native graphics driver. It impacts the laptops that do not follow the assumption and will lead to broken backlight interface. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 2025195] Re: HDMI output with More than one child device for port B in VBT error
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1017.17 --- linux-oem-6.1 (6.1.0-1017.17) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1017.17 -proposed tracker (LP: #2026459) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper * CVE-2023-3269 - exec: Remove FOLL_FORCE for stack setup - mm: introduce new 'lock_mm_and_find_vma()' page fault helper - mm: make the page fault mmap locking killable - arm64/mm: Convert to using lock_mm_and_find_vma() - powerpc/mm: Convert to using lock_mm_and_find_vma() - mips/mm: Convert to using lock_mm_and_find_vma() - riscv/mm: Convert to using lock_mm_and_find_vma() - arm/mm: Convert to using lock_mm_and_find_vma() - mm/fault: convert remaining simple cases to lock_mm_and_find_vma() - powerpc/mm: convert coprocessor fault to lock_mm_and_find_vma() - mm: make find_extend_vma() fail if write lock not held - execve: expand new process stack manually ahead of time - mm: always expand the stack with the mmap write lock held - [CONFIG]: Set CONFIG_LOCK_MM_AND_FIND_VMA * CVE-2023-3389 - io_uring/poll: serialize poll linked timer start with poll removal * amd_pmf: AMD 7840HS cpufreq locked at 400-544MHz after power unplugged (LP: #2025670) - platform/x86/amd/pmf: Register notify handler only if SPS is enabled * Mute/mic LEDs no function on some HP Platforms (LP: #2025444) - ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on EliteBook * Various backlight issues with the 6.0/6.1 kernel (LP: #2023638) - ACPI: video: Stop trying to use vendor backlight control on laptops from after ~2012 * HDMI output with More than one child device for port B in VBT error (LP: #2025195) - SAUCE: drm/i915/quirks: Add multiple VBT quirk for HP ZBook Power G10 -- You-Sheng Yang Wed, 12 Jul 2023 11:26:03 +0800 ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3269 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3389 -- 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/2025195 Title: HDMI output with More than one child device for port B in VBT error Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The HDMI monitor doesn't work, no events while plug/unplug then cable. [Fix] From the bug report[1], skip the return workaround the issue, so I created the DMI quirk to list affected platforms. Intel is submitting patches[2][3] to fix the issue, but it requires to backport huge drm structure changes, too. As there is no regression found with this workaround, it's safer to use the DMI quirk to handle this issue. 1. https://gitlab.freedesktop.org/drm/intel/-/issues/7709 2. https://patchwork.freedesktop.org/series/117641/ 3. https://patchwork.freedesktop.org/series/114200/ [Test] Verified by me, FE, and ODM. [Where problems could occur] I have no idea what might happen, so only make the workaround avaiable on the listed platforms. So far, no regressions have been observed with plug/unplug, switch modes, reboot, and suspend tests. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025444] Re: Mute/mic LEDs no function on some HP Platforms
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1017.17 --- linux-oem-6.1 (6.1.0-1017.17) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1017.17 -proposed tracker (LP: #2026459) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper * CVE-2023-3269 - exec: Remove FOLL_FORCE for stack setup - mm: introduce new 'lock_mm_and_find_vma()' page fault helper - mm: make the page fault mmap locking killable - arm64/mm: Convert to using lock_mm_and_find_vma() - powerpc/mm: Convert to using lock_mm_and_find_vma() - mips/mm: Convert to using lock_mm_and_find_vma() - riscv/mm: Convert to using lock_mm_and_find_vma() - arm/mm: Convert to using lock_mm_and_find_vma() - mm/fault: convert remaining simple cases to lock_mm_and_find_vma() - powerpc/mm: convert coprocessor fault to lock_mm_and_find_vma() - mm: make find_extend_vma() fail if write lock not held - execve: expand new process stack manually ahead of time - mm: always expand the stack with the mmap write lock held - [CONFIG]: Set CONFIG_LOCK_MM_AND_FIND_VMA * CVE-2023-3389 - io_uring/poll: serialize poll linked timer start with poll removal * amd_pmf: AMD 7840HS cpufreq locked at 400-544MHz after power unplugged (LP: #2025670) - platform/x86/amd/pmf: Register notify handler only if SPS is enabled * Mute/mic LEDs no function on some HP Platforms (LP: #2025444) - ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on EliteBook * Various backlight issues with the 6.0/6.1 kernel (LP: #2023638) - ACPI: video: Stop trying to use vendor backlight control on laptops from after ~2012 * HDMI output with More than one child device for port B in VBT error (LP: #2025195) - SAUCE: drm/i915/quirks: Add multiple VBT quirk for HP ZBook Power G10 -- You-Sheng Yang Wed, 12 Jul 2023 11:26:03 +0800 ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3269 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3389 -- 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/2025444 Title: Mute/mic LEDs no function on some HP Platforms Status in OEM Priority Project: Fix Committed Status in linux-oem-6.1 package in Ubuntu: New Status in linux-oem-6.1 source package in Jammy: Fix Released Bug description: [Impact] The mic mute/audio mute LEDS are not work on some HP Platforms [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk on linux-oem-6.1, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2025444/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025670] Re: amd_pmf: AMD 7840HS cpufreq locked at 400-544MHz after power unplugged
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1017.17
---
linux-oem-6.1 (6.1.0-1017.17) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1017.17 -proposed tracker (LP: #2026459)
* Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
* CVE-2023-3269
- exec: Remove FOLL_FORCE for stack setup
- mm: introduce new 'lock_mm_and_find_vma()' page fault helper
- mm: make the page fault mmap locking killable
- arm64/mm: Convert to using lock_mm_and_find_vma()
- powerpc/mm: Convert to using lock_mm_and_find_vma()
- mips/mm: Convert to using lock_mm_and_find_vma()
- riscv/mm: Convert to using lock_mm_and_find_vma()
- arm/mm: Convert to using lock_mm_and_find_vma()
- mm/fault: convert remaining simple cases to lock_mm_and_find_vma()
- powerpc/mm: convert coprocessor fault to lock_mm_and_find_vma()
- mm: make find_extend_vma() fail if write lock not held
- execve: expand new process stack manually ahead of time
- mm: always expand the stack with the mmap write lock held
- [CONFIG]: Set CONFIG_LOCK_MM_AND_FIND_VMA
* CVE-2023-3389
- io_uring/poll: serialize poll linked timer start with poll removal
* amd_pmf: AMD 7840HS cpufreq locked at 400-544MHz after power unplugged
(LP: #2025670)
- platform/x86/amd/pmf: Register notify handler only if SPS is enabled
* Mute/mic LEDs no function on some HP Platforms (LP: #2025444)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on
EliteBook
* Various backlight issues with the 6.0/6.1 kernel (LP: #2023638)
- ACPI: video: Stop trying to use vendor backlight control on laptops from
after ~2012
* HDMI output with More than one child device for port B in VBT error
(LP: #2025195)
- SAUCE: drm/i915/quirks: Add multiple VBT quirk for HP ZBook Power G10
-- You-Sheng Yang Wed, 12 Jul 2023
11:26:03 +0800
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3269
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3389
--
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/2025670
Title:
amd_pmf: AMD 7840HS cpufreq locked at 400-544MHz after power unplugged
Status in linux package in Ubuntu:
New
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:
Fix Released
Status in linux source package in Lunar:
New
Status in linux-oem-6.1 source package in Lunar:
Invalid
Status in linux source package in Mantic:
New
Status in linux-oem-6.1 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2025670
[Impact]
Call trace dumped in events workqueue power_supply_changed_work, and
cpufreq locked to 400-544MHz.
```
[ 22.592162] Call Trace:
[ 22.592164]
[ 22.592164] ? rcu_note_context_switch+0x5e0/0x660
[ 22.592166] ? __warn+0x81/0x130
[ 22.592171] ? rcu_note_context_switch+0x5e0/0x660
[ 22.592172] ? report_bug+0x171/0x1a0
[ 22.592175] ? prb_read_valid+0x1b/0x30
[ 22.592177] ? handle_bug+0x3c/0x80
[ 22.592178] ? exc_invalid_op+0x17/0x70
[ 22.592179] ? asm_exc_invalid_op+0x1a/0x20
[ 22.592182] ? rcu_note_context_switch+0x5e0/0x660
[ 22.592183] ? acpi_ut_delete_object_desc+0x86/0xb0
[ 22.592186] ? acpi_ut_update_ref_count.part.0+0x22d/0x930
[ 22.592187] __schedule+0xc0/0x1410
[ 22.592189] ? ktime_get+0x3c/0xa0
[ 22.592191] ? lapic_next_event+0x1d/0x30
[ 22.592193] ? hrtimer_start_range_ns+0x25b/0x350
[ 22.592196] schedule+0x5e/0xd0
[ 22.592197] schedule_hrtimeout_range_clock+0xbe/0x140
[ 22.592199] ? __pfx_hrtimer_wakeup+0x10/0x10
[ 22.592200] usleep_range_state+0x64/0x90
[ 22.592203] amd_pmf_send_cmd+0x106/0x2a0 [amd_pmf
bddfe0fe3712aaa99acce3d5487405c5213c6616]
[ 22.592207] amd_pmf_update_slider+0x56/0x1b0 [amd_pmf
bddfe0fe3712aaa99acce3d5487405c5213c6616]
[ 22.592210] amd_pmf_set_sps_power_limits+0x72/0x80 [amd_pmf
bddfe0fe3712aaa99acce3d5487405c5213c6616]
[ 22.592213] amd_pmf_pwr_src_notify_call+0x49/0x90 [amd_pmf
bddfe0fe3712aaa99acce3d5487405c5213c6616]
[ 22.592216] notifier_call_chain+0x5a/0xd0
[ 22.592218] atomic_notifier_call_chain+0x32/0x50
```
[Fix]
Upstream v6.4 fixed with commit
[146b6f6855e76](https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-
drivers-x86.git/commit/?h=fixes=146b6f6855e7656e8329910606595220c761daac)
("platform/x86/amd/pmf: Register notify handler only if SPS is
enabled"). It has also been backported to stable trees v6.1.36
(oem-6.1 in v6.1.34 now), v6.2.15 (linux/lunar in v6.2.13 now),
v6.3.10 (linux/mantic in
[Kernel-packages] [Bug 2027914] Re: missing nvidia kernel module for generic kernel (linux-objects-nvidia-535-6.2.0-25-generic)
Hello Andrew, Regarding https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/2027592, I personally experienced two different root causes for black screens during kernel updates: 1) apt is holding back linux-modules-nvidia-*-generic. This happened to me at least three times. See https://www.reddit.com/r/Ubuntu/comments/12efuxu/nvidia_drivers_regularly_borked_by_phased_updates/. 2) linux-modules-nvidia-535-6.2.0-25-generic does not exist. This happened to me with the combination of linux-generic 6.2.0-25 and nvidia-driver-535. See the discussion in this ticket. I also experienced a black screen during the update from nvidia-driver-525 to nvidia-driver-535. This was without a kernel update. See https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2025640. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2027914 Title: missing nvidia kernel module for generic kernel (linux-objects- nvidia-535-6.2.0-25-generic) Status in linux-restricted-modules package in Ubuntu: Confirmed Bug description: For latest generic kernel for Ubuntu 23.04 there in no package of kernel module. Present is for previous kernel: # aptitude search linux-objects-nvidia-535.*generic i A linux-objects-nvidia-535-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-open-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-open-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) There is no package for 6.2.0-25 kernel. So after upgrade to new kernel - gpu isn't working, as the module is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2027914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025538] Re: Unrequested kernel update
ok i think someone is joking here with us? Got today a update notification, thouhgt "oh wow finaly someone did something usefull" with the result Again blinking screens... Again errors all over the system... Now with no possibility to even try another driver since apt runs into a timeout (WTF?) ... manual try to fix it runs into install errors the like "no kernel header sources found" (Seriously?) And here i see now a status that it is in progress? Hell? What will you write if you will accept that it is a mess? Status "Aptmaggedon, all hope is lost, go and install windows!!!11!one!1eleven!" ? Please forget that bulls*ht about agile and do at least some of that oldschool basic quality checks ... in the about 30 years before you pretend to be developers that uncool quality check stuff had worked just fine and there wasn't such mess after the millenium parties... So please get your stuff together and make it at least stable or give an open statement that you aren't able to do that stuff of work so that everyone can take the conclusions and can decide if there is further hope for ubuntu or knows then at least who are the culprits in person who messed up a once glorious and brilliant OS so that we can do serious jokes about them in reddit if there isn't much other stuff we can do Sorry but i am totaly frustrated... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-restricted-modules package in Ubuntu: Triaged Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2025538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028165] Re: nvidia-dkms-* FTBS with linux 6.5
** Changed in: nvidia-graphics-drivers-390 (Ubuntu Mantic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Mantic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Mantic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Mantic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Mantic) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Mantic) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Mantic) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Mantic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/2028165 Title: nvidia-dkms-* FTBS with linux 6.5 Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-525 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 source package in Mantic: In Progress Status in nvidia-graphics-drivers-470 source package in Mantic: In Progress Status in nvidia-graphics-drivers-470-server source package in Mantic: In Progress Status in nvidia-graphics-drivers-525 source package in Mantic: In Progress Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21, from /var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function ‘NV_GET_USER_PAGES_REMOTE’: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] 164 |return get_user_pages_remote(tsk, mm, start, nr_pages, flags, | ^~~ | | | struct task_struct * ... [Fix] Apply the attached fix. [How to test] Install (and build) the patched packet. [Regression potential] The fix is composed of two patches: 1) the first patch simply garbage collect a reference to a function that was never used but that had the API changed in Linux 6.5 - so, it's a trivial change. 2) the second patch actually reimplement part of the vma scanning that was removed in __get_user_pages_locked() in upstream commit b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas array from internal GUP functions" - here is where most likely any regression could be found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028557] Re: package linux-image-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
so now with a crippled system, which is working somehow more bad than anything else now at least, so i can give some more input Got update notifications that there is a new nvidia driver and new kernel available... try to install it, got timeouts in apt-get update, even with apt-get update -uf... Try to restart, system went up with blinking screens... so i got a totaly useless system (again, the god knows which messed up update count i got since march) Try to install the stuff via synaptic, got a final error message of linux header sources not installed... Try to change driver... Got timeout messages... so it is impossible to use another driver ... So i can only guess that there is some serious kernel and nvidia driver problem since march running and no one cared so far and on top there is some repository issue since apt runs into some nasty timeouts... Please find some one to fix that mess Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2028557 Title: package linux-image-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: dont know what you messed up, but you messed it royally up, my screen is blinking and i cant't see anythiong so i havE HEADACHES AND TRY TO FILL OUT a bug report blindly -.- please fix that since march i have only problems with ubuntu... and no one seems to care at the developers side -.- ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teri 3532 F wireplumber /dev/snd/controlC1: teri 3532 F wireplumber /dev/snd/seq:teri 3529 F pipewire CasperMD5CheckResult: unknown Date: Mon Jul 24 16:12:38 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2019-10-08 (1384 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-25-generic root=UUID=b6e53f2c-9bcd-47b4-8f20-6e8d8de82741 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: Upgraded to lunar on 2023-04-08 (107 days ago) dmi.bios.date: 08/20/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22:bd08/20/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2028557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024900] Re: Disable hv-kvp-daemon if /dev/vmbus/hv_kvp is not present
** Tags removed: verification-needed-focal verification-needed-jammy verification-needed-lunar ** Tags added: verification-done-focal verification-done-jammy verification-done-lunar -- 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/2024900 Title: Disable hv-kvp-daemon if /dev/vmbus/hv_kvp is not present Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] If the daemon is started and the vmbus is not present it will just exit with an error: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/tree/tools/hv/hv_kvp_daemon.c#n1424 Thus, it would make sense to add "ConditionPathExists=/dev/vmbus/hv_kvp" in linux-cloud-tools- common.hv-kvp-daemon.service to prevent systemd from starting the daemon if the device is not there. [Test Plan] Start an Azure cloud instance and check for /dev/vmbus/hv_kvp and that hv-kvp-daemon is running. Start a non-Azure cloud instance and check that hv-kvp-daemon is not running. [Regression potential] Its possible that kv-hvp-daemon is not started when it should be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028557] Re: package linux-image-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2028557 Title: package linux-image-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: dont know what you messed up, but you messed it royally up, my screen is blinking and i cant't see anythiong so i havE HEADACHES AND TRY TO FILL OUT a bug report blindly -.- please fix that since march i have only problems with ubuntu... and no one seems to care at the developers side -.- ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teri 3532 F wireplumber /dev/snd/controlC1: teri 3532 F wireplumber /dev/snd/seq:teri 3529 F pipewire CasperMD5CheckResult: unknown Date: Mon Jul 24 16:12:38 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2019-10-08 (1384 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-25-generic root=UUID=b6e53f2c-9bcd-47b4-8f20-6e8d8de82741 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: Upgraded to lunar on 2023-04-08 (107 days ago) dmi.bios.date: 08/20/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22:bd08/20/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2028557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028557] [NEW] package linux-image-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Public bug reported: dont know what you messed up, but you messed it royally up, my screen is blinking and i cant't see anythiong so i havE HEADACHES AND TRY TO FILL OUT a bug report blindly -.- please fix that since march i have only problems with ubuntu... and no one seems to care at the developers side -.- ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teri 3532 F wireplumber /dev/snd/controlC1: teri 3532 F wireplumber /dev/snd/seq:teri 3529 F pipewire CasperMD5CheckResult: unknown Date: Mon Jul 24 16:12:38 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2019-10-08 (1384 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-25-generic root=UUID=b6e53f2c-9bcd-47b4-8f20-6e8d8de82741 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: Upgraded to lunar on 2023-04-08 (107 days ago) dmi.bios.date: 08/20/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22:bd08/20/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2028557 Title: package linux-image-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: dont know what you messed up, but you messed it royally up, my screen is blinking and i cant't see anythiong so i havE HEADACHES AND TRY TO FILL OUT a bug report blindly -.- please fix that since march i have only problems with ubuntu... and no one seems to care at the developers side -.- ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teri 3532 F wireplumber /dev/snd/controlC1: teri 3532 F wireplumber /dev/snd/seq:teri 3529 F pipewire CasperMD5CheckResult: unknown Date: Mon Jul 24 16:12:38 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2019-10-08 (1384 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-25-generic root=UUID=b6e53f2c-9bcd-47b4-8f20-6e8d8de82741 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: Upgraded to lunar on 2023-04-08 (107 days ago) dmi.bios.date: 08/20/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS
[Kernel-packages] [Bug 2028165] Re: nvidia-dkms-* FTBS with linux 6.5
** Also affects: nvidia-graphics-drivers-470-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/2028165 Title: nvidia-dkms-* FTBS with linux 6.5 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-470-server package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: New Status in nvidia-graphics-drivers-390 source package in Mantic: New Status in nvidia-graphics-drivers-470 source package in Mantic: New Status in nvidia-graphics-drivers-470-server source package in Mantic: New Status in nvidia-graphics-drivers-525 source package in Mantic: New Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21, from /var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function ‘NV_GET_USER_PAGES_REMOTE’: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] 164 |return get_user_pages_remote(tsk, mm, start, nr_pages, flags, | ^~~ | | | struct task_struct * ... [Fix] Apply the attached fix. [How to test] Install (and build) the patched packet. [Regression potential] The fix is composed of two patches: 1) the first patch simply garbage collect a reference to a function that was never used but that had the API changed in Linux 6.5 - so, it's a trivial change. 2) the second patch actually reimplement part of the vma scanning that was removed in __get_user_pages_locked() in upstream commit b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas array from internal GUP functions" - here is where most likely any regression could be found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024479] Re: kdump fails on big arm64 systems when offset is not specified
# VERIFICATION FOCAL kexec-tools & hwe kernel 5.15 For this set of verification we test both kexec-tools and kernel 5.15 from proposed.. 1) On a focal machine with 184G of memory, installed kexec-tools and hwe kernel 5.15 from proposed and triggered a crash. Crashdump file is generated successfully. root@bigfossa:/var/crash# uname -rv 5.15.0-1043-azure #50~20.04.1-Ubuntu SMP Wed Jul 19 16:39:01 UTC 2023 root@bigfossa:/var/crash# dpkg -l | grep kexec-tools ii kexec-tools 1:2.0.18-1ubuntu1.1 arm64tools to support fast kexec reboots root@bigfossa:/var/crash# cat /etc/default/grub.d/kdump-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" root@bigfossa:/var/crash# ls 202307211020/ dmesg.202307211020 dump.202307211020 root@bigfossa:/var/crash# 2) On a jammy machine with 4G of memory, installed kexec-tools and hwe kernel 5.15 from proposed and triggered a crash. Crashdump file is generated successfully. root@smallfossa:/var/crash# uname -rv 5.15.0-1043-azure #50~20.04.1-Ubuntu SMP Wed Jul 19 16:39:01 UTC 2023 root@smallfossa:/var/crash# dpkg -l | grep kexec-tools ii kexec-tools 1:2.0.18-1ubuntu1.1 arm64tools to support fast kexec reboots root@smallfossa:/var/crash# cat /etc/default/grub.d/kdump-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=320M" root@smallfossa:/var/crash# ls 202307241309/ dmesg.202307241309 dump.202307241309 root@smallfossa:/var/crash# ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on big arm64 systems when offset is not specified Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in kexec-tools source package in Focal: Fix Committed Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.15 source package in Focal: In Progress Status in kexec-tools source package in Jammy: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-hwe-5.15 source package in Jammy: Invalid Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in linux-hwe-5.15 source package in Kinetic: Invalid Status in kexec-tools source package in Lunar: Fix Committed Status in kexec-tools source package in Mantic: Fix Released Bug description: [Impact] kdump fails on arm64, on machines with a lot of memory when offset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel region. [Fix] To address this issue the following upstream commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the Focal 5.15 hwe kernel (from Jammy) will be fixed. [Test Plan] You need an arm64 machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump, configure the crash kernel size, and trigger a crash. 1) Failing scenario (crashkernel >= 4G, without offset "@"): It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. 2) Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G') This must continue to work with the new patches (ie, no regressions), including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on Focal).
[Kernel-packages] [Bug 2024479] Re: kdump fails on big arm64 systems when offset is not specified
# VERIFICATION FOCAL kexec-tools & kernel 5.4 For this set of verifications we will test the kexec-tools in -proposed with the 5.4 kernel. The 5.4 kernel will not work in cases where the crashkernel need to be allocated in both low and high memory because we have not patched it. Therefore the tests are done only on a test machine with little memory. The purpose is to confirm that kexec-tools in -proposed does not introduce regressions. 1) Not applicable. 2) On a focal machine with 4G of memory, running 5.4 kernel installed kexec-tools from proposed and triggered a crash. Crashdump file is generated successfully. root@smallfossa:/var/crash# uname -rv 5.4.0-1113-azure #119-Ubuntu SMP Wed Jul 19 16:08:59 UTC 2023 root@smallfossa:/var/crash# dpkg -l | grep kexec-tools ii kexec-tools 1:2.0.18-1ubuntu1.1 arm64tools to support fast kexec reboots root@smallfossa:/var/crash# cat /etc/default/grub.d/kdump-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=320M" root@smallfossa:/var/crash# ls 202307241318/ dmesg.202307241318 dump.202307241318 root@smallfossa:/var/crash# -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on big arm64 systems when offset is not specified Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in kexec-tools source package in Focal: Fix Committed Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.15 source package in Focal: In Progress Status in kexec-tools source package in Jammy: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-hwe-5.15 source package in Jammy: Invalid Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in linux-hwe-5.15 source package in Kinetic: Invalid Status in kexec-tools source package in Lunar: Fix Committed Status in kexec-tools source package in Mantic: Fix Released Bug description: [Impact] kdump fails on arm64, on machines with a lot of memory when offset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel region. [Fix] To address this issue the following upstream commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the Focal 5.15 hwe kernel (from Jammy) will be fixed. [Test Plan] You need an arm64 machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump, configure the crash kernel size, and trigger a crash. 1) Failing scenario (crashkernel >= 4G, without offset "@"): It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. 2) Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G') This must continue to work with the new patches (ie, no regressions), including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on Focal). [Regression Potential] KERNEL 5.15 - Jammy (and Focal via the HWE kernel): To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot
[Kernel-packages] [Bug 2028550] [NEW] Backport support to tolerate ZSTD compressed firmware files
Public bug reported: [ Impact ] * To ensure reliable dist-upgrades in case of partial upgrades or upgrade failures, it is desirable for LTS GA kernel to support features that next-LTS GA kernel will rely on. * Specifically it is being discussed to switch linux-firmware to ZSTD compressed one * To ensure that failed dist-upgrades can still boot after-partial upgrade it is desirable to suppport zstd compressed firmware [ Test Plan ] * Boot new build of GA linux kernel with CONFIG_FW_LOADER_COMPRESS_ZSTD * Check that existing firmware files loaded on a given machine can be compressed with zstd and still loaded by this kernel * Check that depmod / initramfs-tools all support .zst compressed firmware [ Where problems could occur ] * Once this is inroduced in jammy-GA kernel it may cripple into focal- hwe kernels too, and people may start relying on this feature despite not universally supported by all other focal kernels. This should be trivial to catch in SRUs for example, do not accept SRUs of firmwares that ship themselves as .zst in Jammy and lower. [ Other Info ] * See https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042652.html ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028550 Title: Backport support to tolerate ZSTD compressed firmware files Status in linux package in Ubuntu: New Bug description: [ Impact ] * To ensure reliable dist-upgrades in case of partial upgrades or upgrade failures, it is desirable for LTS GA kernel to support features that next-LTS GA kernel will rely on. * Specifically it is being discussed to switch linux-firmware to ZSTD compressed one * To ensure that failed dist-upgrades can still boot after-partial upgrade it is desirable to suppport zstd compressed firmware [ Test Plan ] * Boot new build of GA linux kernel with CONFIG_FW_LOADER_COMPRESS_ZSTD * Check that existing firmware files loaded on a given machine can be compressed with zstd and still loaded by this kernel * Check that depmod / initramfs-tools all support .zst compressed firmware [ Where problems could occur ] * Once this is inroduced in jammy-GA kernel it may cripple into focal-hwe kernels too, and people may start relying on this feature despite not universally supported by all other focal kernels. This should be trivial to catch in SRUs for example, do not accept SRUs of firmwares that ship themselves as .zst in Jammy and lower. [ Other Info ] * See https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042652.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028165] Re: nvidia-dkms-* FTBS with linux 6.5
** Patch added: "nvidia-graphics-drivers-470_470.199.02-0ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2028165/+attachment/5688058/+files/nvidia-graphics-drivers-470_470.199.02-0ubuntu2.debdiff -- 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/2028165 Title: nvidia-dkms-* FTBS with linux 6.5 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: New Status in nvidia-graphics-drivers-390 source package in Mantic: New Status in nvidia-graphics-drivers-470 source package in Mantic: New Status in nvidia-graphics-drivers-525 source package in Mantic: New Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21, from /var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function ‘NV_GET_USER_PAGES_REMOTE’: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] 164 |return get_user_pages_remote(tsk, mm, start, nr_pages, flags, | ^~~ | | | struct task_struct * ... [Fix] Apply the attached fix. [How to test] Install (and build) the patched packet. [Regression potential] The fix is composed of two patches: 1) the first patch simply garbage collect a reference to a function that was never used but that had the API changed in Linux 6.5 - so, it's a trivial change. 2) the second patch actually reimplement part of the vma scanning that was removed in __get_user_pages_locked() in upstream commit b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas array from internal GUP functions" - here is where most likely any regression could be found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017006] Re: fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
The solution suggested above was rejected on the kernel when I submitted the
change where we expose the parent kernel abi
https://lists.ubuntu.com/archives/kernel-team/2023-June/140090.html
This led to a new proposal that would introduce a configure script used during
build (or before) and it would automatically detect the signature changes in
the linux header. This solution would remove the need for versioning.
Since this change is a deviation from upstream, I sent it there but it was
rejected. You can see the discussion here
https://lore.kernel.org/lttng-dev/2c6e0b29-0e88-4dc7-6691-7a89a5428...@efficios.com/T/#t.
They are not willing to change an approach that works most of the time for our
particular use case because it would be difficult for them to maintain the new
change, even though I volunteer to help them maintain the configure script...
I went back to our kernel mailing list and suggested to go back to my
original proposal but it was still rejected. Discussion is here
https://lists.ubuntu.com/archives/kernel-team/2023-July/140822.html
Conclusion: Lttng-module upstream refused to accept a better proposal of
dealing with changes in linux kernel headers and the solution where we
expose a kernel abi is gonna add technical debt to our kernel and it's
not worth doing it for a kernel that's gonna be EOL soon. And as for
jammy and lunar kernels, they should be replaced soon by 6.2 kernels.
I am not sure how I should try again convincing upstream, but I will at
some point.
--
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/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
Invalid
Status in lttng-modules package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in lttng-modules source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in lttng-modules source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Invalid
Status in lttng-modules source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Invalid
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name,
[Kernel-packages] [Bug 2017006] Re: fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
** Changed in: lttng-modules (Ubuntu)
Status: In Progress => Won't Fix
** Changed in: lttng-modules (Ubuntu Jammy)
Status: Fix Committed => Won't Fix
** Changed in: lttng-modules (Ubuntu Kinetic)
Status: Confirmed => Won't Fix
** Changed in: lttng-modules (Ubuntu Lunar)
Status: Fix Committed => Won't Fix
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Invalid
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Invalid
** Changed in: linux (Ubuntu Kinetic)
Status: In Progress => Invalid
** Changed in: linux (Ubuntu Lunar)
Status: In Progress => Invalid
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
Invalid
Status in lttng-modules package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in lttng-modules source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in lttng-modules source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Invalid
Status in lttng-modules source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Invalid
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
[Kernel-packages] [Bug 2023176] Re: system hang after running stress-ng softlockup stressor while iwlwifi is connected to the station
** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-intel-iotg (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-intel-iotg (Ubuntu Focal) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) ** Changed in: linux-intel-iotg (Ubuntu Jammy) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2023176 Title: system hang after running stress-ng softlockup stressor while iwlwifi is connected to the station Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Focal: Fix Committed Status in linux-intel-iotg source package in Jammy: Fix Committed Bug description: [ Impact ] * system got hang after running stress-ng softlockup test while iwlwifi is connected to the station [ Test Plan ] * connect wifi (iwlwifi) to any station. (must do this) * execute the following command: $ sudo stress-ng --softlockup NUM_CPU_CORES --timeout 30 * make sure the system still responses after testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2023176/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025106] Re: No sounds output after resume from shutdown and reboot
** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2025106 Title: No sounds output after resume from shutdown and reboot Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: Fix Committed Bug description: [ Impact ] * when unmuting mic, there is no sound output after resuming or rebooting. unless mute and unmute the mic again. [ Test Plan ] * boot into the system and unmute the mic by alsamixer. * reboot or suspend/resume * make sure there is sound from the speaker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2025106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026470] Re: AX210 (8086:6024) WLAN init failed ucode -5 on 5.15 intel IoTG kernel
** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-intel-iotg (Ubuntu Jammy) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2026470 Title: AX210 (8086:6024) WLAN init failed ucode -5 on 5.15 intel IoTG kernel Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: Fix Committed Bug description: [Summary] AX210 (8086:6024) WLAN init failed ucode -5 on 5.15 Intel IoTG kernel. [Steps to reproduce] install 5.15 Intel IoTG kernel. [Expected result] WLAN works with no problem. [Actual result] Can't detect WLAN. [Failure rate] 100% The ucode version 66 would not be loaded successfully on this model with the folloing error messages: [5.704854] iwlwifi :01:00.0: Detected RF GF, rfid=0x10d000 [5.706056] iwlwifi :01:00.0: Microcode SW error detected. Restarting 0x0. [5.706258] iwlwifi :01:00.0: Start IWL Error Log Dump: [5.706265] iwlwifi :01:00.0: Transport status: 0x004A, valid: 6 [5.706273] iwlwifi :01:00.0: Loaded firmware version: 66.f1c864e0.0 ty-a0-gf-a0-66.ucode [5.706281] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [5.706288] iwlwifi :01:00.0: 0x002002F0 | trm_hw_status0 [5.706294] iwlwifi :01:00.0: 0x | trm_hw_status1 [5.706299] iwlwifi :01:00.0: 0x004DA722 | branchlink2 [5.706306] iwlwifi :01:00.0: 0x004D0CCE | interruptlink1 [5.706311] iwlwifi :01:00.0: 0x004D0CCE | interruptlink2 ... [6.726292] iwlwifi :01:00.0: Failed to run INIT ucode: -5 Since ucode version 63 works well on this, and we did the api version limitation to the same series model (8086:6020) before, so do the trick as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2026470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028059] Re: remove debug kernel notice in dmesg caused by trace_printk()
** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-intel-iotg (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-intel-iotg (Ubuntu Focal) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) ** Changed in: linux-intel-iotg (Ubuntu Jammy) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2028059 Title: remove debug kernel notice in dmesg caused by trace_printk() Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Focal: Fix Committed Status in linux-intel-iotg source package in Jammy: Fix Committed Bug description: [Impact] a test kernel notice in dmesg would confuse users. [Test Plan] 1. compile test. 2. install the kernel and boot into it. 3. check there is no test kernel notice in dmesg. [Regression potential] Low. remove/replace trace_printk does not affect the functions. [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2028059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB
Hi Steve Langasek, I reinstalled today my PC with Ubuntu Desktop IOT. And i use latest packages from proposed repository. This issue is now resolved. My PC now running this: Kernel version: 5.15.0-1035-intel-iotg #40-Ubuntu SMP Fri Jul 14 08:03:36 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Mutter version: dpkg -l | grep mutter ii gir1.2-mutter-10:amd64 42.9-0ubuntu4 amd64GObject introspection data for Mutter ii libmutter-10-0:amd64 42.9-0ubuntu4 amd64window manager library from the Mutter window manager ii mutter-common 42.9-0ubuntu4 all shared files for the Mutter window manager Thank you Daniel and Unnikrishnan for your support. A good day. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in linux-oem-5.17 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workarounds ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment or upgrade to a newer kernel: sudo apt install linux-generic-hwe-22.04 [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027814] Re: subiquity crash when installing kernel on Dell Precision 3660
if I refresh the installer the issue also occurs, when or after
installing Kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2027814
Title:
subiquity crash when installing kernel on Dell Precision 3660
Status in linux-signed-hwe-5.15 package in Ubuntu:
New
Bug description:
This issue does not occur when installing on a vSphere virtual machine
on ESXi 7.0.3 or 8.0.1.
just using a basic autoinstall config
#cloud-config
autoinstall:
version: 1
keyboard:
layout: gb
toggle: null
locale: en_GB.UTF-8
identity:
hostname: ubuntu-focal
password:
"$6$exDY1mhS4KUYCE/2$zmn9ToZwTKLhCw.b4/b.ZRTIZM30JZ4QrOQ2aOXJ8yk96xpcCof0kxKwuX1kqLG/ygbJ1f8wxED22bTL4F46P0"
username: administrator
realname: 'Mr Administrator'
packages:
- build-essential
- ubuntu-desktop
- net-tools
- realmd
- libnss-sss
- libpam-sss
- sssd
- sssd-tools
- adcli
- samba-common-bin
- oddjob
- oddjob-mkhomedir
- packagekit
- samba
- krb5-user
- ntp
- ntpdate
ssh:
allow-pw: true
authorized-keys: []
install-server: true
updates: all
timezone: "Europe/London"
regular crash when trying to Install Kernel, HWE Kernel used to support newer
hardware network interface which is not included in standard kernel.
1689345611.836603403.install_fail.crash
ProblemType: Bug
Architecture: amd64
CrashDB: {'impl': 'launchpad', 'project': 'subiquity'}
Description:Ubuntu 20.04.6 LTS
Release:20.04
dmi.bios.date: 05/16/2023
dmi.bios.release: 2.5
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.5.1
dmi.board.name: 0J1C3P
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.3
dmi.modalias:
dmi:bvnDellInc.:bvr2.5.1:bd05/16/2023:br2.5:efr1.3:svnDellInc.:pnPrecision3660:pvr:rvnDellInc.:rn0J1C3P:rvrA00:cvnDellInc.:ct3:cvr:sku0A9F:
dmi.product.family: Precision
dmi.product.name: Precision 3660
dmi.product.sku: 0A9F
dmi.sys.vendor: Dell Inc.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.15.0-67-generic (not installed)
Uname: Linux 5.15.0-67-generic x86_64
Architecture: amd64
Date: Fri Jul 14 15:57:34 2023
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-hwe-5.15
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2027814/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027814] Re: subiquity crash when installing kernel on Dell Precision 3660
went back to basics today, and write the iso I'm using to different
flash drives using Rufus and Ventoy, both show a crash as above.
also created a basic config from the media and also sever from web
server, and also crashes in the same place with
cat > user-data << 'EOF'
#cloud-config
autoinstall:
version: 1
identity:
hostname: ubuntu-server
password:
"$6$exDY1mhS4KUYCE/2$zmn9ToZwTKLhCw.b4/b.ZRTIZM30JZ4QrOQ2aOXJ8yk96xpcCof0kxKwuX1kqLG/ygbJ1f8wxED22bTL4F46P0"
username: ubuntu
EOF
touch meta-data
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2027814
Title:
subiquity crash when installing kernel on Dell Precision 3660
Status in linux-signed-hwe-5.15 package in Ubuntu:
New
Bug description:
This issue does not occur when installing on a vSphere virtual machine
on ESXi 7.0.3 or 8.0.1.
just using a basic autoinstall config
#cloud-config
autoinstall:
version: 1
keyboard:
layout: gb
toggle: null
locale: en_GB.UTF-8
identity:
hostname: ubuntu-focal
password:
"$6$exDY1mhS4KUYCE/2$zmn9ToZwTKLhCw.b4/b.ZRTIZM30JZ4QrOQ2aOXJ8yk96xpcCof0kxKwuX1kqLG/ygbJ1f8wxED22bTL4F46P0"
username: administrator
realname: 'Mr Administrator'
packages:
- build-essential
- ubuntu-desktop
- net-tools
- realmd
- libnss-sss
- libpam-sss
- sssd
- sssd-tools
- adcli
- samba-common-bin
- oddjob
- oddjob-mkhomedir
- packagekit
- samba
- krb5-user
- ntp
- ntpdate
ssh:
allow-pw: true
authorized-keys: []
install-server: true
updates: all
timezone: "Europe/London"
regular crash when trying to Install Kernel, HWE Kernel used to support newer
hardware network interface which is not included in standard kernel.
1689345611.836603403.install_fail.crash
ProblemType: Bug
Architecture: amd64
CrashDB: {'impl': 'launchpad', 'project': 'subiquity'}
Description:Ubuntu 20.04.6 LTS
Release:20.04
dmi.bios.date: 05/16/2023
dmi.bios.release: 2.5
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.5.1
dmi.board.name: 0J1C3P
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.3
dmi.modalias:
dmi:bvnDellInc.:bvr2.5.1:bd05/16/2023:br2.5:efr1.3:svnDellInc.:pnPrecision3660:pvr:rvnDellInc.:rn0J1C3P:rvrA00:cvnDellInc.:ct3:cvr:sku0A9F:
dmi.product.family: Precision
dmi.product.name: Precision 3660
dmi.product.sku: 0A9F
dmi.sys.vendor: Dell Inc.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.15.0-67-generic (not installed)
Uname: Linux 5.15.0-67-generic x86_64
Architecture: amd64
Date: Fri Jul 14 15:57:34 2023
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-hwe-5.15
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2027814/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028534] [NEW] Jammy update: v6.1.40 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.40 upstream stable release from git://git.kernel.org/ Linux 6.1.40 net/ncsi: change from ndo_set_mac_address to dev_set_mac_address net/ncsi: make one oem_gma function for all mfr id drm/atomic: Fix potential use-after-free in nonblocking commits net/sched: sch_qfq: reintroduce lmax bound check for MTU swiotlb: mark swiotlb_memblock_alloc() as __init Revert "drm/amd: Disable PSR-SU on Parade 0803 TCON" MIPS: kvm: Fix build error with KVM_MIPS_DEBUG_COP0_COUNTERS enabled scsi: qla2xxx: Fix end of loop test scsi: qla2xxx: Remove unused nvme_ls_waitq wait queue scsi: qla2xxx: Pointer may be dereferenced scsi: qla2xxx: Correct the index of array scsi: qla2xxx: Check valid rport returned by fc_bsg_to_rport() scsi: qla2xxx: Fix potential NULL pointer dereference scsi: qla2xxx: Fix buffer overrun scsi: qla2xxx: Avoid fcport pointer dereference scsi: qla2xxx: Array index may go out of bound scsi: qla2xxx: Fix mem access after free scsi: qla2xxx: Wait for io return on terminate rport scsi: qla2xxx: Fix hang in task management scsi: qla2xxx: Fix task management cmd fail due to unavailable resource scsi: qla2xxx: Fix task management cmd failure scsi: qla2xxx: Multi-que support for TMF tracing/user_events: Fix struct arg size match check tracing/probes: Fix to update dynamic data counter if fetcharg uses it tracing/probes: Fix not to count error code to total length selftests: mptcp: pm_nl_ctl: fix 32-bit support selftests: mptcp: depend on SYN_COOKIES selftests: mptcp: userspace_pm: report errors with 'remove' tests selftests: mptcp: userspace_pm: use correct server port selftests: mptcp: sockopt: return error if wrong mark selftests: mptcp: connect: fail if nft supposed to work tracing: Fix null pointer dereference in tracing_err_log_open() fprobe: Ensure running fprobe_exit_handler() finished before calling rethook_free() fprobe: Release rethook after the ftrace_ops is unregistered pwm: meson: fix handling of period/duty if greater than UINT_MAX pwm: meson: modify and simplify calculation in meson_pwm_get_state PM: QoS: Restore support for default value on frequency QoS perf/x86: Fix lockdep warning in for_each_sibling_event() on SPR xtensa: ISS: fix call to split_if_spec cifs: if deferred close is disabled then close files immediately drm/amd/pm: conditionally disable pcie lane/speed switching for SMU13 drm/amd/pm: share the code around SMU13 pcie parameters update ftrace: Fix possible warning on checking all pages used in ftrace_process_locs() ring-buffer: Fix deadloop issue on reading trace_pipe net: ena: fix shift-out-of-bounds in exponential backoff regmap-irq: Fix out-of-bounds access when allocating config buffers perf: RISC-V: Remove PERF_HES_STOPPED flag checking in riscv_pmu_start() samples: ftrace: Save required argument registers in sample trampolines nvme: don't reject probe due to duplicate IDs for single-ported PCIe devices tracing: Fix memory leak of iter->temp when reading trace_pipe tracing/histograms: Add histograms to hist_vars if they have referenced variables dm: verity-loadpin: Add NULL pointer check for 'bdev' parameter s390/decompressor: fix misaligned symbol build error bus: ixp4xx: fix IXP4XX_EXP_T1_MASK Revert "8250: add support for ASIX devices with a FIFO bug" soundwire: qcom: fix storing port config out-of-bounds opp: Fix use-after-free in lazy_opp_tables after probe deferral meson saradc: fix clock divider mask length xhci: Show ZHAOXIN xHCI root hub speed correctly xhci: Fix TRB prefetch issue of ZHAOXIN hosts xhci: Fix resume issue of some ZHAOXIN hosts ceph: don't let check_caps skip sending responses for revoke msgs ceph: fix blindly expanding the readahead windows ceph: add a dedicated private data for netfs rreq libceph: harden msgr2.1 frame segment length checks firmware: stratix10-svc: Fix a potential resource leak in svc_create_memory_pool() tty: serial: imx: fix rs485 rx after tx tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() when iterating clk tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() in case of error serial: atmel: don't enable IRQs prematurely drm/ttm: Don't leak a resource on swapout move error drm/amdgpu: avoid restore process run into dead loop. drm/amd/display: Add monitor specific edid quirk drm/amd/display: Correct `DMUB_FW_VERSION` macro drm/amd/display: add a NULL pointer check drm/amd: Disable PSR-SU on Parade 0803 TCON drm/amdgpu: fix clearing mappings for BOs that are always valid in VM drm/amd/display:
[Kernel-packages] [Bug 2024187] Re: xfrm: packets sent trough a raw socket don't match ipsec policies with proto selector
Any news?
--
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/2024187
Title:
xfrm: packets sent trough a raw socket don't match ipsec policies with
proto selector
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
When a userland application sends packets through an IPv4 or IPv6 raw
socket, these packets don't match ipsec policies that are configured
with a protocol selector.
The problem has been fixed in linux v6.4 with commit 3632679d9e4f
("ipv{4,6}/raw: fix output xfrm lookup wrt protocol").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3632679d9e4f
This commit has been backported in linux 5.15.115:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=395d846c61c5
[Test Case]
Configure an ipsec policy with a protocol selector and send ip packets
that match this policy through an IP raw socket.
Example to match the proto icmp:
ip xfrm policy add src 10.100.0.0/24 dst 10.200.0.0/24 proto icmp dir out
tmpl src 10.125.0.1 dst 10.125.0.2 proto esp mode tunnel reqid 1
[Regression Potential]
The patch introduces a new API to fix this problem, thus the
regression potential is low for existing applications.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024187/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028528] [NEW] Jammy update: v6.1.39 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.39 upstream stable release from git://git.kernel.org/ Linux 6.1.39 io_uring: Use io_schedule* in cqring wait sh: hd64461: Handle virq offset for offchip IRQ base and HD64461 IRQ sh: mach-dreamcast: Handle virq offset in cascaded IRQ demux sh: mach-highlander: Handle virq offset in cascaded IRL demux sh: mach-r2d: Handle virq offset in cascaded IRL demux block/partition: fix signedness issue for Amiga partitions tty: serial: fsl_lpuart: add earlycon for imx8ulp platform wireguard: netlink: send staged packets when setting initial private key wireguard: queueing: use saner cpu selection wrapping netfilter: nf_tables: prevent OOB access in nft_byteorder_eval netfilter: nf_tables: do not ignore genmask when looking up chain by id netfilter: conntrack: Avoid nf_ct_helper_hash uses after free netfilter: nf_tables: unbind non-anonymous set if rule construction fails mtd: parsers: refer to ARCH_BCMBCA instead of ARCH_BCM4908 drm/i915/tc: Fix system resume MST mode restore for DP-alt sinks drm/i915/tc: Fix TC port link ref init for DP MST during HW readout drm/i915: Fix TypeC mode initialization during system resume mm/mmap: Fix extra maple tree write xfs: fix xfs_inodegc_stop racing with mod_delayed_work xfs: disable reaping in fscounters scrub xfs: check that per-cpu inodegc workers actually run on that cpu xfs: explicitly specify cpu when forcing inodegc delayed work to run immediately fs: no need to check source blktrace: use inline function for blk_trace_remove() while blktrace is disabled leds: trigger: netdev: Recheck NETDEV_LED_MODE_LINKUP on dev rename ARM: orion5x: fix d2net gpio initialization ARM: dts: qcom: ipq4019: fix broken NAND controller properties override regulator: tps65219: Fix matching interrupts for their regulators ASoC: mediatek: mt8173: Fix snd_soc_component_initialize error path ASoC: mediatek: mt8173: Fix irq error path btrfs: do not BUG_ON() on tree mod log failure at __btrfs_cow_block() btrfs: fix extent buffer leak after tree mod log failure at split_node() btrfs: fix race when deleting quota root from the dirty cow roots list btrfs: reinsert BGs failed to reclaim btrfs: add block-group tree to lockdep classes btrfs: bail out reclaim process if filesystem is read-only btrfs: delete unused BGs while reclaiming BGs btrfs: add handling for RAID1C23/DUP to btrfs_reduce_alloc_profile ipvs: increase ip_vs_conn_tab_bits range for 64BIT usb: typec: ucsi: Mark dGPUs as DEVICE scope i2c: nvidia-gpu: Remove ccgx,firmware-build property i2c: nvidia-gpu: Add ACPI property to align with device-tree fs: Lock moved directories fs: Establish locking order for unrelated directories Revert "f2fs: fix potential corruption when moving a directory" ext4: Remove ext4 locking of moved directory fs: avoid empty option when generating legacy mount string jffs2: reduce stack usage in jffs2_build_xattr_subsystem() shmem: use ramfs_kill_sb() for kill_sb method of ramfs-based tmpfs mm/damon/ops-common: atomically test and clear young on ptes and pmds autofs: use flexible array in ioctl structure integrity: Fix possible multiple allocation in integrity_inode_get() um: Use HOST_DIR for mrproper watch_queue: prevent dangling pipe pointer bcache: Fix __bch_btree_node_alloc to make the failure behavior consistent bcache: Remove unnecessary NULL point check in node allocations bcache: fixup btree_cache_wait list damage wifi: mt76: mt7921e: fix init command fail with enabled device wifi: ath10k: Serialize wake_tx_queue ops wifi: cfg80211: fix regulatory disconnect for non-MLO mmc: sdhci: fix DMA configure compatibility issue when 64bit DMA mode is used. mmc: mmci: Set PROBE_PREFER_ASYNCHRONOUS mmc: core: disable TRIM on Micron MTFC4GACAJCN-1M mmc: core: disable TRIM on Kingston EMMC04G-M627 io_uring: wait interruptibly for request completions on exit irqchip/loongson-pch-pic: Fix initialization of HT vector register NFSD: add encoding of op_recall flag for write delegation irqchip/loongson-pch-pic: Fix potential incorrect hwirq assignment i2c: qup: Add missing unwind goto in qup_i2c_probe() btrfs: do not BUG_ON() on tree mod log failure at balance_level() extcon: usbc-tusb320: Unregister typec port on driver removal extcon: usbc-tusb320: Convert to i2c's .probe_new() dm ioctl: Avoid double-fetch of version dm ioctl: have constant on the right side of the test dm: avoid split of quoted strings where possible dm: fix undue/missing spaces i2c: xiic: Don't try to handle more interrupt events after error apparmor: fix missing
[Kernel-packages] [Bug 2017444] Re: Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20
** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2017444
Title:
Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-firmware source package in Lunar:
Invalid
Bug description:
== SRU Justification ==
[Impact]
Some Atom based system cannot boot on kernel 6.2 because of atomisp
driver.
[Fix]
Disable the driver via config, suggested by the driver dev.
[Test]
Users confirmed disabling the config works.
[Where problems could occur]
The ISP camera dever worked on Linux. So disabling it shouldn't
introduce any surprise.
== Original Bug Report ==
Computers with Intel Atom CPU will not boot with Kernel 6.2.0-20 OR any other
Kernel in 6.2 series or Kernel 6.3.0.
This bug affects all Intel Atom CPU computers in all Linux
distributions making impossible to install or boot to OS with kernel
6.2 or higher.
The bug is caused by Intel atomisp camera driver module which has
firmware missing: shisp_2401a_v21.bin. Missing firmware causes a
watchdog bug notice and Soft Lockup of boot sequence.
NEW SOLUTION AND NOTICE TO UBUNTU KERNEL MAINTAINERS, April 29th:
The following persons are in charge of atomisp kernel development:
Hans de Goede (maintainer:STAGING - ATOMISP DRIVER)
Mauro Carvalho Chehab (maintainer:STAGING - ATOMISP
DRIVER)
Sakari Ailus (reviewer:STAGING - ATOMISP
DRIVER)
Greg Kroah-Hartman (supporter:STAGING SUBSYSTEM)
linux-me...@vger.kernel.org (open list:STAGING - ATOMISP DRIVER)
linux-stag...@lists.linux.dev (open list:STAGING SUBSYSTEM)
linux-ker...@vger.kernel.org (open list)
April 29th Hans de Goede adviced me personally(
https://github.com/linux-surface/linux-surface/issues/1095 ), that
atomisp driver is still in development and should be disabled. By
disabling driver he meant disabling atomisp modules in kernel.
OLD SOLUTION FOR THIS BUG:
Copying (installing) firmware shisp_2401a0_v21.bin from:
https://github.com/intel-aero/meta-intel-aero-
base/blob/master/recipes-kernel/linux/linux-yocto/shisp_2401a0_v21.bin
to /lib/firmware will solve the bug (partially - it still gives error
messages - but at least the computer boots).**
(dmesg.log with shisp-file with kernel 6.2.0-06 and 6.3.0-06 as
attachments 9. and 10.)
(Another solution - which Manjaro kernel maintainer did - was to
disable atomisp and related modules).
Afterwards Intel Atom CPU computer will be able to boot with kernel
6.2.
DMESG.LOG OF KUBUNTU 23.04 LIVE USB AND MORE INFORMATION IN:
https://askubuntu.com/questions/1464926/not-able-to-boot-
kubuntu-23-04-with-kernel-6-2-and-intel-atom-cpu
The last stable Ubuntu Kernel Intel Atom CPU computer will boot with
is 6.1.25.
This bug was already in 5.19, as you can see from dmesg.logs. It
appears that atomisp failes to launch in both 5.19.0-40 and 6.1.25 but
still the computer boots.
This bug is also reported in Manjaro ( " https://github.com/linux-
surface/linux-surface/issues/1095 ")and Arch Linux ("
https://bbs.archlinux.org/viewtopic.php?id=283920 ") so it is not
limited to Ubuntu Kernels.
This bug has already been reported for Ubuntu 23.04 Beta in Ubuntu
bugtracking system (" https://www.mail-archive.com/kernel-
packa...@lists.launchpad.net/msg501664.html ") with Bug number
#2015794.
Attachments:
1. Picture of stuck boot sequence of HP x2 210 G2 with Intel Atom CPU trying
to boot in to Kubuntu 23.04 with Kernel 6.2.0-20.
2. dmesg.log of the computer with Ubuntu Kernel 6.1.25.
3. xsession-errors of the computer with Ubuntu Kernel 6.1.25.
4. dmesg.log of the computer with Ubuntu Kernel 5.19.0-40.
5. Video of boot sequence with Kernel 6.2.0-20.
6. uname-a.log of Kernel 6.1.25.
7. lspci-vvnn.log of Kernel 6.1.25.
8. version.log of Kernel 5.19.0-40.
9. dmesg.log with shisp-file with ubuntu kernel 6.2.0-06.**
10. dmesg.log with shisp-file with ubuntu kernel 6.3.0-06**
P.S. The apport-collect data is from Kernel 5.19.0-40.
P.S.P.S I had difficulty determining Tags so they are to be changed by you.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017444/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB
** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in linux-oem-5.17 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workarounds ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment or upgrade to a newer kernel: sudo apt install linux-generic-hwe-22.04 [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB
Test environment OS: Ubuntu 22.04.02 kernel: 5.15.0-76 Processor: 12th Gen Intel(R) Core(TM) i7-1270P mutter-common: 42.9-0ubuntu1 Problem: Stuck at a black screen after entering hard disk encryption password. Not getting any login screen for entering username/password Tried proposed fix by installing 42.9-0ubuntu4 from Jammy-proposed Rebooted machine Now login screen is loaded after entering hard disk encryption password ** Tags removed: verification-needed-jammy ** Tags added: block-proposed verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in linux-oem-5.17 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workarounds ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment or upgrade to a newer kernel: sudo apt install linux-generic-hwe-22.04 [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
