[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
Hi @Juerg, thanks a lot, I downloaded linux-image-unsigned-6.2.0-32-generic_6.2.0-32.32+lp2031537_amd64.deb linux-modules-6.2.0-32-generic_6.2.0-32.32+lp2031537_amd64.deb linux-modules-extra-6.2.0-32-generic_6.2.0-32.32+lp2031537_amd64.deb linux-modules-ipu6-6.2.0-32-generic_6.2.0-32.32+lp2031537_amd64.deb linux-modules-ivsc-6.2.0-32-generic_6.2.0-32.32+lp2031537_amd64.deb linux-modules-iwlwifi-6.2.0-32-generic_6.2.0-32.32+lp2031537_amd64.deb put them in a folder and ran 'sudo dpkg -i *.deb' and there is some error Selecting previously unselected package linux-image-unsigned-6.2.0-32-generic. dpkg: regarding linux-image-unsigned-6.2.0-32-generic_6.2.0-32.32+lp2031537_amd64.deb containing linux-image-unsigned-6.2.0-32-generic: linux-image-unsigned-6.2.0-32-generic conflicts with linux-image-6.2.0-32-generic linux-image-6.2.0-32-generic (version 6.2.0-32.32) is present and installed. dpkg: error processing archive linux-image-unsigned-6.2.0-32-generic_6.2.0-32.32+lp2031537_amd64.deb (--install): conflicting packages - not installing linux-image-unsigned-6.2.0-32-generic (Reading database ... 255755 files and directories currently installed.) Preparing to unpack linux-modules-6.2.0-32-generic_6.2.0-32.32+lp2031537_amd64.deb ... Unpacking linux-modules-6.2.0-32-generic (6.2.0-32.32+lp2031537) over (6.2.0-32.32) ... Preparing to unpack linux-modules-extra-6.2.0-32-generic_6.2.0-32.32+lp2031537_amd64.deb ... Unpacking linux-modules-extra-6.2.0-32-generic (6.2.0-32.32+lp2031537) over (6.2.0-32.32) ... Selecting previously unselected package linux-modules-ipu6-6.2.0-32-generic. Preparing to unpack linux-modules-ipu6-6.2.0-32-generic_6.2.0-32.32+lp2031537_amd64.deb ... Unpacking linux-modules-ipu6-6.2.0-32-generic (6.2.0-32.32+lp2031537) ... Selecting previously unselected package linux-modules-ivsc-6.2.0-32-generic. Preparing to unpack linux-modules-ivsc-6.2.0-32-generic_6.2.0-32.32+lp2031537_amd64.deb ... Unpacking linux-modules-ivsc-6.2.0-32-generic (6.2.0-32.32+lp2031537) ... Selecting previously unselected package linux-modules-iwlwifi-6.2.0-32-generic. Preparing to unpack linux-modules-iwlwifi-6.2.0-32-generic_6.2.0-32.32+lp2031537_amd64.deb ... Unpacking linux-modules-iwlwifi-6.2.0-32-generic (6.2.0-32.32+lp2031537) ... Setting up linux-modules-6.2.0-32-generic (6.2.0-32.32+lp2031537) ... Setting up linux-modules-extra-6.2.0-32-generic (6.2.0-32.32+lp2031537) ... Setting up linux-modules-ipu6-6.2.0-32-generic (6.2.0-32.32+lp2031537) ... Setting up linux-modules-ivsc-6.2.0-32-generic (6.2.0-32.32+lp2031537) ... Setting up linux-modules-iwlwifi-6.2.0-32-generic (6.2.0-32.32+lp2031537) ... Processing triggers for linux-image-6.2.0-32-generic (6.2.0-32.32) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-6.2.0-32-generic /etc/kernel/postinst.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-6.2.0-32-generic Found initrd image: /boot/initrd.img-6.2.0-32-generic Found linux image: /boot/vmlinuz-6.2.0-31-generic Found initrd image: /boot/initrd.img-6.2.0-31-generic Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi Warning: os-prober will not be executed to detect other bootable partitions. Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. Adding boot menu entry for UEFI Firmware Settings ... done Errors were encountered while processing: is there any thing I am missing here? -- 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/2031537 Title: Ethernet not stable 23.04 (RTL8168/8169) Status in linux package in Ubuntu: Confirmed Bug description: hello, it is my first time reporting a pug hope it is the last there is thread here https://ubuntuforums.org/showthread.php?t=2489146&p=14151513 another user experienced similar issue my network work fine at startup keep working for hours then disconnect and cannot reconnect without a restart I tested the cable using another pc and it was working repluged with no difference I thought it is caused by nvidia driver so changed it and the problem persist I use systemd-networkd uname -a Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux lspci: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b) dmesg: [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): apparmor="ALLOWED" operation="file_perm" class="file" profile="libreoffice-oosplash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000
[Kernel-packages] [Bug 2034506] Re: Audio device fails to function randomly on Intel MTL platform: No CPC match in the firmware file's manifest
The fix has been included in mainline kernel, but will only be available
for 6.6+. Affects mantic 6.5 as well.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.5 (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.5 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-6.5 (Ubuntu Mantic)
Status: New => Invalid
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => High
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Tags added: oem-priority originate-from-2033504 somerville
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2034506
Title:
Audio device fails to function randomly on Intel MTL platform: No CPC
match in the firmware file's manifest
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
sof-audio-pci-intel-mtl :00:1f.3: no llp found, fall back to default HDA
path
sof-audio-pci-intel-mtl :00:1f.3: COPIER (UUID:
9BA00C83-CA12-4A83-943C-1FA2E82F9DDA): No CPC match in the firmware file's
manifest (ibs/obs: 384/192)
Proposed fix in upstream commit 26ef47e5ba60 ("ASoC: SOF:
ipc4-topology: Add module parameter to ignore the CPC value") that to
allow ignoring CPC validation for current fw release.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2034506/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034504] [NEW] Enable ASPM for NVMe behind VMD
Public bug reported: [Impact] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. ** Affects: linux (Ubuntu) Importance: Low Status: Confirmed ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Low Status: Confirmed ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Low Status: Confirmed ** Affects: linux (Ubuntu Lunar) Importance: Low Status: Confirmed ** Affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Mantic) Importance: Low Status: Confirmed ** Affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Lunar) Status: New => Confirmed ** Changed in: linux (Ubuntu Mantic) Status: New => Confirmed ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Low ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Low ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided => Low ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-6.5 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => 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/2034504 Title: Enable ASPM for NVMe behind VMD Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1374084] Re: Bluetooth: hci0 SCO packet for unknown connection handle 41
** Changed in: linux Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1374084 Title: Bluetooth: hci0 SCO packet for unknown connection handle 41 Status in Linux: Invalid Status in linux package in Ubuntu: Triaged Bug description: [63716.030347] input: 00:1E:7C:22:33:21 as /devices/virtual/input/input13 [63721.787306] Bluetooth: hci0 SCO packet for unknown connection handle 41 [63721.787316] Bluetooth: hci0 SCO packet for unknown connection handle 41 [63814.034162] Bluetooth: hci0 SCO packet for unknown connection handle 35 [63814.034176] Bluetooth: hci0 SCO packet for unknown connection handle 35 [63814.034183] Bluetooth: hci0 SCO packet for unknown connection handle 35 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-17-generic 3.16.0-17.23 [modified: boot/vmlinuz-3.16.0-17-generic] ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2110 F...m pulseaudio /dev/snd/controlC0: caravena 2110 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 25 15:36:47 2014 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2014-09-25 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-17-generic.efi.signed root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1374084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1374084]
working had is the key -- 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/1374084 Title: Bluetooth: hci0 SCO packet for unknown connection handle 41 Status in Linux: Invalid Status in linux package in Ubuntu: Triaged Bug description: [63716.030347] input: 00:1E:7C:22:33:21 as /devices/virtual/input/input13 [63721.787306] Bluetooth: hci0 SCO packet for unknown connection handle 41 [63721.787316] Bluetooth: hci0 SCO packet for unknown connection handle 41 [63814.034162] Bluetooth: hci0 SCO packet for unknown connection handle 35 [63814.034176] Bluetooth: hci0 SCO packet for unknown connection handle 35 [63814.034183] Bluetooth: hci0 SCO packet for unknown connection handle 35 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-17-generic 3.16.0-17.23 [modified: boot/vmlinuz-3.16.0-17-generic] ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2110 F...m pulseaudio /dev/snd/controlC0: caravena 2110 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 25 15:36:47 2014 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2014-09-25 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-17-generic.efi.signed root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1374084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1374084]
*** This bug has been marked as a duplicate of bug 80791 *** -- 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/1374084 Title: Bluetooth: hci0 SCO packet for unknown connection handle 41 Status in Linux: Invalid Status in linux package in Ubuntu: Triaged Bug description: [63716.030347] input: 00:1E:7C:22:33:21 as /devices/virtual/input/input13 [63721.787306] Bluetooth: hci0 SCO packet for unknown connection handle 41 [63721.787316] Bluetooth: hci0 SCO packet for unknown connection handle 41 [63814.034162] Bluetooth: hci0 SCO packet for unknown connection handle 35 [63814.034176] Bluetooth: hci0 SCO packet for unknown connection handle 35 [63814.034183] Bluetooth: hci0 SCO packet for unknown connection handle 35 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-17-generic 3.16.0-17.23 [modified: boot/vmlinuz-3.16.0-17-generic] ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2110 F...m pulseaudio /dev/snd/controlC0: caravena 2110 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 25 15:36:47 2014 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2014-09-25 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-17-generic.efi.signed root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1374084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034479] Re: Fix suspend hang on Lenovo workstation
** Description changed: [Impact] The system hang after resume from S3. Error logs: kernel: igb :02:00.0: disabling already-disabled device kernel: WARNING: CPU: 0 PID: 277 at drivers/pci/pci.c:2248 pci_disable_device+0xc4/0xf0 kernel: RIP: 0010:pci_disable_device+0xc4/0xf0 kernel: Call Trace: kernel: kernel: igb_io_error_detected+0x3e/0x60 kernel: report_error_detected+0xd6/0x1c0 kernel: ? __pfx_report_normal_detected+0x10/0x10 kernel: report_normal_detected+0x16/0x30 kernel: pci_walk_bus+0x74/0xa0 kernel: pcie_do_recovery+0xb9/0x340 kernel: ? __pfx_aer_root_reset+0x10/0x10 kernel: aer_process_err_devices+0x168/0x220 kernel: aer_isr+0x1b5/0x1e0 kernel: ? __pfx_irq_thread_fn+0x10/0x10 kernel: irq_thread_fn+0x21/0x70 kernel: irq_thread+0xf8/0x1c0 kernel: ? __pfx_irq_thread_dtor+0x10/0x10 kernel: ? __pfx_irq_thread+0x10/0x10 kernel: kthread+0xef/0x120 kernel: ? __pfx_kthread+0x10/0x10 kernel: ret_from_fork+0x29/0x50 kernel: kernel: ---[ end trace ]--- [Fix] The pci io error detected ops is called before the driver resumed. Avoid this race condition to fix the issue. [Test] Tested on hardware, the system suspend/resume OK. [Where problems could occur] It may break igb driver. - The commit is included in 6.5-rc1, SRU for Jammy, Lunar and OEM-6.1 + The commit is included in 6.5-rc1 and merge by stable update in oem-6.1, + SRU for Jammy and Lunar ** Description changed: [Impact] The system hang after resume from S3. Error logs: kernel: igb :02:00.0: disabling already-disabled device kernel: WARNING: CPU: 0 PID: 277 at drivers/pci/pci.c:2248 pci_disable_device+0xc4/0xf0 kernel: RIP: 0010:pci_disable_device+0xc4/0xf0 kernel: Call Trace: kernel: kernel: igb_io_error_detected+0x3e/0x60 kernel: report_error_detected+0xd6/0x1c0 kernel: ? __pfx_report_normal_detected+0x10/0x10 kernel: report_normal_detected+0x16/0x30 kernel: pci_walk_bus+0x74/0xa0 kernel: pcie_do_recovery+0xb9/0x340 kernel: ? __pfx_aer_root_reset+0x10/0x10 kernel: aer_process_err_devices+0x168/0x220 kernel: aer_isr+0x1b5/0x1e0 kernel: ? __pfx_irq_thread_fn+0x10/0x10 kernel: irq_thread_fn+0x21/0x70 kernel: irq_thread+0xf8/0x1c0 kernel: ? __pfx_irq_thread_dtor+0x10/0x10 kernel: ? __pfx_irq_thread+0x10/0x10 kernel: kthread+0xef/0x120 kernel: ? __pfx_kthread+0x10/0x10 kernel: ret_from_fork+0x29/0x50 kernel: kernel: ---[ end trace ]--- [Fix] The pci io error detected ops is called before the driver resumed. Avoid this race condition to fix the issue. [Test] Tested on hardware, the system suspend/resume OK. [Where problems could occur] It may break igb driver. - The commit is included in 6.5-rc1 and merge by stable update in oem-6.1, - SRU for Jammy and Lunar + The commit is included in 6.5-rc1 and merged by stable update in + oem-6.1, SRU for Jammy and Lunar. ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: In Progress => Invalid ** Changed in: linux-oem-6.1 (Ubuntu) Status: In Progress => Invalid -- 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/2034479 Title: Fix suspend hang on Lenovo workstation Status in HWE Next: In Progress 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: In Progress Status in linux-oem-6.1 source package in Jammy: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The system hang after resume from S3. Error logs: kernel: igb :02:00.0: disabling already-disabled device kernel: WARNING: CPU: 0 PID: 277 at drivers/pci/pci.c:2248 pci_disable_device+0xc4/0xf0 kernel: RIP: 0010:pci_disable_device+0xc4/0xf0 kernel: Call Trace: kernel: kernel: igb_io_error_detected+0x3e/0x60 kernel: report_error_detected+0xd6/0x1c0 kernel: ? __pfx_report_normal_detected+0x10/0x10 kernel: report_normal_detected+0x16/0x30 kernel: pci_walk_bus+0x74/0xa0 kernel: pcie_do_recovery+0xb9/0x340 kernel: ? __pfx_aer_root_reset+0x10/0x10 kernel: aer_process_err_devices+0x168/0x220 kernel: aer_isr+0x1b5/0x1e0 kernel: ? __pfx_irq_thread_fn+0x10/0x10 kernel: irq_thread_fn+0x21/0x70 kernel: irq_thread+0xf8/0x1c0 kernel: ? __pfx_irq_thread_dtor+0x10/0x10 kernel: ? __pfx_irq_thread+0x10/0x10 kernel: kthread+0xef/0x120 kernel: ? __pfx_kthread+0x10/0x10 kernel: ret_from_fork+0x29/0x50 kernel: kernel: ---[ end trace ]--- [Fix] The pci io error detected ops is called before the driver resumed. Avoid this race condition to fix the issue. [Test] Tested on hardware, the system suspend/resume OK. [Wh
[Kernel-packages] [Bug 1809630] Re: seccomp in ubuntu_kernel_selftest failed on X/B/C s390x KVM
On X-hwe-4.15.0-216.227~16.04.1 openstack s390x instance, this is failing with the following 4 test cases: [ RUN ] TRACE_syscall.skip_after_RET_TRACE [ FAIL ] TRACE_syscall.skip_after_RET_TRACE [ RUN ] TRACE_syscall.kill_after_RET_TRACE [ FAIL ] TRACE_syscall.kill_after_RET_TRACE [ RUN ] TRACE_syscall.skip_after_ptrace [ FAIL ] TRACE_syscall.skip_after_ptrace [ RUN ] TRACE_syscall.kill_after_ptrace [ FAIL ] TRACE_syscall.kill_after_ptrace [==] 61 / 65 tests passed. ** Tags added: 4.15 -- 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/1809630 Title: seccomp in ubuntu_kernel_selftest failed on X/B/C s390x KVM Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Cosmic: Won't Fix Bug description: There are 7 test cases failed in secomp_bpf test, and this can be reproduced with test suites from the upstream: [ RUN ] TRACE_syscall.ptrace_syscall_dropped TRACE_syscall.ptrace_syscall_dropped: Test failed at step #159 [ FAIL ] TRACE_syscall.ptrace_syscall_dropped [ RUN ] TRACE_syscall.syscall_dropped TRACE_syscall.syscall_dropped: Test failed at step #2 [ FAIL ] TRACE_syscall.syscall_dropped [ RUN ] TRACE_syscall.skip_after_RET_TRACE seccomp_bpf.c:1884:TRACE_syscall.skip_after_RET_TRACE:Expected -1 (18446744073709551615) == syscall(20) (14184) seccomp_bpf.c:1885:TRACE_syscall.skip_after_RET_TRACE:Expected 1 (1) == (*__errno_location ()) (0) TRACE_syscall.skip_after_RET_TRACE: Test failed at step #12 [ FAIL ] TRACE_syscall.skip_after_RET_TRACE [ RUN ] TRACE_syscall.kill_after_RET_TRACE TRACE_syscall.kill_after_RET_TRACE: Test exited normally instead of by signal (code: 0) [ FAIL ] TRACE_syscall.kill_after_RET_TRACE [ RUN ] TRACE_syscall.skip_after_ptrace seccomp_bpf.c:1946:TRACE_syscall.skip_after_ptrace:Expected -1 (18446744073709551615) == syscall(20) (14184) seccomp_bpf.c:1947:TRACE_syscall.skip_after_ptrace:Expected 1 (1) == (*__errno_location ()) (0) TRACE_syscall.skip_after_ptrace: Test failed at step #15 [ FAIL ] TRACE_syscall.skip_after_ptrace [ RUN ] TRACE_syscall.kill_after_ptrace TRACE_syscall.kill_after_ptrace: Test exited normally instead of by signal (code: 0) [ FAIL ] TRACE_syscall.kill_after_ptrace [ RUN ] global.get_metadata seccomp_bpf.c:2913:global.get_metadata:Expected sizeof(md) (16) == ptrace(0x420d, pid, sizeof(md), &md) (18446744073709551615) global.get_metadata: Test terminated by assertion [ FAIL ] global.get_metadata Please find the complete test report here: https://pastebin.ubuntu.com/p/tfmVypShtX/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Dec 24 03:33:04 2018 HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034491] Re: Fix blank display when Thunderbolt monitor is plugged second time
** Tags added: oem-priority originate-from-2033251 stella -- 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/2034491 Title: Fix blank display when Thunderbolt monitor is plugged second time Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] When a Thunderbolt monitor gets plugged to an AMD laptop for second time, the Thunderbolt monitor remains blank. [Fix] Reinitialize TMU and perform proper Time Synchronization Handshake every time. [Test] The Thunderbolt monitor still has image after many replugging. [Where problems could occur] This change the flow on disabling TMU, which is responsible for time synchronization, so behavior of Thunderbolt docking might be affected. Per my limited test no issue has been observed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034491] [NEW] Fix blank display when Thunderbolt monitor is plugged second time
Public bug reported: [Impact] When a Thunderbolt monitor gets plugged to an AMD laptop for second time, the Thunderbolt monitor remains blank. [Fix] Reinitialize TMU and perform proper Time Synchronization Handshake every time. [Test] The Thunderbolt monitor still has image after many replugging. [Where problems could occur] This change the flow on disabling TMU, which is responsible for time synchronization, so behavior of Thunderbolt docking might be affected. Per my limited test no issue has been observed. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Low Status: Confirmed ** Affects: linux (Ubuntu Lunar) Importance: Low Status: Confirmed ** Affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Lunar) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Low ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided => Low -- 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/2034491 Title: Fix blank display when Thunderbolt monitor is plugged second time Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] When a Thunderbolt monitor gets plugged to an AMD laptop for second time, the Thunderbolt monitor remains blank. [Fix] Reinitialize TMU and perform proper Time Synchronization Handshake every time. [Test] The Thunderbolt monitor still has image after many replugging. [Where problems could occur] This change the flow on disabling TMU, which is responsible for time synchronization, so behavior of Thunderbolt docking might be affected. Per my limited test no issue has been observed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034479] Re: Fix suspend hang on Lenovo workstation
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: hwe-next Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => In Progress ** Changed in: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) -- 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/2034479 Title: Fix suspend hang on Lenovo workstation Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The system hang after resume from S3. Error logs: kernel: igb :02:00.0: disabling already-disabled device kernel: WARNING: CPU: 0 PID: 277 at drivers/pci/pci.c:2248 pci_disable_device+0xc4/0xf0 kernel: RIP: 0010:pci_disable_device+0xc4/0xf0 kernel: Call Trace: kernel: kernel: igb_io_error_detected+0x3e/0x60 kernel: report_error_detected+0xd6/0x1c0 kernel: ? __pfx_report_normal_detected+0x10/0x10 kernel: report_normal_detected+0x16/0x30 kernel: pci_walk_bus+0x74/0xa0 kernel: pcie_do_recovery+0xb9/0x340 kernel: ? __pfx_aer_root_reset+0x10/0x10 kernel: aer_process_err_devices+0x168/0x220 kernel: aer_isr+0x1b5/0x1e0 kernel: ? __pfx_irq_thread_fn+0x10/0x10 kernel: irq_thread_fn+0x21/0x70 kernel: irq_thread+0xf8/0x1c0 kernel: ? __pfx_irq_thread_dtor+0x10/0x10 kernel: ? __pfx_irq_thread+0x10/0x10 kernel: kthread+0xef/0x120 kernel: ? __pfx_kthread+0x10/0x10 kernel: ret_from_fork+0x29/0x50 kernel: kernel: ---[ end trace ]--- [Fix] The pci io error detected ops is called before the driver resumed. Avoid this race condition to fix the issue. [Test] Tested on hardware, the system suspend/resume OK. [Where problems could occur] It may break igb driver. The commit is included in 6.5-rc1, SRU for Jammy, Lunar and OEM-6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034479] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2034479 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034479 Title: Fix suspend hang on Lenovo workstation Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: New Status in linux source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: New Bug description: [Impact] The system hang after resume from S3. Error logs: kernel: igb :02:00.0: disabling already-disabled device kernel: WARNING: CPU: 0 PID: 277 at drivers/pci/pci.c:2248 pci_disable_device+0xc4/0xf0 kernel: RIP: 0010:pci_disable_device+0xc4/0xf0 kernel: Call Trace: kernel: kernel: igb_io_error_detected+0x3e/0x60 kernel: report_error_detected+0xd6/0x1c0 kernel: ? __pfx_report_normal_detected+0x10/0x10 kernel: report_normal_detected+0x16/0x30 kernel: pci_walk_bus+0x74/0xa0 kernel: pcie_do_recovery+0xb9/0x340 kernel: ? __pfx_aer_root_reset+0x10/0x10 kernel: aer_process_err_devices+0x168/0x220 kernel: aer_isr+0x1b5/0x1e0 kernel: ? __pfx_irq_thread_fn+0x10/0x10 kernel: irq_thread_fn+0x21/0x70 kernel: irq_thread+0xf8/0x1c0 kernel: ? __pfx_irq_thread_dtor+0x10/0x10 kernel: ? __pfx_irq_thread+0x10/0x10 kernel: kthread+0xef/0x120 kernel: ? __pfx_kthread+0x10/0x10 kernel: ret_from_fork+0x29/0x50 kernel: kernel: ---[ end trace ]--- [Fix] The pci io error detected ops is called before the driver resumed. Avoid this race condition to fix the issue. [Test] Tested on hardware, the system suspend/resume OK. [Where problems could occur] It may break igb driver. The commit is included in 6.5-rc1, SRU for Jammy, Lunar and OEM-6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034479] [NEW] Fix suspend hang on Lenovo workstation
Public bug reported: [Impact] The system hang after resume from S3. Error logs: kernel: igb :02:00.0: disabling already-disabled device kernel: WARNING: CPU: 0 PID: 277 at drivers/pci/pci.c:2248 pci_disable_device+0xc4/0xf0 kernel: RIP: 0010:pci_disable_device+0xc4/0xf0 kernel: Call Trace: kernel: kernel: igb_io_error_detected+0x3e/0x60 kernel: report_error_detected+0xd6/0x1c0 kernel: ? __pfx_report_normal_detected+0x10/0x10 kernel: report_normal_detected+0x16/0x30 kernel: pci_walk_bus+0x74/0xa0 kernel: pcie_do_recovery+0xb9/0x340 kernel: ? __pfx_aer_root_reset+0x10/0x10 kernel: aer_process_err_devices+0x168/0x220 kernel: aer_isr+0x1b5/0x1e0 kernel: ? __pfx_irq_thread_fn+0x10/0x10 kernel: irq_thread_fn+0x21/0x70 kernel: irq_thread+0xf8/0x1c0 kernel: ? __pfx_irq_thread_dtor+0x10/0x10 kernel: ? __pfx_irq_thread+0x10/0x10 kernel: kthread+0xef/0x120 kernel: ? __pfx_kthread+0x10/0x10 kernel: ret_from_fork+0x29/0x50 kernel: kernel: ---[ end trace ]--- [Fix] The pci io error detected ops is called before the driver resumed. Avoid this race condition to fix the issue. [Test] Tested on hardware, the system suspend/resume OK. [Where problems could occur] It may break igb driver. The commit is included in 6.5-rc1, SRU for Jammy, Lunar and OEM-6.1 ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: oem-priority originate-from-2022309 sutton ** Tags added: oem-priority originate-from-2022309 sutton -- 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/2034479 Title: Fix suspend hang on Lenovo workstation Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The system hang after resume from S3. Error logs: kernel: igb :02:00.0: disabling already-disabled device kernel: WARNING: CPU: 0 PID: 277 at drivers/pci/pci.c:2248 pci_disable_device+0xc4/0xf0 kernel: RIP: 0010:pci_disable_device+0xc4/0xf0 kernel: Call Trace: kernel: kernel: igb_io_error_detected+0x3e/0x60 kernel: report_error_detected+0xd6/0x1c0 kernel: ? __pfx_report_normal_detected+0x10/0x10 kernel: report_normal_detected+0x16/0x30 kernel: pci_walk_bus+0x74/0xa0 kernel: pcie_do_recovery+0xb9/0x340 kernel: ? __pfx_aer_root_reset+0x10/0x10 kernel: aer_process_err_devices+0x168/0x220 kernel: aer_isr+0x1b5/0x1e0 kernel: ? __pfx_irq_thread_fn+0x10/0x10 kernel: irq_thread_fn+0x21/0x70 kernel: irq_thread+0xf8/0x1c0 kernel: ? __pfx_irq_thread_dtor+0x10/0x10 kernel: ? __pfx_irq_thread+0x10/0x10 kernel: kthread+0xef/0x120 kernel: ? __pfx_kthread+0x10/0x10 kernel: ret_from_fork+0x29/0x50 kernel: kernel: ---[ end trace ]--- [Fix] The pci io error detected ops is called before the driver resumed. Avoid this race condition to fix the issue. [Test] Tested on hardware, the system suspend/resume OK. [Where problems could occur] It may break igb driver. The commit is included in 6.5-rc1, SRU for Jammy, Lunar and OEM-6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028749] Re: Make TTY switching possible for NVIDIA when it's boot VGA
** Changed in: oem-priority Status: New => Fix Released ** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) ** Changed in: oem-priority Importance: Undecided => High -- 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/2028749 Title: Make TTY switching possible for NVIDIA when it's boot VGA Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Incomplete 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 Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] TTY switching is not possible on some workstations when iGPU is present and NVIDIA GFX is boot VGA. On that case, fbdev /dev/fb* is not created. [Fix] Find the correct boot VGA and remove overlapped aperture (BAR), so fbdev can be created properly. [Test] Once the fix gets applied, /dev/fb0 is present and TTY switching works. [Where problems could occur] The fix is a major overhaul over resource management on video apertures (BAR), so the boot VGA discovery might change and different aperture might be evicted. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2028749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029384] Re: External thunderbolt3 & built-in monitor black out on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics
** Changed in: oem-priority
Status: New => Fix Released
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Assignee: (unassigned) => Andy Chi (andch)
--
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/2029384
Title:
External thunderbolt3 & built-in monitor black out on AMD Ryzen 9 PRO
7940HS w/ Radeon 780M Graphics
Status in HWE Next:
New
Status in OEM Priority Project:
Fix Released
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Lunar:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Monitors black out when an external one connects via thunderbolt3 on AMD Ryzen
9 PRO 7940HS w/ Radeon 780M Graphics.
[Fix]
This can be fixed by upstream linux-firmware commit 253cc179d849 ("amdgpu:
Update DMCUB for DCN314 & Yellow Carp").
However, in linux-firmware/lunar and jammy, the commit history related to the
files to be updated often associated with many other more, they're now updated
with overwrites without cherry-pick ancestor commits along the history.
For linux-firmware/mantic, a simple cherry-pick would do.
[Test Case]
Connect an tbt3 featured external monitor (ASUS PA27AC) after boot to GUI.
Check if both the built-in and external monitors lights up as usual.
[Where problems could occur]
Update amdgpu firmware are error prone, verified on targeting series as
possible.
[Other Info]
While this affects linux-oem-6.1/jammy, as well as linux/lunar kernels, Jammy
and Lunar are nominated for fix.
== original bug report ==
When connect the tbt3 external monitor, both the build-in and the
external monitor show black.
This can be fixed by
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/amdgpu/?id=253cc179d849fc82489773b2b553a49858d8725f.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2029384/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034478] [NEW] nvidia-dkms-525-open 525.125.06-0ubuntu0.22.04.1: nvidia kernel module failed to build
Public bug reported: This error occurred while installing the update. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-525-open 525.125.06-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown DKMSKernelVersion: 5.15.0-83-generic Date: Wed Sep 6 08:35:25 2023 DuplicateSignature: dkms:nvidia-dkms-525-open:525.125.06-0ubuntu0.22.04.1:gcc: error: unrecognized command line option ‘-mharden-sls=all’ InstallationDate: Installed on 2022-08-25 (376 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 525.125.06-0ubuntu0.22.04.1 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: nvidia-graphics-drivers-525 Title: nvidia-dkms-525-open 525.125.06-0ubuntu0.22.04.1: nvidia kernel module failed to build UpgradeStatus: Upgraded to jammy on 2022-12-06 (273 days ago) ** Affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2034478 Title: nvidia-dkms-525-open 525.125.06-0ubuntu0.22.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-525 package in Ubuntu: New Bug description: This error occurred while installing the update. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-525-open 525.125.06-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown DKMSKernelVersion: 5.15.0-83-generic Date: Wed Sep 6 08:35:25 2023 DuplicateSignature: dkms:nvidia-dkms-525-open:525.125.06-0ubuntu0.22.04.1:gcc: error: unrecognized command line option ‘-mharden-sls=all’ InstallationDate: Installed on 2022-08-25 (376 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 525.125.06-0ubuntu0.22.04.1 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: nvidia-graphics-drivers-525 Title: nvidia-dkms-525-open 525.125.06-0ubuntu0.22.04.1: nvidia kernel module failed to build UpgradeStatus: Upgraded to jammy on 2022-12-06 (273 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2034478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029384] Re: External thunderbolt3 & built-in monitor black out on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics
** Tags added: originate-from-2026326
--
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/2029384
Title:
External thunderbolt3 & built-in monitor black out on AMD Ryzen 9 PRO
7940HS w/ Radeon 780M Graphics
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Lunar:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Monitors black out when an external one connects via thunderbolt3 on AMD Ryzen
9 PRO 7940HS w/ Radeon 780M Graphics.
[Fix]
This can be fixed by upstream linux-firmware commit 253cc179d849 ("amdgpu:
Update DMCUB for DCN314 & Yellow Carp").
However, in linux-firmware/lunar and jammy, the commit history related to the
files to be updated often associated with many other more, they're now updated
with overwrites without cherry-pick ancestor commits along the history.
For linux-firmware/mantic, a simple cherry-pick would do.
[Test Case]
Connect an tbt3 featured external monitor (ASUS PA27AC) after boot to GUI.
Check if both the built-in and external monitors lights up as usual.
[Where problems could occur]
Update amdgpu firmware are error prone, verified on targeting series as
possible.
[Other Info]
While this affects linux-oem-6.1/jammy, as well as linux/lunar kernels, Jammy
and Lunar are nominated for fix.
== original bug report ==
When connect the tbt3 external monitor, both the build-in and the
external monitor show black.
This can be fixed by
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/amdgpu/?id=253cc179d849fc82489773b2b553a49858d8725f.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2029384/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] [NEW] Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Public bug reported: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
@Eli, re-built with 23.04, would you please have a try, thanks https://drive.google.com/drive/folders/1XmxwqgiUB_vjLRWiIaSpzXc89ilSwItx?usp=sharing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: In Progress Bug description: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install undervolt==0.3.0) to force particular power limits (the provided values are intentional overkill): 1 │ from undervolt import read_power_limit, set_power_limit, PowerLimit, ADDRESSES 2 │ from pprint import pprint 3 │ 4 │ limits = read_power_limit(ADDRESSES) 5 │ pprint(vars(limits)) # print current values before setting them 6 │ 7 │ POWER_LIMITS = PowerLimit() 8 │ POWER_LIMITS.locked = True # lock means don't allow the value to be reset until a reboot. 9 │ POWER_LIMITS.backup_rest = 281474976776192 # afaik this is just a backup-on-failure setting, it has no effect here. 10 │ POWER_LIMITS.long_term_enabled = True 11 │ POWER_LIMITS.long_te
[Kernel-packages] [Bug 2034033] Re: Ubuntu 22.04 update to 6.2.0-31 kernel version breaks mount.cifs to vers=1.0 server cifs_mount failed w/return code = -5
Ubuntu has release kernel version "6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux" which has successfully resolved this defect case. One of the Samba maintainers told me I should check if SMB 1.0 protocol was purposely removed from the Ubuntu 6.2.0-31 kernel version. This evening I received that changelog, and could not see a hint of it being removed by Ubuntu on purpose. Then my system notified me of a yet newer kernel package. I pulled it down, and was happy to see it has successfully resolved this defect. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034033 Title: Ubuntu 22.04 update to 6.2.0-31 kernel version breaks mount.cifs to vers=1.0 server cifs_mount failed w/return code = -5 Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: My Xubuntu system this weekend alerted me to a new kernel update being available. The following versions are the existing/working version: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 And the updated/not working version: linux-image-6.2.0-31-generic 6.2.0-31.31~22.04.1 And yes I run my system with: linux-image-generic-hwe-22.04 6.2.0.31.31~22.04.8 Booted to the 6.2.0-31 kernel version, attempting to do a mount.cifs operation to our Samba NT4 PDC, results in the following output into syslog: Sep 4 08:03:24 jaakob kernel: [ 107.703886] FS-Cache: Loaded Sep 4 08:03:24 jaakob kernel: [ 107.824160] Key type cifs.spnego registered Sep 4 08:03:24 jaakob kernel: [ 107.824169] Key type cifs.idmap registered Sep 4 08:03:24 jaakob kernel: [ 107.824454] Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Sep 4 08:03:24 jaakob kernel: [ 107.824454] Sep 4 08:03:24 jaakob kernel: [ 107.824457] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Sep 4 08:03:24 jaakob kernel: [ 107.824460] CIFS: Attempting to mount \\ldslnx01\data Sep 4 08:03:24 jaakob kernel: [ 107.859554] CIFS: VFS: cifs_mount failed w/return code = -5 And none of the Samba mounts will establish. Booting back to the prior 6.2.0-26 kernel version, Samba mounts work just fine. I use the following switches to the mount.cifs command in order to establish connections to our Samba NT4 PDC: "-o credentials=/home/mdlueck/.smbcredentials,uid=mdlueck,gid=mdlueck,dir_mode=0777,file_mode=0666,nobrl,vers=1.0" That last vers= option was the last that needed to be added to continue making use of our Samba NT4 style PDC. Since it is a version upgrade of only the kernel, not Samba package, I would not think that yet another switch to mount.cifs was needed in order to continue connecting successfully. So did the latest Kernel update suddenly break Samba's mount.cifs vers=1.0 support? Nothing gets logged to our Samba server for the failed mount attempt. Booting for not back to the working 6.2.0-26 kernel version. Please kindly advise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034447] Re: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic
Here's the full log from where that snippet was pulled. ** Attachment added: "hidon.log.1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034447/+attachment/5697793/+files/hidon.log.1 -- 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/2034447 Title: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic Status in linux package in Ubuntu: Incomplete Bug description: Seeing a panic on hidon (an Nvidia H100) after booting the 5.15.0-85-generic kernel: [ 58.935877] [ cut here ] [ 58.935893] refcount_t: underflow; use-after-free. [ 58.935920] WARNING: CPU: 207 PID: 2985 at lib/refcount.c:28 refcount_warn_saturate+0xf7/0x150 [ 58.935943] Modules linked in: x86_pkg_temp_thermal(+) intel_powerclamp coretemp nls_iso8859_1 rapl irdma(+) i40e qat_4xxx(+) isst_if_mbox_pci intel_qat pmt_telemetry pmt_crashlog idxd(+) isst_if_mmio pmt_class isst_if_common authenc idxd_bus intel_th_gth mei_me intel_th_pci intel_th mei switchtec ipmi_ssif acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 multipath linear mlx5_ib ib_uverbs ib_core ast i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper raid0 mlx5_core syscopyarea sysfillrect sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul ixgbe cec mlxfw ghash_clmulni_intel aesni_intel psample crypto_simd xfrm_algo ice rc_core cryptd tls nvme i2c_i801 dca xhci_pci intel_pmt drm [ 58.936077] pci_hyperv_intf i2c_ismt i2c_smbus [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936083] mdio [ 58.936096] xhci_pci_renesas nvme_core wmi pinctrl_emmitsburg [ 58.936106] CPU: 207 PID: 2985 Comm: systemd-udevd Not tainted 5.15.0-85-generic #95-Ubuntu [ 58.936115] Hardware name: NVIDIA DGXH100/DGXH100, BIOS 1.0.7 05/08/2023 [ 58.936119] RIP: 0010:refcount_warn_saturate+0xf7/0x150 [ 58.936130] Code: eb 9e 0f b6 1d 5e e6 b9 01 80 fb 01 0f 87 f4 63 6f 00 83 e3 01 75 89 48 c7 c7 88 c3 23 9e c6 05 42 e6 b9 01 01 e8 d8 e4 6b 00 <0f> 0b e9 6f ff ff ff 0f b6 1d 2d e6 b9 01 80 fb 01 0f 87 b1 63 6f [ 58.936135] RSP: 0018:ff4d5d94b2c7fa28 EFLAGS: 00010282 [ 58.936142] RAX: RBX: RCX: 0027 [ 58.936146] RDX: ff314dbbbf9e0588 RSI: 0001 RDI: ff314dbbbf9e0580 [ 58.936149] RBP: ff4d5d94b2c7fa30 R08: 0026 R09: ff4d5d94b2c7f9c0 [ 58.936153] R10: 0028 R11: 0001 R12: [ 58.936156] R13: ff314cbfdbcb6900 R14: ff314cbfdbcb67b8 R15: ff314cbfd24b4000 [ 58.936159] FS: 7fadd2f6c8c0() GS:ff314dbbbf9c() knlGS: [ 58.936163] CS: 0010 DS: ES: CR0: 80050033 [ 58.936167] CR2: 7fadd243b584 CR3: 00012972c006 CR4: 00771ee0 [ 58.936171] DR0: DR1: DR2: [ 58.936174] DR3: DR6: fffe07f0 DR7: 0400 [ 58.936177] PKRU: 5554 [ 58.936179] Call Trace: [ 58.936184] [ 58.936188] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936204] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936212] ? crypto_mod_put+0x6b/0x80 [ 58.936225] ? show_regs.part.0+0x23/0x29 [ 58.936232] ? show_regs.cold+0x8/0xd [ 58.936239] ? refcount_warn_saturate+0xf7/0x150 [ 58.936246] ? __warn+0x8c/0x100 [ 58.936255] ? refcount_warn_saturate+0xf7/0x150 [ 58.936263] ? report_bug+0xa4/0xd0 [ 58.936274] ? down_trylock+0x2e/0x40 [ 58.936285] ? handle_bug+0x39/0x90 [ 58.936296] ? exc_invalid_op+0x19/0x70 [ 58.936301] ? asm_exc_invalid_op+0x1b/0x20 [ 58.936310] ? refcount_warn_saturate+0xf7/0x150 [ 58.936317] ? refcount_warn_saturate+0xf7/0x150 [ 58.936323] crypto_mod_put+0x6b/0x80 [ 58.936329] crypto_destroy_tfm+0x4e/0xa0 [ 58.936336] pkcs1pad_exit_tfm+0x15/0x20 [ 58.936345] crypto_akcipher_exit_tfm+0x13/0x20 [ 58.936352] crypto_destroy_tfm+0x43/0xa0 [ 58.936358] public_key_verify_signature+0x2dc/0x3c0 [ 58.936366] ? find_asymmetric_key+0xd2/0x1d0 [ 58.936374] ? kfree+0x1f7/0x250 [ 58.936385] public_key_verify_signature_2+0x15/0x20 [ 58.936389] verify_signature+0x37/0x60 [ 58.936393] pkcs7_validate_trust_one.constprop.0+0x156/0x1e0 [
[Kernel-packages] [Bug 2034447] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2034447 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034447 Title: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic Status in linux package in Ubuntu: Incomplete Bug description: Seeing a panic on hidon (an Nvidia H100) after booting the 5.15.0-85-generic kernel: [ 58.935877] [ cut here ] [ 58.935893] refcount_t: underflow; use-after-free. [ 58.935920] WARNING: CPU: 207 PID: 2985 at lib/refcount.c:28 refcount_warn_saturate+0xf7/0x150 [ 58.935943] Modules linked in: x86_pkg_temp_thermal(+) intel_powerclamp coretemp nls_iso8859_1 rapl irdma(+) i40e qat_4xxx(+) isst_if_mbox_pci intel_qat pmt_telemetry pmt_crashlog idxd(+) isst_if_mmio pmt_class isst_if_common authenc idxd_bus intel_th_gth mei_me intel_th_pci intel_th mei switchtec ipmi_ssif acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 multipath linear mlx5_ib ib_uverbs ib_core ast i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper raid0 mlx5_core syscopyarea sysfillrect sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul ixgbe cec mlxfw ghash_clmulni_intel aesni_intel psample crypto_simd xfrm_algo ice rc_core cryptd tls nvme i2c_i801 dca xhci_pci intel_pmt drm [ 58.936077] pci_hyperv_intf i2c_ismt i2c_smbus [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936083] mdio [ 58.936096] xhci_pci_renesas nvme_core wmi pinctrl_emmitsburg [ 58.936106] CPU: 207 PID: 2985 Comm: systemd-udevd Not tainted 5.15.0-85-generic #95-Ubuntu [ 58.936115] Hardware name: NVIDIA DGXH100/DGXH100, BIOS 1.0.7 05/08/2023 [ 58.936119] RIP: 0010:refcount_warn_saturate+0xf7/0x150 [ 58.936130] Code: eb 9e 0f b6 1d 5e e6 b9 01 80 fb 01 0f 87 f4 63 6f 00 83 e3 01 75 89 48 c7 c7 88 c3 23 9e c6 05 42 e6 b9 01 01 e8 d8 e4 6b 00 <0f> 0b e9 6f ff ff ff 0f b6 1d 2d e6 b9 01 80 fb 01 0f 87 b1 63 6f [ 58.936135] RSP: 0018:ff4d5d94b2c7fa28 EFLAGS: 00010282 [ 58.936142] RAX: RBX: RCX: 0027 [ 58.936146] RDX: ff314dbbbf9e0588 RSI: 0001 RDI: ff314dbbbf9e0580 [ 58.936149] RBP: ff4d5d94b2c7fa30 R08: 0026 R09: ff4d5d94b2c7f9c0 [ 58.936153] R10: 0028 R11: 0001 R12: [ 58.936156] R13: ff314cbfdbcb6900 R14: ff314cbfdbcb67b8 R15: ff314cbfd24b4000 [ 58.936159] FS: 7fadd2f6c8c0() GS:ff314dbbbf9c() knlGS: [ 58.936163] CS: 0010 DS: ES: CR0: 80050033 [ 58.936167] CR2: 7fadd243b584 CR3: 00012972c006 CR4: 00771ee0 [ 58.936171] DR0: DR1: DR2: [ 58.936174] DR3: DR6: fffe07f0 DR7: 0400 [ 58.936177] PKRU: 5554 [ 58.936179] Call Trace: [ 58.936184] [ 58.936188] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936204] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936212] ? crypto_mod_put+0x6b/0x80 [ 58.936225] ? show_regs.part.0+0x23/0x29 [ 58.936232] ? show_regs.cold+0x8/0xd [ 58.936239] ? refcount_warn_saturate+0xf7/0x150 [ 58.936246] ? __warn+0x8c/0x100 [ 58.936255] ? refcount_warn_saturate+0xf7/0x150 [ 58.936263] ? report_bug+0xa4/0xd0 [ 58.936274] ? down_trylock+0x2e/0x40 [ 58.936285] ? handle_bug+0x39/0x90 [ 58.936296] ? exc_invalid_op+0x19/0x70 [ 58.936301] ? asm_exc_invalid_op+0x1b/0x20 [ 58.936310] ? refcount_warn_saturate+0xf7/0x150 [ 58.936317] ? refcount_warn_saturate+0xf7/0x150 [ 58.936323] crypto_mod_put+0x6b/0x80 [ 58.936329] crypto_destroy_tfm+0x4e/0xa0 [ 58.936336] pkcs1pad_exit_tfm+0x15/0x20 [ 58.936
[Kernel-packages] [Bug 2034447] [NEW] `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic
Public bug reported: Seeing a panic on hidon (an Nvidia H100) after booting the 5.15.0-85-generic kernel: [ 58.935877] [ cut here ] [ 58.935893] refcount_t: underflow; use-after-free. [ 58.935920] WARNING: CPU: 207 PID: 2985 at lib/refcount.c:28 refcount_warn_saturate+0xf7/0x150 [ 58.935943] Modules linked in: x86_pkg_temp_thermal(+) intel_powerclamp coretemp nls_iso8859_1 rapl irdma(+) i40e qat_4xxx(+) isst_if_mbox_pci intel_qat pmt_telemetry pmt_crashlog idxd(+) isst_if_mmio pmt_class isst_if_common authenc idxd_bus intel_th_gth mei_me intel_th_pci intel_th mei switchtec ipmi_ssif acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 multipath linear mlx5_ib ib_uverbs ib_core ast i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper raid0 mlx5_core syscopyarea sysfillrect sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul ixgbe cec mlxfw ghash_clmulni_intel aesni_intel psample crypto_simd xfrm_algo ice rc_core cryptd tls nvme i2c_i801 dca xhci_pci intel_pmt drm [ 58.936077] pci_hyperv_intf i2c_ismt i2c_smbus [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936083] mdio [ 58.936096] xhci_pci_renesas nvme_core wmi pinctrl_emmitsburg [ 58.936106] CPU: 207 PID: 2985 Comm: systemd-udevd Not tainted 5.15.0-85-generic #95-Ubuntu [ 58.936115] Hardware name: NVIDIA DGXH100/DGXH100, BIOS 1.0.7 05/08/2023 [ 58.936119] RIP: 0010:refcount_warn_saturate+0xf7/0x150 [ 58.936130] Code: eb 9e 0f b6 1d 5e e6 b9 01 80 fb 01 0f 87 f4 63 6f 00 83 e3 01 75 89 48 c7 c7 88 c3 23 9e c6 05 42 e6 b9 01 01 e8 d8 e4 6b 00 <0f> 0b e9 6f ff ff ff 0f b6 1d 2d e6 b9 01 80 fb 01 0f 87 b1 63 6f [ 58.936135] RSP: 0018:ff4d5d94b2c7fa28 EFLAGS: 00010282 [ 58.936142] RAX: RBX: RCX: 0027 [ 58.936146] RDX: ff314dbbbf9e0588 RSI: 0001 RDI: ff314dbbbf9e0580 [ 58.936149] RBP: ff4d5d94b2c7fa30 R08: 0026 R09: ff4d5d94b2c7f9c0 [ 58.936153] R10: 0028 R11: 0001 R12: [ 58.936156] R13: ff314cbfdbcb6900 R14: ff314cbfdbcb67b8 R15: ff314cbfd24b4000 [ 58.936159] FS: 7fadd2f6c8c0() GS:ff314dbbbf9c() knlGS: [ 58.936163] CS: 0010 DS: ES: CR0: 80050033 [ 58.936167] CR2: 7fadd243b584 CR3: 00012972c006 CR4: 00771ee0 [ 58.936171] DR0: DR1: DR2: [ 58.936174] DR3: DR6: fffe07f0 DR7: 0400 [ 58.936177] PKRU: 5554 [ 58.936179] Call Trace: [ 58.936184] [ 58.936188] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936204] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936212] ? crypto_mod_put+0x6b/0x80 [ 58.936225] ? show_regs.part.0+0x23/0x29 [ 58.936232] ? show_regs.cold+0x8/0xd [ 58.936239] ? refcount_warn_saturate+0xf7/0x150 [ 58.936246] ? __warn+0x8c/0x100 [ 58.936255] ? refcount_warn_saturate+0xf7/0x150 [ 58.936263] ? report_bug+0xa4/0xd0 [ 58.936274] ? down_trylock+0x2e/0x40 [ 58.936285] ? handle_bug+0x39/0x90 [ 58.936296] ? exc_invalid_op+0x19/0x70 [ 58.936301] ? asm_exc_invalid_op+0x1b/0x20 [ 58.936310] ? refcount_warn_saturate+0xf7/0x150 [ 58.936317] ? refcount_warn_saturate+0xf7/0x150 [ 58.936323] crypto_mod_put+0x6b/0x80 [ 58.936329] crypto_destroy_tfm+0x4e/0xa0 [ 58.936336] pkcs1pad_exit_tfm+0x15/0x20 [ 58.936345] crypto_akcipher_exit_tfm+0x13/0x20 [ 58.936352] crypto_destroy_tfm+0x43/0xa0 [ 58.936358] public_key_verify_signature+0x2dc/0x3c0 [ 58.936366] ? find_asymmetric_key+0xd2/0x1d0 [ 58.936374] ? kfree+0x1f7/0x250 [ 58.936385] public_key_verify_signature_2+0x15/0x20 [ 58.936389] verify_signature+0x37/0x60 [ 58.936393] pkcs7_validate_trust_one.constprop.0+0x156/0x1e0 [ 58.936400] pkcs7_validate_trust+0x4a/0xa0 [ 58.936406] verify_pkcs7_message_sig+0x83/0x120 [ 58.936418] verify_pkcs7_signature+0x4f/0x80 [ 58.936424] mod_verify_sig+0xb5/0xf0 [ 58.936435] load_module+0x275/0xbc0 [ 58.936440] ? kernel_read_file_from_fd+0x56/0xa0 [ 58.936450] __do_sys_finit_module+0xbf/0x120 [ 58.936496] __x64_sys_finit_module+0x18/0x20 [ 58.936504] do_syscall_64+0x59/0xc0 [ 58.936510] ? exit_to_user_mode_prepare+0x37/0xb0 [ 58.936521] ? syscall_exit_to_user_mode+0x35/0x50 [ 58.936530] ? __x64_sys_mmap+0x33/0x50 [ 58.936539] ? do_syscall_64+0x69/0xc0 [
[Kernel-packages] [Bug 2028746] Re: Fix UBSAN in Intel EDAC driver
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1021.21 --- linux-oem-6.1 (6.1.0-1021.21) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1021.21 -proposed tracker (LP: #2030428) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper * Jammy update: v6.1.46 upstream stable release (LP: #2032632) - gcc-plugins: Reorganize gimple includes for GCC 13 - Revert "loongarch/cpu: Switch to arch_cpu_finalize_init()" - tpm: Disable RNG for all AMD fTPMs - tpm: Add a helper for checking hwrng enabled - ksmbd: validate command request size - ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea() - KVM: SEV: snapshot the GHCB before accessing it - KVM: SEV: only access GHCB fields once - wifi: nl80211: fix integer overflow in nl80211_parse_mbssid_elems() - wifi: rtw89: fix 8852AE disconnection caused by RX full flags - selftests: forwarding: Set default IPv6 traceroute utility - wireguard: allowedips: expand maximum node depth - mmc: moxart: read scr register without changing byte order - ipv6: adjust ndisc_is_useropt() to also return true for PIO - selftests: mptcp: join: fix 'delete and re-add' test - selftests: mptcp: join: fix 'implicit EP' test - mptcp: avoid bogus reset on fallback close - mptcp: fix disconnect vs accept race - dmaengine: pl330: Return DMA_PAUSED when transaction is paused - net: mana: Fix MANA VF unload when hardware is unresponsive - riscv/kexec: load initrd high in available memory - riscv,mmio: Fix readX()-to-delay() ordering - riscv/kexec: handle R_RISCV_CALL_PLT relocation type - nvme-pci: add NVME_QUIRK_BOGUS_NID for Samsung PM9B1 256G and 512G - drm/nouveau/gr: enable memory loads on helper invocation on all channels - drm/nouveau/nvkm/dp: Add workaround to fix DP 1.3+ DPCD issues - drm/shmem-helper: Reset vma->vm_ops before calling dma_buf_mmap() - drm/amdgpu: fix possible UAF in amdgpu_cs_pass1() - drm/amd/display: check attr flag before set cursor degamma on DCN3+ - drm/amdgpu: add S/G display parameter - drm/amd: Disable S/G for APUs when 64GB or more host memory - drm/amd/display: limit DPIA link rate to HBR3 - cpuidle: dt_idle_genpd: Add helper function to remove genpd topology - hwmon: (pmbus/bel-pfe) Enable PMBUS_SKIP_STATUS_CHECK for pfe1100 - radix tree test suite: fix incorrect allocation size for pthreads - nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput - drm/amd/pm: fulfill swsmu peak profiling mode shader/memory clock settings - drm/amd/pm: expose swctf threshold setting for legacy powerplay - drm/amd/pm: fulfill powerplay peak profiling mode shader/memory clock settings - drm/amd/pm: avoid unintentional shutdown due to temperature momentary fluctuation - drm/amd/display: Handle virtual hardware detect - drm/amd/display: Add function for validate and update new stream - drm/amd/display: Handle seamless boot stream - drm/amd/display: Update OTG instance in the commit stream - drm/amd/display: Avoid ABM when ODM combine is enabled for eDP - drm/amd/display: Use update plane and stream routine for DCN32x - drm/amd/display: Disable phantom OTG after enable for plane disable - drm/amd/display: Retain phantom plane/stream if validation fails - drm/amd/display: fix the build when DRM_AMD_DC_DCN is not set - drm/amd/display: trigger timing sync only if TG is running - io_uring: correct check for O_TMPFILE - iio: cros_ec: Fix the allocation size for cros_ec_command - iio: frequency: admv1013: propagate errors from regulator_get_voltage() - iio: adc: ad7192: Fix ac excitation feature - iio: adc: ina2xx: avoid NULL pointer dereference on OF device match - binder: fix memory leak in binder_init() - misc: rtsx: judge ASPM Mode to set PETXCFG Reg - usb-storage: alauda: Fix uninit-value in alauda_check_media() - usb: dwc3: Properly handle processing of pending events - USB: Gadget: core: Help prevent panic during UVC unconfigure - usb: common: usb-conn-gpio: Prevent bailing out if initial role is none - usb: typec: tcpm: Fix response to vsafe0V event - usb: typec: altmodes/displayport: Signal hpd when configuring pin assignment - x86/mm: Fix VDSO and VVAR placement on 5-level paging machines - x86/sev: Do not try to parse for the CC blob on non-AMD hardware - x86/speculation: Add cpu_show_gds() prototype - x86: Move gds_ucode_mitigated() declaration to header - drm/nouveau/disp: Revert a NULL check inside nouveau_connector_get_modes - iio: core: Prevent invalid memory access when there is no parent - interconnect: qcom: Add support for mask-based BCMs - interconnect: qcom: sm8450: add enable_mask for bcm nodes - selftests/rseq: Fix build with undefined __weak - selftests: forwarding: Add a
[Kernel-packages] [Bug 2028749] Re: Make TTY switching possible for NVIDIA when it's boot VGA
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1021.21 --- linux-oem-6.1 (6.1.0-1021.21) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1021.21 -proposed tracker (LP: #2030428) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper * Jammy update: v6.1.46 upstream stable release (LP: #2032632) - gcc-plugins: Reorganize gimple includes for GCC 13 - Revert "loongarch/cpu: Switch to arch_cpu_finalize_init()" - tpm: Disable RNG for all AMD fTPMs - tpm: Add a helper for checking hwrng enabled - ksmbd: validate command request size - ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea() - KVM: SEV: snapshot the GHCB before accessing it - KVM: SEV: only access GHCB fields once - wifi: nl80211: fix integer overflow in nl80211_parse_mbssid_elems() - wifi: rtw89: fix 8852AE disconnection caused by RX full flags - selftests: forwarding: Set default IPv6 traceroute utility - wireguard: allowedips: expand maximum node depth - mmc: moxart: read scr register without changing byte order - ipv6: adjust ndisc_is_useropt() to also return true for PIO - selftests: mptcp: join: fix 'delete and re-add' test - selftests: mptcp: join: fix 'implicit EP' test - mptcp: avoid bogus reset on fallback close - mptcp: fix disconnect vs accept race - dmaengine: pl330: Return DMA_PAUSED when transaction is paused - net: mana: Fix MANA VF unload when hardware is unresponsive - riscv/kexec: load initrd high in available memory - riscv,mmio: Fix readX()-to-delay() ordering - riscv/kexec: handle R_RISCV_CALL_PLT relocation type - nvme-pci: add NVME_QUIRK_BOGUS_NID for Samsung PM9B1 256G and 512G - drm/nouveau/gr: enable memory loads on helper invocation on all channels - drm/nouveau/nvkm/dp: Add workaround to fix DP 1.3+ DPCD issues - drm/shmem-helper: Reset vma->vm_ops before calling dma_buf_mmap() - drm/amdgpu: fix possible UAF in amdgpu_cs_pass1() - drm/amd/display: check attr flag before set cursor degamma on DCN3+ - drm/amdgpu: add S/G display parameter - drm/amd: Disable S/G for APUs when 64GB or more host memory - drm/amd/display: limit DPIA link rate to HBR3 - cpuidle: dt_idle_genpd: Add helper function to remove genpd topology - hwmon: (pmbus/bel-pfe) Enable PMBUS_SKIP_STATUS_CHECK for pfe1100 - radix tree test suite: fix incorrect allocation size for pthreads - nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput - drm/amd/pm: fulfill swsmu peak profiling mode shader/memory clock settings - drm/amd/pm: expose swctf threshold setting for legacy powerplay - drm/amd/pm: fulfill powerplay peak profiling mode shader/memory clock settings - drm/amd/pm: avoid unintentional shutdown due to temperature momentary fluctuation - drm/amd/display: Handle virtual hardware detect - drm/amd/display: Add function for validate and update new stream - drm/amd/display: Handle seamless boot stream - drm/amd/display: Update OTG instance in the commit stream - drm/amd/display: Avoid ABM when ODM combine is enabled for eDP - drm/amd/display: Use update plane and stream routine for DCN32x - drm/amd/display: Disable phantom OTG after enable for plane disable - drm/amd/display: Retain phantom plane/stream if validation fails - drm/amd/display: fix the build when DRM_AMD_DC_DCN is not set - drm/amd/display: trigger timing sync only if TG is running - io_uring: correct check for O_TMPFILE - iio: cros_ec: Fix the allocation size for cros_ec_command - iio: frequency: admv1013: propagate errors from regulator_get_voltage() - iio: adc: ad7192: Fix ac excitation feature - iio: adc: ina2xx: avoid NULL pointer dereference on OF device match - binder: fix memory leak in binder_init() - misc: rtsx: judge ASPM Mode to set PETXCFG Reg - usb-storage: alauda: Fix uninit-value in alauda_check_media() - usb: dwc3: Properly handle processing of pending events - USB: Gadget: core: Help prevent panic during UVC unconfigure - usb: common: usb-conn-gpio: Prevent bailing out if initial role is none - usb: typec: tcpm: Fix response to vsafe0V event - usb: typec: altmodes/displayport: Signal hpd when configuring pin assignment - x86/mm: Fix VDSO and VVAR placement on 5-level paging machines - x86/sev: Do not try to parse for the CC blob on non-AMD hardware - x86/speculation: Add cpu_show_gds() prototype - x86: Move gds_ucode_mitigated() declaration to header - drm/nouveau/disp: Revert a NULL check inside nouveau_connector_get_modes - iio: core: Prevent invalid memory access when there is no parent - interconnect: qcom: Add support for mask-based BCMs - interconnect: qcom: sm8450: add enable_mask for bcm nodes - selftests/rseq: Fix build with undefined __weak - selftests: forwarding: Add a
[Kernel-packages] [Bug 2029199] Re: NULL pointer dereference on CS35L41 HDA AMP
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1021.21 --- linux-oem-6.1 (6.1.0-1021.21) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1021.21 -proposed tracker (LP: #2030428) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper * Jammy update: v6.1.46 upstream stable release (LP: #2032632) - gcc-plugins: Reorganize gimple includes for GCC 13 - Revert "loongarch/cpu: Switch to arch_cpu_finalize_init()" - tpm: Disable RNG for all AMD fTPMs - tpm: Add a helper for checking hwrng enabled - ksmbd: validate command request size - ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea() - KVM: SEV: snapshot the GHCB before accessing it - KVM: SEV: only access GHCB fields once - wifi: nl80211: fix integer overflow in nl80211_parse_mbssid_elems() - wifi: rtw89: fix 8852AE disconnection caused by RX full flags - selftests: forwarding: Set default IPv6 traceroute utility - wireguard: allowedips: expand maximum node depth - mmc: moxart: read scr register without changing byte order - ipv6: adjust ndisc_is_useropt() to also return true for PIO - selftests: mptcp: join: fix 'delete and re-add' test - selftests: mptcp: join: fix 'implicit EP' test - mptcp: avoid bogus reset on fallback close - mptcp: fix disconnect vs accept race - dmaengine: pl330: Return DMA_PAUSED when transaction is paused - net: mana: Fix MANA VF unload when hardware is unresponsive - riscv/kexec: load initrd high in available memory - riscv,mmio: Fix readX()-to-delay() ordering - riscv/kexec: handle R_RISCV_CALL_PLT relocation type - nvme-pci: add NVME_QUIRK_BOGUS_NID for Samsung PM9B1 256G and 512G - drm/nouveau/gr: enable memory loads on helper invocation on all channels - drm/nouveau/nvkm/dp: Add workaround to fix DP 1.3+ DPCD issues - drm/shmem-helper: Reset vma->vm_ops before calling dma_buf_mmap() - drm/amdgpu: fix possible UAF in amdgpu_cs_pass1() - drm/amd/display: check attr flag before set cursor degamma on DCN3+ - drm/amdgpu: add S/G display parameter - drm/amd: Disable S/G for APUs when 64GB or more host memory - drm/amd/display: limit DPIA link rate to HBR3 - cpuidle: dt_idle_genpd: Add helper function to remove genpd topology - hwmon: (pmbus/bel-pfe) Enable PMBUS_SKIP_STATUS_CHECK for pfe1100 - radix tree test suite: fix incorrect allocation size for pthreads - nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput - drm/amd/pm: fulfill swsmu peak profiling mode shader/memory clock settings - drm/amd/pm: expose swctf threshold setting for legacy powerplay - drm/amd/pm: fulfill powerplay peak profiling mode shader/memory clock settings - drm/amd/pm: avoid unintentional shutdown due to temperature momentary fluctuation - drm/amd/display: Handle virtual hardware detect - drm/amd/display: Add function for validate and update new stream - drm/amd/display: Handle seamless boot stream - drm/amd/display: Update OTG instance in the commit stream - drm/amd/display: Avoid ABM when ODM combine is enabled for eDP - drm/amd/display: Use update plane and stream routine for DCN32x - drm/amd/display: Disable phantom OTG after enable for plane disable - drm/amd/display: Retain phantom plane/stream if validation fails - drm/amd/display: fix the build when DRM_AMD_DC_DCN is not set - drm/amd/display: trigger timing sync only if TG is running - io_uring: correct check for O_TMPFILE - iio: cros_ec: Fix the allocation size for cros_ec_command - iio: frequency: admv1013: propagate errors from regulator_get_voltage() - iio: adc: ad7192: Fix ac excitation feature - iio: adc: ina2xx: avoid NULL pointer dereference on OF device match - binder: fix memory leak in binder_init() - misc: rtsx: judge ASPM Mode to set PETXCFG Reg - usb-storage: alauda: Fix uninit-value in alauda_check_media() - usb: dwc3: Properly handle processing of pending events - USB: Gadget: core: Help prevent panic during UVC unconfigure - usb: common: usb-conn-gpio: Prevent bailing out if initial role is none - usb: typec: tcpm: Fix response to vsafe0V event - usb: typec: altmodes/displayport: Signal hpd when configuring pin assignment - x86/mm: Fix VDSO and VVAR placement on 5-level paging machines - x86/sev: Do not try to parse for the CC blob on non-AMD hardware - x86/speculation: Add cpu_show_gds() prototype - x86: Move gds_ucode_mitigated() declaration to header - drm/nouveau/disp: Revert a NULL check inside nouveau_connector_get_modes - iio: core: Prevent invalid memory access when there is no parent - interconnect: qcom: Add support for mask-based BCMs - interconnect: qcom: sm8450: add enable_mask for bcm nodes - selftests/rseq: Fix build with undefined __weak - selftests: forwarding: Add a
[Kernel-packages] [Bug 2030860] Re: Jammy update: v6.1.43 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1021.21 --- linux-oem-6.1 (6.1.0-1021.21) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1021.21 -proposed tracker (LP: #2030428) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper * Jammy update: v6.1.46 upstream stable release (LP: #2032632) - gcc-plugins: Reorganize gimple includes for GCC 13 - Revert "loongarch/cpu: Switch to arch_cpu_finalize_init()" - tpm: Disable RNG for all AMD fTPMs - tpm: Add a helper for checking hwrng enabled - ksmbd: validate command request size - ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea() - KVM: SEV: snapshot the GHCB before accessing it - KVM: SEV: only access GHCB fields once - wifi: nl80211: fix integer overflow in nl80211_parse_mbssid_elems() - wifi: rtw89: fix 8852AE disconnection caused by RX full flags - selftests: forwarding: Set default IPv6 traceroute utility - wireguard: allowedips: expand maximum node depth - mmc: moxart: read scr register without changing byte order - ipv6: adjust ndisc_is_useropt() to also return true for PIO - selftests: mptcp: join: fix 'delete and re-add' test - selftests: mptcp: join: fix 'implicit EP' test - mptcp: avoid bogus reset on fallback close - mptcp: fix disconnect vs accept race - dmaengine: pl330: Return DMA_PAUSED when transaction is paused - net: mana: Fix MANA VF unload when hardware is unresponsive - riscv/kexec: load initrd high in available memory - riscv,mmio: Fix readX()-to-delay() ordering - riscv/kexec: handle R_RISCV_CALL_PLT relocation type - nvme-pci: add NVME_QUIRK_BOGUS_NID for Samsung PM9B1 256G and 512G - drm/nouveau/gr: enable memory loads on helper invocation on all channels - drm/nouveau/nvkm/dp: Add workaround to fix DP 1.3+ DPCD issues - drm/shmem-helper: Reset vma->vm_ops before calling dma_buf_mmap() - drm/amdgpu: fix possible UAF in amdgpu_cs_pass1() - drm/amd/display: check attr flag before set cursor degamma on DCN3+ - drm/amdgpu: add S/G display parameter - drm/amd: Disable S/G for APUs when 64GB or more host memory - drm/amd/display: limit DPIA link rate to HBR3 - cpuidle: dt_idle_genpd: Add helper function to remove genpd topology - hwmon: (pmbus/bel-pfe) Enable PMBUS_SKIP_STATUS_CHECK for pfe1100 - radix tree test suite: fix incorrect allocation size for pthreads - nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput - drm/amd/pm: fulfill swsmu peak profiling mode shader/memory clock settings - drm/amd/pm: expose swctf threshold setting for legacy powerplay - drm/amd/pm: fulfill powerplay peak profiling mode shader/memory clock settings - drm/amd/pm: avoid unintentional shutdown due to temperature momentary fluctuation - drm/amd/display: Handle virtual hardware detect - drm/amd/display: Add function for validate and update new stream - drm/amd/display: Handle seamless boot stream - drm/amd/display: Update OTG instance in the commit stream - drm/amd/display: Avoid ABM when ODM combine is enabled for eDP - drm/amd/display: Use update plane and stream routine for DCN32x - drm/amd/display: Disable phantom OTG after enable for plane disable - drm/amd/display: Retain phantom plane/stream if validation fails - drm/amd/display: fix the build when DRM_AMD_DC_DCN is not set - drm/amd/display: trigger timing sync only if TG is running - io_uring: correct check for O_TMPFILE - iio: cros_ec: Fix the allocation size for cros_ec_command - iio: frequency: admv1013: propagate errors from regulator_get_voltage() - iio: adc: ad7192: Fix ac excitation feature - iio: adc: ina2xx: avoid NULL pointer dereference on OF device match - binder: fix memory leak in binder_init() - misc: rtsx: judge ASPM Mode to set PETXCFG Reg - usb-storage: alauda: Fix uninit-value in alauda_check_media() - usb: dwc3: Properly handle processing of pending events - USB: Gadget: core: Help prevent panic during UVC unconfigure - usb: common: usb-conn-gpio: Prevent bailing out if initial role is none - usb: typec: tcpm: Fix response to vsafe0V event - usb: typec: altmodes/displayport: Signal hpd when configuring pin assignment - x86/mm: Fix VDSO and VVAR placement on 5-level paging machines - x86/sev: Do not try to parse for the CC blob on non-AMD hardware - x86/speculation: Add cpu_show_gds() prototype - x86: Move gds_ucode_mitigated() declaration to header - drm/nouveau/disp: Revert a NULL check inside nouveau_connector_get_modes - iio: core: Prevent invalid memory access when there is no parent - interconnect: qcom: Add support for mask-based BCMs - interconnect: qcom: sm8450: add enable_mask for bcm nodes - selftests/rseq: Fix build with undefined __weak - selftests: forwarding: Add a
[Kernel-packages] [Bug 2030861] Re: Jammy update: v6.1.44 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1021.21 --- linux-oem-6.1 (6.1.0-1021.21) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1021.21 -proposed tracker (LP: #2030428) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper * Jammy update: v6.1.46 upstream stable release (LP: #2032632) - gcc-plugins: Reorganize gimple includes for GCC 13 - Revert "loongarch/cpu: Switch to arch_cpu_finalize_init()" - tpm: Disable RNG for all AMD fTPMs - tpm: Add a helper for checking hwrng enabled - ksmbd: validate command request size - ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea() - KVM: SEV: snapshot the GHCB before accessing it - KVM: SEV: only access GHCB fields once - wifi: nl80211: fix integer overflow in nl80211_parse_mbssid_elems() - wifi: rtw89: fix 8852AE disconnection caused by RX full flags - selftests: forwarding: Set default IPv6 traceroute utility - wireguard: allowedips: expand maximum node depth - mmc: moxart: read scr register without changing byte order - ipv6: adjust ndisc_is_useropt() to also return true for PIO - selftests: mptcp: join: fix 'delete and re-add' test - selftests: mptcp: join: fix 'implicit EP' test - mptcp: avoid bogus reset on fallback close - mptcp: fix disconnect vs accept race - dmaengine: pl330: Return DMA_PAUSED when transaction is paused - net: mana: Fix MANA VF unload when hardware is unresponsive - riscv/kexec: load initrd high in available memory - riscv,mmio: Fix readX()-to-delay() ordering - riscv/kexec: handle R_RISCV_CALL_PLT relocation type - nvme-pci: add NVME_QUIRK_BOGUS_NID for Samsung PM9B1 256G and 512G - drm/nouveau/gr: enable memory loads on helper invocation on all channels - drm/nouveau/nvkm/dp: Add workaround to fix DP 1.3+ DPCD issues - drm/shmem-helper: Reset vma->vm_ops before calling dma_buf_mmap() - drm/amdgpu: fix possible UAF in amdgpu_cs_pass1() - drm/amd/display: check attr flag before set cursor degamma on DCN3+ - drm/amdgpu: add S/G display parameter - drm/amd: Disable S/G for APUs when 64GB or more host memory - drm/amd/display: limit DPIA link rate to HBR3 - cpuidle: dt_idle_genpd: Add helper function to remove genpd topology - hwmon: (pmbus/bel-pfe) Enable PMBUS_SKIP_STATUS_CHECK for pfe1100 - radix tree test suite: fix incorrect allocation size for pthreads - nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput - drm/amd/pm: fulfill swsmu peak profiling mode shader/memory clock settings - drm/amd/pm: expose swctf threshold setting for legacy powerplay - drm/amd/pm: fulfill powerplay peak profiling mode shader/memory clock settings - drm/amd/pm: avoid unintentional shutdown due to temperature momentary fluctuation - drm/amd/display: Handle virtual hardware detect - drm/amd/display: Add function for validate and update new stream - drm/amd/display: Handle seamless boot stream - drm/amd/display: Update OTG instance in the commit stream - drm/amd/display: Avoid ABM when ODM combine is enabled for eDP - drm/amd/display: Use update plane and stream routine for DCN32x - drm/amd/display: Disable phantom OTG after enable for plane disable - drm/amd/display: Retain phantom plane/stream if validation fails - drm/amd/display: fix the build when DRM_AMD_DC_DCN is not set - drm/amd/display: trigger timing sync only if TG is running - io_uring: correct check for O_TMPFILE - iio: cros_ec: Fix the allocation size for cros_ec_command - iio: frequency: admv1013: propagate errors from regulator_get_voltage() - iio: adc: ad7192: Fix ac excitation feature - iio: adc: ina2xx: avoid NULL pointer dereference on OF device match - binder: fix memory leak in binder_init() - misc: rtsx: judge ASPM Mode to set PETXCFG Reg - usb-storage: alauda: Fix uninit-value in alauda_check_media() - usb: dwc3: Properly handle processing of pending events - USB: Gadget: core: Help prevent panic during UVC unconfigure - usb: common: usb-conn-gpio: Prevent bailing out if initial role is none - usb: typec: tcpm: Fix response to vsafe0V event - usb: typec: altmodes/displayport: Signal hpd when configuring pin assignment - x86/mm: Fix VDSO and VVAR placement on 5-level paging machines - x86/sev: Do not try to parse for the CC blob on non-AMD hardware - x86/speculation: Add cpu_show_gds() prototype - x86: Move gds_ucode_mitigated() declaration to header - drm/nouveau/disp: Revert a NULL check inside nouveau_connector_get_modes - iio: core: Prevent invalid memory access when there is no parent - interconnect: qcom: Add support for mask-based BCMs - interconnect: qcom: sm8450: add enable_mask for bcm nodes - selftests/rseq: Fix build with undefined __weak - selftests: forwarding: Add a
[Kernel-packages] [Bug 2032631] Re: Jammy update: v6.1.45 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1021.21 --- linux-oem-6.1 (6.1.0-1021.21) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1021.21 -proposed tracker (LP: #2030428) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper * Jammy update: v6.1.46 upstream stable release (LP: #2032632) - gcc-plugins: Reorganize gimple includes for GCC 13 - Revert "loongarch/cpu: Switch to arch_cpu_finalize_init()" - tpm: Disable RNG for all AMD fTPMs - tpm: Add a helper for checking hwrng enabled - ksmbd: validate command request size - ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea() - KVM: SEV: snapshot the GHCB before accessing it - KVM: SEV: only access GHCB fields once - wifi: nl80211: fix integer overflow in nl80211_parse_mbssid_elems() - wifi: rtw89: fix 8852AE disconnection caused by RX full flags - selftests: forwarding: Set default IPv6 traceroute utility - wireguard: allowedips: expand maximum node depth - mmc: moxart: read scr register without changing byte order - ipv6: adjust ndisc_is_useropt() to also return true for PIO - selftests: mptcp: join: fix 'delete and re-add' test - selftests: mptcp: join: fix 'implicit EP' test - mptcp: avoid bogus reset on fallback close - mptcp: fix disconnect vs accept race - dmaengine: pl330: Return DMA_PAUSED when transaction is paused - net: mana: Fix MANA VF unload when hardware is unresponsive - riscv/kexec: load initrd high in available memory - riscv,mmio: Fix readX()-to-delay() ordering - riscv/kexec: handle R_RISCV_CALL_PLT relocation type - nvme-pci: add NVME_QUIRK_BOGUS_NID for Samsung PM9B1 256G and 512G - drm/nouveau/gr: enable memory loads on helper invocation on all channels - drm/nouveau/nvkm/dp: Add workaround to fix DP 1.3+ DPCD issues - drm/shmem-helper: Reset vma->vm_ops before calling dma_buf_mmap() - drm/amdgpu: fix possible UAF in amdgpu_cs_pass1() - drm/amd/display: check attr flag before set cursor degamma on DCN3+ - drm/amdgpu: add S/G display parameter - drm/amd: Disable S/G for APUs when 64GB or more host memory - drm/amd/display: limit DPIA link rate to HBR3 - cpuidle: dt_idle_genpd: Add helper function to remove genpd topology - hwmon: (pmbus/bel-pfe) Enable PMBUS_SKIP_STATUS_CHECK for pfe1100 - radix tree test suite: fix incorrect allocation size for pthreads - nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput - drm/amd/pm: fulfill swsmu peak profiling mode shader/memory clock settings - drm/amd/pm: expose swctf threshold setting for legacy powerplay - drm/amd/pm: fulfill powerplay peak profiling mode shader/memory clock settings - drm/amd/pm: avoid unintentional shutdown due to temperature momentary fluctuation - drm/amd/display: Handle virtual hardware detect - drm/amd/display: Add function for validate and update new stream - drm/amd/display: Handle seamless boot stream - drm/amd/display: Update OTG instance in the commit stream - drm/amd/display: Avoid ABM when ODM combine is enabled for eDP - drm/amd/display: Use update plane and stream routine for DCN32x - drm/amd/display: Disable phantom OTG after enable for plane disable - drm/amd/display: Retain phantom plane/stream if validation fails - drm/amd/display: fix the build when DRM_AMD_DC_DCN is not set - drm/amd/display: trigger timing sync only if TG is running - io_uring: correct check for O_TMPFILE - iio: cros_ec: Fix the allocation size for cros_ec_command - iio: frequency: admv1013: propagate errors from regulator_get_voltage() - iio: adc: ad7192: Fix ac excitation feature - iio: adc: ina2xx: avoid NULL pointer dereference on OF device match - binder: fix memory leak in binder_init() - misc: rtsx: judge ASPM Mode to set PETXCFG Reg - usb-storage: alauda: Fix uninit-value in alauda_check_media() - usb: dwc3: Properly handle processing of pending events - USB: Gadget: core: Help prevent panic during UVC unconfigure - usb: common: usb-conn-gpio: Prevent bailing out if initial role is none - usb: typec: tcpm: Fix response to vsafe0V event - usb: typec: altmodes/displayport: Signal hpd when configuring pin assignment - x86/mm: Fix VDSO and VVAR placement on 5-level paging machines - x86/sev: Do not try to parse for the CC blob on non-AMD hardware - x86/speculation: Add cpu_show_gds() prototype - x86: Move gds_ucode_mitigated() declaration to header - drm/nouveau/disp: Revert a NULL check inside nouveau_connector_get_modes - iio: core: Prevent invalid memory access when there is no parent - interconnect: qcom: Add support for mask-based BCMs - interconnect: qcom: sm8450: add enable_mask for bcm nodes - selftests/rseq: Fix build with undefined __weak - selftests: forwarding: Add a
[Kernel-packages] [Bug 2032632] Re: Jammy update: v6.1.46 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1021.21 --- linux-oem-6.1 (6.1.0-1021.21) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1021.21 -proposed tracker (LP: #2030428) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper * Jammy update: v6.1.46 upstream stable release (LP: #2032632) - gcc-plugins: Reorganize gimple includes for GCC 13 - Revert "loongarch/cpu: Switch to arch_cpu_finalize_init()" - tpm: Disable RNG for all AMD fTPMs - tpm: Add a helper for checking hwrng enabled - ksmbd: validate command request size - ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea() - KVM: SEV: snapshot the GHCB before accessing it - KVM: SEV: only access GHCB fields once - wifi: nl80211: fix integer overflow in nl80211_parse_mbssid_elems() - wifi: rtw89: fix 8852AE disconnection caused by RX full flags - selftests: forwarding: Set default IPv6 traceroute utility - wireguard: allowedips: expand maximum node depth - mmc: moxart: read scr register without changing byte order - ipv6: adjust ndisc_is_useropt() to also return true for PIO - selftests: mptcp: join: fix 'delete and re-add' test - selftests: mptcp: join: fix 'implicit EP' test - mptcp: avoid bogus reset on fallback close - mptcp: fix disconnect vs accept race - dmaengine: pl330: Return DMA_PAUSED when transaction is paused - net: mana: Fix MANA VF unload when hardware is unresponsive - riscv/kexec: load initrd high in available memory - riscv,mmio: Fix readX()-to-delay() ordering - riscv/kexec: handle R_RISCV_CALL_PLT relocation type - nvme-pci: add NVME_QUIRK_BOGUS_NID for Samsung PM9B1 256G and 512G - drm/nouveau/gr: enable memory loads on helper invocation on all channels - drm/nouveau/nvkm/dp: Add workaround to fix DP 1.3+ DPCD issues - drm/shmem-helper: Reset vma->vm_ops before calling dma_buf_mmap() - drm/amdgpu: fix possible UAF in amdgpu_cs_pass1() - drm/amd/display: check attr flag before set cursor degamma on DCN3+ - drm/amdgpu: add S/G display parameter - drm/amd: Disable S/G for APUs when 64GB or more host memory - drm/amd/display: limit DPIA link rate to HBR3 - cpuidle: dt_idle_genpd: Add helper function to remove genpd topology - hwmon: (pmbus/bel-pfe) Enable PMBUS_SKIP_STATUS_CHECK for pfe1100 - radix tree test suite: fix incorrect allocation size for pthreads - nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput - drm/amd/pm: fulfill swsmu peak profiling mode shader/memory clock settings - drm/amd/pm: expose swctf threshold setting for legacy powerplay - drm/amd/pm: fulfill powerplay peak profiling mode shader/memory clock settings - drm/amd/pm: avoid unintentional shutdown due to temperature momentary fluctuation - drm/amd/display: Handle virtual hardware detect - drm/amd/display: Add function for validate and update new stream - drm/amd/display: Handle seamless boot stream - drm/amd/display: Update OTG instance in the commit stream - drm/amd/display: Avoid ABM when ODM combine is enabled for eDP - drm/amd/display: Use update plane and stream routine for DCN32x - drm/amd/display: Disable phantom OTG after enable for plane disable - drm/amd/display: Retain phantom plane/stream if validation fails - drm/amd/display: fix the build when DRM_AMD_DC_DCN is not set - drm/amd/display: trigger timing sync only if TG is running - io_uring: correct check for O_TMPFILE - iio: cros_ec: Fix the allocation size for cros_ec_command - iio: frequency: admv1013: propagate errors from regulator_get_voltage() - iio: adc: ad7192: Fix ac excitation feature - iio: adc: ina2xx: avoid NULL pointer dereference on OF device match - binder: fix memory leak in binder_init() - misc: rtsx: judge ASPM Mode to set PETXCFG Reg - usb-storage: alauda: Fix uninit-value in alauda_check_media() - usb: dwc3: Properly handle processing of pending events - USB: Gadget: core: Help prevent panic during UVC unconfigure - usb: common: usb-conn-gpio: Prevent bailing out if initial role is none - usb: typec: tcpm: Fix response to vsafe0V event - usb: typec: altmodes/displayport: Signal hpd when configuring pin assignment - x86/mm: Fix VDSO and VVAR placement on 5-level paging machines - x86/sev: Do not try to parse for the CC blob on non-AMD hardware - x86/speculation: Add cpu_show_gds() prototype - x86: Move gds_ucode_mitigated() declaration to header - drm/nouveau/disp: Revert a NULL check inside nouveau_connector_get_modes - iio: core: Prevent invalid memory access when there is no parent - interconnect: qcom: Add support for mask-based BCMs - interconnect: qcom: sm8450: add enable_mask for bcm nodes - selftests/rseq: Fix build with undefined __weak - selftests: forwarding: Add a
[Kernel-packages] [Bug 2020295] Re: Include the MAC address pass through function on RTL8153DD-CG
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1017.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- 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/2020295 Title: Include the MAC address pass through function on RTL8153DD-CG Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] When user connect network cable on the RJ45 port of RTL8153DD-CG on dock, it should show pass through MAC address set in BIOS. But the LAN MAC address pass through doesn't function on RTL8153DD-CG sku. [Fix] Commit in v6.3-rc1 fixes the issue. ec51fbd1b8a2 r8152: add USB device driver for config selection [Test] Verified by OEM. [Where problems could occur] It won't affect the old behavior if there is no preferred cfg is configured and will select the preferred one while probing. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016398] Re: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?)
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1017.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- 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/2016398 Title: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?) Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress 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: Confirmed Bug description: [Impact] Opened files reported in /proc/pid/map_files can be shows with the wrong mount point using overlayfs with filesystem namspaces. This incorrect behavior is fixed: UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files However, the fix introduced a new regression, the reference to the original file stored in vma->vm_prfile is not properly released when vma->vm_prfile is replaced with a new file. This can cause a reference counter unbalance, leading errors such as "target is busy" when trying to unmount overlayfs, even if the filesystem has not active reference. [Test case] Reproducer provided by original bug reporter: https://launchpadlibrarian.net/663151659/overlayfsscript_example [Fix] Fix by properly releasing the original file stored in vm_prfile. [Regression potential] This fix seems to solve the reported bug (verified with the reproducer) and it doesn't seem to introduce other regressions or behavior change. However, we may experience regressions in overlayfs or potentially other "target is busy" errors when unmounting overlayfs filesystems with this fix applied, if there are still other corner cases not covered properly. [Original bug report] Hi BACKGROUND: --- I have a set of scripts that debootstraps and builds vanilla Debian installs, where the only modifications are what packages are installed. Then that becomes the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and then that becomes the chroot where config changes are made with more scripts. This overlayfs is mounted in its own mount namespace as the script is unshare'd Within these scripts, I make packages with a fork of checkinstall I made which uses the / as the lowerdir, as overlayfs allows that, a tmpfs as the upperdir, the install command is run with chroot, and then the contents are copied. THE ISSUE: -- I noticed that it appears that my ramdisks are remaining in memory, I have isolated it out to the overlayfs mounts with the overlayfs as the lowerdir where chroot is being called on it. I tried entering the namespace myself and umounting it, and notice I get the error "Target is busy" With the "Target Is Busy" issue, I tried to `lsof` and `fuser` and `lsfd` as much as I could, but every user mode tool shows absolutely NO files open at all I was using Kubuntu 18.04, it was an old install and 32 bit, so I had no upgrade path to be using more recent versions. Now I am on 23.04, but I also think this is happening on a 22.10 laptop DIAGNOSIS: -- I am able to isolate it out, and get this to replicate in the smallest script that I could that is now attached. the chroot is important. I am able to unmount the second overlayfs if chroot is never called. Nothing ever has to run IN the chroot, trying to call a binary that does not exist, and then trying to unmount it results in "target is busy" with no open files reportable by user mode tools FURTHER TESTING: Trying to find out the version of Linux this was introduced, I made a script that builds a very minimal ext4 file for a VM with a small debootstrapped system, builds a kernel, and runs the kernel with QEMU.. but when I started, after all that, I can't replicate it at all with a vanilla 6.2.0 kernel. I used the same config out of my /boot to the .config, only tweaking a few options like SYSTEM_TRUSTED_KEYS. Trying to unmount the s
[Kernel-packages] [Bug 2015400] Re: losetup with mknod fails on jammy with kernel 5.15.0-69-generic
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1017.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- 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/2015400 Title: losetup with mknod fails on jammy with kernel 5.15.0-69-generic Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Invalid Bug description: [ Impact ] * Regression in the loop block driver in Jammy kernel between 5.15.0-67 to 5.15.0-68 (in v5.15.86 stable), due to a change in the default behavior (value) of kernel parameter `max_loop` (from 0 to 8) in commit: `loop: Fix the max_loop commandline argument treatment when it is set to 0` (comment #6). * Users of loop devices (major 7) with minor >= 8 now fail to `open()` a loop device created with `mknod()`. * This is a corner case, as most people use `losetup` with usual /dev/loopNUMBER (or `--find`) which are not affected as it uses a different code path. (`losetup` for `/dev/loopNOT-A-NUMBER` is affected.) * Workaround: kernel parameter `max_loop=0`. [ Test Steps ] * Run the test cases (losetup and test-loop.c in comment #6): - max_loop not set (default) - max_loop=0 - max_loop=8 * Verify the default behavior (max_loop not set) is restored. * Verify the modified behavior (max_loop is set) is unchanged. [ Regression Potential ] * Regressions would be limited to the loop block driver, more specifically its default behavior (but it's that now) or specific usage of max_loop parameter (tested; looks OK). [ Other Info ] * Patch 1 [1] is not quite a fix, but adds CONFIG guards that Patch 2 [2] depends on. (Alternatively, a Patch 2 backport with that could be done, but Patch 1 seems trivial enough.) * The fix on Jammy is only Patch 2, with a trivial backport (that CONFIG option is not in Jammy/v5.15, only in v5.18). * The fix on Lunar is both patches; clean cherry-picks. * The fix on Mantic is both patches too, now in v6.5-rc3, which should be automatically incorporated as Mantic apparently will release with the 6.5 kernel [3] [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=23881aec85f3219e8462e87c708815ee2cd82358 [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bb5faa99f0ce40756ab7bbbce4f16c01ca5ebd5a [3] https://discourse.ubuntu.com/t/introducing-kernel-6-5-for-the-23-10-mantic-minotaur-release Original Description: --- losetup fails with devices created manually by mknod on kernel 5.15.0-69-generic # fallocate -l 1G test # mknod -m 660 /dev/loop8 b 7 8 # chown root:disk /dev/loop8 # losetup /dev/loop8 ./test losetup: ./test: failed to set up loop device: Device or resource busy Possibly as a result of this patch: https://lore.kernel.org/lkml/20221208200605.756287-1-isaacmanjar...@google.com/T/ which was introduced in 5.15.0-68: http://launchpadlibrarian.net/653145495/linux_5.15.0-67.74_5.15.0-68.75.diff.gz On a machine prior to this change (no issue with losetup): # cat /sys/module/loop/parameters/max_loop 0 # uname -r 5.15.0-58-generic On a machine after the change (has losetup issue as described above): # cat /sys/module/loop/parameters/max_loop 8 # uname -r 5.15.0-69-generic So it looks like the default changed and the max amount of loop devices that can be created with mknod (not loop-control) is 8. If we set max_loop=0 on the kernel command line, it works as before. Cannot unload and reload module on a running system to change the parameter because it is built into the kernel. Another workaround is to use `losetup --find` but that means you cannot create with named devices created with mknod. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 2028550] Re: Backport support to tolerate ZSTD compressed firmware files
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1017.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- 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: In Progress 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 (see bug #1942260) * 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 and https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.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 2026028] Re: usbrtl sometimes doesn't reload firmware
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1017.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- 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/2026028 Title: usbrtl sometimes doesn't reload firmware Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Fix Committed Bug description: [Impact] The btrtl driver in the 5.15 jammy kernel sometimes doesn't (re-) load firmware which results in the BT adapter running potentially old firmware rather than the current version from /lib/firmware provided by the linux-firmware package. This will show in logs like so: Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=dfc6 lmp_ver=0a lmp_subver=d922 Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: unknown IC info, lmp subver d922, hci rev dfc6, hci ver 000a Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: assuming no firmware upload needed The driver reads subver from the adapter to determine chip type. But that value is overwritten by a firmware load. In the above case, a firmware was already loaded which returns subver d922 which the driver does not recognize and it therefore won't load new firmware. [Test Case] 1) Boot machine with USB adapter plugged in. 2) Verify firmware is loaded. 3) Reboot a couple of times and verify that firmware is reloaded every time. [Where Problems Could Occur] Limited to Realtek USB bluetooth adapters that use the btrtl driver. Issues could show up as Bluetooth connection/initialization problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1017.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- 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 Released Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.15 source package in Focal: Fix Released Status in kexec-tools source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Committed 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 Released 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 up, potentially things could go wrong there as well. kexec-tools - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality.
[Kernel-packages] [Bug 2029138] Re: cifs: fix mid leak during reconnection after timeout threshold
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1017.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- 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/2029138 Title: cifs: fix mid leak during reconnection after timeout threshold Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Status in linux-azure source package in Jammy: In Progress Status in linux source package in Lunar: Fix Committed Status in linux-azure source package in Lunar: In Progress Bug description: SRU Justification [Impact] A regression in the Ubuntu 5.15 kernel has been causing problems for multiple customers on Azure. This bug has been fixed in the mainline kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69cba9d3c1284e0838ae408830a02c4a063104bc [Test Plan] Microsoft tested [Regression Potential] Reconnections could fail. [Other Info] SF: #00365185 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2029138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031093] Re: libgnutls report "trap invalid opcode" when trying to install packages over https
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1017.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- 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/2031093 Title: libgnutls report "trap invalid opcode" when trying to install packages over https Status in ubuntu-kernel-tests: New Status in gnutls28 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in gnutls28 source package in Focal: Confirmed Status in linux source package in Focal: Fix Released Status in gnutls28 source package in Jammy: Confirmed Status in linux source package in Jammy: Fix Released Status in gnutls28 source package in Lunar: Confirmed Status in linux source package in Lunar: Fix Released Bug description: [Impact] When booting linux with Gather Data Sampling mitigations without updated microcode on an affected CPU, AVX will be disabled. This will cause programs connecting to https using gnutls on Jammy to break, including apt and git. [Test case] git clone https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests Cloning into 'autotest-client-tests'... error: git-remote-https died of signal 4 dmesg: [ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000] Works fine with the mitigation disabled by default. [Potential regressions] Users booting on affected parts without microcode updates will be subject to Gather Data Sampling attacks (which can be done by local untrusted attackers), which may leak confidential data, including keys. - When trying to install linux-libc-dev on Oracle BM.Standard2.52 (seems to be the only affected instance) with Jammy 5.15.0-81-generic, it will get interrupted with: E: Method https has died unexpectedly! E: Sub-process https received signal 4. $ sudo apt install linux-libc-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: linux-libc-dev 0 upgraded, 1 newly installed, 0 to remove and 54 not upgraded. Need to get 1353 kB of archives. After this operation, 6943 kB of additional disk space will be used. E: Method https has died unexpectedly! E: Sub-process https received signal 4. From dmesg you will see: [ 1078.750067] traps: https[4572] trap invalid opcode ip:7f3c1e6316be sp:7ffea26b61c0 error:0 in libgnutls.so.30.31.0[7f3c1e50f000+129000] Also, git clone is not working as well. $ git clone --depth=1 https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests Cloning into 'autotest-client-tests'... error: git-remote-https died of signal 4 dmesg: [ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000] libgnutls30 version:3.7.3-4ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032954] Re: Re-enable CONFIG_MEMCG on the Tegra kernels
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1017.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2032954 Title: Re-enable CONFIG_MEMCG on the Tegra kernels Status in linux-nvidia-tegra package in Ubuntu: New Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: For a time, CONFIG_MEMCG had been disabled by the RT patchset to resolve a bug in its interaction with PREEMPT_RT. This has since been resolved and the Ubuntu RT kernel has re-enabled this configuration option, but this has not been reflected in the Tegra kernels. The Tegra kernels will be updated to have this configuration option enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2032954/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031567] Re: NVIDIA pull requests 2023-08-07, 2023-08-11, 2023-08-22
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1017.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2031567 Title: NVIDIA pull requests 2023-08-07, 2023-08-11, 2023-08-22 Status in linux-nvidia-tegra package in Ubuntu: New Bug description: Apply patches from NVIDIA pull requests sent on 2023-08-07 and 2023-08-11 to jammy:linux-nvidia-tegra. 2023-08-07: Johnny Liu (1): UBUNTU: SAUCE: memory: tegra: add nvlink clients for NVGPU Revanth Kumar Uppala (1): UBUNTU: SAUCE: arm64: configs: Disable BRCMFMAC driver Sandipan Patra (1): UBUNTU: SAUCE: arm64: config: Enable ZRAM config as module Sumit Gupta (1): UBUNTU: SAUCE: soc/tegra: cbb: set ERD bit during resume for error interrupt --- 2023-08-11: Kartik (1): UBUNTU: SAUCE: tty/serial: tegra-tcu: skip esc and ccplex_id Rajkumar Kasirajan (1): UBUNTU: SAUCE: ina3221: add support for summation channel control Revanth Kumar Uppala (2): UBUNTU: SAUCE: arm64: configs: Sanitize arm64 defconfig UBUNTU: SAUCE: arm64: config: Enable configs for nf_tables Wayne Chang (1): UBUNTU: SAUCE: arm64: configs: Set USB_CONFIGFS_F_ACC to y --- 2023-08-22: Ankur Pawar (1): NVIDIA: SAUCE: arm64: configs: disable inbuilt IMX219 driver Bharath H S (2): NVIDIA: SAUCE: configs: Sync defconfigs using make defconfig NVIDIA: SAUCE: configs: Enable nvme target, tcp driver Sumit Gupta (1): NVIDIA: SAUCE: driver: cpufreq: use refclk delta based loop instead of udelay Yi-Wei Wang (1): NVIDIA: SAUCE: arm64: defconfig: Enable CONFIG_DEVFREQ_THERMAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2031567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028937] Re: [23.10 FEAT] [SEC2341] pkey: support generation of keys of type PKEY_TYPE_EP11_AES
Kernel test build(s) available in this PPA: https://launchpad.net/~fheimes/+archive/ubuntu/lp2028937 Pull request submitted to kernel team's mailing list: https://lists.ubuntu.com/archives/kernel-team/2023-September/thread.html#142499 Changing status to 'In Progress'. Assigning kernel team. ** Changed in: ubuntu-z-systems Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- 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/2028937 Title: [23.10 FEAT] [SEC2341] pkey: support generation of keys of type PKEY_TYPE_EP11_AES Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: Add support to the pkey kernel module to generate keys of key type PKEY_TYPE_EP11_AES. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2028937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034277] Re: Azure: net: mana: Add page pool for RX buffers
** Changed in: linux-azure (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Mantic) Status: New => Fix Committed ** Changed in: linux-azure (Ubuntu Mantic) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/2034277 Title: Azure: net: mana: Add page pool for RX buffers Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Lunar: In Progress Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested this path be added to the 5.15 and 6.2 Azure kernels. Add page pool for RX buffers for faster buffer cycle and reduce CPU usage. [Test Plan] MSFT tested. [Regression Potential] Could cause receive packet corruption. [Other Info] SF: #00365760 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2034277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034277] Re: Azure: net: mana: Add page pool for RX buffers
** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Lunar) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/2034277 Title: Azure: net: mana: Add page pool for RX buffers Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Lunar: In Progress Status in linux-azure source package in Mantic: New Bug description: SRU Justification [Impact] Microsoft has requested this path be added to the 5.15 and 6.2 Azure kernels. Add page pool for RX buffers for faster buffer cycle and reduce CPU usage. [Test Plan] MSFT tested. [Regression Potential] Could cause receive packet corruption. [Other Info] SF: #00365760 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2034277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034277] [NEW] Azure: net: mana: Add page pool for RX buffers
Public bug reported: SRU Justification [Impact] Microsoft has requested this path be added to the 5.15 and 6.2 Azure kernels. Add page pool for RX buffers for faster buffer cycle and reduce CPU usage. [Test Plan] MSFT tested. [Regression Potential] Could cause receive packet corruption. [Other Info] SF: #00365760 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Mantic) Importance: Undecided Status: New -- 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/2034277 Title: Azure: net: mana: Add page pool for RX buffers Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Jammy: New Status in linux-azure source package in Lunar: New Status in linux-azure source package in Mantic: New Bug description: SRU Justification [Impact] Microsoft has requested this path be added to the 5.15 and 6.2 Azure kernels. Add page pool for RX buffers for faster buffer cycle and reduce CPU usage. [Test Plan] MSFT tested. [Regression Potential] Could cause receive packet corruption. [Other Info] SF: #00365760 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2034277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2030525] Re: Installation support for SMARC RZ/G2L platform
Dear Maintainer We are not able to install Ubuntu on Renesas platform using USB sticks. (https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC). This requires following configuration update. CONFIG_RESET_RZG2L_USBPHY_CTRL=y Please can you update this configuration. We need this change urgently. We can apply this change to Mantic, if it helps to speed up the merge process. Best Regards John -- 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/2030525 Title: Installation support for SMARC RZ/G2L platform Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Lunar: New Status in linux source package in Mantic: Confirmed Bug description: Dear Maintainer The Ubuntu installation on Renesas RZ/G2L platform board is failing due to the following configuration: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n10339 The configuration CONFIG_RESET_RZG2L_USBPHY_CTRL=y is required to allow the installation on Renesas SMARC platform. Alternatively, the module "reset-rzg2l-usbphy-ctrl.ko" to be added in the inside installer initrd. This change is required on Lunar and Jammy versions as well. Please update once the changes merged to test them on Renesas SMARC RZ/G2L platform. Best Regards John To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930783] Re: integrity: Problem loading X.509 certificate
Also affects: Computer: Acer Nitro 515 Ubuntu version: Ubuntu 22.04.2 LTS Kernel: linux-image-5.19.0-35-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930783 Title: integrity: Problem loading X.509 certificate Status in linux package in Ubuntu: Confirmed Bug description: Following error shows on Acer machines while booting when UEFI boot is enabled. integrity: Problem loading X.509 certificate -65 The issue is discussed at https://bugzilla.opensuse.org/show_bug.cgi?id=1129471 and a patch is available at https://lkml.org/lkml/2019/7/16/23. Seems like this patch is not included in Ubuntu as I'm still getting this error. I'm using Linux Mint 20, which is based on Ubuntu 20.04. This error comes while live booting Ubuntu 20.04 and Ubuntu 18.04 also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034103] Re: Missing firmware for AMD GPU GC 11.0.3
linux/mantic-proposed version 6.5.0-4-generic has same hotplug blank
screen problem but without warnings.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux (Ubuntu Lunar)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/2034103
Title:
Missing firmware for AMD GPU GC 11.0.3
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
In Progress
Status in linux source package in Lunar:
Incomplete
Status in linux-firmware source package in Lunar:
Incomplete
Bug description:
Add new FWs for GPU with GC 11.0.3:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=d6d655ade8fed37b93631ef17e406afc4fff5f21
("amdgpu: add initial GC 11.0.3 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b1a7d7624fd227ebbc46a04a34fdcd08795ee69c
("amdgpu: add initial PSP 13.0.10 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b3f512fb5386e462269ad5a43fbbed6b19fd4b4f
("amdgpu: add initial SDMA 6.0.3 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=22fb12f2f61a3748b155fe083fe71b79bad7c897
("amdgpu: add initial SMU 13.0.10 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=59fbffa9ec8e4b0b31d2d13e715cf6580ad0e99c
("amdgpu: update VCN 4.0.0 firmware")
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2034103/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012157] Re: Removable storage device reset in 22.04, works fine in 16.04
Problem was solved in one of the last Ubuntu 22.04 updates (~ august 2023). -- 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/2012157 Title: Removable storage device reset in 22.04, works fine in 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is a kobo ebook reader. When I plug it in it connects but gets reset by something. I tried several cables and ports, same result. The device works fine on 16.04. some things are shown in dmesg: [31802.497386] usb 1-3: new high-speed USB device number 8 using xhci_hcd [31802.737788] usb 1-3: New USB device found, idVendor=2237, idProduct=4223, bcdDevice= 1.10 [31802.737792] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [31802.737793] usb 1-3: Product: eReader-4.25.15875 [31802.737794] usb 1-3: Manufacturer: Kobo [31802.737795] usb 1-3: SerialNumber: RN4377AT01453 [31802.756812] usb-storage 1-3:1.0: USB Mass Storage device detected [31802.756888] scsi host6: usb-storage 1-3:1.0 [31803.768914] scsi 6:0:0:0: Direct-Access Kobo eReader-4.25.158 0110 PQ: 0 ANSI: 2 [31803.769056] sd 6:0:0:0: Attached scsi generic sg3 type 0 [31803.771864] sd 6:0:0:0: Power-on or device reset occurred [31803.774869] sd 6:0:0:0: [sdd] 6614013 512-byte logical blocks: (3.39 GB/3.15 GiB) [31803.883899] sd 6:0:0:0: [sdd] Write Protect is off [31803.883903] sd 6:0:0:0: [sdd] Mode Sense: 0f 00 00 00 [31803.993898] sd 6:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [31804.218106] sdd: [31804.219125] sd 6:0:0:0: [sdd] Attached SCSI removable disk [31812.151422] r8169 :07:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM [31829.639174] logitech-djreceiver 0003:046D:C537.0002: Unexpected input report number 128 [31829.801174] logitech-djreceiver 0003:046D:C537.0002: Unexpected input report number 128 [31835.427152] usb 1-3: reset high-speed USB device number 8 using xhci_hcd [31835.589902] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=31s [31835.589906] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 00 88 00 00 78 00 [31835.589907] blk_print_req_error: 17 callbacks suppressed [31835.589908] I/O error, dev sdd, sector 136 op 0x0:(READ) flags 0x80700 phys_seg 15 prio class 0 [31835.694978] sd 6:0:0:0: Power-on or device reset occurred [31835.694987] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s [31835.694989] sd 6:0:0:0: [sdd] tag#0 Sense Key : Unit Attention [current] [31835.694991] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Power on, reset, or bus device reset occurred [31835.694992] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 01 08 00 00 08 00 [31835.694993] I/O error, dev sdd, sector 264 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [31836.078177] logitech-djreceiver 0003:046D:C537.0002: Unexpected input report number 128 [31836.210175] logitech-djreceiver 0003:046D:C537.0002: Unexpected input report number 128 [31838.124177] logitech-djreceiver 0003:046D:C537.0002: Unexpected input report number 128 [31838.258176] logitech-djreceiver 0003:046D:C537.0002: Unexpected input report number 128 [31841.381178] logitech-djreceiver 0003:046D:C537.0002: Unexpected input report number 128 [31841.505179] logitech-djreceiver 0003:046D:C537.0002: Unexpected input report number 128 [31841.680590] audit: type=1400 audit(1679182686.458:129): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=5680 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [31842.394175] logitech-djreceiver 0003:046D:C537.0002: Unexpected input report number 128 [31842.493175] logitech-djreceiver 0003:046D:C537.0002: Unexpected input report number 128 [31847.198179] logitech-djreceiver 0003:046D:C537.0002: Unexpected input report number 128 [31847.316178] logitech-djreceiver 0003:046D:C537.0002: Unexpected input report number 128 [31850.020180] logitech-djreceiver 0003:046D:C537.0002: Unexpected input report number 128 [31850.113179] logitech-djreceiver 0003:046D:C537.0002: Unexpected input report number 128 [31866.151085] usb 1-3: reset high-speed USB device number 8 using xhci_hcd [31866.314002] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=30s [31866.314007] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 01 10 00 00 f0 00 [31866.314009] I/O error, dev sdd, sector 272 op 0x0:(READ) flags 0x80700 phys_seg 28 prio class 0 [31866.316049] sd 6:0:0:0: Power-on or device reset occurred [31866.316062] sd 6:0:0:0: [sdd] tag#0 device offline or changed [31866.316065] I/O error, dev sdd, sector 272 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 0 [31866.316068] buf
[Kernel-packages] [Bug 2011357] Re: ereader USB keeps disconnecting connecting disconnecting
Problem was solved in one of the last Ubuntu 22.04 updates (~ august 2023). -- 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/2011357 Title: ereader USB keeps disconnecting connecting disconnecting Status in linux package in Ubuntu: Confirmed Bug description: I plug my kobo ereader in my Ubuntu 22.04.2 LTS, the usb device keeps disconnecting and reconnecting, $ dmesg ... [ 58.691707] usb 1-4: new high-speed USB device number 18 using xhci_hcd [ 58.928200] usb 1-4: New USB device found, idVendor=2237, idProduct=4223, bcdDevice= 1.10 [ 58.928205] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 58.928207] usb 1-4: Product: eReader-4.25.15875 [ 58.928208] usb 1-4: Manufacturer: Kobo [ 58.928209] usb 1-4: SerialNumber: RN4377AT01453 [ 58.947205] usb-storage 1-4:1.0: USB Mass Storage device detected [ 58.947381] scsi host6: usb-storage 1-4:1.0 [ 59.887296] usb 1-4: USB disconnect, device number 18 [ 60.164461] usb 1-4: new high-speed USB device number 19 using xhci_hcd [ 60.401207] usb 1-4: New USB device found, idVendor=2237, idProduct=4223, bcdDevice= 1.10 [ 60.401211] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 60.401212] usb 1-4: Product: eReader-4.25.15875 [ 60.401213] usb 1-4: Manufacturer: Kobo [ 60.401214] usb 1-4: SerialNumber: RN4377AT01453 [ 60.420212] usb-storage 1-4:1.0: USB Mass Storage device detected [ 60.420381] scsi host6: usb-storage 1-4:1.0 [ 60.431387] usb 1-4: USB disconnect, device number 19 ... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-56-generic 5.15.0-56.62 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hippo 1573 F pulseaudio /dev/snd/controlC0: hippo 1573 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 12 23:09:36 2023 EcryptfsInUse: Yes HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2022-01-12 (424 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220112) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: MATERIEL.NET BACKSTAB MAX ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=a8f69897-4682-47a4-a98e-5a95944b7803 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 23:09:53.363: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2803 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING B550-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2803:bd04/27/2022:br5.17:svnMATERIEL.NET:pnBACKSTABMAX:pvrV1:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB550-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuAR202112200049: dmi.product.family: CMA dmi.product.name: BACKSTAB MAX dmi.product.sku: AR202112200049 dmi.product.version: V1 dmi.sys.vendor: MATERIEL.NET To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
@koba Everything here has been 23.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: In Progress Bug description: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install undervolt==0.3.0) to force particular power limits (the provided values are intentional overkill): 1 │ from undervolt import read_power_limit, set_power_limit, PowerLimit, ADDRESSES 2 │ from pprint import pprint 3 │ 4 │ limits = read_power_limit(ADDRESSES) 5 │ pprint(vars(limits)) # print current values before setting them 6 │ 7 │ POWER_LIMITS = PowerLimit() 8 │ POWER_LIMITS.locked = True # lock means don't allow the value to be reset until a reboot. 9 │ POWER_LIMITS.backup_rest = 281474976776192 # afaik this is just a backup-on-failure setting, it has no effect here. 10 │ POWER_LIMITS.long_term_enabled = True 11 │ POWER_LIMITS.long_term_power = 160 # values are intentional overkill 12 │ POWER_LIMITS.long_term_time = 2880.0 13
[Kernel-packages] [Bug 2034103] Re: Missing firmware for AMD GPU GC 11.0.3
Along with proposed firmware, hotplug on Lunar kernel 6.2.0-32-generic is still not working. Will take some more fix in kernel amdgpu driver: [ 33.245252] [ cut here ] [ 33.245259] WARNING: CPU: 8 PID: 2902 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:600 amdgpu_irq_put+0x9f/0xb0 [amdgpu] [ 33.246080] Modules linked in: thunderbolt nvme_fabrics rfcomm snd_seq_dummy snd_hrtimer cmac algif_hash algif_skcipher af_alg bnep binfmt_misc snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_hda_codec_realtek snd_sof_intel_hda snd_sof_pci snd_hda_codec_generic snd_sof_xtensa_dsp ledtrig_audio snd_sof snd_sof_utils x86_pkg_temp_thermal snd_soc_hdac_hda intel_powerclamp snd_hda_ext_core iwlmvm snd_soc_acpi_intel_match snd_soc_acpi coretemp soundwire_bus r8153_ecm mac80211 snd_soc_core cdc_ether nls_iso8859_1 kvm_intel usbnet snd_compress amdgpu libarc4 ac97_bus snd_pcm_dmaengine kvm i915 snd_hda_codec_hdmi snd_hda_intel irqbypass crct10dif_pclmul iommu_v2 polyval_clmulni snd_intel_dspcfg polyval_generic gpu_sched snd_intel_sdw_acpi ghash_clmulni_intel drm_ttm_helper drm_buddy snd_hda_codec sha512_ssse3 iwlwifi btusb ttm aesni_intel btrtl btbcm snd_seq_midi drm_display_helper btintel snd_seq_midi_event snd_hda_core [ 33.246213] crypto_simd btmtk cryptd snd_rawmidi cmdlinepart snd_hwdep cec processor_thermal_device_pci snd_seq bluetooth rapl spi_nor snd_pcm rc_core r8152 processor_thermal_device snd_seq_device ecdh_generic processor_thermal_rfim mii input_leds ecc mei_hdcp mei_pxp intel_rapl_msr wmi_bmof cfg80211 joydev mtd intel_cstate drm_kms_helper snd_timer processor_thermal_mbox processor_thermal_rapl i2c_algo_bit 8250_dw syscopyarea snd sysfillrect intel_rapl_common sysimgblt soundcore int340x_thermal_zone int3400_thermal intel_hid acpi_tad mei_me acpi_thermal_rel acpi_pad sparse_keymap mei mac_hid msr parport_pc ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c dm_mirror dm_region_hash dm_log hid_generic usbhid hid spi_pxa2xx_platform dw_dmac dw_dmac_core nvme nvme_core ahci nvme_common libahci spi_intel_pci e1000e crc32_pclmul xhci_pci spi_intel i2c_i801 vmd intel_lpss_pci i2c_smbus intel_lpss xhci_pci_renesas idma64 vide o wmi [ 33.246338] pinctrl_alderlake [ 33.246344] CPU: 8 PID: 2902 Comm: kworker/8:3 Not tainted 6.2.0-32-generic #32-Ubuntu [ 33.246351] Hardware name: Intel Corporation Raptor Lake Client Platform/RPL-S ADP-S DDR5 UDIMM CRB, BIOS RPLSFWI1.R00.3047.A00.2201290228 01/29/2022 [ 33.246355] Workqueue: pm pm_runtime_work [ 33.246366] RIP: 0010:amdgpu_irq_put+0x9f/0xb0 [amdgpu] [ 33.247082] Code: 31 f6 31 ff c3 cc cc cc cc 44 89 e2 48 89 de 4c 89 f7 e8 94 fc ff ff 5b 41 5c 41 5d 41 5e 5d 31 d2 31 f6 31 ff c3 cc cc cc cc <0f> 0b b8 ea ff ff ff eb c3 b8 fe ff ff ff eb bc 90 90 90 90 90 90 [ 33.247087] RSP: 0018:c0ec06e03c10 EFLAGS: 00010246 [ 33.247093] RAX: RBX: 9d2fcf514e40 RCX: [ 33.247097] RDX: RSI: RDI: [ 33.247100] RBP: c0ec06e03c30 R08: R09: [ 33.247102] R10: R11: R12: [ 33.247105] R13: 0001 R14: 9d2fcf50 R15: 9d2fcf50 [ 33.247108] FS: () GS:9d371f60() knlGS: [ 33.247112] CS: 0010 DS: ES: CR0: 80050033 [ 33.247115] CR2: 7f3198849000 CR3: 00018461 CR4: 00750ee0 [ 33.247119] PKRU: 5554 [ 33.247122] Call Trace: [ 33.247125] [ 33.247130] ? show_regs+0x6d/0x80 [ 33.247140] ? __warn+0x89/0x160 [ 33.247151] ? amdgpu_irq_put+0x9f/0xb0 [amdgpu] [ 33.247844] ? report_bug+0x17e/0x1b0 [ 33.247858] ? handle_bug+0x46/0x90 [ 33.247867] ? exc_invalid_op+0x18/0x80 [ 33.247875] ? asm_exc_invalid_op+0x1b/0x20 [ 33.247883] ? amdgpu_irq_put+0x9f/0xb0 [amdgpu] [ 33.248577] jpeg_v4_0_hw_fini+0x84/0xd0 [amdgpu] [ 33.249402] jpeg_v4_0_suspend+0x12/0x30 [amdgpu] [ 33.250178] amdgpu_device_ip_suspend_phase2+0x25a/0x490 [amdgpu] [ 33.250695] amdgpu_device_suspend+0x142/0x1b0 [amdgpu] [ 33.251212] amdgpu_pmops_runtime_suspend+0xdf/0x200 [amdgpu] [ 33.251717] ? __pfx_vga_switcheroo_runtime_suspend+0x10/0x10 [ 33.251731] pci_pm_runtime_suspend+0x67/0x1f0 [ 33.251741] ? __pfx_vga_switcheroo_runtime_suspend+0x10/0x10 [ 33.251753] vga_switcheroo_runtime_suspend+0x23/0xc0 [ 33.251764] ? __pfx_vga_switcheroo_runtime_suspend+0x10/0x10 [ 33.251775] __rpm_callback+0x4d/0x170 [ 33.251783] ? __pfx_vga_switcheroo_runtime_suspend+0x10/0x10 [ 33.251793] rpm_callback+0x6d/0x80 [ 33.251800] ? __pfx_vga_switcheroo_runtime_suspend+0x10/0x10 [ 33.251810] rpm_suspend+0x122/0x730 [ 33.251817] ? raw_spin_rq_unlock+0x10/0x40 [ 33.251826] ? finish_tas
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)
Currently testing kernel 6.5.0-1003-oem on 5/9/2023 on 22.04 desktop and the flickering does not occur anymore -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux source package in Lunar: New Status in linux-hwe-5.19 source package in Lunar: Invalid Status in linux-hwe-6.2 source package in Lunar: Invalid Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel parameter i915.enable_dc=0 intel_idle.max_cstate=2 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
@Eli, are you using 23.04/22.04? I built with 22.04 configuration. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: In Progress Bug description: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install undervolt==0.3.0) to force particular power limits (the provided values are intentional overkill): 1 │ from undervolt import read_power_limit, set_power_limit, PowerLimit, ADDRESSES 2 │ from pprint import pprint 3 │ 4 │ limits = read_power_limit(ADDRESSES) 5 │ pprint(vars(limits)) # print current values before setting them 6 │ 7 │ POWER_LIMITS = PowerLimit() 8 │ POWER_LIMITS.locked = True # lock means don't allow the value to be reset until a reboot. 9 │ POWER_LIMITS.backup_rest = 281474976776192 # afaik this is just a backup-on-failure setting, it has no effect here. 10 │ POWER_LIMITS.long_term_enabled = True 11 │ POWER_LIMITS.long_term_power = 160 # values are intentional overkill 12 │ POWER_LIMITS.long
[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
@koba I've tried to install the vanilla kernel you linked, I'm installing with a `dpkg -i *.deb` command in a folder of the unpacked downloaded zip of that folder. I'm getting the following error (I've been having issues with the nvidia 535 driver, I don't know exactly what's going on here, currently I'm on the 525 driver. I can't tell if I can boot into this or if it failed. I'll try to find time to reboot/debug this, its the middle of my work day.): /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.4.0-060400rc3-generic Error! Could not locate dkms.conf file. File: /var/lib/dkms/nvidia/535.104.05/source/dkms.conf does not exist. Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.4.0-060400rc3-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/6.4.0-060400rc3-generic/build LD=/usr/bin/ld.bfd CONFIG_X86_KERNEL_IBT= modules(bad exit status: 2) ERROR (dkms apport): kernel package linux-headers-6.4.0-060400rc3-generic is not supported Error! Bad return status for module build on kernel: 6.4.0-060400rc3-generic (x86_64) Consult /var/lib/dkms/nvidia/525.125.06/build/make.log for more information. dkms autoinstall on 6.4.0-060400rc3-generic/x86_64 failed for nvidia(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: autoinstall for kernel 6.4.0-060400rc3-generic ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-unsigned-6.4.0-060400rc3-generic (--install): installed linux-image-unsigned-6.4.0-060400rc3-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-headers-6.4.0-060400rc3-generic linux-image-unsigned-6.4.0-060400rc3-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: In Progress Bug description: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clea
[Kernel-packages] [Bug 2033371] Re: package linux-image-6.2.0-31-generic 6.2.0-31.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
See #2034256 :D -- 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/2033371 Title: package linux-image-6.2.0-31-generic 6.2.0-31.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: Confirmed Bug description: Dunno was just upgrading. Last upgrade was problematic as well and had to roll back. This error was autogenerated mid update and have not experienced any problem per se. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-31-generic 6.2.0-31.31 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cottrell 2129 F wireplumber /dev/snd/controlC1: cottrell 2129 F wireplumber /dev/snd/seq:cottrell 2108 F pipewire CasperMD5CheckResult: unknown Date: Tue Aug 29 08:55:21 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2018-11-23 (1739 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Micro-Star International Co., Ltd. MS-7B48 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=a7722e1d-5d7c-41ca-b9f1-bb6e360731c5 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.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: dkms Title: package linux-image-6.2.0-31-generic 6.2.0-31.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: Upgraded to lunar on 2023-07-25 (34 days ago) dmi.bios.date: 03/08/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.40 dmi.board.asset.tag: Default string dmi.board.name: Z370-A PRO (MS-7B48) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.40:bd03/08/2018:br5.12:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B48:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370-APRO(MS-7B48):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B48 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2033371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034256] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034256 Title: package linux-image-6.2.0-32-generic 6.2.0-32.32 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in linux package in Ubuntu: Confirmed Bug description: See also #2033371 = Kernel 6.2.0-27 running -- kernel 6.2.0-31 installed but inoperable Upgrading to kernel 6.2.0-32.32 fails: (Reading database ... 209096 files and directories currently installed.) Purging configuration files for linux-modules-6.2.0-31-generic (6.2.0-31.31) ... Purging configuration files for linux-modules-nvidia-535-6.2.0-31-generic (6.2.0-31.31) ... Purging configuration files for linux-image-6.2.0-31-generic (6.2.0-31.31) ... Purging configuration files for linux-objects-nvidia-535-6.2.0-31-generic (6.2.0-31.31) ... Purging configuration files for linux-modules-extra-6.2.0-31-generic (6.2.0-31.31) ... Processing triggers for linux-image-6.2.0-32-generic (6.2.0-32.32) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-32-generic Sign command: /lib/modules/6.2.0-32-generic/build/scripts/sign-file Binary /lib/modules/6.2.0-32-generic/build/scripts/sign-file not found, modules won't be signed Error! Your kernel headers for kernel 6.2.0-32-generic cannot be found at /lib/modules/6.2.0-32-generic/build or /lib/modules/6.2.0-32-generic/source. Please install the linux-headers-6.2.0-32-generic package or use the --kernelsourcedir option to tell DKMS where it's located. dkms autoinstall on 6.2.0-32-generic/x86_64 failed for zfs(1) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: autoinstall for kernel 6.2.0-32-generic ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-32-generic (--configure): installed linux-image-6.2.0-32-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-6.2.0-32-generic E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up linux-image-6.2.0-32-generic (6.2.0-32.32) ... I: /boot/initrd.img.old is now a symlink to initrd.img-6.2.0-32-generic Processing triggers for linux-image-6.2.0-32-generic (6.2.0-32.32) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-32-generic Sign command: /lib/modules/6.2.0-32-generic/build/scripts/sign-file Binary /lib/modules/6.2.0-32-generic/build/scripts/sign-file not found, modules won't be signed Error! Your kernel headers for kernel 6.2.0-32-generic cannot be found at /lib/modules/6.2.0-32-generic/build or /lib/modules/6.2.0-32-generic/source. Please install the linux-headers-6.2.0-32-generic package or use the --kernelsourcedir option to tell DKMS where it's located. dkms autoinstall on 6.2.0-32-generic/x86_64 failed for zfs(1) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: autoinstall for kernel 6.2.0-32-generic ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-32-generic (--configure): installed linux-image-6.2.0-32-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-6.2.0-32-generic ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: burdi015159 F wireplumber /dev/snd/controlC0: burdi015159 F wireplumber /dev/snd/seq:burdi015157 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Sep 5 16:23:11 2023 HibernationDevice: RESUME=none IwConfig: lono wireless extensions. enp39s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C35 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p10 ro pci=noaer 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-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0
[Kernel-packages] [Bug 2034256] Re: package linux-image-6.2.0-32-generic 6.2.0-32.32 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
After pointing /boot/{initrd.img,vmlinuz} back to 6.2.0-27 and rebooting the
software-updater wanted to remove the 6.2.0-31 kernel (done) and I catched the
above log.
Indeed the /lib/modules/6.2.0-32-generic/build symlink and hence the
~/scripts/sign-file is missing.
And indeed the linux-headers-6.2.0-32-generic package is missing.
As recommended I installed that package, which resolved the problem.
:D
--
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/2034256
Title:
package linux-image-6.2.0-32-generic 6.2.0-32.32 failed to
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
return code 11
Status in linux package in Ubuntu:
Confirmed
Bug description:
See also #2033371
=
Kernel 6.2.0-27 running -- kernel 6.2.0-31 installed but inoperable
Upgrading to kernel 6.2.0-32.32 fails:
(Reading database ... 209096 files and directories currently installed.)
Purging configuration files for linux-modules-6.2.0-31-generic (6.2.0-31.31)
...
Purging configuration files for linux-modules-nvidia-535-6.2.0-31-generic
(6.2.0-31.31) ...
Purging configuration files for linux-image-6.2.0-31-generic (6.2.0-31.31) ...
Purging configuration files for linux-objects-nvidia-535-6.2.0-31-generic
(6.2.0-31.31) ...
Purging configuration files for linux-modules-extra-6.2.0-31-generic
(6.2.0-31.31) ...
Processing triggers for linux-image-6.2.0-32-generic (6.2.0-32.32) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 6.2.0-32-generic
Sign command: /lib/modules/6.2.0-32-generic/build/scripts/sign-file
Binary /lib/modules/6.2.0-32-generic/build/scripts/sign-file not found,
modules won't be signed
Error! Your kernel headers for kernel 6.2.0-32-generic cannot be found at
/lib/modules/6.2.0-32-generic/build or /lib/modules/6.2.0-32-generic/source.
Please install the linux-headers-6.2.0-32-generic package or use the
--kernelsourcedir option to tell DKMS where it's located.
dkms autoinstall on 6.2.0-32-generic/x86_64 failed for zfs(1)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
* dkms: autoinstall for kernel 6.2.0-32-generic
...fail!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: error processing package linux-image-6.2.0-32-generic (--configure):
installed linux-image-6.2.0-32-generic package post-installation script
subprocess returned error exit status 1
Errors were encountered while processing:
linux-image-6.2.0-32-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up linux-image-6.2.0-32-generic (6.2.0-32.32) ...
I: /boot/initrd.img.old is now a symlink to initrd.img-6.2.0-32-generic
Processing triggers for linux-image-6.2.0-32-generic (6.2.0-32.32) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 6.2.0-32-generic
Sign command: /lib/modules/6.2.0-32-generic/build/scripts/sign-file
Binary /lib/modules/6.2.0-32-generic/build/scripts/sign-file not found,
modules won't be signed
Error! Your kernel headers for kernel 6.2.0-32-generic cannot be found at
/lib/modules/6.2.0-32-generic/build or /lib/modules/6.2.0-32-generic/source.
Please install the linux-headers-6.2.0-32-generic package or use the
--kernelsourcedir option to tell DKMS where it's located.
dkms autoinstall on 6.2.0-32-generic/x86_64 failed for zfs(1)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
* dkms: autoinstall for kernel 6.2.0-32-generic
...fail!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: error processing package linux-image-6.2.0-32-generic (--configure):
installed linux-image-6.2.0-32-generic package post-installation script
subprocess returned error exit status 1
Errors were encountered while processing:
linux-image-6.2.0-32-generic
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-32-generic 6.2.0-32.32
ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16
Uname: Linux 6.2.0-32-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: burdi015159 F wireplumber
/dev/snd/controlC0: burdi015159 F wireplumber
/dev/snd/seq:burdi015157 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Tue Sep 5 16:23:11 2023
HibernationDevice: RESUME=none
IwConfig:
lono wireless extensions.
enp39s0 no wireless extensions.
MachineType: Micro-Star International Co., Ltd. MS-7C35
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p10 ro pci=noaer
PulseLis
[Kernel-packages] [Bug 2029390] Re: [23.10 FEAT] [SEC2352] pkey: support EP11 API ordinal 6 for secure guests
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2029390 Title: [23.10 FEAT] [SEC2352] pkey: support EP11 API ordinal 6 for secure guests Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Secure Execution guests must use the EP11 API ordinal 6 to create (generate, unwrap, derive) secure keys which encodes a NULL PIN (no session) as a string of zero-bytes. Therefore, the pkey module must be updated to check whether the Linux system is running as a secure guest and if so modify secure key creating requests (key(pair) gen, unwrap) to use ordinal 6 API. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2029390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003674] Re: [23.10 FEAT] KVM: Enable Secure Execution Crypto Passthrough - kernel part
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003674 Title: [23.10 FEAT] KVM: Enable Secure Execution Crypto Passthrough - kernel part Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Feature Description: Enable KVM and QEMU for AP passthrough to Secure Execution guests. This includes setup, configuration and teardown of AP related resources. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033654] Re: amdgpu: Fixes for S0i3 resume on Phoenix
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033654 Title: amdgpu: Fixes for S0i3 resume on Phoenix Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Hard hangs in some cases on resume from suspend on AMD Phoenix [Fix] pick three commits from v6.5-rc7 (also in 6.1.47): 730d44e1fa306a2 drm/amd/pm: skip the RLC stop when S0i3 suspend for SMU v13.0.4/11 f1740b1ab2703b2 drm/amdgpu: skip fence GFX interrupts disable/enable for S0ix a7b7d9e8aee4f71 drm/amd: flush any delayed gfxoff on suspend entry [Test Case] Check the updated kernel on a failing system, and test resume from suspend. [Where problems could occur] These are cherry-picks from upstream stable, and limited to Phoenix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034256] [NEW] package linux-image-6.2.0-32-generic 6.2.0-32.32 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Public bug reported: See also #2033371 = Kernel 6.2.0-27 running -- kernel 6.2.0-31 installed but inoperable Upgrading to kernel 6.2.0-32.32 fails: (Reading database ... 209096 files and directories currently installed.) Purging configuration files for linux-modules-6.2.0-31-generic (6.2.0-31.31) ... Purging configuration files for linux-modules-nvidia-535-6.2.0-31-generic (6.2.0-31.31) ... Purging configuration files for linux-image-6.2.0-31-generic (6.2.0-31.31) ... Purging configuration files for linux-objects-nvidia-535-6.2.0-31-generic (6.2.0-31.31) ... Purging configuration files for linux-modules-extra-6.2.0-31-generic (6.2.0-31.31) ... Processing triggers for linux-image-6.2.0-32-generic (6.2.0-32.32) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-32-generic Sign command: /lib/modules/6.2.0-32-generic/build/scripts/sign-file Binary /lib/modules/6.2.0-32-generic/build/scripts/sign-file not found, modules won't be signed Error! Your kernel headers for kernel 6.2.0-32-generic cannot be found at /lib/modules/6.2.0-32-generic/build or /lib/modules/6.2.0-32-generic/source. Please install the linux-headers-6.2.0-32-generic package or use the --kernelsourcedir option to tell DKMS where it's located. dkms autoinstall on 6.2.0-32-generic/x86_64 failed for zfs(1) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: autoinstall for kernel 6.2.0-32-generic ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-32-generic (--configure): installed linux-image-6.2.0-32-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-6.2.0-32-generic E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up linux-image-6.2.0-32-generic (6.2.0-32.32) ... I: /boot/initrd.img.old is now a symlink to initrd.img-6.2.0-32-generic Processing triggers for linux-image-6.2.0-32-generic (6.2.0-32.32) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-32-generic Sign command: /lib/modules/6.2.0-32-generic/build/scripts/sign-file Binary /lib/modules/6.2.0-32-generic/build/scripts/sign-file not found, modules won't be signed Error! Your kernel headers for kernel 6.2.0-32-generic cannot be found at /lib/modules/6.2.0-32-generic/build or /lib/modules/6.2.0-32-generic/source. Please install the linux-headers-6.2.0-32-generic package or use the --kernelsourcedir option to tell DKMS where it's located. dkms autoinstall on 6.2.0-32-generic/x86_64 failed for zfs(1) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: autoinstall for kernel 6.2.0-32-generic ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-32-generic (--configure): installed linux-image-6.2.0-32-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-6.2.0-32-generic ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: burdi015159 F wireplumber /dev/snd/controlC0: burdi015159 F wireplumber /dev/snd/seq:burdi015157 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Sep 5 16:23:11 2023 HibernationDevice: RESUME=none IwConfig: lono wireless extensions. enp39s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C35 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p10 ro pci=noaer 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-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.30 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MEG X570 UNIFY (MS-7C35) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi
[Kernel-packages] [Bug 2030721] Re: no boot after upgrade to Ubuntu 22.04.3 LTS
it is a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2031352 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2030721 Title: no boot after upgrade to Ubuntu 22.04.3 LTS Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Hi, Yersterday, after a routinely update. it seems that Ubuntu kernel was updated to 6.2.0-26 Since then my machine won't boot. i have to choose previous kernel 5.19 on grub menu My system was Ubuntu 22.04.2 LTS but it seems to have been updated to Ubuntu 22.04.3 LTS Distributor ID: Ubuntu Description: Ubuntu 22.04.3 LTS Release: 22.04 Codename: jammy here is my hardware infos 00:00.0 Host bridge: Intel Corporation Device 4668 (rev 02) 00:01.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x16 Controller #1 (rev 02) 00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 (rev 02) 00:0a.0 Signal processing controller: Intel Corporation Platform Monitoring Technology (rev 01) 00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller 00:14.0 USB controller: Intel Corporation Device 7ae0 (rev 11) 00:14.2 RAM memory: Intel Corporation Device 7aa7 (rev 11) 00:15.0 Serial bus controller: Intel Corporation Device 7acc (rev 11) 00:15.1 Serial bus controller: Intel Corporation Device 7acd (rev 11) 00:15.2 Serial bus controller: Intel Corporation Device 7ace (rev 11) 00:16.0 Communication controller: Intel Corporation Device 7ae8 (rev 11) 00:17.0 SATA controller: Intel Corporation Device 7ae2 (rev 11) 00:1a.0 PCI bridge: Intel Corporation Device 7ac8 (rev 11) 00:1b.0 PCI bridge: Intel Corporation Device 7ac0 (rev 11) 00:1c.0 PCI bridge: Intel Corporation Device 7ab8 (rev 11) 00:1d.0 PCI bridge: Intel Corporation Device 7ab0 (rev 11) 00:1f.0 ISA bridge: Intel Corporation Device 7a84 (rev 11) 00:1f.3 Audio device: Intel Corporation Device 7ad0 (rev 11) 00:1f.4 SMBus: Intel Corporation Device 7aa3 (rev 11) 00:1f.5 Serial bus controller: Intel Corporation Device 7aa4 (rev 11) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (17) I219-V (rev 11) 01:00.0 VGA compatible controller: NVIDIA Corporation GA106 [GeForce RTX 3060 Lite Hash Rate] (rev a1) 01:00.1 Audio device: NVIDIA Corporation Device 228e (rev a1) 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA106 [GeForce RTX 3060 Lite Hash Rate] [10de:2504] (rev a1) Subsystem: Gigabyte Technology Co., Ltd GA106 [GeForce RTX 3060 Lite Hash Rate] [1458:4096] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2030721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033025] Re: Fix numerous AER related issues
** 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/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029914] Re: package linux-image-6.2.0-26-generic (not installed) failed to install/upgrade: installed linux-image-6.2.0-26-generic package pre-removal script subprocess returne
Also posted question here: https://ubuntuforums.org/showthread.php?t=2490463&p=14156773#post14156773 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2029914 Title: package linux-image-6.2.0-26-generic (not installed) failed to install/upgrade: installed linux-image-6.2.0-26-generic package pre- removal script subprocess returned error exit status 1 Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Lenovo Legion R7000P ARH7 (2022 model) (Chineese version) Crashes with kernels greater than 5.15 (got crashes using kernels 5.19, 6.1 and 6.2) Tried with Ubuntu 22.04, 22.10, 23.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic (not installed) ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Aug 4 15:30:21 2023 ErrorMessage: installed linux-image-6.2.0-26-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2023-07-21 (14 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-signed-hwe-6.2 Title: package linux-image-6.2.0-26-generic (not installed) failed to install/upgrade: installed linux-image-6.2.0-26-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2029914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032767] Re: Fix ACPI TAD on some Intel based systems
** 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/2032767 Title: Fix ACPI TAD on some Intel based systems 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-oem-6.5 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-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] ACPI TAD doesn't really work on several systems. When accessing TAD interface via sysfs, like setting/getting realtime, it also causes errors: [ 478.255453] ACPI Error: No handler for Region [RTCM] (a8d2dd39) [SystemCMOS] (20230331/evregion-130) [ 478.255458] ACPI Error: Region SystemCMOS (ID=5) has no handler (20230331/exfldio-261) [ 478.255461] Initialized Local Variables for Method [_GRT]: [ 478.255461] Local1: f182542cInteger [ 478.255464] No Arguments are initialized for method [_GRT] [ 478.255465] ACPI Error: Aborting method \_SB.AWAC._GRT due to previous error (AE_NOT_EXIST) (20230331/psparse-529) [Fix] Let the driver to install a handler for its SystemCMOS region. The spec on whether certain devices can use SystemCMOS or not is quite vague, so follow the de facto implementation, Windows :) [Test] Once the patch is applied, setting and getting realtime through TAD sysfs work, and there's no more error in dmesg. [Where problems could occur] Now ACPI TAD driver also depends on ACPI RTC driver, so the memory usage will go up slightly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2032767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034095] Re: Fix a regression from 6.3-rc1 which causes Cirrus audio codec resume failure
** Changed in: linux-oem-6.5 (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 in Ubuntu. https://bugs.launchpad.net/bugs/2034095 Title: Fix a regression from 6.3-rc1 which causes Cirrus audio codec resume failure Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Incomplete Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] [Impact] The two CS42L42 codecs fails to output sound after runtime resume since kernel 6.3-rc1. [Fix] Backport a fix from Cirrus on https://patchwork.kernel.org/project/alsa-devel/patch/20230904160033.908135-1-vita...@opensource.cirrus.com/. [Test] 1. Power on the laptop 2. Wait for at least 1 minute after login Ubuntu 3. Go to the audio settings and press the audio output test button 4. Verify if there's any audio output [Where problems could occur] It only happens on particular audio codec and clarified by the vendor that the delay during resume will suffice after fix across different versions of kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033923] Re: latest xubuntu jammy daily isos fail to install on asus, lenovo & msi
The deprecation of systemd-udev-settle.service has been in place since at least v243[1], and upstream OpenZFS has been tracking this for a few years[2]. I don't think anything should change in systemd WRT the deprecation notice. [1] https://github.com/systemd/systemd/commit/1662732768d4846805bb0143eb08bfaa38e89423 [2] https://github.com/systemd/systemd/commit/1662732768d4846805bb0143eb08bfaa38e89423 ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2033923 Title: latest xubuntu jammy daily isos fail to install on asus, lenovo & msi Status in Ubuntu CD Images: Invalid Status in linux-hwe-6.2 package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: New Bug description: Hi, I downloaded the latest xubuntu jammy images 20230901 (and previous ones, verified them) On a Mac all went well with a fresh install, however on a Lenovo, Asus, MSI the installer fails... udev startup job hangs and is restarted several times with 3 minutes increments I get several different errors: Dependency failed for Install ZFS kernel module Dependency failed for Import ZFS,... Failing start job without limit! Load Kernel Module efi_pstore Thank you for sorting this out Kind regards Otto To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/2033923/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032704] Re: Fix panel brightness issues on HP laptops
** 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/2032704 Title: Fix panel brightness issues on HP laptops 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-oem-6.5 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-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Brightness can't be changed or can only be changed once on some modern HP laptops. [Fix] BIOS folks identified the issue where the ACPI _PS0 method isn't called for the panel device. On Windows the method is being invoked. This is due to missing _PSC, but since Windows is the de facto spec, we have to perform the same to make the device functional. [Test] Once the fix is applied, the brightness can be changed smoothly. [Where problems could occur] According to BIOS folks, Windows also invokes _PS3 for sleep and shutdown, we need to tackle that in the future. Right now not calling _PS3 has no ill-effect, per BIOS folks. X-HWE-Bug: Bug #2032704 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2032704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033452] Re: Enable D3cold at s2idle for Intel DG2 GPU
** 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/2033452 Title: Enable D3cold at s2idle for Intel DG2 GPU Status in HWE Next: In Progress Status in linux 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.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: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The system wakes up during s2idle with Intel DG2 GPU. It causes high power consumption during suspend. [Fix] Enable D3cold at s2idle. [Test] Tested on hardware, the system sleeps as long as expected, the power consumption is lower. [Where problems could occur] It may break i915 driver. It's a fix of regression in v6.1, no need for jammy and already in 6.5. SRU for lunar and oem-6.1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034068] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2034068 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034068 Title: Ubuntu 22.04.3 linux 6.2 fails to autodetect nvidia aditional drivers Status in linux package in Ubuntu: Incomplete Bug description: After the system upgrades to 22.04.3 LTS using kernel 6.2, my nvidia card can't be located using "Software and Updates"->"More Drivers", my NVIDIA card. Using 'lspci' I got this: ´´´ 01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] (rev a1) ´´´ The system just stoped to use this card, with a big performance impact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034068/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034068] Re: Ubuntu 22.04.3 linux 6.2 fails to autodetect nvidia aditional drivers
** Package changed: systemd (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034068 Title: Ubuntu 22.04.3 linux 6.2 fails to autodetect nvidia aditional drivers Status in linux package in Ubuntu: Incomplete Bug description: After the system upgrades to 22.04.3 LTS using kernel 6.2, my nvidia card can't be located using "Software and Updates"->"More Drivers", my NVIDIA card. Using 'lspci' I got this: ´´´ 01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] (rev a1) ´´´ The system just stoped to use this card, with a big performance impact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034068/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034068] [NEW] Ubuntu 22.04.3 linux 6.2 fails to autodetect nvidia aditional drivers
You have been subscribed to a public bug: After the system upgrades to 22.04.3 LTS using kernel 6.2, my nvidia card can't be located using "Software and Updates"->"More Drivers", my NVIDIA card. Using 'lspci' I got this: ´´´ 01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] (rev a1) ´´´ The system just stoped to use this card, with a big performance impact. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Ubuntu 22.04.3 linux 6.2 fails to autodetect nvidia aditional drivers https://bugs.launchpad.net/bugs/2034068 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2030858] Re: Jammy update: v6.1.41 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2030858 Title: Jammy update: v6.1.41 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released 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.41 upstream stable release from git://git.kernel.org/ Linux 6.1.41 x86/cpu/amd: Add a Zenbleed fix x86/cpu/amd: Move the errata checking functionality up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2030858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2030859] Re: Jammy update: v6.1.42 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2030859 Title: Jammy update: v6.1.42 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released 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.42 upstream stable release from git://git.kernel.org/ Linux 6.1.42 Revert "drm/amd/display: edp do not add non-edid timings" drm/amd/display: Add polling method to handle MST reply packet drm/amd/display: fix linux dp link lost handled only one time drm/amd/display: Clean up errors & warnings in amdgpu_dm.c drm/amd/display: force connector state when bpc changes during compliance drm/dp_mst: Clear MSG_RDY flag before sending new message drm/amd/display: fix some coding style issues drm/amd/display: use max_dsc_bpp in amdgpu_dm selftests/bpf: Fix sk_assign on s390x selftests/bpf: Workaround verification failure for fexit_bpf2bpf/func_replace_return_code selftests/bpf: make test_align selftest more robust bpf: aggressively forget precise markings during state checkpointing bpf: stop setting precise in current state bpf: allow precision tracking for programs with subprogs scripts/kallsyms: update the usage in the comment block scripts/kallsyms.c Make the comment up-to-date with current implementation kallsyms: add kallsyms_seqs_of_names to list of special symbols spi: dw: Remove misleading comment for Mount Evans SoC drm/ttm: fix bulk_move corruption when adding a entry tracing/histograms: Return an error if we fail to add histogram to hist_vars list jbd2: recheck chechpointing non-dirty buffer net: phy: prevent stale pointer dereference in phy_init() tcp: annotate data-races around fastopenq.max_qlen tcp: annotate data-races around icsk->icsk_user_timeout tcp: annotate data-races around tp->notsent_lowat tcp: annotate data-races around rskq_defer_accept tcp: annotate data-races around tp->linger2 tcp: annotate data-races around icsk->icsk_syn_retries tcp: annotate data-races around tp->keepalive_probes tcp: annotate data-races around tp->keepalive_intvl tcp: annotate data-races around tp->keepalive_time tcp: annotate data-races around tp->tsoffset tcp: annotate data-races around tp->tcp_tx_delay Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor() Bluetooth: ISO: fix iso_conn related locking and validity issues Bluetooth: hci_event: call disconnect callback before deleting conn Bluetooth: use RCU for hci_conn_params and iterate safely in hci_sync netfilter: nf_tables: skip bound chain on rule flush netfilter: nf_tables: skip bound chain in netns release path netfilter: nft_set_pipapo: fix improper element removal netfilter: nf_tables: can't schedule in nft_chain_validate netfilter: nf_tables: fix spurious set element insertion failure ALSA: hda/realtek: Fix generic fixup definition for cs35l41 amp llc: Don't drop packet from non-root netns. fbdev: au1200fb: Fix missing IRQ check in au1200fb_drv_probe Revert "tcp: avoid the lookup process failing to get sk in ehash table" net:ipv6: check return value of pskb_trim() net: ipv4: Use kfree_sensitive instead of kfree tcp: annotate data-races around tcp_rsk(req)->ts_recent tcp: annotate data-races around tcp_rsk(req)->txhash net: ipv4: use consistent txhash in TIME_WAIT and SYN_RECV igc: Prevent garbled TX queue with XDP ZEROCOPY igc: Avoid transmit queue timeout for XDP bpf, arm64: Fix BTI type used for freplace attached functions bpf: Repeat check_max_stack_depth for async callbacks bpf: Fix subprog idx logic in check_max_stack_depth octeontx2-pf: Dont allocate BPIDs for LBK interfaces security: keys: Modify mismatched function name iavf: fix reset task race with iavf_remove() iavf: fix a deadlock caused by rtnl and driver's lock circular dependencies iavf: Wait for reset in callbacks which trigger it iavf: make functions static where possible iavf: send VLAN offloading caps once after VFR iavf: Move netdev_update_features() into watchdog task iavf: use internal state to free traffic IRQs iavf: Fix out-of-bounds when setting channels on remove iavf: Fix use-after-free in free_netdev net: dsa: microchip: correct KSZ8795 static MAC table access net: dsa: mi
[Kernel-packages] [Bug 2033327] Re: Desktop cannot resume after suspend: screen not detected
Got it; so what happened is there is a separate malloc call elsewhere in the amdgpu display code that failed due to the low memory situation. Is this a "one time thing" or is this a regular occurrence that you can reproduce in how you use your machine? I would have to look at context to see if it made sense to reserve that memory all the time, but if this is the only place that explodes maybe we can store a local variable in the amdgpu device structure for the thing that is malloc'ed. -- 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/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Confirmed Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchp
[Kernel-packages] [Bug 2033533] Re: [qxl] installing with lvm and encryption requires arrow key spam after reboot to get to encryption passphrase prompt
Removed the kernel task because there's no evidence yet the qxl driver
is doing anything wrong.
I might attempt a Plymouth fix for bug 1869655 and this before 23.10 but
that wouldn't be without risks.
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2033533
Title:
[qxl] installing with lvm and encryption requires arrow key spam after
reboot to get to encryption passphrase prompt
Status in plymouth package in Ubuntu:
New
Bug description:
This also happens with the canary image and is happening with the
Mantic daily image.
When installing with LVM and encryption, after the "remove
installation medium and press enter to reboot", the user is greeted
with a permanent black screen. After pressing arrow keys, the gui
prompt is then shown to prompt the user to put in the encryption
passphrase.
It is also somehow possible to not get the black screen by changing
the grub prior to installing by removing splash from the grub options.
The user is then greeted with a text-only passphrase prompt after
rebooting.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 30 16:39:39 2023
InstallationDate: Installed on 2023-08-30 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
SourcePackage: subiquity
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-08-30 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: ubiquity
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Tags: mantic third-party-packages wayland-session
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Uname: Linux 6.3.0-7-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages. If that does not
work, then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.16.0-debian-1.16.0-5
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-7.2
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.16.0-debian-1.16.0-5:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-7.2
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2033533/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
This also fixed the problem on my end. My Dell xps 15 9510 NVIDIA GA107m RTX3050 Ti Linux version 6.2.0-31-generic (buildd@lcy02-amd64-032) (x86_64-linux-gnu-gcc-11 (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) On Tue, Sep 5, 2023 at 12:50 AM Juan Manuel Vicente < 2031...@bugs.launchpad.net> wrote: > After following @juergh updates. I realized the problem was the nouveau > drivers, also I saw my fresh installation (Ubuntu 22.04.3) was not > detecting my RTX 3070. So I fixed both problems installing the drivers. > > > sudo apt install nvidia-driver-535 > > Now, I can shutdown and/or restart my machine without issues. The only > problem is this driver is the propertary one. However in my case is not > a problem. > > Regards > Juan > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2031352 > > Title: > Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot > screen > > Status in linux package in Ubuntu: > Confirmed > Status in linux-hwe-6.2 package in Ubuntu: > Confirmed > Status in systemd package in Ubuntu: > Invalid > Status in linux-hwe-6.2 source package in Jammy: > Confirmed > Status in linux source package in Lunar: > Confirmed > > Bug description: > [Impact] > > After updating to Kernel 6.2 a few days ago, I have been experiencing > issues with my system's shutdown and reboot functions. During these > processes, the system becomes unresponsive and hangs on a black > screen, which displays both the Dell and Ubuntu logos. This issue is > inconsistent; it happens sporadically. Currently, the only workaround > I've found to successfully shut down the system is to forcibly power > off the machine by holding down the power button for 5 seconds. > > I've also tested a fresh installation of Ubuntu 22.04.3. > > [Fix] > > Updated patch from linux-next: > https://patchwork.freedesktop.org/patch/538562/ > > [Test Case] > > Suspend,resume,shutdown,reboot should all work correctly. No nouveau > stack trace in the kernel log. > > [Where Problems Could Occur] > > Limited to nouveau driver that wants to load nonexistent ACR firmware. > Only nvidia GPUs are affected. > > [Additional information] > > > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: systemd 249.11-0ubuntu3.9 > ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 > Uname: Linux 6.2.0-26-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.11-0ubuntu82.5 > Architecture: amd64 > CasperMD5CheckResult: pass > CurrentDesktop: ubuntu:GNOME > Date: Mon Aug 14 22:41:14 2023 > InstallationDate: Installed on 2023-08-14 (1 days ago) > InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) > MachineType: Dell Inc. XPS 8930 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic > root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 > SourcePackage: systemd > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 03/14/2023 > dmi.bios.release: 1.1 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.1.30 > dmi.board.name: 0T88YD > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 3 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: Not Specified > dmi.modalias: > dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: > dmi.product.family: XPS > dmi.product.name: XPS 8930 > dmi.product.sku: 0859 > dmi.product.version: 1.1.30 > dmi.sys.vendor: Dell Inc. > modified.conffile..etc.default.apport: ># set this to 0 to disable apport, or to 1 to enable it ># you can temporarily override this with ># sudo service apport start force_start=1 >enabled=0 > mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 > mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031352/+subscriptions > > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2031352 Title: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Bug description: [Impact] After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; i
[Kernel-packages] [Bug 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
@juanma-v82 this also fixed my issue. > sudo apt install nvidia-driver-535 Linux version 6.2.0-31-generic (buildd@lcy02-amd64-032) (x86_64-linux- gnu-gcc-11 (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) Dell xps 15 9510 NVIDIA Corporation GA107M [GeForce RTX 3050 Ti Mobile] Regards, Ian -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2031352 Title: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Bug description: [Impact] After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. [Fix] Updated patch from linux-next: https://patchwork.freedesktop.org/patch/538562/ [Test Case] Suspend,resume,shutdown,reboot should all work correctly. No nouveau stack trace in the kernel log. [Where Problems Could Occur] Limited to nouveau driver that wants to load nonexistent ACR firmware. Only nvidia GPUs are affected. [Additional information] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.30 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.30 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025040] Re: increased power usage after upgrade from kinetic to lunar
Confirm that 6.2.0-34.34 can reach package C8 -- 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/2025040 Title: increased power usage after upgrade from kinetic to lunar Status in linux package in Ubuntu: Fix Committed Bug description: Hi I have just upgrade and power usage is double or more under lunar. Kernel version went from 5.19.0-43 to 6.2.0-20. Running powertop, I see that C8 is being used with 5.19 but 6.2 does not go to a higher power saving state than C3. I tried the Ubuntu kernel from jammy ie 5.15.0-73. It also uses C8. I have also tried the 5.15.108 & 5.10.17 mainline kernels. Both of these do not go to higher power saving state than C3. All these tests have been run on the same partition ie. only the kernel version has changed. Laptop is a HP 15s-fq4011TU 11th Gen Intel with Tiger Lake Iris Xe graphics. So it seems to me: 1) Ubuntu has applied a patch to the mainline kernel that improves power saving in 5.15 and 5.19 2) This patch either hasn't been applied to 6.2 or no longer works. Could you pls let me know what other info you need or what I could look at next? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034088] Re: 4k white screen on kernel-6.20 with AMD7950x
** Changed in: linux Status: Unknown => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034088 Title: 4k white screen on kernel-6.20 with AMD7950x Status in Linux: New Status in linux-hwe-6.2 package in Ubuntu: New Bug description: 1. AMD7950X, without any other gpu 2. 4k display 3. if kernel.version >= 6.14 => the 4k display white screen ps1: https://gitlab.freedesktop.org/drm/amd/-/issues/2354 ps2: this bug has occured long time ago, but amd never fix it, so i can not upgrade my ubuntu kernel version to default 6.20 for ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116 Uname: Linux 5.15.0-83-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 5 10:46:23 2023 DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164e] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8877] InstallationDate: Installed on 2023-07-31 (35 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic root=UUID=656f1bf0-3f83-44eb-9793-47a2aeaa819a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2023-08-30 (5 days ago) dmi.bios.date: 07/28/2023 dmi.bios.release: 16.36 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1636 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING B650M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1636:bd07/28/2023:br16.36:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650M-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034095] Re: Fix a regression from 6.3-rc1 which causes Cirrus audio codec resume failure
** Tags added: oem-priority originate-from-2031060 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034095 Title: Fix a regression from 6.3-rc1 which causes Cirrus audio codec resume failure Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: Incomplete Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] [Impact] The two CS42L42 codecs fails to output sound after runtime resume since kernel 6.3-rc1. [Fix] Backport a fix from Cirrus on https://patchwork.kernel.org/project/alsa-devel/patch/20230904160033.908135-1-vita...@opensource.cirrus.com/. [Test] 1. Power on the laptop 2. Wait for at least 1 minute after login Ubuntu 3. Go to the audio settings and press the audio output test button 4. Verify if there's any audio output [Where problems could occur] It only happens on particular audio codec and clarified by the vendor that the delay during resume will suffice after fix across different versions of kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034095] Re: Fix a regression from 6.3-rc1 which causes Cirrus audio codec resume failure
** No longer affects: linux (Ubuntu Lunar) ** No longer affects: linux-oem-6.5 (Ubuntu 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/2034095 Title: Fix a regression from 6.3-rc1 which causes Cirrus audio codec resume failure Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: Incomplete Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] [Impact] The two CS42L42 codecs fails to output sound after runtime resume since kernel 6.3-rc1. [Fix] Backport a fix from Cirrus on https://patchwork.kernel.org/project/alsa-devel/patch/20230904160033.908135-1-vita...@opensource.cirrus.com/. [Test] 1. Power on the laptop 2. Wait for at least 1 minute after login Ubuntu 3. Go to the audio settings and press the audio output test button 4. Verify if there's any audio output [Where problems could occur] It only happens on particular audio codec and clarified by the vendor that the delay during resume will suffice after fix across different versions of kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034088] Re: 4k white screen on kernel-6.20 with AMD7950x
It looks like kernel 5.15 is only working because there's no graphics driver there that supports the GPU. So it's defaulting to legacy software rendering which kind of works... You can do the same in kernel 6.2 by using the kernel parameter "nomodeset". ** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu) ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2354 https://gitlab.freedesktop.org/drm/amd/-/issues/2354 ** Also affects: linux via https://gitlab.freedesktop.org/drm/amd/-/issues/2354 Importance: Unknown Status: Unknown ** Tags added: amdgpu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034088 Title: 4k white screen on kernel-6.20 with AMD7950x Status in Linux: Unknown Status in linux-hwe-6.2 package in Ubuntu: New Bug description: 1. AMD7950X, without any other gpu 2. 4k display 3. if kernel.version >= 6.14 => the 4k display white screen ps1: https://gitlab.freedesktop.org/drm/amd/-/issues/2354 ps2: this bug has occured long time ago, but amd never fix it, so i can not upgrade my ubuntu kernel version to default 6.20 for ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116 Uname: Linux 5.15.0-83-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 5 10:46:23 2023 DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164e] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8877] InstallationDate: Installed on 2023-07-31 (35 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic root=UUID=656f1bf0-3f83-44eb-9793-47a2aeaa819a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2023-08-30 (5 days ago) dmi.bios.date: 07/28/2023 dmi.bios.release: 16.36 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1636 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING B650M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1636:bd07/28/2023:br16.36:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650M-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034088] [NEW] 4k white screen on kernel-6.20 with AMD7950x
You have been subscribed to a public bug: 1. AMD7950X, without any other gpu 2. 4k display 3. if kernel.version >= 6.14 => the 4k display white screen ps1: https://gitlab.freedesktop.org/drm/amd/-/issues/2354 ps2: this bug has occured long time ago, but amd never fix it, so i can not upgrade my ubuntu kernel version to default 6.20 for ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116 Uname: Linux 5.15.0-83-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 5 10:46:23 2023 DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164e] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8877] InstallationDate: Installed on 2023-07-31 (35 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic root=UUID=656f1bf0-3f83-44eb-9793-47a2aeaa819a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2023-08-30 (5 days ago) dmi.bios.date: 07/28/2023 dmi.bios.release: 16.36 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1636 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING B650M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1636:bd07/28/2023:br16.36:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650M-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ubuntu -- 4k white screen on kernel-6.20 with AMD7950x https://bugs.launchpad.net/bugs/2034088 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
I've built a test kernel with the referenced fixes: https://kernel.ubuntu.com/~juergh/lp2031537/ Can somebody test it please? Note that it's an unsigned kernel so you need to temporarily disable SecureBoot in the BIOS to be able to boot it. Install linux-image-unsigned, linux-modules and probably linux- modules-extra. Let us know if that fixes the issue. -- 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/2031537 Title: Ethernet not stable 23.04 (RTL8168/8169) Status in linux package in Ubuntu: Confirmed Bug description: hello, it is my first time reporting a pug hope it is the last there is thread here https://ubuntuforums.org/showthread.php?t=2489146&p=14151513 another user experienced similar issue my network work fine at startup keep working for hours then disconnect and cannot reconnect without a restart I tested the cable using another pc and it was working repluged with no difference I thought it is caused by nvidia driver so changed it and the problem persist I use systemd-networkd uname -a Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux lspci: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b) dmesg: [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): apparmor="ALLOWED" operation="file_perm" class="file" profile="libreoffice-oosplash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [Mon Aug 7 12:39:19 2023] [ cut here ] [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clm ulni_intel rc_core [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus xhci_pci_renesas idma64 wmi pinctrl_cannonlake [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 6.2.0-26-generic #26-Ubuntu [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 2.13.1 05/10/2023 [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246 [Mon Aug 7 12:39:19 2023] RAX: RBX: 997996868000 RCX: [Mon Aug 7 12:39:19 2023] RDX: RSI: RDI: [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08: R09: [Mon Aug 7 12:39:19 2023] R10: R11: R12: 9979968684c8 [Mon Aug 7 12:39:19 2023] R13: 99799686841c R14: R15: [Mon Aug 7 12:39:19 2023] FS: () GS:997da930() knlGS: [Mon Aug 7 12:39:19 2023] CS: 0010 DS: ES: CR0: 80050033 [Mon Aug 7 12:39:19 2023] CR2: 0c4c01aa8000
[Kernel-packages] [Bug 2034103] Re: Missing firmware for AMD GPU GC 11.0.3
All the commits were in linux-firmware/mantic now.
For linux-firmware/jammy, it takes one more ancestor commit 683c91f7e82c
("amdgpu: update VCN 4.0.0 firmware for amd.5.5 release").
** Also affects: linux-firmware (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-firmware (Ubuntu)
Status: New => Fix Released
** Changed in: linux-firmware (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Lunar)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux-firmware (Ubuntu Lunar)
Importance: Undecided => High
** Changed in: linux-firmware (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux-firmware (Ubuntu Lunar)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
--
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/2034103
Title:
Missing firmware for AMD GPU GC 11.0.3
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Lunar:
In Progress
Bug description:
Add new FWs for GPU with GC 11.0.3:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=d6d655ade8fed37b93631ef17e406afc4fff5f21
("amdgpu: add initial GC 11.0.3 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b1a7d7624fd227ebbc46a04a34fdcd08795ee69c
("amdgpu: add initial PSP 13.0.10 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b3f512fb5386e462269ad5a43fbbed6b19fd4b4f
("amdgpu: add initial SDMA 6.0.3 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=22fb12f2f61a3748b155fe083fe71b79bad7c897
("amdgpu: add initial SMU 13.0.10 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=59fbffa9ec8e4b0b31d2d13e715cf6580ad0e99c
("amdgpu: update VCN 4.0.0 firmware")
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2034103/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034103] [NEW] Missing firmware for AMD GPU GC 11.0.3
Public bug reported:
Add new FWs for GPU with GC 11.0.3:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=d6d655ade8fed37b93631ef17e406afc4fff5f21
("amdgpu: add initial GC 11.0.3 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b1a7d7624fd227ebbc46a04a34fdcd08795ee69c
("amdgpu: add initial PSP 13.0.10 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b3f512fb5386e462269ad5a43fbbed6b19fd4b4f
("amdgpu: add initial SDMA 6.0.3 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=22fb12f2f61a3748b155fe083fe71b79bad7c897
("amdgpu: add initial SMU 13.0.10 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=59fbffa9ec8e4b0b31d2d13e715cf6580ad0e99c
("amdgpu: update VCN 4.0.0 firmware")
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-firmware (Ubuntu Jammy)
Importance: Undecided
Status: New
** Affects: linux-firmware (Ubuntu Lunar)
Importance: Undecided
Status: New
** Tags: amd oem-priority originate-from-2028601
** Tags added: amd oem-priority originate-from-2028601
--
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/2034103
Title:
Missing firmware for AMD GPU GC 11.0.3
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
New
Status in linux-firmware source package in Jammy:
New
Status in linux-firmware source package in Lunar:
New
Bug description:
Add new FWs for GPU with GC 11.0.3:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=d6d655ade8fed37b93631ef17e406afc4fff5f21
("amdgpu: add initial GC 11.0.3 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b1a7d7624fd227ebbc46a04a34fdcd08795ee69c
("amdgpu: add initial PSP 13.0.10 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b3f512fb5386e462269ad5a43fbbed6b19fd4b4f
("amdgpu: add initial SDMA 6.0.3 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=22fb12f2f61a3748b155fe083fe71b79bad7c897
("amdgpu: add initial SMU 13.0.10 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=59fbffa9ec8e4b0b31d2d13e715cf6580ad0e99c
("amdgpu: update VCN 4.0.0 firmware")
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2034103/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033533] Re: [qxl] installing with lvm and encryption requires arrow key spam after reboot to get to encryption passphrase prompt
Great stuff :) Let me know if you need anything else o7
--
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/2033533
Title:
[qxl] installing with lvm and encryption requires arrow key spam after
reboot to get to encryption passphrase prompt
Status in linux package in Ubuntu:
Confirmed
Status in plymouth package in Ubuntu:
New
Bug description:
This also happens with the canary image and is happening with the
Mantic daily image.
When installing with LVM and encryption, after the "remove
installation medium and press enter to reboot", the user is greeted
with a permanent black screen. After pressing arrow keys, the gui
prompt is then shown to prompt the user to put in the encryption
passphrase.
It is also somehow possible to not get the black screen by changing
the grub prior to installing by removing splash from the grub options.
The user is then greeted with a text-only passphrase prompt after
rebooting.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 30 16:39:39 2023
InstallationDate: Installed on 2023-08-30 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
SourcePackage: subiquity
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-08-30 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: ubiquity
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Tags: mantic third-party-packages wayland-session
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Uname: Linux 6.3.0-7-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages. If that does not
work, then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.16.0-debian-1.16.0-5
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-7.2
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.16.0-debian-1.16.0-5:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-7.2
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033533/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
