[Kernel-packages] [Bug 1554455] Re: "update-initramfs" is executed several times when you remove old kernels
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (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/1554455 Title: "update-initramfs" is executed several times when you remove old kernels Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Here is an example. I had several old kernels: linux-image-3.19.0-49-generic linux-image-4.2.0-25-generic linux-signed-image-3.19.0-49-generic linux-signed-image-4.2.0-25-generic I used apt-get autoremove and here is the result: apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: grub-pc-bin linux-headers-3.19.0-49 linux-headers-3.19.0-49-generic linux-image-3.19.0-49-generic linux-image-4.2.0-25-generic linux-image-extra-3.19.0-49-generic linux-image-extra-4.2.0-25-generic linux-signed-image-3.19.0-49-generic linux-signed-image-4.2.0-25-generic 0 upgraded, 0 newly installed, 9 to remove and 0 not upgraded. After this operation, 502 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 211099 files and directories currently installed.) Removing grub-pc-bin (2.02~beta2-9ubuntu1.7) ... Removing linux-headers-3.19.0-49-generic (3.19.0-49.55~14.04.1) ... Removing linux-headers-3.19.0-49 (3.19.0-49.55~14.04.1) ... Removing linux-signed-image-3.19.0-49-generic (3.19.0-49.55~14.04.1) ... Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.2.0-30-generic Found initrd image: /boot/initrd.img-4.2.0-30-generic Found linux image: /boot/vmlinuz-4.2.0-27-generic Found initrd image: /boot/initrd.img-4.2.0-27-generic Found linux image: /boot/vmlinuz-3.19.0-51-generic Found initrd image: /boot/initrd.img-3.19.0-51-generic Found linux image: /boot/vmlinuz-3.19.0-49-generic Found initrd image: /boot/initrd.img-3.19.0-49-generic Found linux image: /boot/vmlinuz-4.2.0-30-generic Found initrd image: /boot/initrd.img-4.2.0-30-generic Found linux image: /boot/vmlinuz-4.2.0-27-generic Found initrd image: /boot/initrd.img-4.2.0-27-generic Found linux image: /boot/vmlinuz-3.19.0-51-generic Found initrd image: /boot/initrd.img-3.19.0-51-generic Found linux image: /boot/vmlinuz-3.19.0-49-generic Found initrd image: /boot/initrd.img-3.19.0-49-generic Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi Found Ubuntu Xenial Xerus (development branch) (16.04) on /dev/mapper/VG-root Adding boot menu entry for EFI firmware configuration done Removing linux-image-extra-3.19.0-49-generic (3.19.0-49.55~14.04.1) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic update-initramfs: Generating /boot/initrd.img-3.19.0-49-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.2.0-30-generic Found initrd image: /boot/initrd.img-4.2.0-30-generic Found linux image: /boot/vmlinuz-4.2.0-27-generic Found initrd image: /boot/initrd.img-4.2.0-27-generic Found linux image: /boot/vmlinuz-3.19.0-51-generic Found initrd image: /boot/initrd.img-3.19.0-51-generic Found linux image: /boot/vmlinuz-3.19.0-49-generic Found initrd image: /boot/initrd.img-3.19.0-49-generic Found linux image: /boot/vmlinuz-4.2.0-30-generic Found initrd image: /boot/initrd.img-4.2.0-30-generic Found linux image: /boot/vmlinuz-4.2.0-27-generic Found initrd image: /boot/initrd.img-4.2.0-27-generic Found linux image: /boot/vmlinuz-3.19.0-51-generic Found initrd image: /boot/initrd.img-3.19.0-51-generic Found linux image: /boot/vmlinuz-3.19.0-49-generic Found initrd image: /boot/initrd.img-3.19.0-49-generic Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi Found Ubuntu Xenial Xerus (development branch) (16.04) on /dev/mapper/VG-root Adding boot menu entry for EFI firmware configuration done Removing linux-image-3.19.0-49-generic (3.19.0-49.55~14.04.1) ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic update-initramfs: Deleting /boot/initrd.img-3.19.0-49-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub
[Kernel-packages] [Bug 1934582] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518994/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518988/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518993/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518980/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518979/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518992/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518976/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518978/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518990/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518975/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] Re: Cannot recover after Suspend
apport information ** Tags added: apport-collected ** Description changed: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu65.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: skelem 4294 F pulseaudio + /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio + /dev/snd/controlC0: skelem 4294 F pulseaudio + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 21.04 + InstallationDate: Installed on 2021-07-07 (42 days ago) + InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) + MachineType: HP OMEN by HP Laptop 17-cb1xxx + NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair + Package: linux (not installed) + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 + RelatedPackageVersions: + linux-restricted-modules-5.11.0-31-generic N/A + linux-backports-modules-5.11.0-31-generic N/A + linux-firmware 1.197.3 + Tags: hirsute + Uname: Linux 5.11.0-31-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data + _MarkForUpload: True + dmi.bios.date: 11/04/2020 + dmi.bios.release: 15.20 + dmi.bios.vendor: AMI + dmi.bios.version: F.20 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: 8748 + dmi.board.vendor: HP + dmi.board.version: 05.33 + dmi.chassis.type: 10 + dmi.chassis.vendor: HP + dmi.chassis.version: Chassis Version + dmi.ec.firmware.release: 5.33 + dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: + dmi.product.family: 103C_5335KV HP OMEN + dmi.product.name: OMEN by HP Laptop 17-cb1xxx + dmi.product.sku: 1X445UA#ABA + dmi.sys.vendor: HP ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518974/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute
[Kernel-packages] [Bug 1934582] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518984/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518987/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518981/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518977/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518983/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518982/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518985/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518989/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1934582/+attachment/5518986/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skelem 4294 F pulseaudio /dev/snd/pcmC1D0p: skelem 4294 F...m pulseaudio /dev/snd/controlC0: skelem 4294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-07 (42 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP OMEN by HP Laptop 17-cb1xxx NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_0815n1@/vmlinuz-5.11.0-31-generic root=ZFS=rpool/ROOT/ubuntu_0815n1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm colord crontab dip fax games gnats lpadmin mail netdev pulse pulse-access sambashare scanner src staff sudo svn tape tty urbackup uucp vboxusers www-data _MarkForUpload: True dmi.bios.date: 11/04/2020 dmi.bios.release: 15.20 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8748 dmi.board.vendor: HP dmi.board.version: 05.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 5.33 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/04/2020:br15.20:efr5.33:svnHP:pnOMENbyHPLaptop17-cb1xxx:pvr:rvnHP:rn8748:rvr05.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb1xxx dmi.product.sku: 1X445UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940488] Re: dell300x: rsi wifi and bluetooth crash after suspend and resume
** Description changed: - This bug is for tracking purpose. + I tested the upstream stable kernel 4.19.191, also could reproduce + this issue, and reported this testing result to stable mail list. + + + [Impact] + On the Dell300x machine, after system suspend and resume, the wifi + and bluetooth can't work anymore. + + [Fix] + Revert a patch which was applied to bionic kernel from stable update. + + [Test] + Booting up with the patched kernel, run $sudo rtcwake -m freeze -s 10, + then check dmesg to make sure there is crashing log, and run 'nmcli d + wifi' and 'bluetoothctl, power on, scan on', all worked well. + + [Where problems could occur] + After applying this SRU, the rsi wifi and bluetooth could have come + change, like wifi and bluetooth can't work well after resume, but this + possibility is very low, I already run '$sudo rtcwake -m freeze -s 10' + for 50 times, the wifi and bluetooth still worked well. -- 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/1940488 Title: dell300x: rsi wifi and bluetooth crash after suspend and resume Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I tested the upstream stable kernel 4.19.191, also could reproduce this issue, and reported this testing result to stable mail list. [Impact] On the Dell300x machine, after system suspend and resume, the wifi and bluetooth can't work anymore. [Fix] Revert a patch which was applied to bionic kernel from stable update. [Test] Booting up with the patched kernel, run $sudo rtcwake -m freeze -s 10, then check dmesg to make sure there is crashing log, and run 'nmcli d wifi' and 'bluetoothctl, power on, scan on', all worked well. [Where problems could occur] After applying this SRU, the rsi wifi and bluetooth could have come change, like wifi and bluetooth can't work well after resume, but this possibility is very low, I already run '$sudo rtcwake -m freeze -s 10' for 50 times, the wifi and bluetooth still worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows
** Tags removed: cosmic disco ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1799679 Title: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Nvidia driver causes Xorg to use 100% CPU and shows high lag and stutter... but only when dragging glxgears/glxheads, or any window over them. Other apps do not exhibit the problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 24 19:11:15 2018 InstallationDate: Installed on 2018-05-26 (151 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1799679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940488] [NEW] dell300x: rsi wifi and bluetooth crash after suspend and resume
Public bug reported: This bug is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: High Status: In Progress ** Tags: oem-priority originate-from-1936685 plano ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Tags added: oem-priority originate-from-1936685 plano ** Summary changed: - rsi wifi and bluetooth crash after suspend and resume + dell300x: rsi wifi and bluetooth crash after suspend and resume -- 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/1940488 Title: dell300x: rsi wifi and bluetooth crash after suspend and resume Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940154] Re: Xorg freeze (nouveau/ttm use-after-free with full-screen video)
> I don't see why it shouldn't run Linux for more than 11 years. Linux itself is not the problem. The problem is just with Nvidia GPUs more than a few years old. Nvidia stops supporting older GPUs in their current drivers after a few years. And the older drivers that do support the older GPUs only support older kernel versions. So you would need to be using Ubuntu 20.04 with kernel 5.4 on this machine and then you would have the ability to use the stable Nvidia-340 driver. Also Ubuntu 20.04 is supported for much longer than 21.04 (https://wiki.ubuntu.com/Releases). The free nouveau driver that's built into the Linux kernel is frankly unfinished and causes a lot of bugs. Even when it's not causing bugs, the performance of that driver does not compare to Nvidia's own proprietary drivers. -- 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/1940154 Title: Xorg freeze (nouveau/ttm use-after-free with full-screen video) Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to Ubuntu 21.04 yesterday, I've noticed several hangs during full-screen video playback (watching Youtube videos in Chromium). Often, it happens just after or during the switch to full- screen. The system stays running and I can connect via ssh, but restarting gdm3 has no effect and most of the time I've had to reboot. The latest hang recovered automatically when I left the machine alone for about 2 minutes, and produced the following messages in dmesg (I'll attach a more complete log): ``` [ 3520.856803] [TTM] Buffer eviction failed [ 3520.856856] [ cut here ] [ 3520.856859] refcount_t: underflow; use-after-free. [ 3520.856888] WARNING: CPU: 3 PID: 6842 at lib/refcount.c:28 refcount_warn_saturate+0xae/0xf0 ... [ 3520.857292] Call Trace: [ 3520.857305] ttm_bo_put+0x3f/0x50 [ttm] [ 3520.857331] nouveau_gem_new+0xc4/0x100 [nouveau] [ 3520.857611] ? nouveau_gem_new+0x100/0x100 [nouveau] [ 3520.857871] nouveau_gem_ioctl_new+0x5b/0x100 [nouveau] [ 3520.858133] ? nouveau_gem_new+0x100/0x100 [nouveau] [ 3520.858398] drm_ioctl_kernel+0xae/0xf0 [drm] [ 3520.858500] drm_ioctl+0x245/0x400 [drm] [ 3520.858586] ? nouveau_gem_new+0x100/0x100 [nouveau] [ 3520.858850] ? __fget_files+0x5f/0x90 [ 3520.858864] ? __fget_light+0x32/0x80 [ 3520.858879] nouveau_drm_ioctl+0x66/0xc0 [nouveau] [ 3520.859145] __x64_sys_ioctl+0x91/0xc0 [ 3520.859158] do_syscall_64+0x38/0x90 [ 3520.859170] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 3520.859182] RIP: 0033:0x7fce8ceb0317 ``` ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 16 23:36:04 2021 DistUpgraded: 2021-08-15 02:10:41,733 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GT218M [GeForce 310M] [10de:0a70] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd GT218M [GeForce 310M] [144d:c079] InstallationDate: Installed on 2014-06-27 (2607 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. Q430/Q530 ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=fc20db83-0138-4e0c-b7e9-04da38c1e9e9 ro quiet splash acpi_backlight=vendor crashkernel=512M-:192M acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to hirsute on 2021-08-15 (1 days ago) dmi.bios.date: 05/29/2010 dmi.bios.release: 2.0 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 02KF.M008.20100529.KSJ dmi.board.asset.tag: Tag 12345 dmi.board.name: Q430/Q530 dmi.board.vendor: SAMSUNG ELECTRONICS
[Kernel-packages] [Bug 1939966] Re: Random system stops
Thanks. Unfortunately that's not showing any crashes that would freeze the whole system... https://errors.ubuntu.com/user/33b53024b6560a3f0dadd0a3a5d1ad8822eb6f710ba414e81e95f3d16e6364a25093a5802b05a6d529c5e1af30a072e3c4eae81025a134ac4ea39a6b8be4dc79 ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: Random system stops Status in linux package in Ubuntu: Incomplete Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939966/+subscriptions --
[Kernel-packages] [Bug 1893493] Re: ubuntu groovy desktop, change screen position and lost background, then background went low-signal blotchy tv like
*** This bug is a duplicate of bug 1925279 *** https://bugs.launchpad.net/bugs/1925279 Since groovy has reached end-of-life let's use bug 1925279 instead. ** This bug has been marked a duplicate of bug 1925279 ubuntu desktop install & background is changing on selecting options(drop-downs) in ubiquity -- 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/1893493 Title: ubuntu groovy desktop, change screen position and lost background, then background went low-signal blotchy tv like Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu groovy QA-test (live) I changed screen setup to match my setup (2x 1920x1080 displays one above the other, the default-right got moved to above my other monitor). On doing this screen background disappeared and became black. On using system, background changes from all BLACK to blocky-low- signal digital-tv like blocks that is unusable for reading detail on screen, but it seems to return to all black in time (or with use) I can change wallpapers and that appears to work correctly at least for a time, the new wallpaper will disappear (again with time or use) and wallpaper goes dead-black again (though primary screen may also have mimimized windows appearing in blocky-low-signal-tv like; not neat and readable but messy & changing.. nice easy black on second monitor) I've been unable to take screen dumps, not sure why. /var/crash/ is empty Minimized windows do not disappear from screen, hitting minimize on a window does nothing (visually). It's these images that appear to become the blocky-blotchety-low-signal background that eventually becomes all black. Once a window was made to minimize, even though image is fully on screen, clicking mouse on visible-window works now like you're clicking background (though minimized window is displayed). If i could get screendumps this effect could be lost. Currently this report is low quality (can't get screencaptures, no photo), but the behavior differs between my screens. My upper screen is a lot less problematic than my-lower (primary) display. Opening the menu blackens (completely) the background on lower display (yeah, the older windows that were minimized can be distracting..) and improves usability. /var/crash now has contents ubuntu@ubuntu:~$ ls -la /var/crash total 168 drwxrwsrwt 1 root whoopsie100 Aug 29 01:18 . drwxr-xr-x 1 root root160 Aug 28 08:15 .. -rw-r- 1 ubuntu whoopsie 164662 Aug 29 01:18 _usr_share_apport_dump_acpi_tables.py.999.crash -rw-rw-r-- 1 ubuntu whoopsie 0 Aug 29 01:18 _usr_share_apport_dump_acpi_tables.py.999.upload -rw--- 1 whoopsie whoopsie 37 Aug 29 01:18 _usr_share_apport_dump_acpi_tables.py.999.uploaded I haven't worked out a pattern on what causes the strange behavior, it's not all the time -- however I can create the worst of it by just changing the screen orientation (even just a little). Do that and any chosen wallpaper is gone, and my background appears to be filled with detail from possibly prior? pages!?? eg. rather than my two screens directly one above the other, I move to top to be slight left/right a little.. As I type this into firefox window (on lp), I'm getting glitches on the background that is somewhat distracting/annoying. I wouldn't use this system as it is. The issue is likely graphics driver related.. though I've tagged kernel. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4611 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 29 01:17:01 2020 IwConfig: lono wireless extensions. enp0s25 no wireless extensions. LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200828) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version:
[Kernel-packages] [Bug 1929504] Re: Add support for IO functions of AAEON devices
-- 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/1929504 Title: Add support for IO functions of AAEON devices Status in linux package in Ubuntu: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: [Impact] Require drivers to enable AAEON devices. [Fix] AAEON provides a series of patches to support its GPIO/LED/Watchdog/HWMON devices. https://www.spinics.net/lists/linux-gpio/msg61301.html [Test] Verified on AAEON platform. [Where problems could occur] No, they are new drivers, should not introduce any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940486] 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 1940486 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/1940486 Title: M570 trackball doesn't work after latest kernel update. Status in linux package in Ubuntu: Incomplete Bug description: After latest kernel update my trackball mouse (Logitech M570) stop working after system is wake up from sleep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939966] [NEW] Random system stops
You have been subscribed to a public bug: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal ubuntu -- Random system stops https://bugs.launchpad.net/bugs/1939966 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 1940486] Re: M570 trackball doesn't work after latest kernel update.
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940486 Title: M570 trackball doesn't work after latest kernel update. Status in linux package in Ubuntu: New Bug description: After latest kernel update my trackball mouse (Logitech M570) stop working after system is wake up from sleep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940486] [NEW] M570 trackball doesn't work after latest kernel update.
You have been subscribed to a public bug: After latest kernel update my trackball mouse (Logitech M570) stop working after system is wake up from sleep. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- M570 trackball doesn't work after latest kernel update. https://bugs.launchpad.net/bugs/1940486 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 1931021] Re: Focal (20.04): IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
Please delete this bug report. The bug has been fixed in Focal. -- 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/1931021 Title: Focal (20.04): IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49 Status in linux package in Ubuntu: Incomplete Bug description: The bug reported at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926030 affects Focal (20.04). I use an IR remote with the ir-keytable package. Everything was working fine until kernel 5.8.0-49 was automatically installed by Software Updater on Ubuntu 20.04.2. When any key is pressed on the remote, the key is repeated about 500 times. The kernel is now 5.8.0-50, and the problem persists. Other users on the MythTV mailing list are reporting the issue, and it appears that the problem is related to changes in the following files: drivers/media/rc/ir-mce_kbd-decoder.c drivers/media/rc/rc-main.c b/drivers/media/rc/rc-main.c drivers/media/rc/serial_ir.c It has been reported that reverting the ir-mce_kbd-decoder.c and rc- main.c files to the older versions fixes the problem. /proc/version_signature > version.log: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 lspci -vnvn: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:590f] (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1043:8694] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore ir-keytable -V: IR keytable control version 1.18.0 lsb_release -rd: Description: Ubuntu 20.04.2 LTS Release: 20.04 uname -r: 5.8.0-55-generic This test F-hwe-5.8 / G-5.8 kernel works: https://people.canonical.com/~phlin/kernel/lp-1926030-revert-for-ir/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940482] Re: [thunderx2] Synchronous external abort: 96000610 [#1] SMP
After some further poking, The latest Internal Error (via kernel
5.4.0-83-generic #93-Ubuntu) has rendered the system responsive via
network communication , (ICMP) requests. However, ssh itself appears to
sit idle indefinitely when trying to login to the machine remotely.
OpenSSH_7.6p1 Ubuntu-4ubuntu0.5, OpenSSL 1.0.2n 7 Dec 2017
debug1: Reading configuration data /home/maas/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: /etc/ssh/ssh_config line 59: Applying options for *
debug1: auto-mux: Trying existing master
debug2: fd 3 setting O_NONBLOCK
debug2: mux_client_hello_exchange: master version 4
debug3: mux_client_forwards: request forwardings: 0 local, 0 remote
debug3: mux_client_request_session: entering
debug3: mux_client_request_alive: entering
debug3: mux_client_request_alive: done pid = 174117
debug3: mux_client_request_session: session request sent
Something else is at play, however, we can not see what it is due to
this being a cloud image. Login on the CLI is not allowed.
--
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/1940482
Title:
[thunderx2] Synchronous external abort: 96000610 [#1] SMP
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
Incomplete
Bug description:
[Impact]:
ThunderX2 will not deploy Focal, Arm64 Cloud Image - 20210811
focal": {"stable": {"content_id": "maas:v2:download", "kflavor": "generic",
"path": "ubuntu/arm64/ga-20.04/focal/20210811/boot-initrd", "product_name":
"maas:boot:ubuntu:arm64:ga-20.04:focal"
[ 286.968817] Internal error: synchronous external abort: 96000610 [#1] SMP
[ 286.975594] Modules linked in: nls_iso8859_1 bcache crc64 zfs(PO)
zunicode(PO) zlua(PO) zcommon(PO) znvpair(PO) zavl(PO) icp(PO) spl(O)
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua overlay btrfs zstd_compress
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear i2c_smbus hid_generic
ast drm_vram_helper ttm usbhid drm_kms_helper crct10dif_ce hid syscopyarea
ghash_ce sysfillrect sha2_ce qede mpt3sas sha256_arm64 ipmi_ssif sysimgblt uas
sha1_ce fb_sys_fops qed ipmi_devintf igb raid_class drm ipmi_msghandler
scsi_transport_sas ahci i2c_algo_bit crc8 gpio_xlp i2c_xlp9xx usb_storage
aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher
[ 287.040312] CPU: 1 PID: 1 Comm: shutdown Tainted: P O
5.4.0-80-generic #90-Ubuntu
[ 287.049083] Hardware name: To be filled by O.E.M. Saber/Saber, BIOS
0ACKL030 06/04/2020
[ 287.057072] pstate: 6049 (nZCv daif +PAN -UAO)
[ 287.061864] pc : igb_rd32+0x30/0xd8 [igb]
[ 287.065865] lr : __igb_shutdown+0x84/0x1d8 [igb]
[ 287.070468] sp : 80001255bb90
[ 287.073769] x29: 80001255bb90 x28: 00bf5434e900
[ 287.079067] x27: x26: 009eef029130
[ 287.084365] x25: x24: 009ed603ce08
[ 287.089663] x23: 80001255bc37 x22: 009eef029000
[ 287.094960] x21: 009ed603ce08 x20: 0008
[ 287.100258] x19: 8000301c0008 x18:
[ 287.10] x17: x16: 0032
[ 287.110853] x15: 0004 x14: 0003
[ 287.116150] x13: x12: 009ed50f3530
[ 287.121448] x11: 009ed50f3478 x10:
[ 287.126745] x9 : 0001 x8 : 00210d00
[ 287.132043] x7 : x6 : 0001
[ 287.137340] x5 : x4 : fe027b2d5c20
[ 287.142638] x3 : 00bf5434e900 x2 :
[ 287.147935] x1 : 8000301c x0 : 890491c4
[ 287.153234] Call trace:
[ 287.155673] igb_rd32+0x30/0xd8 [igb]
[ 287.159326] __igb_shutdown+0x84/0x1d8 [igb]
[ 287.163586] igb_shutdown+0x38/0x90 [igb]
[ 287.167585] pci_device_shutdown+0x48/0x88
[ 287.171670] device_shutdown+0x14c/0x298
[ 287.175582] kernel_restart_prepare+0x48/0x58
[ 287.179925] kernel_restart+0x24/0x80
[ 287.183573] __do_sys_reboot+0x100/0x228
[ 287.187482] __arm64_sys_reboot+0x30/0x40
[ 287.191480] el0_svc_common.constprop.0+0xe4/0x1f0
[ 287.196256] el0_svc_handler+0x38/0xa8
[ 287.13] el0_svc+0x10/0x2c8
[ 287.203124] Code: d503201f f94006a1 b40002c1 8b344033 (b9400273)
[ 287.209320] ---[ end trace b2addffb79e92219 ]---
[ 287.214039] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b
[ 287.221755] Kernel Offset: disabled
[ 287.225231] CPU features: 0x6002,62000c38
[ 287.229226] Memory Limit: none
[ 287.232296] ---[ end Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b ]---
Rom...
CRC: len=0xf080, cal=0x27ff5de9, img=0x27ff5de9, match!
[Test Case]:
Deploy
[Kernel-packages] [Bug 1940485] [NEW] thermald often limits CPU frequency while on AC
Public bug reported: I'm not entirely sure if this is a thermald issue, but on my laptop (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC, is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz turbo frequency. Restarting thermald (with `systemctl restart thermald`) will let the system scale up to the expected ~3.8GHz boost frequency. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thermald 2.4.6-1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:24:56 2021 InstallationDate: Installed on 2021-06-26 (53 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: thermald (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- 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/1940485 Title: thermald often limits CPU frequency while on AC Status in thermald package in Ubuntu: New Bug description: I'm not entirely sure if this is a thermald issue, but on my laptop (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC, is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz turbo frequency. Restarting thermald (with `systemctl restart thermald`) will let the system scale up to the expected ~3.8GHz boost frequency. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thermald 2.4.6-1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:24:56 2021 InstallationDate: Installed on 2021-06-26 (53 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940482] Re: [thunderx2] Synchronous external abort: 96000610 [#1] SMP
Full Log Attached
** Attachment added: "thunderx2focalupdate.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940482/+attachment/5518866/+files/thunderx2focalupdate.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1940482
Title:
[thunderx2] Synchronous external abort: 96000610 [#1] SMP
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
Incomplete
Bug description:
[Impact]:
ThunderX2 will not deploy Focal, Arm64 Cloud Image - 20210811
focal": {"stable": {"content_id": "maas:v2:download", "kflavor": "generic",
"path": "ubuntu/arm64/ga-20.04/focal/20210811/boot-initrd", "product_name":
"maas:boot:ubuntu:arm64:ga-20.04:focal"
[ 286.968817] Internal error: synchronous external abort: 96000610 [#1] SMP
[ 286.975594] Modules linked in: nls_iso8859_1 bcache crc64 zfs(PO)
zunicode(PO) zlua(PO) zcommon(PO) znvpair(PO) zavl(PO) icp(PO) spl(O)
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua overlay btrfs zstd_compress
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear i2c_smbus hid_generic
ast drm_vram_helper ttm usbhid drm_kms_helper crct10dif_ce hid syscopyarea
ghash_ce sysfillrect sha2_ce qede mpt3sas sha256_arm64 ipmi_ssif sysimgblt uas
sha1_ce fb_sys_fops qed ipmi_devintf igb raid_class drm ipmi_msghandler
scsi_transport_sas ahci i2c_algo_bit crc8 gpio_xlp i2c_xlp9xx usb_storage
aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher
[ 287.040312] CPU: 1 PID: 1 Comm: shutdown Tainted: P O
5.4.0-80-generic #90-Ubuntu
[ 287.049083] Hardware name: To be filled by O.E.M. Saber/Saber, BIOS
0ACKL030 06/04/2020
[ 287.057072] pstate: 6049 (nZCv daif +PAN -UAO)
[ 287.061864] pc : igb_rd32+0x30/0xd8 [igb]
[ 287.065865] lr : __igb_shutdown+0x84/0x1d8 [igb]
[ 287.070468] sp : 80001255bb90
[ 287.073769] x29: 80001255bb90 x28: 00bf5434e900
[ 287.079067] x27: x26: 009eef029130
[ 287.084365] x25: x24: 009ed603ce08
[ 287.089663] x23: 80001255bc37 x22: 009eef029000
[ 287.094960] x21: 009ed603ce08 x20: 0008
[ 287.100258] x19: 8000301c0008 x18:
[ 287.10] x17: x16: 0032
[ 287.110853] x15: 0004 x14: 0003
[ 287.116150] x13: x12: 009ed50f3530
[ 287.121448] x11: 009ed50f3478 x10:
[ 287.126745] x9 : 0001 x8 : 00210d00
[ 287.132043] x7 : x6 : 0001
[ 287.137340] x5 : x4 : fe027b2d5c20
[ 287.142638] x3 : 00bf5434e900 x2 :
[ 287.147935] x1 : 8000301c x0 : 890491c4
[ 287.153234] Call trace:
[ 287.155673] igb_rd32+0x30/0xd8 [igb]
[ 287.159326] __igb_shutdown+0x84/0x1d8 [igb]
[ 287.163586] igb_shutdown+0x38/0x90 [igb]
[ 287.167585] pci_device_shutdown+0x48/0x88
[ 287.171670] device_shutdown+0x14c/0x298
[ 287.175582] kernel_restart_prepare+0x48/0x58
[ 287.179925] kernel_restart+0x24/0x80
[ 287.183573] __do_sys_reboot+0x100/0x228
[ 287.187482] __arm64_sys_reboot+0x30/0x40
[ 287.191480] el0_svc_common.constprop.0+0xe4/0x1f0
[ 287.196256] el0_svc_handler+0x38/0xa8
[ 287.13] el0_svc+0x10/0x2c8
[ 287.203124] Code: d503201f f94006a1 b40002c1 8b344033 (b9400273)
[ 287.209320] ---[ end trace b2addffb79e92219 ]---
[ 287.214039] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b
[ 287.221755] Kernel Offset: disabled
[ 287.225231] CPU features: 0x6002,62000c38
[ 287.229226] Memory Limit: none
[ 287.232296] ---[ end Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b ]---
Rom...
CRC: len=0xf080, cal=0x27ff5de9, img=0x27ff5de9, match!
[Test Case]:
Deploy Focal/Arm64-Generic to a ThunderX2 in the MAAS (Metal As a Service)
provisioner. Using MAAS version: 2.9.3~beta1 (9197-g.afe92bb63) via a snap,
the daily focal image appears to be 20210811
From the kernel teams standpoint this kernel in the initrd, did pass
SRU testing before its release.
[Fix]:
N/A
[Regression]:
Probably No (From Kernel Viewpoint) this could possibly be caused by
something other than kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940482/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940482] Re: [thunderx2] Synchronous external abort: 96000610 [#1] SMP
After updating the MAAS images to use an update version of the -stable images, it now appears the ThunderX2 will boot with focal linux-generic: See Below, The Deployed kernel did not experience a "synchronous external abort: 96000610 [#1] SMP" when a reboot command was issued to power cycle. Deployed Kernel: 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 19:10:30 UTC 2021 After rebooting into the new -proposed kernel at this time, the Host came up , followed by the kernel panic. This did NOT render the system unusable. Upgraded Kernel: 5.4.0-83-generic #93-Ubuntu helo-kernel login: [ 139.500352] Internal error: synchronous external abort: 96000610 [#1] SMP [ 139.507134] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua joydev input_leds ipmi_ssif ipmi_devintf ipmi_msghandler thunderx2_pmu cppc_cpufreq sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear i2c_smbus hid_generic usbhid hid uas ast drm_vram_helper ttm crct10dif_ce drm_kms_helper ghash_ce syscopyarea sha2_ce sysfillrect sha256_arm64 mpt3sas sysimgblt usb_storage qede sha1_ce fb_sys_fops raid_class qed drm scsi_transport_sas igb ahci i2c_algo_bit crc8 gpio_xlp i2c_xlp9xx aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [ 139.570639] CPU: 56 PID: 4157 Comm: landscape-sysin Not tainted 5.4.0-83-generic #93-Ubuntu [ 139.578976] Hardware name: To be filled by O.E.M. Saber/Saber, BIOS 0ACKL030 06/04/2020 [ 139.586965] pstate: 2049 (nzCv daif +PAN -UAO) [ 139.591767] pc : qed_memcpy_hw+0x98/0x140 [qed] [ 139.596295] lr : qed_memcpy_hw+0x12c/0x140 [qed] [ 139.600898] sp : 8000364131b0 [ 139.604199] x29: 8000364131b0 x28: [ 139.609497] x27: 009ee6803538 x26: [ 139.614795] x25: 1000 x24: 800036413298 [ 139.620093] x23: 01d04b68 x22: 0040 [ 139.625391] x21: 009ed9b70090 x20: 0040 [ 139.630688] x19: x18: [ 139.635986] x17: x16: [ 139.641283] x15: x14: [ 139.646581] x13: x12: 0020 [ 139.651878] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f [ 139.657176] x9 : x8 : 8000364132d8 [ 139.662473] x7 : 800036413298 x6 : 000f [ 139.667771] x5 : x4 : 0040 [ 139.673068] x3 : 01d04b68 x2 : 800025b8a000 [ 139.678366] x1 : 800025b8 x0 : 0010 [ 139.683665] Call trace: [ 139.686110] qed_memcpy_hw+0x98/0x140 [qed] [ 139.690289] qed_memcpy_from+0x64/0xc0 [qed] [ 139.694555] __qed_get_vport_mstats+0x90/0x148 [qed] [ 139.699515] _qed_get_vport_stats+0x198/0x298 [qed] [ 139.704388] qed_get_vport_stats+0x30/0x88 [qed] [ 139.708997] qede_fill_by_demand_stats+0x44/0x290 [qede] [ 139.714297] qede_get_stats64+0x30/0xd0 [qede] [ 139.718729] dev_get_stats+0x6c/0xd8 [ 139.722292] rtnl_fill_stats+0x50/0x148 [ 139.726115] rtnl_fill_ifinfo+0x510/0xd60 [ 139.730110] rtnl_dump_ifinfo+0x25c/0x528 [ 139.734108] netlink_dump+0xfc/0x330 [ 139.737671] __netlink_dump_start+0x144/0x1c0 [ 139.742013] rtnetlink_rcv_msg+0x240/0x338 [ 139.746096] netlink_rcv_skb+0x60/0x120 [ 139.749918] rtnetlink_rcv+0x2c/0x38 [ 139.753480] netlink_unicast+0x188/0x210 [ 139.757389] netlink_sendmsg+0x1c0/0x368 [ 139.761301] sock_sendmsg+0x58/0x68 [ 139.764776] __sys_sendto+0xe8/0x158 [ 139.768338] __arm64_sys_sendto+0x34/0x48 [ 139.772335] el0_svc_common.constprop.0+0xe4/0x1f0 [ 139.777112] el0_svc_handler+0x38/0xa8 [ 139.780848] el0_svc+0x10/0x2c8 [ 139.783980] Code: d37e7cc8 91001108 8b0800e8 b4000140 (b9400046) [ 139.790060] ---[ end trace f0a24c697c627870 ]--- [ 415.995884] Internal error: synchronous external abort: 96000610 [#2] SMP [ 416.002669] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua joydev input_leds ipmi_ssif ipmi_devintf ipmi_msghandler thunderx2_pmu cppc_cpufreq sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear i2c_smbus hid_generic usbhid hid uas ast drm_vram_helper ttm crct10dif_ce drm_kms_helper ghash_ce syscopyarea sha2_ce sysfillrect sha256_arm64 mpt3sas sysimgblt usb_storage qede sha1_ce fb_sys_fops raid_class qed drm scsi_transport_sas igb ahci i2c_algo_bit crc8 gpio_xlp i2c_xlp9xx aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [ 416.066204] CPU: 0 PID: 14 Comm: kworker/0:1 Tainted: G D 5.4.0-83-generic #93-Ubuntu [ 416.075323] Hardware name: To be filled by O.E.M. Saber/Saber, BIOS 0ACKL030 06/04/2020 [ 416.083337] Workqueue: events
[Kernel-packages] [Bug 1932081] Re: Disable hv-kvp-daemon.service on certain instance types
This bug was fixed in the package linux - 5.13.0-14.14 --- linux (5.13.0-14.14) impish; urgency=medium * impish/linux: 5.13.0-14.14 -proposed tracker (LP: #1938565) * Miscellaneous Ubuntu changes - SAUCE: Revert "UBUNTU: SAUCE: random: Make getrandom() ready earlier" - SAUCE: random: properly make getrandom() ready earlier * Miscellaneous upstream changes - seq_buf: Fix overflow in seq_buf_putmem_hex() - bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc - ext4: cleanup in-core orphan list if ext4_truncate() failed to get a transaction handle - ext4: fix kernel infoleak via ext4_extent_header - ext4: fix overflow in ext4_iomap_alloc() - ext4: return error code when ext4_fill_flex_info() fails - ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit - ext4: remove check for zero nr_to_scan in ext4_es_scan() - ext4: fix avefreec in find_group_orlov - ext4: use ext4_grp_locked_error in mb_find_extent -- Andrea Righi Mon, 02 Aug 2021 14:23:08 +0200 ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932081 Title: Disable hv-kvp-daemon.service on certain instance types Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: [Impact] * Disable hv-kvp-daemon.service on certain instance types. As requested for some azure instance types, hv-kvp-daemon is prohibited from starting, and currently it takes a long time to come up and fail. Configure to disable the service on those instances. At the moment, we can key off kernel command line to detect those. [Test Plan] * Boot preview image in azure * Check that hv-kvp-daemon.service is not running [Where problems could occur] * The conditions/detection could have been more specific as to when the daemon is pointless to run. Thus key-off kernel commandline is good enough for now, but may require changes in the future. [Other Info] @ Kernel team, also see https://trello.com/c/JbomiFOe https://lists.ubuntu.com/archives/kernel-team/2021-June/121384.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928686] Re: Some cloud kernels have Android related config options disabled
This bug was fixed in the package linux-oracle - 5.11.0-1015.16+21.10.1 --- linux-oracle (5.11.0-1015.16+21.10.1) impish; urgency=medium * impish/linux-oracle: 5.11.0-1015.16+21.10.1 -proposed tracker (LP: #1936492) * Packaging resync (LP: #1786013) - update dkms package versions [ Ubuntu: 5.11.0-1015.16 ] * hirsute/linux-oracle: 5.11.0-1015.16 -proposed tracker (LP: #1938476) * arm64 support (LP: #1925421) - [packaging] oracle: Enabling arm64 - [config] oracle: Update arm64 configs to match annotations - [packaging] oracle: Update annotations for arm64 [ Ubuntu: 5.11.0-1014.15 ] * hirsute/linux-oracle: 5.11.0-1014.15 -proposed tracker (LP: #1936494) * Packaging resync (LP: #1786013) - update dkms package versions * large_dir in ext4 broken (LP: #1933074) - SAUCE: ext4: fix directory index node split corruption * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293) - Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test" * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645) - selftests: icmp_redirect: support expected failures * Mute/mic LEDs no function on some HP platfroms (LP: #1934878) - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 450 G8 - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 445 G8 - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 630 G8 * [SRU][OEM-5.10/H] Fix HDMI output issue on Intel TGL GPU (LP: #1934864) - drm/i915: Fix HAS_LSPCON macro for platforms between GEN9 and GEN10 * mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC (LP: #1934239) - ALSA: hda/realtek: fix mute/micmute LEDs for HP EliteBook 830 G8 Notebook PC * ubuntu-host driver lacks lseek ops (LP: #1934110) - ubuntu-host: add generic lseek op * ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8 (LP: #1927749) - selftests/ftrace: fix event-no-pid on 1-core machine * Hirsute update: upstream stable patchset 2021-06-29 (LP: #1934012) - proc: Track /proc/$pid/attr/ opener mm_struct - ASoC: max98088: fix ni clock divider calculation - ASoC: amd: fix for pcm_read() error - spi: Fix spi device unregister flow - spi: spi-zynq-qspi: Fix stack violation bug - bpf: Forbid trampoline attach for functions with variable arguments - net/nfc/rawsock.c: fix a permission check bug - usb: cdns3: Fix runtime PM imbalance on error - ASoC: Intel: bytcr_rt5640: Add quirk for the Glavey TM800A550L tablet - ASoC: Intel: bytcr_rt5640: Add quirk for the Lenovo Miix 3-830 tablet - vfio-ccw: Reset FSM state to IDLE inside FSM - vfio-ccw: Serialize FSM IDLE state with I/O completion - ASoC: sti-sas: add missing MODULE_DEVICE_TABLE - spi: sprd: Add missing MODULE_DEVICE_TABLE - usb: chipidea: udc: assign interrupt number to USB gadget structure - isdn: mISDN: netjet: Fix crash in nj_probe: - bonding: init notify_work earlier to avoid uninitialized use - netlink: disable IRQs for netlink_lock_table() - net: mdiobus: get rid of a BUG_ON() - cgroup: disable controllers at parse time - wq: handle VM suspension in stall detection - net/qla3xxx: fix schedule while atomic in ql_sem_spinlock - RDS tcp loopback connection can hang - net:sfc: fix non-freed irq in legacy irq mode - scsi: bnx2fc: Return failure if io_req is already in ABTS processing - scsi: vmw_pvscsi: Set correct residual data length - scsi: hisi_sas: Drop free_irq() of devm_request_irq() allocated irq - scsi: target: qla2xxx: Wait for stop_phase1 at WWN removal - net: macb: ensure the device is available before accessing GEMGXL control registers - net: appletalk: cops: Fix data race in cops_probe1 - net: dsa: microchip: enable phy errata workaround on 9567 - nvme-fabrics: decode host pathing error for connect - MIPS: Fix kernel hang under FUNCTION_GRAPH_TRACER and PREEMPT_TRACER - dm verity: fix require_signatures module_param permissions - bnx2x: Fix missing error code in bnx2x_iov_init_one() - nvme-tcp: remove incorrect Kconfig dep in BLK_DEV_NVME - nvmet: fix false keep-alive timeout when a controller is torn down - powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P2041 i2c controllers - powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P1010 i2c controllers - spi: Don't have controller clean up spi device before driver unbind - spi: Cleanup on failure of initial setup - i2c: mpc: Make use of i2c_recover_bus() - i2c: mpc: implement erratum A-004447 workaround - ALSA: seq: Fix race of snd_seq_timer_open() - ALSA: firewire-lib: fix the context to call snd_pcm_stop_xrun() - spi: bcm2835: Fix out-of-bounds access with more than 4 slaves - Revert "ACPI: sleep: Put the FACS table after using it" - drm: Fix
[Kernel-packages] [Bug 1840488] Re: Disable Bluetooth in cloud kernels
This bug was fixed in the package linux-gcp - 5.11.0-1016.18+21.10.2 --- linux-gcp (5.11.0-1016.18+21.10.2) impish; urgency=medium * impish/linux-gcp: 5.11.0-1016.18+21.10.2 -proposed tracker (LP: #1936486) * Packaging resync (LP: #1786013) - update dkms package versions * Disable Bluetooth in cloud kernels (LP: #1840488) - [Config] gcp: Disable CONFIG_BT [ Ubuntu: 5.11.0-1016.18 ] * hirsute/linux-gcp: 5.11.0-1016.18 -proposed tracker (LP: #1938651) * Some cloud kernels have Android related config options disabled (LP: #1928686) - [config] gcp: Enable Android options for anbox * Disable Bluetooth in cloud kernels (LP: #1840488) - [config] gcp: Disable CONFIG_BT * Packaging resync (LP: #1786013) - update dkms package versions * large_dir in ext4 broken (LP: #1933074) - SAUCE: ext4: fix directory index node split corruption * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293) - Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test" * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645) - selftests: icmp_redirect: support expected failures * Mute/mic LEDs no function on some HP platfroms (LP: #1934878) - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 450 G8 - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 445 G8 - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 630 G8 * [SRU][OEM-5.10/H] Fix HDMI output issue on Intel TGL GPU (LP: #1934864) - drm/i915: Fix HAS_LSPCON macro for platforms between GEN9 and GEN10 * mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC (LP: #1934239) - ALSA: hda/realtek: fix mute/micmute LEDs for HP EliteBook 830 G8 Notebook PC * ubuntu-host driver lacks lseek ops (LP: #1934110) - ubuntu-host: add generic lseek op * ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8 (LP: #1927749) - selftests/ftrace: fix event-no-pid on 1-core machine * Hirsute update: upstream stable patchset 2021-06-29 (LP: #1934012) - proc: Track /proc/$pid/attr/ opener mm_struct - ASoC: max98088: fix ni clock divider calculation - ASoC: amd: fix for pcm_read() error - spi: Fix spi device unregister flow - spi: spi-zynq-qspi: Fix stack violation bug - bpf: Forbid trampoline attach for functions with variable arguments - net/nfc/rawsock.c: fix a permission check bug - usb: cdns3: Fix runtime PM imbalance on error - ASoC: Intel: bytcr_rt5640: Add quirk for the Glavey TM800A550L tablet - ASoC: Intel: bytcr_rt5640: Add quirk for the Lenovo Miix 3-830 tablet - vfio-ccw: Reset FSM state to IDLE inside FSM - vfio-ccw: Serialize FSM IDLE state with I/O completion - ASoC: sti-sas: add missing MODULE_DEVICE_TABLE - spi: sprd: Add missing MODULE_DEVICE_TABLE - usb: chipidea: udc: assign interrupt number to USB gadget structure - isdn: mISDN: netjet: Fix crash in nj_probe: - bonding: init notify_work earlier to avoid uninitialized use - netlink: disable IRQs for netlink_lock_table() - net: mdiobus: get rid of a BUG_ON() - cgroup: disable controllers at parse time - wq: handle VM suspension in stall detection - net/qla3xxx: fix schedule while atomic in ql_sem_spinlock - RDS tcp loopback connection can hang - net:sfc: fix non-freed irq in legacy irq mode - scsi: bnx2fc: Return failure if io_req is already in ABTS processing - scsi: vmw_pvscsi: Set correct residual data length - scsi: hisi_sas: Drop free_irq() of devm_request_irq() allocated irq - scsi: target: qla2xxx: Wait for stop_phase1 at WWN removal - net: macb: ensure the device is available before accessing GEMGXL control registers - net: appletalk: cops: Fix data race in cops_probe1 - net: dsa: microchip: enable phy errata workaround on 9567 - nvme-fabrics: decode host pathing error for connect - MIPS: Fix kernel hang under FUNCTION_GRAPH_TRACER and PREEMPT_TRACER - dm verity: fix require_signatures module_param permissions - bnx2x: Fix missing error code in bnx2x_iov_init_one() - nvme-tcp: remove incorrect Kconfig dep in BLK_DEV_NVME - nvmet: fix false keep-alive timeout when a controller is torn down - powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P2041 i2c controllers - powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P1010 i2c controllers - spi: Don't have controller clean up spi device before driver unbind - spi: Cleanup on failure of initial setup - i2c: mpc: Make use of i2c_recover_bus() - i2c: mpc: implement erratum A-004447 workaround - ALSA: seq: Fix race of snd_seq_timer_open() - ALSA: firewire-lib: fix the context to call snd_pcm_stop_xrun() - spi: bcm2835: Fix out-of-bounds access with more than 4 slaves - Revert "ACPI: sleep: Put the FACS table after using it" - drm:
[Kernel-packages] [Bug 1930713] Re: Kernel package builds running out of space on builders
This bug was fixed in the package linux - 5.13.0-14.14 --- linux (5.13.0-14.14) impish; urgency=medium * impish/linux: 5.13.0-14.14 -proposed tracker (LP: #1938565) * Miscellaneous Ubuntu changes - SAUCE: Revert "UBUNTU: SAUCE: random: Make getrandom() ready earlier" - SAUCE: random: properly make getrandom() ready earlier * Miscellaneous upstream changes - seq_buf: Fix overflow in seq_buf_putmem_hex() - bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc - ext4: cleanup in-core orphan list if ext4_truncate() failed to get a transaction handle - ext4: fix kernel infoleak via ext4_extent_header - ext4: fix overflow in ext4_iomap_alloc() - ext4: return error code when ext4_fill_flex_info() fails - ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit - ext4: remove check for zero nr_to_scan in ext4_es_scan() - ext4: fix avefreec in find_group_orlov - ext4: use ext4_grp_locked_error in mb_find_extent -- Andrea Righi Mon, 02 Aug 2021 14:23:08 +0200 ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930713 Title: Kernel package builds running out of space on builders Status in linux package in Ubuntu: Fix Released Bug description: [Impact] Our kernel builds are sometimes running out of space on the builders when we are building multiple flavours. We've seen this with focal:linux-hwe for amd64 and impish:linux-unstable for arm64. This is in part because package builds are broken up into a build phase (which builds the source tree) and a binary phase (which creates the debs). These are run separately, with the binary phase run under fakeroot to get correct ownership for files in the package archives, requiring builds for multiple flavours to be present on disk at the same time. We have implemented various fixes for this problem over time, and explored many others which have not worked out. But the size of the kernel keeps increasing, and now it seems our only remaining option is to build one flavour and install its files, then remove the flavour build files before building the next flavour. This means that files are installed for later package builds during the build phase, requiring that ownership of these files be fixed up during the binary phase to get correct ownership in the package archives. [Test Plan] Build a full set of kernel packages (inlcuding linux-source and dbgsym packages, which are generally excluded when not building on builders) at a given tag, then build another set from the same tag with the packaging changes applied. Compare the resulting debs to confirm that the set of produced packages is the same, the file lists within the packages are the same, and that file ownership and permissions between the packages is identical. I have done this testing with the proposed patches with a recent linux-unstable tag and found no differences with and without the changes. [Where problems could occur] Incorrect ownership of files in the package archives is the main concern. I have tested for this, but it is possible that future upstream changes could unexpectedly result in files with incorrect ownership. Reordering of the package build sequence could result in missing files which should be in packages, or files present in packages which should be excluded. Some instances of this occurred while developing these changes and have been fixed. Future updates to upstream or to the packaging could cause additional issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931497] Re: Patch To Fix Bug in the Linux Block Layer Responsible For Merging BIOs
This bug was fixed in the package linux-azure - 5.11.0-1013.14+21.10.1 --- linux-azure (5.11.0-1013.14+21.10.1) impish; urgency=medium * impish/linux-azure: 5.11.0-1013.14+21.10.1 -proposed tracker (LP: #1936483) * Packaging resync (LP: #1786013) - update dkms package versions [ Ubuntu: 5.11.0-1013.14 ] * hirsute/linux-azure: 5.11.0-1013.14 -proposed tracker (LP: #1936485) * linux-azure: Ensure the latest linux-image-sgx is installed with the 5.11 kernels (LP: #1937846) - [Packaging] Install the linux-base-sgx version for upstream SGX * Packaging resync (LP: #1786013) - update dkms package versions * large_dir in ext4 broken (LP: #1933074) - SAUCE: ext4: fix directory index node split corruption * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293) - Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test" * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645) - selftests: icmp_redirect: support expected failures * Mute/mic LEDs no function on some HP platfroms (LP: #1934878) - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 450 G8 - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 445 G8 - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 630 G8 * [SRU][OEM-5.10/H] Fix HDMI output issue on Intel TGL GPU (LP: #1934864) - drm/i915: Fix HAS_LSPCON macro for platforms between GEN9 and GEN10 * mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC (LP: #1934239) - ALSA: hda/realtek: fix mute/micmute LEDs for HP EliteBook 830 G8 Notebook PC * ubuntu-host driver lacks lseek ops (LP: #1934110) - ubuntu-host: add generic lseek op * ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8 (LP: #1927749) - selftests/ftrace: fix event-no-pid on 1-core machine * Hirsute update: upstream stable patchset 2021-06-29 (LP: #1934012) - proc: Track /proc/$pid/attr/ opener mm_struct - ASoC: max98088: fix ni clock divider calculation - ASoC: amd: fix for pcm_read() error - spi: Fix spi device unregister flow - spi: spi-zynq-qspi: Fix stack violation bug - bpf: Forbid trampoline attach for functions with variable arguments - net/nfc/rawsock.c: fix a permission check bug - usb: cdns3: Fix runtime PM imbalance on error - ASoC: Intel: bytcr_rt5640: Add quirk for the Glavey TM800A550L tablet - ASoC: Intel: bytcr_rt5640: Add quirk for the Lenovo Miix 3-830 tablet - vfio-ccw: Reset FSM state to IDLE inside FSM - vfio-ccw: Serialize FSM IDLE state with I/O completion - ASoC: sti-sas: add missing MODULE_DEVICE_TABLE - spi: sprd: Add missing MODULE_DEVICE_TABLE - usb: chipidea: udc: assign interrupt number to USB gadget structure - isdn: mISDN: netjet: Fix crash in nj_probe: - bonding: init notify_work earlier to avoid uninitialized use - netlink: disable IRQs for netlink_lock_table() - net: mdiobus: get rid of a BUG_ON() - cgroup: disable controllers at parse time - wq: handle VM suspension in stall detection - net/qla3xxx: fix schedule while atomic in ql_sem_spinlock - RDS tcp loopback connection can hang - net:sfc: fix non-freed irq in legacy irq mode - scsi: bnx2fc: Return failure if io_req is already in ABTS processing - scsi: vmw_pvscsi: Set correct residual data length - scsi: hisi_sas: Drop free_irq() of devm_request_irq() allocated irq - scsi: target: qla2xxx: Wait for stop_phase1 at WWN removal - net: macb: ensure the device is available before accessing GEMGXL control registers - net: appletalk: cops: Fix data race in cops_probe1 - net: dsa: microchip: enable phy errata workaround on 9567 - nvme-fabrics: decode host pathing error for connect - MIPS: Fix kernel hang under FUNCTION_GRAPH_TRACER and PREEMPT_TRACER - dm verity: fix require_signatures module_param permissions - bnx2x: Fix missing error code in bnx2x_iov_init_one() - nvme-tcp: remove incorrect Kconfig dep in BLK_DEV_NVME - nvmet: fix false keep-alive timeout when a controller is torn down - powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P2041 i2c controllers - powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P1010 i2c controllers - spi: Don't have controller clean up spi device before driver unbind - spi: Cleanup on failure of initial setup - i2c: mpc: Make use of i2c_recover_bus() - i2c: mpc: implement erratum A-004447 workaround - ALSA: seq: Fix race of snd_seq_timer_open() - ALSA: firewire-lib: fix the context to call snd_pcm_stop_xrun() - spi: bcm2835: Fix out-of-bounds access with more than 4 slaves - Revert "ACPI: sleep: Put the FACS table after using it" - drm: Fix use-after-free read in drm_getunique() - drm: Lock pointer access in drm_master_release() - perf/x86/intel/uncore: Fix M2M event
[Kernel-packages] [Bug 1932367] Re: Pixel format change broken for Elgato Cam Link 4K
This bug was fixed in the package linux - 5.13.0-14.14 --- linux (5.13.0-14.14) impish; urgency=medium * impish/linux: 5.13.0-14.14 -proposed tracker (LP: #1938565) * Miscellaneous Ubuntu changes - SAUCE: Revert "UBUNTU: SAUCE: random: Make getrandom() ready earlier" - SAUCE: random: properly make getrandom() ready earlier * Miscellaneous upstream changes - seq_buf: Fix overflow in seq_buf_putmem_hex() - bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc - ext4: cleanup in-core orphan list if ext4_truncate() failed to get a transaction handle - ext4: fix kernel infoleak via ext4_extent_header - ext4: fix overflow in ext4_iomap_alloc() - ext4: return error code when ext4_fill_flex_info() fails - ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit - ext4: remove check for zero nr_to_scan in ext4_es_scan() - ext4: fix avefreec in find_group_orlov - ext4: use ext4_grp_locked_error in mb_find_extent -- Andrea Righi Mon, 02 Aug 2021 14:23:08 +0200 ** Changed in: linux (Ubuntu Impish) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932367 Title: Pixel format change broken for Elgato Cam Link 4K Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: [Impact] The Elgato Cam Link 4K HDMI video capture card reports to support three different pixel formats, where the first format depends on the connected HDMI device. ``` $ v4l2-ctl -d /dev/video0 --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [1]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [2]: 'YU12' (Planar YUV 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) ``` Changing the pixel format to anything besides the first pixel format does not work: ``` $ v4l2-ctl -d /dev/video0 --try-fmt-video pixelformat=YU12 Format Video Capture: Width/Height : 3840/2160 Pixel Format : 'NV12' (Y/CbCr 4:2:0) Field : None Bytes per Line: 3840 Size Image: 12441600 Colorspace: sRGB Transfer Function : Rec. 709 YCbCr/HSV Encoding: Rec. 709 Quantization : Default (maps to Limited Range) Flags : ``` User space applications like VLC might show an error message on the terminal in that case: ``` libv4l2: error set_fmt gave us a different result than try_fmt! ``` Depending on the error handling of the user space applications, they might display a distorted video, because they use the wrong pixel format for decoding the stream. [Fix] The Elgato Cam Link 4K responds to the USB video probe VS_PROBE_CONTROL/VS_COMMIT_CONTROL with a malformed data structure: The second byte contains bFormatIndex (instead of being the second byte of bmHint). The first byte is always zero. The third byte is always 1. The firmware bug was reported to Elgato on 2020-12-01 and it was forwarded by the support team to the developers as feature request. There is no firmware update available since then. The latest firmware for Elgato Cam Link 4K as of 2021-03-23 has MCU 20.02.19 and FPGA 67. Therefore correct the malformed data structure for this device. The change was successfully tested with VLC, OBS, and Chromium using different pixel formats (YUYV, NV12, YU12), resolutions (3840x2160, 1920x1080), and frame rates (29.970 and 59.940 fps). [Test Case] Connect an input device to the Cam Link 4K and try all three pixel formats with VLC: vlc v4l2:///dev/video0 --v4l2-chroma=NV12 vlc v4l2:///dev/video0 --v4l2-chroma=YU12 [Other Info] The fix was reviewed and accepted by the subsystem maintainer and will be included upstream: https://git.linuxtv.org/media_stage.git/commit/?id=4c6e0976295add7f0ed94d276c04a3d6f1ea8f83 Attached a backported patch for Ubuntu. I successfully tested it with Linux 5.11 on Ubuntu 21.04 and Linux 5.8 on Ubuntu 20.10. It should work on older kernel versions as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921870] Re: [UBUNTU 21.04] tools/kvm_stat: Add restart delay
This bug was fixed in the package linux - 5.13.0-14.14 --- linux (5.13.0-14.14) impish; urgency=medium * impish/linux: 5.13.0-14.14 -proposed tracker (LP: #1938565) * Miscellaneous Ubuntu changes - SAUCE: Revert "UBUNTU: SAUCE: random: Make getrandom() ready earlier" - SAUCE: random: properly make getrandom() ready earlier * Miscellaneous upstream changes - seq_buf: Fix overflow in seq_buf_putmem_hex() - bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc - ext4: cleanup in-core orphan list if ext4_truncate() failed to get a transaction handle - ext4: fix kernel infoleak via ext4_extent_header - ext4: fix overflow in ext4_iomap_alloc() - ext4: return error code when ext4_fill_flex_info() fails - ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit - ext4: remove check for zero nr_to_scan in ext4_es_scan() - ext4: fix avefreec in find_group_orlov - ext4: use ext4_grp_locked_error in mb_find_extent -- Andrea Righi Mon, 02 Aug 2021 14:23:08 +0200 ** Changed in: linux (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921870 Title: [UBUNTU 21.04] tools/kvm_stat: Add restart delay Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: SRU Justification: [Impact] * Nice to have feature requested by IBM - a systemd service monitoring KVM guests. * Adds a new systemd service, not enabled by default. [Fix] * Install the systemd .service file when installing linux-tools-host [Test Plan] * dpkg -c linux-tools-host_5.11.0-18.19_all.deb ./lib/systemd/system/kvm_stat.service * Install the package and reboot * Check if kvm_stat is present and not active after reboot: ls -l /lib/systemd/system/kvm_stat.service systemctl -a | grep kvm_stat [Where problems could occur] * Service can be enabled and started by mistake or by any further future Makefile change (enabling all services installed by linux-tools-host). * The service logs into /var/log/kvm_stat.csv (not journal!) and package does not provide logrotate by default, thus the logging could eat entire disk space. -- Original Description -- Description: tools/kvm_stat: Add restart delay Symptom: If the kvm service is enabled and the system rebooted, Systemd's initial attempt to start the kvm unit file may fail in case the kvm module is not loaded. However, once the kvm module is loaded, the service is _not_ started. Problem: Since the unit file does not specify a delay for the retries, Systemd restarts with a minimum delay a number of times before giving up and disabling the service. Which means a subsequent kvm module load will have kvm running without monitoring. Solution: Add an appropriate delay in the unit file. Reproduction: (1) Enable the kvm service via systemctl (2) Reboot (3) Verify that the kvm module is not loaded & kvm service not running (4) Load the kvm module via 'modprobe kvm' (5) Verify that the kvm service came up within the next minute. Preventive:yes Just use the attached patch and you're good! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931240] Re: Intel ADL-S graphics feature enabling
This bug was fixed in the package linux - 5.13.0-14.14
---
linux (5.13.0-14.14) impish; urgency=medium
* impish/linux: 5.13.0-14.14 -proposed tracker (LP: #1938565)
* Miscellaneous Ubuntu changes
- SAUCE: Revert "UBUNTU: SAUCE: random: Make getrandom() ready earlier"
- SAUCE: random: properly make getrandom() ready earlier
* Miscellaneous upstream changes
- seq_buf: Fix overflow in seq_buf_putmem_hex()
- bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc
- ext4: cleanup in-core orphan list if ext4_truncate() failed to get a
transaction handle
- ext4: fix kernel infoleak via ext4_extent_header
- ext4: fix overflow in ext4_iomap_alloc()
- ext4: return error code when ext4_fill_flex_info() fails
- ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit
- ext4: remove check for zero nr_to_scan in ext4_es_scan()
- ext4: fix avefreec in find_group_orlov
- ext4: use ext4_grp_locked_error in mb_find_extent
-- Andrea Righi Mon, 02 Aug 2021 14:23:08
+0200
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1931240
Title:
Intel ADL-S graphics feature enabling
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux-oem-5.13 source package in Impish:
Invalid
Bug description:
[SRU Justfication]
[Impact]
While all other ADL-S i915 commits have been included in v5.13-rc1, the
last one missed the train is to add two more PCI IDs.
[Fix]
Commit 3f50033dd88a ("drm/i915/adl_s: ADL-S platform Update PCI ids for
Mobile BGA") that is currently in drm-intel, branch for-linux-next.
[Test Case]
With this patch, i915 kernel module should be automatically probed.
[Where problems could occur]
While this is part of the initial support for i915 on ADL-S platforms,
the hardware to be enabled could still be unstable and feature laking.
But since this patch only addes two additional PCI IDs to the new
family, it should not introduce any regression to the exsiting ones.
[Other Info]
ADL-S support targets kernel version 5.13, so only unstable and oem-5.13
will be nominated for this fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931240/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926579] Re: On TGL platforms screen shows garbage when browsing website by scrolling mouse
This bug was fixed in the package linux - 5.13.0-14.14 --- linux (5.13.0-14.14) impish; urgency=medium * impish/linux: 5.13.0-14.14 -proposed tracker (LP: #1938565) * Miscellaneous Ubuntu changes - SAUCE: Revert "UBUNTU: SAUCE: random: Make getrandom() ready earlier" - SAUCE: random: properly make getrandom() ready earlier * Miscellaneous upstream changes - seq_buf: Fix overflow in seq_buf_putmem_hex() - bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc - ext4: cleanup in-core orphan list if ext4_truncate() failed to get a transaction handle - ext4: fix kernel infoleak via ext4_extent_header - ext4: fix overflow in ext4_iomap_alloc() - ext4: return error code when ext4_fill_flex_info() fails - ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit - ext4: remove check for zero nr_to_scan in ext4_es_scan() - ext4: fix avefreec in find_group_orlov - ext4: use ext4_grp_locked_error in mb_find_extent -- Andrea Righi Mon, 02 Aug 2021 14:23:08 +0200 ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1926579 Title: On TGL platforms screen shows garbage when browsing website by scrolling mouse Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Released Bug description: [Impact] On Dell TGL platforms screen shows garbage when browsing website by scrolling mouse [Fix] This patch fixes the issue https://patchwork.freedesktop.org/patch/430153/?series=89348=1 [Test] Verified on Dell TGL-H platforms. [Where problems could occur] It disable PSR2 on A0 and B0 TGL-H platforms, should introduce no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926579/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929504] Re: Add support for IO functions of AAEON devices
This bug was fixed in the package linux - 5.13.0-14.14 --- linux (5.13.0-14.14) impish; urgency=medium * impish/linux: 5.13.0-14.14 -proposed tracker (LP: #1938565) * Miscellaneous Ubuntu changes - SAUCE: Revert "UBUNTU: SAUCE: random: Make getrandom() ready earlier" - SAUCE: random: properly make getrandom() ready earlier * Miscellaneous upstream changes - seq_buf: Fix overflow in seq_buf_putmem_hex() - bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc - ext4: cleanup in-core orphan list if ext4_truncate() failed to get a transaction handle - ext4: fix kernel infoleak via ext4_extent_header - ext4: fix overflow in ext4_iomap_alloc() - ext4: return error code when ext4_fill_flex_info() fails - ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit - ext4: remove check for zero nr_to_scan in ext4_es_scan() - ext4: fix avefreec in find_group_orlov - ext4: use ext4_grp_locked_error in mb_find_extent -- Andrea Righi Mon, 02 Aug 2021 14:23:08 +0200 ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929504 Title: Add support for IO functions of AAEON devices Status in linux package in Ubuntu: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: [Impact] Require drivers to enable AAEON devices. [Fix] AAEON provides a series of patches to support its GPIO/LED/Watchdog/HWMON devices. https://www.spinics.net/lists/linux-gpio/msg61301.html [Test] Verified on AAEON platform. [Where problems could occur] No, they are new drivers, should not introduce any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931147] Re: Fix non-working GPU on Some HP desktops
This bug was fixed in the package linux - 5.13.0-14.14 --- linux (5.13.0-14.14) impish; urgency=medium * impish/linux: 5.13.0-14.14 -proposed tracker (LP: #1938565) * Miscellaneous Ubuntu changes - SAUCE: Revert "UBUNTU: SAUCE: random: Make getrandom() ready earlier" - SAUCE: random: properly make getrandom() ready earlier * Miscellaneous upstream changes - seq_buf: Fix overflow in seq_buf_putmem_hex() - bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc - ext4: cleanup in-core orphan list if ext4_truncate() failed to get a transaction handle - ext4: fix kernel infoleak via ext4_extent_header - ext4: fix overflow in ext4_iomap_alloc() - ext4: return error code when ext4_fill_flex_info() fails - ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit - ext4: remove check for zero nr_to_scan in ext4_es_scan() - ext4: fix avefreec in find_group_orlov - ext4: use ext4_grp_locked_error in mb_find_extent -- Andrea Righi Mon, 02 Aug 2021 14:23:08 +0200 ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1931147 Title: Fix non-working GPU on Some HP desktops Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] Integrated GPU on AMD based HP desktop doesn't work. [Fix] Coalesce host bridge contiguous apertures so the resources requested by child devices can be met. [Test] Boot affected systems. No picture from the iGPU. With the patch applied, iGPU can work normally. [Where problems could occur] Assume there are device A and device B and they request overlapped resource region, the original logic may not be able to allocate enough resource for A so device B claimed the resource in the end. Once the fix is applied, the region may be big enough for device A, hence device B won't be able to get the resource it needs. Hopefully we don't have such broken systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.91.03-0ubuntu1
---
nvidia-graphics-drivers-460-server (460.91.03-0ubuntu1) impish; urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.13.patch.
-- Alberto Milone Fri, 09 Jul 2021
15:04:27 +0200
--
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/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
Fix Released
Status in fabric-manager-460 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Triaged
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Won't Fix
Status in linux-restricted-modules source package in Groovy:
Won't Fix
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
Won't Fix
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the
[Kernel-packages] [Bug 1928679] Re: Support importing mokx keys into revocation list from the mok table
This bug was fixed in the package linux - 5.13.0-14.14 --- linux (5.13.0-14.14) impish; urgency=medium * impish/linux: 5.13.0-14.14 -proposed tracker (LP: #1938565) * Miscellaneous Ubuntu changes - SAUCE: Revert "UBUNTU: SAUCE: random: Make getrandom() ready earlier" - SAUCE: random: properly make getrandom() ready earlier * Miscellaneous upstream changes - seq_buf: Fix overflow in seq_buf_putmem_hex() - bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc - ext4: cleanup in-core orphan list if ext4_truncate() failed to get a transaction handle - ext4: fix kernel infoleak via ext4_extent_header - ext4: fix overflow in ext4_iomap_alloc() - ext4: return error code when ext4_fill_flex_info() fails - ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit - ext4: remove check for zero nr_to_scan in ext4_es_scan() - ext4: fix avefreec in find_group_orlov - ext4: use ext4_grp_locked_error in mb_find_extent -- Andrea Righi Mon, 02 Aug 2021 14:23:08 +0200 ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1928679 Title: Support importing mokx keys into revocation list from the mok table Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx) which revokes many Ubuntu kernel hashes and 2012 signing key. * Kernel should import those into it's %:.blacklist keyring such that it prohibits signed kexec of the revoked kernels. * v5.13-rc1 kernel has learned how to import mokx and how to import full certs into the %:.blacklist keyring. * However, it only does so by reading MokListXRT efi variable. * Due to the large size of Ubuntu's vendor-dbx, shim does not create MokListXRT efi variable, but instead creates MokListXRT1 MokListXRT2 MokListXRT3 which currently v5.13-rc1 kernel cannot read. Shim also exposes MokListXRT via mokvar table, which is easier to parse and contains all the revocations in full. Kernel needs a patch to read MokListXRT via mokvar table. * We have two options on how to proceed from here, either we include the same hashes and certs as our vendordbx in in the kernel as revocation list, or we fix kernel to read MokListXRT via mokvar table * The above is known as CVE-2020-26541 * Separately it would be nice to add informational dmesg messages when revoking signing certificates, as a good indication that signing key rotation events have happened and have been applied correctly. [Test Plan] * Boot kernel with 15.4 based Ubuntu shim * Install keyutils package * Execute $ sudo keyctl list %:.blacklist it should list in exccess of 300+ hash entries. It also must list assymetric Canonical signing key from 2012. * Separately check dmesg to observe that asymmetric canonical signing key from 2012 is revoked. [Where problems could occur] * EFI variable storage can be full thus preventing shim to mirror efivars and the moktable. On decent hardware this should not happen, but has been observed to be corrupted on some older EDKII based OVMF instances with small EFI variable storage space (pre-4MB). [Other Info] * The patches to fix the above have been submitted upstream https://lore.kernel.org/keyrings/20210512153100.285169-1-dimitri.led...@canonical.com/ https://lore.kernel.org/keyrings/20210512110302.262104-1-dimitri.led...@canonical.com/ This will now be submitted as SAUCE patches for the Ubuntu UNSTABLE kernel, until accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925421] Re: arm64 support
This bug was fixed in the package linux-oracle - 5.11.0-1015.16+21.10.1 --- linux-oracle (5.11.0-1015.16+21.10.1) impish; urgency=medium * impish/linux-oracle: 5.11.0-1015.16+21.10.1 -proposed tracker (LP: #1936492) * Packaging resync (LP: #1786013) - update dkms package versions [ Ubuntu: 5.11.0-1015.16 ] * hirsute/linux-oracle: 5.11.0-1015.16 -proposed tracker (LP: #1938476) * arm64 support (LP: #1925421) - [packaging] oracle: Enabling arm64 - [config] oracle: Update arm64 configs to match annotations - [packaging] oracle: Update annotations for arm64 [ Ubuntu: 5.11.0-1014.15 ] * hirsute/linux-oracle: 5.11.0-1014.15 -proposed tracker (LP: #1936494) * Packaging resync (LP: #1786013) - update dkms package versions * large_dir in ext4 broken (LP: #1933074) - SAUCE: ext4: fix directory index node split corruption * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293) - Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test" * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645) - selftests: icmp_redirect: support expected failures * Mute/mic LEDs no function on some HP platfroms (LP: #1934878) - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 450 G8 - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 445 G8 - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 630 G8 * [SRU][OEM-5.10/H] Fix HDMI output issue on Intel TGL GPU (LP: #1934864) - drm/i915: Fix HAS_LSPCON macro for platforms between GEN9 and GEN10 * mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC (LP: #1934239) - ALSA: hda/realtek: fix mute/micmute LEDs for HP EliteBook 830 G8 Notebook PC * ubuntu-host driver lacks lseek ops (LP: #1934110) - ubuntu-host: add generic lseek op * ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8 (LP: #1927749) - selftests/ftrace: fix event-no-pid on 1-core machine * Hirsute update: upstream stable patchset 2021-06-29 (LP: #1934012) - proc: Track /proc/$pid/attr/ opener mm_struct - ASoC: max98088: fix ni clock divider calculation - ASoC: amd: fix for pcm_read() error - spi: Fix spi device unregister flow - spi: spi-zynq-qspi: Fix stack violation bug - bpf: Forbid trampoline attach for functions with variable arguments - net/nfc/rawsock.c: fix a permission check bug - usb: cdns3: Fix runtime PM imbalance on error - ASoC: Intel: bytcr_rt5640: Add quirk for the Glavey TM800A550L tablet - ASoC: Intel: bytcr_rt5640: Add quirk for the Lenovo Miix 3-830 tablet - vfio-ccw: Reset FSM state to IDLE inside FSM - vfio-ccw: Serialize FSM IDLE state with I/O completion - ASoC: sti-sas: add missing MODULE_DEVICE_TABLE - spi: sprd: Add missing MODULE_DEVICE_TABLE - usb: chipidea: udc: assign interrupt number to USB gadget structure - isdn: mISDN: netjet: Fix crash in nj_probe: - bonding: init notify_work earlier to avoid uninitialized use - netlink: disable IRQs for netlink_lock_table() - net: mdiobus: get rid of a BUG_ON() - cgroup: disable controllers at parse time - wq: handle VM suspension in stall detection - net/qla3xxx: fix schedule while atomic in ql_sem_spinlock - RDS tcp loopback connection can hang - net:sfc: fix non-freed irq in legacy irq mode - scsi: bnx2fc: Return failure if io_req is already in ABTS processing - scsi: vmw_pvscsi: Set correct residual data length - scsi: hisi_sas: Drop free_irq() of devm_request_irq() allocated irq - scsi: target: qla2xxx: Wait for stop_phase1 at WWN removal - net: macb: ensure the device is available before accessing GEMGXL control registers - net: appletalk: cops: Fix data race in cops_probe1 - net: dsa: microchip: enable phy errata workaround on 9567 - nvme-fabrics: decode host pathing error for connect - MIPS: Fix kernel hang under FUNCTION_GRAPH_TRACER and PREEMPT_TRACER - dm verity: fix require_signatures module_param permissions - bnx2x: Fix missing error code in bnx2x_iov_init_one() - nvme-tcp: remove incorrect Kconfig dep in BLK_DEV_NVME - nvmet: fix false keep-alive timeout when a controller is torn down - powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P2041 i2c controllers - powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P1010 i2c controllers - spi: Don't have controller clean up spi device before driver unbind - spi: Cleanup on failure of initial setup - i2c: mpc: Make use of i2c_recover_bus() - i2c: mpc: implement erratum A-004447 workaround - ALSA: seq: Fix race of snd_seq_timer_open() - ALSA: firewire-lib: fix the context to call snd_pcm_stop_xrun() - spi: bcm2835: Fix out-of-bounds access with more than 4 slaves - Revert "ACPI: sleep: Put the FACS table after using it" - drm: Fix
[Kernel-packages] [Bug 1928686] Re: Some cloud kernels have Android related config options disabled
This bug was fixed in the package linux-gcp - 5.11.0-1016.18+21.10.2 --- linux-gcp (5.11.0-1016.18+21.10.2) impish; urgency=medium * impish/linux-gcp: 5.11.0-1016.18+21.10.2 -proposed tracker (LP: #1936486) * Packaging resync (LP: #1786013) - update dkms package versions * Disable Bluetooth in cloud kernels (LP: #1840488) - [Config] gcp: Disable CONFIG_BT [ Ubuntu: 5.11.0-1016.18 ] * hirsute/linux-gcp: 5.11.0-1016.18 -proposed tracker (LP: #1938651) * Some cloud kernels have Android related config options disabled (LP: #1928686) - [config] gcp: Enable Android options for anbox * Disable Bluetooth in cloud kernels (LP: #1840488) - [config] gcp: Disable CONFIG_BT * Packaging resync (LP: #1786013) - update dkms package versions * large_dir in ext4 broken (LP: #1933074) - SAUCE: ext4: fix directory index node split corruption * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293) - Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test" * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645) - selftests: icmp_redirect: support expected failures * Mute/mic LEDs no function on some HP platfroms (LP: #1934878) - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 450 G8 - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 445 G8 - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 630 G8 * [SRU][OEM-5.10/H] Fix HDMI output issue on Intel TGL GPU (LP: #1934864) - drm/i915: Fix HAS_LSPCON macro for platforms between GEN9 and GEN10 * mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC (LP: #1934239) - ALSA: hda/realtek: fix mute/micmute LEDs for HP EliteBook 830 G8 Notebook PC * ubuntu-host driver lacks lseek ops (LP: #1934110) - ubuntu-host: add generic lseek op * ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8 (LP: #1927749) - selftests/ftrace: fix event-no-pid on 1-core machine * Hirsute update: upstream stable patchset 2021-06-29 (LP: #1934012) - proc: Track /proc/$pid/attr/ opener mm_struct - ASoC: max98088: fix ni clock divider calculation - ASoC: amd: fix for pcm_read() error - spi: Fix spi device unregister flow - spi: spi-zynq-qspi: Fix stack violation bug - bpf: Forbid trampoline attach for functions with variable arguments - net/nfc/rawsock.c: fix a permission check bug - usb: cdns3: Fix runtime PM imbalance on error - ASoC: Intel: bytcr_rt5640: Add quirk for the Glavey TM800A550L tablet - ASoC: Intel: bytcr_rt5640: Add quirk for the Lenovo Miix 3-830 tablet - vfio-ccw: Reset FSM state to IDLE inside FSM - vfio-ccw: Serialize FSM IDLE state with I/O completion - ASoC: sti-sas: add missing MODULE_DEVICE_TABLE - spi: sprd: Add missing MODULE_DEVICE_TABLE - usb: chipidea: udc: assign interrupt number to USB gadget structure - isdn: mISDN: netjet: Fix crash in nj_probe: - bonding: init notify_work earlier to avoid uninitialized use - netlink: disable IRQs for netlink_lock_table() - net: mdiobus: get rid of a BUG_ON() - cgroup: disable controllers at parse time - wq: handle VM suspension in stall detection - net/qla3xxx: fix schedule while atomic in ql_sem_spinlock - RDS tcp loopback connection can hang - net:sfc: fix non-freed irq in legacy irq mode - scsi: bnx2fc: Return failure if io_req is already in ABTS processing - scsi: vmw_pvscsi: Set correct residual data length - scsi: hisi_sas: Drop free_irq() of devm_request_irq() allocated irq - scsi: target: qla2xxx: Wait for stop_phase1 at WWN removal - net: macb: ensure the device is available before accessing GEMGXL control registers - net: appletalk: cops: Fix data race in cops_probe1 - net: dsa: microchip: enable phy errata workaround on 9567 - nvme-fabrics: decode host pathing error for connect - MIPS: Fix kernel hang under FUNCTION_GRAPH_TRACER and PREEMPT_TRACER - dm verity: fix require_signatures module_param permissions - bnx2x: Fix missing error code in bnx2x_iov_init_one() - nvme-tcp: remove incorrect Kconfig dep in BLK_DEV_NVME - nvmet: fix false keep-alive timeout when a controller is torn down - powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P2041 i2c controllers - powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P1010 i2c controllers - spi: Don't have controller clean up spi device before driver unbind - spi: Cleanup on failure of initial setup - i2c: mpc: Make use of i2c_recover_bus() - i2c: mpc: implement erratum A-004447 workaround - ALSA: seq: Fix race of snd_seq_timer_open() - ALSA: firewire-lib: fix the context to call snd_pcm_stop_xrun() - spi: bcm2835: Fix out-of-bounds access with more than 4 slaves - Revert "ACPI: sleep: Put the FACS table after using it" - drm:
[Kernel-packages] [Bug 1912789] Re: Add support for selective build of special drivers
This bug was fixed in the package linux - 5.13.0-14.14 --- linux (5.13.0-14.14) impish; urgency=medium * impish/linux: 5.13.0-14.14 -proposed tracker (LP: #1938565) * Miscellaneous Ubuntu changes - SAUCE: Revert "UBUNTU: SAUCE: random: Make getrandom() ready earlier" - SAUCE: random: properly make getrandom() ready earlier * Miscellaneous upstream changes - seq_buf: Fix overflow in seq_buf_putmem_hex() - bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc - ext4: cleanup in-core orphan list if ext4_truncate() failed to get a transaction handle - ext4: fix kernel infoleak via ext4_extent_header - ext4: fix overflow in ext4_iomap_alloc() - ext4: return error code when ext4_fill_flex_info() fails - ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit - ext4: remove check for zero nr_to_scan in ext4_es_scan() - ext4: fix avefreec in find_group_orlov - ext4: use ext4_grp_locked_error in mb_find_extent -- Andrea Righi Mon, 02 Aug 2021 14:23:08 +0200 ** Changed in: linux (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912789 Title: Add support for selective build of special drivers Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: [SRU Justification] = Impact = We want to add some driver code which exists in the primary kernel source but will not get included unless specifically asked for. As long as there are no drivers using this, there is no user-visible change. = Impact = This will be done by adding a new config option which gets turned on via build setup rules. The default will be off. = Testcase = As long as there are no consumers changes can only be seen by inspecting the build logs (if even that). = Regression Potential = This prepares for future consumers. At this stage either the build will fail completely or pass and in that case the produced kernel binaries are the same as they were before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931725] Re: initramfs-tools & kernel: use zstd as the default compression method
This bug was fixed in the package linux - 5.13.0-14.14 --- linux (5.13.0-14.14) impish; urgency=medium * impish/linux: 5.13.0-14.14 -proposed tracker (LP: #1938565) * Miscellaneous Ubuntu changes - SAUCE: Revert "UBUNTU: SAUCE: random: Make getrandom() ready earlier" - SAUCE: random: properly make getrandom() ready earlier * Miscellaneous upstream changes - seq_buf: Fix overflow in seq_buf_putmem_hex() - bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc - ext4: cleanup in-core orphan list if ext4_truncate() failed to get a transaction handle - ext4: fix kernel infoleak via ext4_extent_header - ext4: fix overflow in ext4_iomap_alloc() - ext4: return error code when ext4_fill_flex_info() fails - ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit - ext4: remove check for zero nr_to_scan in ext4_es_scan() - ext4: fix avefreec in find_group_orlov - ext4: use ext4_grp_locked_error in mb_find_extent -- Andrea Righi Mon, 02 Aug 2021 14:23:08 +0200 ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931725 Title: initramfs-tools & kernel: use zstd as the default compression method Status in Ubuntu on IBM z Systems: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Turns out that loading is always the slow part in loading initramfs into memory and decompressing it since decompression is always the final 10-20% or so of the task. It therefore makes sense to use a good compressor that shrinks the initramfs as much as possible with little decompression overhead. Benchmarking zstd vs lz4 shows that while zstd can be ~5x slower in decompression, the image size is much smaller with zstd than lz4, and since ~80-90% of the boot time is loading the image it makes sense to use zstd. Attached is a libreoffice spread sheet showing typical load and decompression times for a fairly standard 3.4 GHZ intel box with data for load times for a 5400 RPM, 7200 RPM and SATA SSD drives. The conclusions from the test results (attached) show: 1. Loading time is always significantly slower than decompression time. 2. ZSTD is 5x slower than LZ4 in decompression speed but produces far better compressed images 3. Given that loading time is the major factor in loading + decompression, ZSTD is best for kernel and initramfs boot timings. (Also refer to https://kernel.ubuntu.com/~cking/boot-speed- eoan-5.3/kernel-compression-method.txt for some raw data on drive load speeds for the same UEFI box I did a couple of years ago). amd64 supports zstd, but s390x does not. Will use this bug to enable zstd support on s390x. Upstream submitted patch https://lore.kernel.org/linux-s390/20210615114150.325080-1-dimitri.led...@canonical.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931131] Re: Update the 465 and the 460 NVIDIA driver series
This bug was fixed in the package nvidia-graphics-drivers-460 - 460.91.03-0ubuntu1 --- nvidia-graphics-drivers-460 (460.91.03-0ubuntu1) impish; urgency=medium * New upstream release (LP: #1933980). -- Alberto Milone Fri, 09 Jul 2021 12:45:02 +0200 ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1931131 Title: Update the 465 and the 460 NVIDIA driver series Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: New Status in nvidia-graphics-drivers-465 package in Ubuntu: In Progress Status in nvidia-settings package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-465 source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Released Status in linux source package in Hirsute: In Progress Status in nvidia-graphics-drivers-390 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Released Bug description: Update the 465 and the 460 NVIDIA driver series, and add support for Linux 5.13 to all the driver series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460.84 == * New upstream release (LP: #1931131): - Added support for the following GPUs: GeForce RTX 3080 Ti * debian/additional_card_ids: - Drop the additional IDs. * debian/rules: - Skip lines that start with "#" in debian/additional_card_ids. * debian/templates/dkms_nvidia.conf.in:
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.144-0ubuntu1
---
nvidia-graphics-drivers-390 (390.144-0ubuntu1) impish; urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.13.patch.
-- Alberto Milone Mon, 05 Jul 2021
10:22:50 +0200
** Changed in: nvidia-graphics-drivers-460-server (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
Fix Released
Status in fabric-manager-460 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Triaged
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Won't Fix
Status in linux-restricted-modules source package in Groovy:
Won't Fix
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
Won't Fix
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in
[Kernel-packages] [Bug 1931254] Re: Google Confidential Compute fails to boot with shim version 1.47
This bug was fixed in the package linux-gcp - 5.11.0-1016.18+21.10.2 --- linux-gcp (5.11.0-1016.18+21.10.2) impish; urgency=medium * impish/linux-gcp: 5.11.0-1016.18+21.10.2 -proposed tracker (LP: #1936486) * Packaging resync (LP: #1786013) - update dkms package versions * Disable Bluetooth in cloud kernels (LP: #1840488) - [Config] gcp: Disable CONFIG_BT [ Ubuntu: 5.11.0-1016.18 ] * hirsute/linux-gcp: 5.11.0-1016.18 -proposed tracker (LP: #1938651) * Some cloud kernels have Android related config options disabled (LP: #1928686) - [config] gcp: Enable Android options for anbox * Disable Bluetooth in cloud kernels (LP: #1840488) - [config] gcp: Disable CONFIG_BT * Packaging resync (LP: #1786013) - update dkms package versions * large_dir in ext4 broken (LP: #1933074) - SAUCE: ext4: fix directory index node split corruption * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293) - Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test" * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645) - selftests: icmp_redirect: support expected failures * Mute/mic LEDs no function on some HP platfroms (LP: #1934878) - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 450 G8 - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 445 G8 - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 630 G8 * [SRU][OEM-5.10/H] Fix HDMI output issue on Intel TGL GPU (LP: #1934864) - drm/i915: Fix HAS_LSPCON macro for platforms between GEN9 and GEN10 * mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC (LP: #1934239) - ALSA: hda/realtek: fix mute/micmute LEDs for HP EliteBook 830 G8 Notebook PC * ubuntu-host driver lacks lseek ops (LP: #1934110) - ubuntu-host: add generic lseek op * ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8 (LP: #1927749) - selftests/ftrace: fix event-no-pid on 1-core machine * Hirsute update: upstream stable patchset 2021-06-29 (LP: #1934012) - proc: Track /proc/$pid/attr/ opener mm_struct - ASoC: max98088: fix ni clock divider calculation - ASoC: amd: fix for pcm_read() error - spi: Fix spi device unregister flow - spi: spi-zynq-qspi: Fix stack violation bug - bpf: Forbid trampoline attach for functions with variable arguments - net/nfc/rawsock.c: fix a permission check bug - usb: cdns3: Fix runtime PM imbalance on error - ASoC: Intel: bytcr_rt5640: Add quirk for the Glavey TM800A550L tablet - ASoC: Intel: bytcr_rt5640: Add quirk for the Lenovo Miix 3-830 tablet - vfio-ccw: Reset FSM state to IDLE inside FSM - vfio-ccw: Serialize FSM IDLE state with I/O completion - ASoC: sti-sas: add missing MODULE_DEVICE_TABLE - spi: sprd: Add missing MODULE_DEVICE_TABLE - usb: chipidea: udc: assign interrupt number to USB gadget structure - isdn: mISDN: netjet: Fix crash in nj_probe: - bonding: init notify_work earlier to avoid uninitialized use - netlink: disable IRQs for netlink_lock_table() - net: mdiobus: get rid of a BUG_ON() - cgroup: disable controllers at parse time - wq: handle VM suspension in stall detection - net/qla3xxx: fix schedule while atomic in ql_sem_spinlock - RDS tcp loopback connection can hang - net:sfc: fix non-freed irq in legacy irq mode - scsi: bnx2fc: Return failure if io_req is already in ABTS processing - scsi: vmw_pvscsi: Set correct residual data length - scsi: hisi_sas: Drop free_irq() of devm_request_irq() allocated irq - scsi: target: qla2xxx: Wait for stop_phase1 at WWN removal - net: macb: ensure the device is available before accessing GEMGXL control registers - net: appletalk: cops: Fix data race in cops_probe1 - net: dsa: microchip: enable phy errata workaround on 9567 - nvme-fabrics: decode host pathing error for connect - MIPS: Fix kernel hang under FUNCTION_GRAPH_TRACER and PREEMPT_TRACER - dm verity: fix require_signatures module_param permissions - bnx2x: Fix missing error code in bnx2x_iov_init_one() - nvme-tcp: remove incorrect Kconfig dep in BLK_DEV_NVME - nvmet: fix false keep-alive timeout when a controller is torn down - powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P2041 i2c controllers - powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P1010 i2c controllers - spi: Don't have controller clean up spi device before driver unbind - spi: Cleanup on failure of initial setup - i2c: mpc: Make use of i2c_recover_bus() - i2c: mpc: implement erratum A-004447 workaround - ALSA: seq: Fix race of snd_seq_timer_open() - ALSA: firewire-lib: fix the context to call snd_pcm_stop_xrun() - spi: bcm2835: Fix out-of-bounds access with more than 4 slaves - Revert "ACPI: sleep: Put the FACS table after using it" - drm:
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package nvidia-graphics-drivers-460 -
460.91.03-0ubuntu1
---
nvidia-graphics-drivers-460 (460.91.03-0ubuntu1) impish; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
12:45:02 +0200
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
Fix Released
Status in fabric-manager-460 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Triaged
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Won't Fix
Status in linux-restricted-modules source package in Groovy:
Won't Fix
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
Won't Fix
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the
[Kernel-packages] [Bug 1934110] Re: ubuntu-host driver lacks lseek ops
This bug was fixed in the package linux - 5.13.0-14.14
---
linux (5.13.0-14.14) impish; urgency=medium
* impish/linux: 5.13.0-14.14 -proposed tracker (LP: #1938565)
* Miscellaneous Ubuntu changes
- SAUCE: Revert "UBUNTU: SAUCE: random: Make getrandom() ready earlier"
- SAUCE: random: properly make getrandom() ready earlier
* Miscellaneous upstream changes
- seq_buf: Fix overflow in seq_buf_putmem_hex()
- bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc
- ext4: cleanup in-core orphan list if ext4_truncate() failed to get a
transaction handle
- ext4: fix kernel infoleak via ext4_extent_header
- ext4: fix overflow in ext4_iomap_alloc()
- ext4: return error code when ext4_fill_flex_info() fails
- ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit
- ext4: remove check for zero nr_to_scan in ext4_es_scan()
- ext4: fix avefreec in find_group_orlov
- ext4: use ext4_grp_locked_error in mb_find_extent
-- Andrea Righi Mon, 02 Aug 2021 14:23:08
+0200
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1934110
Title:
ubuntu-host driver lacks lseek ops
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Groovy:
Won't Fix
Status in linux source package in Hirsute:
Fix Released
Bug description:
[ SRU Justification ][GROOVY][HIRSUTE][IMPISH]
== Impact ==
The ubuntu-host driver lacks procfs lseek ops and lseeking on the
procfs esm-token file will jump to a NULL address causing the
following splat:
942.470568] BUG: kernel NULL pointer dereference, address:
[ 942.471157] #PF: supervisor instruction fetch in kernel mode
[ 942.471724] #PF: error_code(0x0010) - not-present page
[ 942.472297] PGD 0 P4D 0
[ 942.472867] Oops: 0010 [#1] SMP PTI
[ 942.473435] CPU: 2 PID: 5661 Comm: stress-ng Not tainted 5.13.0-9-generic
#9
[ 942.474012] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0
02/06/2015
[ 942.474599] RIP: 0010:0x0
[ 942.475194] Code: Unable to access opcode bytes at RIP 0xffd6.
[ 942.475792] RSP: 0018:aacf80ff7eb8 EFLAGS: 00010246
[ 942.476383] RAX: RBX: 9eaa8a175240 RCX:
0001
[ 942.476986] RDX: RSI: RDI:
9eaa838d5800
[ 942.477600] RBP: aacf80ff7ed0 R08: 4000 R09:
0004
[ 942.478203] R10: 0002 R11: R12:
[ 942.478800] R13: R14: ffea R15:
9eaa838d5800
[ 942.479399] FS: 7f998d487f00() GS:9eaaffc8()
knlGS:
[ 942.480006] CS: 0010 DS: ES: CR0: 80050033
[ 942.480607] CR2: ffd6 CR3: 00010a774002 CR4:
00370ee0
[ 942.481219] DR0: DR1: DR2:
[ 942.481855] DR3: DR6: fffe0ff0 DR7:
0400
[ 942.482458] Call Trace:
[ 942.483052] proc_reg_llseek+0x4e/0x80
[ 942.483646] ? __fdget_pos+0x43/0x50
[ 942.484234] ksys_lseek+0x84/0xc0
[ 942.484815] __x64_sys_lseek+0x1a/0x20
[ 942.485412] do_syscall_64+0x61/0xb0
[ 942.485966] ? asm_exc_page_fault+0x8/0x30
[ 942.486476] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 942.486994] RIP: 0033:0x7f998d5c1cdb
[ 942.487512] Code: ff ff c3 0f 1f 40 00 48 8b 15 89 81 0d 00 f7 d8 64 89 02
48 c7 c0 ff ff ff ff eb ba 0f 1f 00 f3 0f 1e fa b8 08 00 00 00 0f 05 <48> 3d 00
f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 59 81 0d 00 f7 d8
[ 942.488593] RSP: 002b:7ffdf61c5328 EFLAGS: 0246 ORIG_RAX:
0008
[ 942.489148] RAX: ffda RBX: RCX:
7f998d5c1cdb
[ 942.489710] RDX: RSI: RDI:
0004
[ 942.490252] RBP: 0004 R08: 01785e4740dd R09:
562dbebb9e50
[ 942.490801] R10: 7ffdf61c5300 R11: 0246 R12:
7ffdf61c63f0
[ 942.491354] R13: 7ffdf61c53f0 R14: 0003 R15:
01e9
== Fix ==
Add the default_llseek ops:
diff --git a/ubuntu/ubuntu-host/ubuntu-host.c
b/ubuntu/ubuntu-host/ubuntu-host.c
index 1abd402..a4c0636 100644
--- a/ubuntu/ubuntu-host/ubuntu-host.c
+++ b/ubuntu/ubuntu-host/ubuntu-host.c
@@ -38,6 +38,8 @@ static ssize_t esm_token_write(struct file *f, const char
__user *buf,
static const struct proc_ops esm_token_fops = {
.proc_read = esm_token_read,
.proc_write = esm_token_write,
+ .proc_lseek = default_llseek,
+
};
== Test plan ==
modrobe ubuntu-host
stress-ng --procfs 0 -t 60
without the fix we hit the splat. With the fix it's OK.
== Where problems could
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.142.00-0ubuntu1
---
nvidia-graphics-drivers-450-server (450.142.00-0ubuntu1) impish; urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.13.patch.
-- Alberto Milone Fri, 09 Jul 2021
14:39:52 +0200
** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
Fix Released
Status in fabric-manager-460 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Triaged
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Won't Fix
Status in linux-restricted-modules source package in Groovy:
Won't Fix
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
Won't Fix
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.211.00-0ubuntu1
---
nvidia-graphics-drivers-418-server (418.211.00-0ubuntu1) impish; urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.13.patch.
-- Alberto Milone Tue, 06 Jul 2021
17:52:33 +0200
** Changed in: nvidia-graphics-drivers-418-server (Ubuntu)
Status: In Progress => Fix Released
** Changed in: nvidia-graphics-drivers-450-server (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
Fix Released
Status in fabric-manager-460 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Triaged
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Won't Fix
Status in linux-restricted-modules source package in Groovy:
Won't Fix
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
Won't Fix
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in
[Kernel-packages] [Bug 1937846] Re: linux-azure: Ensure the latest linux-image-sgx is installed with the 5.11 kernels
This bug was fixed in the package linux-azure - 5.11.0-1013.14+21.10.1 --- linux-azure (5.11.0-1013.14+21.10.1) impish; urgency=medium * impish/linux-azure: 5.11.0-1013.14+21.10.1 -proposed tracker (LP: #1936483) * Packaging resync (LP: #1786013) - update dkms package versions [ Ubuntu: 5.11.0-1013.14 ] * hirsute/linux-azure: 5.11.0-1013.14 -proposed tracker (LP: #1936485) * linux-azure: Ensure the latest linux-image-sgx is installed with the 5.11 kernels (LP: #1937846) - [Packaging] Install the linux-base-sgx version for upstream SGX * Packaging resync (LP: #1786013) - update dkms package versions * large_dir in ext4 broken (LP: #1933074) - SAUCE: ext4: fix directory index node split corruption * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293) - Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test" * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645) - selftests: icmp_redirect: support expected failures * Mute/mic LEDs no function on some HP platfroms (LP: #1934878) - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 450 G8 - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 445 G8 - ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 630 G8 * [SRU][OEM-5.10/H] Fix HDMI output issue on Intel TGL GPU (LP: #1934864) - drm/i915: Fix HAS_LSPCON macro for platforms between GEN9 and GEN10 * mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC (LP: #1934239) - ALSA: hda/realtek: fix mute/micmute LEDs for HP EliteBook 830 G8 Notebook PC * ubuntu-host driver lacks lseek ops (LP: #1934110) - ubuntu-host: add generic lseek op * ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8 (LP: #1927749) - selftests/ftrace: fix event-no-pid on 1-core machine * Hirsute update: upstream stable patchset 2021-06-29 (LP: #1934012) - proc: Track /proc/$pid/attr/ opener mm_struct - ASoC: max98088: fix ni clock divider calculation - ASoC: amd: fix for pcm_read() error - spi: Fix spi device unregister flow - spi: spi-zynq-qspi: Fix stack violation bug - bpf: Forbid trampoline attach for functions with variable arguments - net/nfc/rawsock.c: fix a permission check bug - usb: cdns3: Fix runtime PM imbalance on error - ASoC: Intel: bytcr_rt5640: Add quirk for the Glavey TM800A550L tablet - ASoC: Intel: bytcr_rt5640: Add quirk for the Lenovo Miix 3-830 tablet - vfio-ccw: Reset FSM state to IDLE inside FSM - vfio-ccw: Serialize FSM IDLE state with I/O completion - ASoC: sti-sas: add missing MODULE_DEVICE_TABLE - spi: sprd: Add missing MODULE_DEVICE_TABLE - usb: chipidea: udc: assign interrupt number to USB gadget structure - isdn: mISDN: netjet: Fix crash in nj_probe: - bonding: init notify_work earlier to avoid uninitialized use - netlink: disable IRQs for netlink_lock_table() - net: mdiobus: get rid of a BUG_ON() - cgroup: disable controllers at parse time - wq: handle VM suspension in stall detection - net/qla3xxx: fix schedule while atomic in ql_sem_spinlock - RDS tcp loopback connection can hang - net:sfc: fix non-freed irq in legacy irq mode - scsi: bnx2fc: Return failure if io_req is already in ABTS processing - scsi: vmw_pvscsi: Set correct residual data length - scsi: hisi_sas: Drop free_irq() of devm_request_irq() allocated irq - scsi: target: qla2xxx: Wait for stop_phase1 at WWN removal - net: macb: ensure the device is available before accessing GEMGXL control registers - net: appletalk: cops: Fix data race in cops_probe1 - net: dsa: microchip: enable phy errata workaround on 9567 - nvme-fabrics: decode host pathing error for connect - MIPS: Fix kernel hang under FUNCTION_GRAPH_TRACER and PREEMPT_TRACER - dm verity: fix require_signatures module_param permissions - bnx2x: Fix missing error code in bnx2x_iov_init_one() - nvme-tcp: remove incorrect Kconfig dep in BLK_DEV_NVME - nvmet: fix false keep-alive timeout when a controller is torn down - powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P2041 i2c controllers - powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P1010 i2c controllers - spi: Don't have controller clean up spi device before driver unbind - spi: Cleanup on failure of initial setup - i2c: mpc: Make use of i2c_recover_bus() - i2c: mpc: implement erratum A-004447 workaround - ALSA: seq: Fix race of snd_seq_timer_open() - ALSA: firewire-lib: fix the context to call snd_pcm_stop_xrun() - spi: bcm2835: Fix out-of-bounds access with more than 4 slaves - Revert "ACPI: sleep: Put the FACS table after using it" - drm: Fix use-after-free read in drm_getunique() - drm: Lock pointer access in drm_master_release() - perf/x86/intel/uncore: Fix M2M event
[Kernel-packages] [Bug 1935807] Re: Impish update: v5.13.1 upstream stable release
This bug was fixed in the package linux - 5.13.0-14.14 --- linux (5.13.0-14.14) impish; urgency=medium * impish/linux: 5.13.0-14.14 -proposed tracker (LP: #1938565) * Miscellaneous Ubuntu changes - SAUCE: Revert "UBUNTU: SAUCE: random: Make getrandom() ready earlier" - SAUCE: random: properly make getrandom() ready earlier * Miscellaneous upstream changes - seq_buf: Fix overflow in seq_buf_putmem_hex() - bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc - ext4: cleanup in-core orphan list if ext4_truncate() failed to get a transaction handle - ext4: fix kernel infoleak via ext4_extent_header - ext4: fix overflow in ext4_iomap_alloc() - ext4: return error code when ext4_fill_flex_info() fails - ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit - ext4: remove check for zero nr_to_scan in ext4_es_scan() - ext4: fix avefreec in find_group_orlov - ext4: use ext4_grp_locked_error in mb_find_extent -- Andrea Righi Mon, 02 Aug 2021 14:23:08 +0200 ** Changed in: linux (Ubuntu Impish) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935807 Title: Impish update: v5.13.1 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Impish: 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: v5.13.1 upstream stable release from git://git.kernel.org/ Revert "KVM: x86/mmu: Drop kvm_mmu_extended_role.cr4_la57 hack" Linux 5.13.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940154] Re: Xorg freeze (nouveau/ttm use-after-free with full-screen video)
** Attachment added: "Second stacktrace, similar behaviour observed" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940154/+attachment/5518865/+files/dmesg_vfree_bad_address.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940154 Title: Xorg freeze (nouveau/ttm use-after-free with full-screen video) Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to Ubuntu 21.04 yesterday, I've noticed several hangs during full-screen video playback (watching Youtube videos in Chromium). Often, it happens just after or during the switch to full- screen. The system stays running and I can connect via ssh, but restarting gdm3 has no effect and most of the time I've had to reboot. The latest hang recovered automatically when I left the machine alone for about 2 minutes, and produced the following messages in dmesg (I'll attach a more complete log): ``` [ 3520.856803] [TTM] Buffer eviction failed [ 3520.856856] [ cut here ] [ 3520.856859] refcount_t: underflow; use-after-free. [ 3520.856888] WARNING: CPU: 3 PID: 6842 at lib/refcount.c:28 refcount_warn_saturate+0xae/0xf0 ... [ 3520.857292] Call Trace: [ 3520.857305] ttm_bo_put+0x3f/0x50 [ttm] [ 3520.857331] nouveau_gem_new+0xc4/0x100 [nouveau] [ 3520.857611] ? nouveau_gem_new+0x100/0x100 [nouveau] [ 3520.857871] nouveau_gem_ioctl_new+0x5b/0x100 [nouveau] [ 3520.858133] ? nouveau_gem_new+0x100/0x100 [nouveau] [ 3520.858398] drm_ioctl_kernel+0xae/0xf0 [drm] [ 3520.858500] drm_ioctl+0x245/0x400 [drm] [ 3520.858586] ? nouveau_gem_new+0x100/0x100 [nouveau] [ 3520.858850] ? __fget_files+0x5f/0x90 [ 3520.858864] ? __fget_light+0x32/0x80 [ 3520.858879] nouveau_drm_ioctl+0x66/0xc0 [nouveau] [ 3520.859145] __x64_sys_ioctl+0x91/0xc0 [ 3520.859158] do_syscall_64+0x38/0x90 [ 3520.859170] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 3520.859182] RIP: 0033:0x7fce8ceb0317 ``` ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 16 23:36:04 2021 DistUpgraded: 2021-08-15 02:10:41,733 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GT218M [GeForce 310M] [10de:0a70] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd GT218M [GeForce 310M] [144d:c079] InstallationDate: Installed on 2014-06-27 (2607 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. Q430/Q530 ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=fc20db83-0138-4e0c-b7e9-04da38c1e9e9 ro quiet splash acpi_backlight=vendor crashkernel=512M-:192M acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to hirsute on 2021-08-15 (1 days ago) dmi.bios.date: 05/29/2010 dmi.bios.release: 2.0 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 02KF.M008.20100529.KSJ dmi.board.asset.tag: Tag 12345 dmi.board.name: Q430/Q530 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr02KF.M008.20100529.KSJ:bd05/29/2010:br2.0:svnSAMSUNGELECTRONICSCO.,LTD.:pnQ430/Q530:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnQ430/Q530:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: Q430/Q530 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz
[Kernel-packages] [Bug 1940154] Re: Xorg freeze (nouveau/ttm use-after-free with full-screen video)
Thanks Daniel. I've had on-and-off problems with both the nouveau and NVidia closed-source drivers pretty much since I got this thing and at some point vowed that my next machine would use an AMD card, since I've heard the open-source AMD driver is good. I'll take a look at those links and see if I can do some debugging, since there might be other people out there who are affected by this too, and it'd be a shame to have to stop upgrading their Linux systems as a result. Unless a machine breaks down completely, I don't see why it shouldn't run Linux for more than 11 years. I've noticed at least two flavours of error stacktrace that happen, so there may be two separate bugs. The first (as in the opening report) starts with "refcount_t: underflow; use-after-free" in lib/refcount.c:28 refcount_warn_saturate+0xae/0xf0, and the second starts with "Trying to vfree() bad address" in mm/vmalloc.c:2263 __vunmap+0x263/0x280. The rest of the stack trace is somewhat different, although they both pass through "ttm_bo_put". They both look to be memory management errors (use-after-free and possibly a double-free?). -- 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/1940154 Title: Xorg freeze (nouveau/ttm use-after-free with full-screen video) Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to Ubuntu 21.04 yesterday, I've noticed several hangs during full-screen video playback (watching Youtube videos in Chromium). Often, it happens just after or during the switch to full- screen. The system stays running and I can connect via ssh, but restarting gdm3 has no effect and most of the time I've had to reboot. The latest hang recovered automatically when I left the machine alone for about 2 minutes, and produced the following messages in dmesg (I'll attach a more complete log): ``` [ 3520.856803] [TTM] Buffer eviction failed [ 3520.856856] [ cut here ] [ 3520.856859] refcount_t: underflow; use-after-free. [ 3520.856888] WARNING: CPU: 3 PID: 6842 at lib/refcount.c:28 refcount_warn_saturate+0xae/0xf0 ... [ 3520.857292] Call Trace: [ 3520.857305] ttm_bo_put+0x3f/0x50 [ttm] [ 3520.857331] nouveau_gem_new+0xc4/0x100 [nouveau] [ 3520.857611] ? nouveau_gem_new+0x100/0x100 [nouveau] [ 3520.857871] nouveau_gem_ioctl_new+0x5b/0x100 [nouveau] [ 3520.858133] ? nouveau_gem_new+0x100/0x100 [nouveau] [ 3520.858398] drm_ioctl_kernel+0xae/0xf0 [drm] [ 3520.858500] drm_ioctl+0x245/0x400 [drm] [ 3520.858586] ? nouveau_gem_new+0x100/0x100 [nouveau] [ 3520.858850] ? __fget_files+0x5f/0x90 [ 3520.858864] ? __fget_light+0x32/0x80 [ 3520.858879] nouveau_drm_ioctl+0x66/0xc0 [nouveau] [ 3520.859145] __x64_sys_ioctl+0x91/0xc0 [ 3520.859158] do_syscall_64+0x38/0x90 [ 3520.859170] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 3520.859182] RIP: 0033:0x7fce8ceb0317 ``` ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 16 23:36:04 2021 DistUpgraded: 2021-08-15 02:10:41,733 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GT218M [GeForce 310M] [10de:0a70] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd GT218M [GeForce 310M] [144d:c079] InstallationDate: Installed on 2014-06-27 (2607 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. Q430/Q530 ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=fc20db83-0138-4e0c-b7e9-04da38c1e9e9 ro quiet splash acpi_backlight=vendor crashkernel=512M-:192M acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display
[Kernel-packages] [Bug 1940482] 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 1940482
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
** Changed in: linux (Ubuntu Focal)
Status: New => Incomplete
** Tags added: focal
--
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/1940482
Title:
[thunderx2] Synchronous external abort: 96000610 [#1] SMP
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
Incomplete
Bug description:
[Impact]:
ThunderX2 will not deploy Focal, Arm64 Cloud Image - 20210811
focal": {"stable": {"content_id": "maas:v2:download", "kflavor": "generic",
"path": "ubuntu/arm64/ga-20.04/focal/20210811/boot-initrd", "product_name":
"maas:boot:ubuntu:arm64:ga-20.04:focal"
[ 286.968817] Internal error: synchronous external abort: 96000610 [#1] SMP
[ 286.975594] Modules linked in: nls_iso8859_1 bcache crc64 zfs(PO)
zunicode(PO) zlua(PO) zcommon(PO) znvpair(PO) zavl(PO) icp(PO) spl(O)
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua overlay btrfs zstd_compress
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear i2c_smbus hid_generic
ast drm_vram_helper ttm usbhid drm_kms_helper crct10dif_ce hid syscopyarea
ghash_ce sysfillrect sha2_ce qede mpt3sas sha256_arm64 ipmi_ssif sysimgblt uas
sha1_ce fb_sys_fops qed ipmi_devintf igb raid_class drm ipmi_msghandler
scsi_transport_sas ahci i2c_algo_bit crc8 gpio_xlp i2c_xlp9xx usb_storage
aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher
[ 287.040312] CPU: 1 PID: 1 Comm: shutdown Tainted: P O
5.4.0-80-generic #90-Ubuntu
[ 287.049083] Hardware name: To be filled by O.E.M. Saber/Saber, BIOS
0ACKL030 06/04/2020
[ 287.057072] pstate: 6049 (nZCv daif +PAN -UAO)
[ 287.061864] pc : igb_rd32+0x30/0xd8 [igb]
[ 287.065865] lr : __igb_shutdown+0x84/0x1d8 [igb]
[ 287.070468] sp : 80001255bb90
[ 287.073769] x29: 80001255bb90 x28: 00bf5434e900
[ 287.079067] x27: x26: 009eef029130
[ 287.084365] x25: x24: 009ed603ce08
[ 287.089663] x23: 80001255bc37 x22: 009eef029000
[ 287.094960] x21: 009ed603ce08 x20: 0008
[ 287.100258] x19: 8000301c0008 x18:
[ 287.10] x17: x16: 0032
[ 287.110853] x15: 0004 x14: 0003
[ 287.116150] x13: x12: 009ed50f3530
[ 287.121448] x11: 009ed50f3478 x10:
[ 287.126745] x9 : 0001 x8 : 00210d00
[ 287.132043] x7 : x6 : 0001
[ 287.137340] x5 : x4 : fe027b2d5c20
[ 287.142638] x3 : 00bf5434e900 x2 :
[ 287.147935] x1 : 8000301c x0 : 890491c4
[ 287.153234] Call trace:
[ 287.155673] igb_rd32+0x30/0xd8 [igb]
[ 287.159326] __igb_shutdown+0x84/0x1d8 [igb]
[ 287.163586] igb_shutdown+0x38/0x90 [igb]
[ 287.167585] pci_device_shutdown+0x48/0x88
[ 287.171670] device_shutdown+0x14c/0x298
[ 287.175582] kernel_restart_prepare+0x48/0x58
[ 287.179925] kernel_restart+0x24/0x80
[ 287.183573] __do_sys_reboot+0x100/0x228
[ 287.187482] __arm64_sys_reboot+0x30/0x40
[ 287.191480] el0_svc_common.constprop.0+0xe4/0x1f0
[ 287.196256] el0_svc_handler+0x38/0xa8
[ 287.13] el0_svc+0x10/0x2c8
[ 287.203124] Code: d503201f f94006a1 b40002c1 8b344033 (b9400273)
[ 287.209320] ---[ end trace b2addffb79e92219 ]---
[ 287.214039] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b
[ 287.221755] Kernel Offset: disabled
[ 287.225231] CPU features: 0x6002,62000c38
[ 287.229226] Memory Limit: none
[ 287.232296] ---[ end Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b ]---
Rom...
CRC: len=0xf080, cal=0x27ff5de9, img=0x27ff5de9, match!
[Test Case]:
Deploy Focal/Arm64-Generic to a ThunderX2 in the MAAS (Metal As a Service)
provisioner. Using MAAS version: 2.9.3~beta1 (9197-g.afe92bb63) via a snap,
the daily focal image appears to be 20210811
From the kernel teams standpoint this kernel in the initrd, did pass
SRU testing before its release.
[Fix]:
N/A
[Regression]:
Probably No (From Kernel Viewpoint) this could possibly be
[Kernel-packages] [Bug 1940482] [NEW] [thunderx2] Synchronous external abort: 96000610 [#1] SMP
Public bug reported:
[Impact]:
ThunderX2 will not deploy Focal, Arm64 Cloud Image - 20210811
focal": {"stable": {"content_id": "maas:v2:download", "kflavor": "generic",
"path": "ubuntu/arm64/ga-20.04/focal/20210811/boot-initrd", "product_name":
"maas:boot:ubuntu:arm64:ga-20.04:focal"
[ 286.968817] Internal error: synchronous external abort: 96000610 [#1] SMP
[ 286.975594] Modules linked in: nls_iso8859_1 bcache crc64 zfs(PO)
zunicode(PO) zlua(PO) zcommon(PO) znvpair(PO) zavl(PO) icp(PO) spl(O)
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua overlay btrfs zstd_compress
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear i2c_smbus hid_generic
ast drm_vram_helper ttm usbhid drm_kms_helper crct10dif_ce hid syscopyarea
ghash_ce sysfillrect sha2_ce qede mpt3sas sha256_arm64 ipmi_ssif sysimgblt uas
sha1_ce fb_sys_fops qed ipmi_devintf igb raid_class drm ipmi_msghandler
scsi_transport_sas ahci i2c_algo_bit crc8 gpio_xlp i2c_xlp9xx usb_storage
aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher
[ 287.040312] CPU: 1 PID: 1 Comm: shutdown Tainted: P O
5.4.0-80-generic #90-Ubuntu
[ 287.049083] Hardware name: To be filled by O.E.M. Saber/Saber, BIOS 0ACKL030
06/04/2020
[ 287.057072] pstate: 6049 (nZCv daif +PAN -UAO)
[ 287.061864] pc : igb_rd32+0x30/0xd8 [igb]
[ 287.065865] lr : __igb_shutdown+0x84/0x1d8 [igb]
[ 287.070468] sp : 80001255bb90
[ 287.073769] x29: 80001255bb90 x28: 00bf5434e900
[ 287.079067] x27: x26: 009eef029130
[ 287.084365] x25: x24: 009ed603ce08
[ 287.089663] x23: 80001255bc37 x22: 009eef029000
[ 287.094960] x21: 009ed603ce08 x20: 0008
[ 287.100258] x19: 8000301c0008 x18:
[ 287.10] x17: x16: 0032
[ 287.110853] x15: 0004 x14: 0003
[ 287.116150] x13: x12: 009ed50f3530
[ 287.121448] x11: 009ed50f3478 x10:
[ 287.126745] x9 : 0001 x8 : 00210d00
[ 287.132043] x7 : x6 : 0001
[ 287.137340] x5 : x4 : fe027b2d5c20
[ 287.142638] x3 : 00bf5434e900 x2 :
[ 287.147935] x1 : 8000301c x0 : 890491c4
[ 287.153234] Call trace:
[ 287.155673] igb_rd32+0x30/0xd8 [igb]
[ 287.159326] __igb_shutdown+0x84/0x1d8 [igb]
[ 287.163586] igb_shutdown+0x38/0x90 [igb]
[ 287.167585] pci_device_shutdown+0x48/0x88
[ 287.171670] device_shutdown+0x14c/0x298
[ 287.175582] kernel_restart_prepare+0x48/0x58
[ 287.179925] kernel_restart+0x24/0x80
[ 287.183573] __do_sys_reboot+0x100/0x228
[ 287.187482] __arm64_sys_reboot+0x30/0x40
[ 287.191480] el0_svc_common.constprop.0+0xe4/0x1f0
[ 287.196256] el0_svc_handler+0x38/0xa8
[ 287.13] el0_svc+0x10/0x2c8
[ 287.203124] Code: d503201f f94006a1 b40002c1 8b344033 (b9400273)
[ 287.209320] ---[ end trace b2addffb79e92219 ]---
[ 287.214039] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b
[ 287.221755] Kernel Offset: disabled
[ 287.225231] CPU features: 0x6002,62000c38
[ 287.229226] Memory Limit: none
[ 287.232296] ---[ end Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b ]---
Rom...
CRC: len=0xf080, cal=0x27ff5de9, img=0x27ff5de9, match!
[Test Case]:
Deploy Focal/Arm64-Generic to a ThunderX2 in the MAAS (Metal As a Service)
provisioner. Using MAAS version: 2.9.3~beta1 (9197-g.afe92bb63) via a snap,
the daily focal image appears to be 20210811
>From the kernel teams standpoint this kernel in the initrd, did pass SRU
testing before its release.
[Fix]:
N/A
[Regression]:
Probably No (From Kernel Viewpoint) this could possibly be caused by something
other than kernel.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1940482
Title:
[thunderx2] Synchronous external abort: 96000610 [#1] SMP
Status in linux package in Ubuntu:
New
Status in linux source package in Focal:
New
Bug description:
[Impact]:
ThunderX2 will not deploy Focal, Arm64 Cloud Image - 20210811
focal": {"stable": {"content_id": "maas:v2:download", "kflavor": "generic",
"path": "ubuntu/arm64/ga-20.04/focal/20210811/boot-initrd", "product_name":
"maas:boot:ubuntu:arm64:ga-20.04:focal"
[ 286.968817] Internal error: synchronous external abort: 96000610 [#1] SMP
[ 286.975594] Modules linked in: nls_iso8859_1 bcache crc64 zfs(PO)
zunicode(PO) zlua(PO) zcommon(PO) znvpair(PO) zavl(PO) icp(PO) spl(O)
dm_multipath scsi_dh_rdac
[Kernel-packages] [Bug 1937056] Re: Touchpad not working with ASUS TUF F15
This solves the problem for me. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1937056 Title: Touchpad not working with ASUS TUF F15 Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: == SRU Justification == [Impact] Touchpad and touchscreen don't work on TGL-H laptops. [Fix] Update GPIO mapping so the values can match between Linux and BIOS. [Test] After applying the patch, both touchpad and touchscreen can work correctly. [Where problems could occur] If somehow any of the new pin value is incorrect, it can break devices that require Intel GPIO to work. == Original Bug Report == I am using Kubuntu 21.04 on my ASUS TUF F15 FX506HM_FX566HM. The touchpad isn't detected in Settings and neither in xinput, nor in cat /proc/bus/input/devices. Laptop model: ASUS TUF F15 FX506HM_FX566HM. Manufacturer of the Touchpad: Probably ELAN1203 When the symptom first appeared: From beginning Output of lsb_release -rd Description:Ubuntu 21.04 Release:21.04 Using kernel version 5.13.6. Also tried 5.11, 5.12.8, 5.12.15, 5.13.1, 5.13.2, 5.13.4, 5.13.5, 5.14-rc2, 5.14-rc3 Output of xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Asus Wireless Radio Control id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=11 [slave keyboard (3)] ↳ Intel HID events id=12 [slave keyboard (3)] ↳ Intel HID 5 button array id=13 [slave keyboard (3)] ↳ Asus WMI hotkeys id=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)] Output of lspci :00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 05) :00:01.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #1 (rev 05) :00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) :00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 05) :00:06.0 System peripheral: Intel Corporation Device 09ab :00:07.0 PCI bridge: Intel Corporation Tiger Lake-H Thunderbolt 4 PCI Express Root Port #0 (rev 05) :00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 05) :00:0a.0 Signal processing controller: Intel Corporation Tigerlake Telemetry Aggregator Driver (rev 01) :00:0d.0 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 USB Controller (rev 05) :00:0d.2 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 NHI #0 (rev 05) :00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller :00:14.0 USB controller: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller (rev 11) :00:14.2 RAM memory: Intel Corporation Tiger Lake-H Shared SRAM (rev 11) :00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H Serial IO I2C Controller #0 (rev 11) :00:16.0 Communication controller: Intel Corporation Tiger Lake-H Management Engine Interface (rev 11) :00:1c.0 PCI bridge: Intel Corporation Device 43bf (rev 11) :00:1d.0 PCI bridge: Intel Corporation Device 43b6 (rev 11) :00:1f.0 ISA bridge: Intel Corporation Tiger Lake-H LPC/eSPI Controller (rev 11) :00:1f.3 Audio device: Intel Corporation Tiger Lake-H HD Audio Controller (rev 11)
[Kernel-packages] [Bug 1913768] Re: HP Touchpad Not Detected
No touchpad listed on HP 15-dw3165st with Ubuntu 18.04 ** Attachment added: "devices" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1913768/+attachment/5518840/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1913768 Title: HP Touchpad Not Detected Status in linux-signed-hwe-5.4 package in Ubuntu: Confirmed Bug description: Touchpad is not working and is not shown in output of command: cat /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 29 22:02:57 2021 InstallationDate: Installed on 2021-01-29 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1913768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940470] 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 1940470 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/1940470 Title: Function keys and keyboard backlight not working Status in linux package in Ubuntu: Incomplete Bug description: Samsung Chronos 7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940470] [NEW] Function keys and keyboard backlight not working
Public bug reported: Samsung Chronos 7. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940470 Title: Function keys and keyboard backlight not working Status in linux package in Ubuntu: New Bug description: Samsung Chronos 7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940461] Re: Impish update: v5.13.12 upstream stable release
** Changed in: linux (Ubuntu Impish)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Impish)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1940461
Title:
Impish update: v5.13.12 upstream stable release
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.13.12 upstream stable release
from git://git.kernel.org/
lib: use PFN_PHYS() in devmem_is_allowed()
Revert "usb: dwc3: gadget: Use list_replace_init() before traversing lists"
iio: adc: ti-ads7950: Ensure CS is deasserted after reading channels
iio: adis: set GPIO reset pin direction
iio: humidity: hdc100x: Add margin to the conversion time
iio: adc: Fix incorrect exit of for-loop
ASoC: amd: Fix reference to PCM buffer address
ASoC: xilinx: Fix reference to PCM buffer address
ASoC: uniphier: Fix reference to PCM buffer address
ASoC: tlv320aic31xx: Fix jack detection after suspend
ASoC: kirkwood: Fix reference to PCM buffer address
ASoC: intel: atom: Fix reference to PCM buffer address
i2c: dev: zero out array used for i2c reads from userspace
cifs: Handle race conditions during rename
cifs: create sd context must be a multiple of 8
cifs: Call close synchronously during unlink/rename/lease break.
cifs: use the correct max-length for dentry_path_raw()
io_uring: drop ctx->uring_lock before flushing work item
io_uring: fix ctx-exit io_rsrc_put_work() deadlock
scsi: lpfc: Move initialization of phba->poll_list earlier to avoid crash
cgroup: rstat: fix A-A deadlock on 32bit around u64_stats_sync
seccomp: Fix setting loaded filter count during TSYNC
net: wwan: mhi_wwan_ctrl: Fix possible deadlock
net: ethernet: ti: cpsw: fix min eth packet size for non-switch use-cases
ARC: fp: set FPU_STATUS.FWE to enable FPU_STATUS update on context switch
ceph: reduce contention in ceph_check_delayed_caps()
pinctrl: k210: Fix k210_fpioa_probe()
ACPI: NFIT: Fix support for virtual SPA ranges
libnvdimm/region: Fix label activation vs errors
riscv: kexec: do not add '-mno-relax' flag if compiler doesn't support it
vmlinux.lds.h: Handle clang's module.{c,d}tor sections
drm/i915/gvt: Fix cached atomics setting for Windows VM
drm/i915/display: Fix the 12 BPC bits for PIPE_MISC reg
drm/amd/display: Remove invalid assert for ODM + MPC case
drm/amd/display: use GFP_ATOMIC in amdgpu_dm_irq_schedule_work
drm/amdgpu: Add preferred mode in modeset when freesync video mode's enabled.
drm/amdgpu: don't enable baco on boco platforms in runpm
drm/amdgpu: handle VCN instances when harvesting (v2)
ieee802154: hwsim: fix GPF in hwsim_set_edge_lqi
ieee802154: hwsim: fix GPF in hwsim_new_edge_nl
drm/mediatek: Fix cursor plane no update
pinctrl: mediatek: Fix fallback behavior for bias_set_combo
ASoC: cs42l42: Correct definition of ADC Volume control
ASoC: cs42l42: Don't allow SND_SOC_DAIFMT_LEFT_J
ASoC: cs42l42: Fix bclk calculation for mono
selftests/sgx: Fix Q1 and Q2 calculation in sigstruct.c
ASoC: SOF: Intel: Kconfig: fix SoundWire dependencies
ASoC: SOF: Intel: hda-ipc: fix reply size checking
ASoC: cs42l42: Fix inversion of ADC Notch Switch control
ASoC: cs42l42: Remove duplicate control for WNF filter frequency
netfilter: nf_conntrack_bridge: Fix memory leak when error
ASoC: cs42l42: PLL must be running when changing MCLK_SRC_SEL
ASoC: cs42l42: Fix LRCLK frame start edge
ASoC: cs42l42: Fix mono playback
net: dsa: mt7530: add the missing RxUnicast MIB counter
net: mvvp2: fix short frame size on s390
platform/x86: pcengines-apuv2: Add missing terminating entries to gpio-lookup
tables
perf/x86/intel: Apply mid ACK for small core
drm/amd/pm: Fix a memory leak in an error handling path in
'vangogh_tables_init()'
libbpf: Fix probe for BPF_PROG_TYPE_CGROUP_SOCKOPT
libbpf: Do not close un-owned FD 0 on errors
bpf: Fix integer overflow involving bucket_size
net: dsa: qca: ar9331: make proper initial port defaults
net: phy: micrel: Fix link detection on ksz87xx switch"
ppp: Fix generating ifname when empty IFLA_IFNAME is specified
io_uring: clear TIF_NOTIFY_SIGNAL when running task work
net/smc: fix wait on already cleared link
net/smc: Correct smc
[Kernel-packages] [Bug 1940468] [NEW] Hirsute update: upstream stable patchset 2021-08-18
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2021-08-18
Ported from the following upstream stable releases:
v5.10.54, v5.13.6
from git://git.kernel.org/
igc: Fix use-after-free error during reset
igb: Fix use-after-free error during reset
igc: change default return of igc_read_phy_reg()
ixgbe: Fix an error handling path in 'ixgbe_probe()'
igc: Fix an error handling path in 'igc_probe()'
igb: Fix an error handling path in 'igb_probe()'
fm10k: Fix an error handling path in 'fm10k_probe()'
e1000e: Fix an error handling path in 'e1000_probe()'
iavf: Fix an error handling path in 'iavf_probe()'
igb: Check if num of q_vectors is smaller than max before array access
igb: Fix position of assignment to *ring
gve: Fix an error handling path in 'gve_probe()'
bonding: fix suspicious RCU usage in bond_ipsec_add_sa()
bonding: fix null dereference in bond_ipsec_add_sa()
ixgbevf: use xso.real_dev instead of xso.dev in callback functions of struct
xfrmdev_ops
bonding: fix suspicious RCU usage in bond_ipsec_del_sa()
bonding: disallow setting nested bonding + ipsec offload
bonding: Add struct bond_ipesc to manage SA
bonding: fix suspicious RCU usage in bond_ipsec_offload_ok()
bonding: fix incorrect return value of bond_ipsec_offload_ok()
ipv6: fix 'disable_policy' for fwd packets
stmmac: platform: Fix signedness bug in stmmac_probe_config_dt()
selftests: icmp_redirect: remove from checking for IPv6 route get
selftests: icmp_redirect: IPv6 PMTU info should be cleared after redirect
pwm: sprd: Ensure configuring period and duty_cycle isn't wrongly skipped
cxgb4: fix IRQ free race during driver unload
mptcp: fix warning in __skb_flow_dissect() when do syn cookie for subflow join
nvme-pci: do not call nvme_dev_remove_admin from nvme_remove
KVM: x86/pmu: Clear anythread deprecated bit when 0xa leaf is unsupported on
the SVM
perf inject: Fix dso->nsinfo refcounting
perf probe: Fix dso->nsinfo refcounting
perf env: Fix sibling_dies memory leak
perf test session_topology: Delete session->evlist
perf test event_update: Fix memory leak of evlist
perf dso: Fix memory leak in dso__new_map()
perf test maps__merge_in: Fix memory leak of maps
perf env: Fix memory leak of cpu_pmu_caps
perf report: Free generated help strings for sort option
perf script: Fix memory 'threads' and 'cpus' leaks on exit
perf lzma: Close lzma stream on exit
perf probe-file: Delete namelist in del_events() on the error path
perf data: Close all files in close_dir()
perf sched: Fix record failure when CONFIG_SCHEDSTATS is not set
ASoC: wm_adsp: Correct wm_coeff_tlv_get handling
spi: imx: add a check for speed_hz before calculating the clock
spi: stm32: fixes pm_runtime calls in probe/remove
regulator: hi6421: Use correct variable type for regmap api val argument
regulator: hi6421: Fix getting wrong drvdata
spi: mediatek: fix fifo rx mode
ASoC: rt5631: Fix regcache sync errors on resume
bpf, test: fix NULL pointer dereference on invalid expected_attach_type
bpf: Fix tail_call_reachable rejection for interpreter when jit failed
xdp, net: Fix use-after-free in bpf_xdp_link_release
timers: Fix get_next_timer_interrupt() with no timers pending
liquidio: Fix unintentional sign extension issue on left shift of u16
s390/bpf: Perform r1 range checking before accessing jit->seen_reg[r1]
bpf, sockmap: Fix potential memory leak on unlikely error case
bpf, sockmap, tcp: sk_prot needs inuse_idx set for proc stats
bpf, sockmap, udp: sk_prot needs inuse_idx set for proc stats
bpftool: Check malloc return value in mount_bpffs_for_pin
net: fix uninit-value in caif_seqpkt_sendmsg
usb: hso: fix error handling code of hso_create_net_device
dma-mapping: handle vmalloc addresses in dma_common_{mmap,get_sgtable}
efi/tpm: Differentiate missing and invalid final event log table.
net: decnet: Fix sleeping inside in af_decnet
KVM: PPC: Book3S: Fix CONFIG_TRANSACTIONAL_MEM=n crash
KVM: PPC: Fix kvm_arch_vcpu_ioctl vcpu_load leak
net: sched: fix memory leak in tcindex_partial_destroy_work
sctp: trim optlen when it's a huge value in sctp_setsockopt
netrom: Decrease sock refcount when sock timers expire
scsi: iscsi: Fix iface sysfs attr detection
scsi: target: Fix protect handling in WRITE SAME(32)
spi: cadence: Correct initialisation of runtime PM again
ACPI: Kconfig: Fix table override from built-in initrd
bnxt_en: don't disable an already disabled PCI device
bnxt_en: Refresh RoCE capabilities in bnxt_ulp_probe()
bnxt_en: Add missing check for BNXT_STATE_ABORT_ERR in bnxt_fw_rset_task()
bnxt_en:
[Kernel-packages] [Bug 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
I am getting the same bug. 21' System76 Gazelle (gaze16), Ubuntu 20.04LTS. I am getting this bug with the new INC-004 Belkin CONNECT 11-in-1 USB-C Multiport Hub. Ethernet and HDMI display output are working but USB throws errors. -uname -a 5.11.0-7620-generic #21~1626191760~20.04~55de9c3~dev-Ubuntu SMP Tue Jul 20 18:02:09 x86_64 x86_64 x86_64 GNU/Linux -cat /var/log/syslog | grep kernel Aug 18 13:48:25 exfil kernel: [ 5659.363129] usb 2-3: new SuperSpeed Gen 1 USB device number 9 using xhci_hcd Aug 18 13:48:25 exfil kernel: [ 5659.385549] usb 2-3: New USB device found, idVendor=2109, idProduct=0817, bcdDevice= 3.b4 Aug 18 13:48:25 exfil kernel: [ 5659.385559] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 18 13:48:25 exfil kernel: [ 5659.385562] usb 2-3: Product: USB3.0 Hub Aug 18 13:48:25 exfil kernel: [ 5659.385565] usb 2-3: Manufacturer: VIA Labs, Inc. Aug 18 13:48:25 exfil kernel: [ 5659.387948] hub 2-3:1.0: USB hub found Aug 18 13:48:25 exfil kernel: [ 5659.388502] hub 2-3:1.0: 4 ports detected Aug 18 13:48:29 exfil kernel: [ 5663.471049] usb usb1-port3: Cannot enable. Maybe the USB cable is bad? Aug 18 13:48:29 exfil kernel: [ 5663.471134] usb usb1-port3: attempt power cycle Aug 18 13:48:33 exfil kernel: [ 5667.906931] usb usb1-port3: Cannot enable. Maybe the USB cable is bad? Aug 18 13:48:37 exfil kernel: [ 5672.003075] usb usb1-port3: Cannot enable. Maybe the USB cable is bad? Aug 18 13:48:37 exfil kernel: [ 5672.003155] usb usb1-port3: unable to enumerate USB device Aug 18 13:48:41 exfil kernel: [ 5676.235101] usb usb1-port3: Cannot enable. Maybe the USB cable is bad? Aug 18 13:48:46 exfil kernel: [ 5680.323145] usb usb1-port3: Cannot enable. Maybe the USB cable is bad? Aug 18 13:48:46 exfil kernel: [ 5680.323227] usb usb1-port3: attempt power cycle Aug 18 13:48:50 exfil kernel: [ 5684.731150] usb usb1-port3: Cannot enable. Maybe the USB cable is bad? Aug 18 13:48:54 exfil kernel: [ 5688.819059] usb usb1-port3: Cannot enable. Maybe the USB cable is bad? Aug 18 13:48:54 exfil kernel: [ 5688.819109] usb usb1-port3: unable to enumerate USB device Aug 18 13:48:58 exfil kernel: [ 5693.051196] usb usb1-port3: Cannot enable. Maybe the USB cable is bad? Aug 18 13:49:02 exfil kernel: [ 5697.139187] usb usb1-port3: Cannot enable. Maybe the USB cable is bad? Aug 18 13:49:02 exfil kernel: [ 5697.139272] usb usb1-port3: attempt power cycle Aug 18 13:49:07 exfil kernel: [ 5701.551207] usb usb1-port3: Cannot enable. Maybe the USB cable is bad? Aug 18 13:49:11 exfil kernel: [ 5705.639242] usb usb1-port3: Cannot enable. Maybe the USB cable is bad? Aug 18 13:49:11 exfil kernel: [ 5705.639326] usb usb1-port3: unable to enumerate USB device -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856608 Title: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Confirmed Bug description: This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81. This bug was fixed by simply reverting the offending change. Bug 1859873 tracks root causing the issue and reapplying the change w/ any necessary fixes. [Impact] USB port unusable and boot time takes ~5 minutes longer to complete. Kernel emits messages like: usb usb2-port2: Cannot enable. Maybe the USB cable is bad? [Test Case] dmesg | grep "Cannot enable" [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] Re: Lots of cme when using 5.8.0 but not with 5.4.0
The kernel in use is now 5.11.0-25-generic but the symptoms remain the same. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yannek 5763 F pulseaudio /dev/snd/controlC0: yannek 5763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-26 (204 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20HES0FW00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-25-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: 10/19/2020 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET90W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FW00 dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1931845/+attachment/5518824/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yannek 5763 F pulseaudio /dev/snd/controlC0: yannek 5763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-26 (204 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20HES0FW00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-25-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: 10/19/2020 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET90W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FW00 dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1931845/+attachment/5518819/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yannek 5763 F pulseaudio /dev/snd/controlC0: yannek 5763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-26 (204 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20HES0FW00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-25-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: 10/19/2020 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET90W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FW00 dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1931845/+attachment/5518810/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yannek 5763 F pulseaudio /dev/snd/controlC0: yannek 5763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-26 (204 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20HES0FW00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-25-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: 10/19/2020 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET90W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FW00 dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1931845/+attachment/5518817/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yannek 5763 F pulseaudio /dev/snd/controlC0: yannek 5763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-26 (204 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20HES0FW00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-25-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: 10/19/2020 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET90W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FW00 dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1931845/+attachment/5518820/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yannek 5763 F pulseaudio /dev/snd/controlC0: yannek 5763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-26 (204 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20HES0FW00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-25-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: 10/19/2020 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET90W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FW00 dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1931845/+attachment/5518823/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yannek 5763 F pulseaudio /dev/snd/controlC0: yannek 5763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-26 (204 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20HES0FW00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-25-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: 10/19/2020 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET90W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FW00 dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1931845/+attachment/5518809/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yannek 5763 F pulseaudio /dev/snd/controlC0: yannek 5763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-26 (204 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20HES0FW00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-25-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: 10/19/2020 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET90W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FW00 dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1931845/+attachment/5518808/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yannek 5763 F pulseaudio /dev/snd/controlC0: yannek 5763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-26 (204 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20HES0FW00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-25-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: 10/19/2020 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET90W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FW00 dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1931845/+attachment/5518815/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yannek 5763 F pulseaudio /dev/snd/controlC0: yannek 5763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-26 (204 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20HES0FW00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-25-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: 10/19/2020 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET90W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FW00 dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1931845/+attachment/5518818/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yannek 5763 F pulseaudio /dev/snd/controlC0: yannek 5763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-26 (204 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20HES0FW00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-25-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: 10/19/2020 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET90W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FW00 dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1931845/+attachment/5518816/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yannek 5763 F pulseaudio /dev/snd/controlC0: yannek 5763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-26 (204 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20HES0FW00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-25-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: 10/19/2020 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET90W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FW00 dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1931845/+attachment/5518812/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yannek 5763 F pulseaudio /dev/snd/controlC0: yannek 5763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-26 (204 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20HES0FW00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-25-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: 10/19/2020 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET90W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FW00 dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1931845/+attachment/5518814/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yannek 5763 F pulseaudio /dev/snd/controlC0: yannek 5763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-26 (204 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20HES0FW00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-25-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: 10/19/2020 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET90W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FW00 dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1931845/+attachment/5518821/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yannek 5763 F pulseaudio /dev/snd/controlC0: yannek 5763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-26 (204 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20HES0FW00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-25-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: 10/19/2020 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET90W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FW00 dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1931845/+attachment/5518822/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yannek 5763 F pulseaudio /dev/snd/controlC0: yannek 5763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-26 (204 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20HES0FW00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-25-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: 10/19/2020 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET90W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FW00 dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1931845/+attachment/5518813/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yannek 5763 F pulseaudio /dev/snd/controlC0: yannek 5763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-26 (204 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20HES0FW00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-25-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: 10/19/2020 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET90W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FW00 dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1931845/+attachment/5518811/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yannek 5763 F pulseaudio /dev/snd/controlC0: yannek 5763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-26 (204 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20HES0FW00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-25-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: 10/19/2020 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET90W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0FW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0FW00 dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931845] Re: Lots of cme when using 5.8.0 but not with 5.4.0
apport information ** Tags added: apport-collected focal ** Description changed: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [0.627089] mce: [Hardware Error]: TSC c619c16f1 ADDR 4414b2940 MISC 306485 Jun 14 10:57:50 monster kernel: [0.627090] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1623661045 SOCKET 0 APIC 2 microcode de Using rasdaemon and the fixed ras-mc-ctl script from upstream this got elaborated to $ ras-mc-ctl --errors --snip-- 188 2021-06-14 10:54:21 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc400e8000100151, addr=0x2146b9240, misc=0x00516485, walltime=0x60c7193d, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 189 2021-06-14 10:54:22 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc4002100151, addr=0x4344eee40, misc=0x02526485, walltime=0x60c7193e, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 190 2021-06-14 10:54:26 +0200 error: Instruction CACHE Level-1 Instruction-Fetch Error, mcg mcgstatus=0, mci Error_overflow Corrected_error Threshold based error status: yellow, mcgcap=0x0c08, status=0xcc40064000100151, addr=0x21447e7c0, misc=0x02526485, walltime=0x60c71942, cpu=0x0001, cpuid=0x000806e9, apicid=0x0002, bank=0x0003 --snap-- Is this just better reporting by the 5.8 kernel or is this a mismatch of kernel and hardware? I have no sudden application crashes or other indications for failing hardware. And a few hours of memtest86+ (not the broken version from the repo but a current one from a boot cd) report no errors. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.18 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: yannek 5763 F pulseaudio + /dev/snd/controlC0: yannek 5763 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: KDE + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-01-26 (204 days ago) + InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + MachineType: LENOVO 20HES0FW00 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 + RelatedPackageVersions: + linux-restricted-modules-5.11.0-25-generic N/A + linux-backports-modules-5.11.0-25-generic N/A + linux-firmware 1.187.16 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: focal + Uname: Linux 5.11.0-25-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: 10/19/2020 + dmi.bios.release: 1.65 + dmi.bios.vendor: LENOVO + dmi.bios.version: N1QET90W (1.65 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20HES0FW00 + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40697 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.ec.firmware.release: 1.35 + dmi.modalias: dmi:bvnLENOVO:bvrN1QET90W(1.65):bd10/19/2020:br1.65:efr1.35:svnLENOVO:pn20HES0FW00:pvrThinkPadT470:rvnLENOVO:rn20HES0FW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad T470 + dmi.product.name: 20HES0FW00 + dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 + dmi.product.version: ThinkPad T470 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1931845/+attachment/5518807/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931845 Title: Lots of cme when using 5.8.0 but not with 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: I'm using a 20.04.2 LTS install on a t470 thinkpad. After installing the linux-image-generic-hwe-20.04 the boot kernel switched to 5.8.0.55 when a lot of mce messages appeared in the kernel log, e.g. kern.log, e.g.: Jun 14 10:57:50 monster kernel: [0.627088] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: 8c40004000100151 Jun 14 10:57:50 monster kernel: [
[Kernel-packages] [Bug 1940461] [NEW] Impish update: v5.13.12 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.13.12 upstream stable release
from git://git.kernel.org/
lib: use PFN_PHYS() in devmem_is_allowed()
Revert "usb: dwc3: gadget: Use list_replace_init() before traversing lists"
iio: adc: ti-ads7950: Ensure CS is deasserted after reading channels
iio: adis: set GPIO reset pin direction
iio: humidity: hdc100x: Add margin to the conversion time
iio: adc: Fix incorrect exit of for-loop
ASoC: amd: Fix reference to PCM buffer address
ASoC: xilinx: Fix reference to PCM buffer address
ASoC: uniphier: Fix reference to PCM buffer address
ASoC: tlv320aic31xx: Fix jack detection after suspend
ASoC: kirkwood: Fix reference to PCM buffer address
ASoC: intel: atom: Fix reference to PCM buffer address
i2c: dev: zero out array used for i2c reads from userspace
cifs: Handle race conditions during rename
cifs: create sd context must be a multiple of 8
cifs: Call close synchronously during unlink/rename/lease break.
cifs: use the correct max-length for dentry_path_raw()
io_uring: drop ctx->uring_lock before flushing work item
io_uring: fix ctx-exit io_rsrc_put_work() deadlock
scsi: lpfc: Move initialization of phba->poll_list earlier to avoid crash
cgroup: rstat: fix A-A deadlock on 32bit around u64_stats_sync
seccomp: Fix setting loaded filter count during TSYNC
net: wwan: mhi_wwan_ctrl: Fix possible deadlock
net: ethernet: ti: cpsw: fix min eth packet size for non-switch use-cases
ARC: fp: set FPU_STATUS.FWE to enable FPU_STATUS update on context switch
ceph: reduce contention in ceph_check_delayed_caps()
pinctrl: k210: Fix k210_fpioa_probe()
ACPI: NFIT: Fix support for virtual SPA ranges
libnvdimm/region: Fix label activation vs errors
riscv: kexec: do not add '-mno-relax' flag if compiler doesn't support it
vmlinux.lds.h: Handle clang's module.{c,d}tor sections
drm/i915/gvt: Fix cached atomics setting for Windows VM
drm/i915/display: Fix the 12 BPC bits for PIPE_MISC reg
drm/amd/display: Remove invalid assert for ODM + MPC case
drm/amd/display: use GFP_ATOMIC in amdgpu_dm_irq_schedule_work
drm/amdgpu: Add preferred mode in modeset when freesync video mode's enabled.
drm/amdgpu: don't enable baco on boco platforms in runpm
drm/amdgpu: handle VCN instances when harvesting (v2)
ieee802154: hwsim: fix GPF in hwsim_set_edge_lqi
ieee802154: hwsim: fix GPF in hwsim_new_edge_nl
drm/mediatek: Fix cursor plane no update
pinctrl: mediatek: Fix fallback behavior for bias_set_combo
ASoC: cs42l42: Correct definition of ADC Volume control
ASoC: cs42l42: Don't allow SND_SOC_DAIFMT_LEFT_J
ASoC: cs42l42: Fix bclk calculation for mono
selftests/sgx: Fix Q1 and Q2 calculation in sigstruct.c
ASoC: SOF: Intel: Kconfig: fix SoundWire dependencies
ASoC: SOF: Intel: hda-ipc: fix reply size checking
ASoC: cs42l42: Fix inversion of ADC Notch Switch control
ASoC: cs42l42: Remove duplicate control for WNF filter frequency
netfilter: nf_conntrack_bridge: Fix memory leak when error
ASoC: cs42l42: PLL must be running when changing MCLK_SRC_SEL
ASoC: cs42l42: Fix LRCLK frame start edge
ASoC: cs42l42: Fix mono playback
net: dsa: mt7530: add the missing RxUnicast MIB counter
net: mvvp2: fix short frame size on s390
platform/x86: pcengines-apuv2: Add missing terminating entries to gpio-lookup
tables
perf/x86/intel: Apply mid ACK for small core
drm/amd/pm: Fix a memory leak in an error handling path in
'vangogh_tables_init()'
libbpf: Fix probe for BPF_PROG_TYPE_CGROUP_SOCKOPT
libbpf: Do not close un-owned FD 0 on errors
bpf: Fix integer overflow involving bucket_size
net: dsa: qca: ar9331: make proper initial port defaults
net: phy: micrel: Fix link detection on ksz87xx switch"
ppp: Fix generating ifname when empty IFLA_IFNAME is specified
io_uring: clear TIF_NOTIFY_SIGNAL when running task work
net/smc: fix wait on already cleared link
net/smc: Correct smc link connection counter in case of smc client
net: sched: act_mirred: Reset ct info when mirror/redirect skb
ice: Prevent probing virtual functions
ice: Stop processing VF messages during teardown
ice: don't remove netdev->dev_addr from uc sync list
iavf: Set RSS LUT and key in reset handle path
psample: Add a fwd declaration for skbuff
bareudp: Fix invalid read beyond skb's linear data
io-wq: fix bug of creating io-wokers unconditionally
io-wq: fix IO_WORKER_F_FIXED issue in create_io_worker()
net/mlx5: Don't skip subfunction cleanup in case of error in module init
net/mlx5: DR, Add fail on error check on decap
net/mlx5e: Avoid creating tunnel headers for local route
net/mlx5e: Destroy page pool after XDP SQ to fix
[Kernel-packages] [Bug 1935034] Re: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04
I just updated the files in link in comment #7. Please test with the updated test kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935034 Title: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04 Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: New Status in linux source package in Hirsute: New Status in linux source package in Impish: Confirmed Bug description: This is a feature request to update the mpt3sas driver to latest version in upstream 38.100.00.00 in Ubuntu 21.10 and Ubuntu 20.04. This will allow users to use fixes and enhancements that landed upstream in 5.14. For this reason, Broadcom and Dell have requested to pull these patches to update the mpt3sas driver to the current upstream version. I could see both Ubuntu 21.10 and 20.04 HWE has mpt3sas driver v36.100.00.00, following are the commit ID's to update to 38.100.00.00 8b3c803529 scsi: mpt3sas: Signedness bug in _base_get_diag_triggers() 39718fe7ad scsi: mpt3sas: Fix spelling mistake in Kconfig "compatiblity" -> "compatibility" bfb3f00c06 scsi: mpt3sas: Simplify bool comparison d309ae0732 scsi: mpt3sas: Fix ReplyPostFree pool allocation 664f0dce20 scsi: mpt3sas: Add support for shared host tagset for CPU hotplug 688c1a0a13 scsi: mpt3sas: Additional diagnostic buffer query interface 446b5f3d3f scsi: mpt3sas: Update driver version to 37.100.00.00 8278807abd scsi: core: Add scsi_device_busy() wrapper 020b0f0a31 scsi: core: Replace sdev->device_busy with sbitmap e015e0ded1 scsi: mpt3sas: Fix misspelling of _base_put_smid_default_atomic() 2111ba8781 scsi: mpt3sas: Move a little data from the stack onto the heap cf9e575e62 scsi: mpt3sas: Fix a bunch of potential naming doc-rot 54cb88dc30 scsi: mpt3sas: Fix a couple of misdocumented functions/params 782a1ab33f scsi: mpt3sas: Fix some kernel-doc misnaming issues a50bd64616 scsi: mpt3sas: Do not use GFP_KERNEL in atomic context a1c4d77413 scsi: mpt3sas: Replace unnecessary dynamic allocation with a static one d6adc251dd scsi: mpt3sas: Force PCIe scatterlist allocations to be within same 4 GB region 7dd847dae1 scsi: mpt3sas: Force chain buffer allocations to be within same 4 GB region 970ac2bb70 scsi: mpt3sas: Force sense buffer allocations to be within same 4 GB region 58501fd937 scsi: mpt3sas: Force reply buffer allocations to be within same 4 GB region 2e4e858732 scsi: mpt3sas: Force reply post buffer allocations to be within same 4 GB region c569de899b scsi: mpt3sas: Force reply post array allocations to be within same 4 GB region 37067b9793 scsi: mpt3sas: Update driver version to 37.101.00.00 a8d548b0b3 scsi: mpt3sas: Fix a few kernel-doc issues 3401ecf7fc scsi: mpt3sas: Fix error return code of mpt3sas_base_attach() 206a3afa94 scsi: mpt3sas: Fix a typo 4c51f95696 scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES c0629d70ca scsi: mpt3sas: Fix endianness for ActiveCablePowerRequirement 3c8604691d scsi: mpt3sas: Block PCI config access from userspace during reset 16660db3fc scsi: mpt3sas: Fix out-of-bounds warnings in _ctl_addnl_diag_query 3ad0b1da0d scsi: mpt3sas: Fix two kernel-doc headers 2910a4a9e9 scsi: mpt3sas: Documentation cleanup e2fac6c44a scsi: mpt3sas: Fix deadlock while cancelling the running firmware event 19a622c39a scsi: mpt3sas: Handle firmware faults during first half of IOC init a0815c45c8 scsi: mpt3sas: Handle firmware faults during second half of IOC init f2b1e9c6f8 scsi: core: Introduce scsi_build_sense() 84a84cc6af scsi: mpt3sas: Fix fall-through warnings for Clang cf750be8e6 scsi: mpt3sas: Fix Coverity reported issue d6c2ce435f scsi: mpt3sas: Fix error return value in _scsih_expander_add() Note: We have already posted patch to update driver version to 38.100.00.00 Other patches are already available in upstream . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935034/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940449] [NEW] package linux-image-5.11.0-27-generic (not installed) failed to install/upgrade: installed linux-image-5.11.0-27-generic package pre-removal script subprocess ret
Public bug reported: Whenever I (or some other process) try to remove kernel 5.11, the process fails. This matters for me because 5.11 introduces a regression that I can only mitigate by running an older kernel (like 5.8 or 5.4). ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic (not installed) ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 18 09:32:40 2021 ErrorMessage: installed linux-image-5.11.0-27-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-signed-hwe-5.11 Title: package linux-image-5.11.0-27-generic (not installed) failed to install/upgrade: installed linux-image-5.11.0-27-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1940449 Title: package linux-image-5.11.0-27-generic (not installed) failed to install/upgrade: installed linux-image-5.11.0-27-generic package pre- removal script subprocess returned error exit status 1 Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Whenever I (or some other process) try to remove kernel 5.11, the process fails. This matters for me because 5.11 introduces a regression that I can only mitigate by running an older kernel (like 5.8 or 5.4). ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic (not installed) ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 18 09:32:40 2021 ErrorMessage: installed linux-image-5.11.0-27-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-signed-hwe-5.11 Title: package linux-image-5.11.0-27-generic (not installed) failed to install/upgrade: installed linux-image-5.11.0-27-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-5.11/+bug/1940449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940448] [NEW] CT state not reset when packet redirected to different port
Public bug reported: * Explain the bug(s) CT state not reset when packet redirected to different port, thus making it possible to match rules with wrong ct state on the other port. * brief explanation of fixes Reset ct state when redirecting to a different port. The sauce fix being reverted and should apply the upstream fix to catch all cases correctly. * How to test tc qdisc add dev veth0 clsact # The same with "action mirred egress mirror dev veth1" or "action mirred ingress redirect dev veth1" tc filter add dev veth0 egress chain 1 protocol ip flower ct_state +trk action mirred ingress mirror dev veth1 tc filter add dev veth0 egress chain 0 protocol ip flower ct_state -inv action ct commit action goto chain 1 tc qdisc add dev veth1 clsact tc filter add dev veth1 ingress chain 0 protocol ip flower ct_state +trk action drop ping & tc -s filter show dev veth1 ingress With command 'tc -s filter show', we can find the pkts were dropped on veth1. * What it could break. Wrong matching. Traffic failure when redirecting to different ports and there are more rules to match on the other port. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1940448 Title: CT state not reset when packet redirected to different port Status in linux-bluefield package in Ubuntu: New Bug description: * Explain the bug(s) CT state not reset when packet redirected to different port, thus making it possible to match rules with wrong ct state on the other port. * brief explanation of fixes Reset ct state when redirecting to a different port. The sauce fix being reverted and should apply the upstream fix to catch all cases correctly. * How to test tc qdisc add dev veth0 clsact # The same with "action mirred egress mirror dev veth1" or "action mirred ingress redirect dev veth1" tc filter add dev veth0 egress chain 1 protocol ip flower ct_state +trk action mirred ingress mirror dev veth1 tc filter add dev veth0 egress chain 0 protocol ip flower ct_state -inv action ct commit action goto chain 1 tc qdisc add dev veth1 clsact tc filter add dev veth1 ingress chain 0 protocol ip flower ct_state +trk action drop ping & tc -s filter show dev veth1 ingress With command 'tc -s filter show', we can find the pkts were dropped on veth1. * What it could break. Wrong matching. Traffic failure when redirecting to different ports and there are more rules to match on the other port. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1940448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930719] Re: Replace AMD nvme workaround from oem-5.10 with upstream version
** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux (Ubuntu Impish) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1930719 Title: Replace AMD nvme workaround from oem-5.10 with upstream version Status in amd: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: The workaround carried in linux-oem-5.10 to support suspend to idle on AMD platforms: https://kernel.ubuntu.com/git/kernel-ppa/mirror/ubuntu- oem-5.10-focal.git/commit/drivers/nvme?h=oem-5.10-next=2d37b035a0f469d40ab0322b0f9dd7f2d43bc9b8 Should be replaced with what's going upstream for 5.14: http://git.infradead.org/nvme.git/commit/e21e0243e7b0f1c2a21d21f4d115f7b37175772a And please also apply it to oem-5.13. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1930719/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934809] Re: Backport support for AMD SMU statistics
** Changed in: linux (Ubuntu Impish) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1934809 Title: Backport support for AMD SMU statistics Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] AMD RN and CZN SOC can collect extra debugging data for s0i3. This information is useful for finding problems with IP blocks not going into correct states. [Fix] The following patch series adds support for these stats and will be included in 5.14. https://patchwork.kernel.org/project/platform-driver-x86/patch/20210629084803.248498-2-shyam-sundar@amd.com/ [Test] Check for extra debugfs files on amd platform. Verify that s0i3 shows successful enter (counter increases to non-zero). [Where problems could occur] The code is only used on amd platforms in s2idle. It would be specific to those platforms and cases (where it is adding support for debugging). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939743] Re: No Touchpad on TravelMate-P2 laptop
It's weird there's a mouse detected but not recognized as an input device. Can you show me the result of the command `ls /sys/bus/acpi/devices/`? Since there's a PS2M(ps/2 touchpad) device and a TPD0 (i2c interface) device in the ACPI dsdt file which should represent the Touchpad. I need to know which one is recognized by ACPI and I can tell the touchpad is from Elantech or Synaptic. The we can dig further for what really happened. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939743 Title: No Touchpad on TravelMate-P2 laptop Status in linux package in Ubuntu: Confirmed Bug description: On the TravelMate P215-53 V1.10 by Acer when running Ubuntu, the trackpad is entirely non-functional and does not appear in the /proc/bus/input/devices list. A wired usb mouse works perfectly, but there does not seem to be a tweak that enables the trackpad to be seen by the kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 12 14:30:39 2021 InstallationDate: Installed on 2020-12-09 (245 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer TravelMate P215-53 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=/dev/nvme0n1p2 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.15 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 12/17/2020 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BassDrum_TL dmi.board.vendor: TGL dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.10:bd12/17/2020:svnAcer:pnTravelMateP215-53:pvrV1.10:rvnTGL:rnBassDrum_TL:rvrV1.10:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: TravelMate P2 dmi.product.name: TravelMate P215-53 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
