[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
Similar to @lproven , I have over half a dozen thinkpads (T/W520/530, W540/541), all of which depend on 390, and for the 6x kernels, nouveau isn't working. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released 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-430 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-455 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-460 package in Ubuntu: Invalid Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028165] Re: nvidia-dkms-* FTBS with linux 6.5
I'm having to stay with 22.04, with a prayer that I won't be stuck with my over half dozen thinpads of the 520/530/540 generation will no longer be able to run Ubuntu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/2028165 Title: nvidia-dkms-* FTBS with linux 6.5 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-450-server source package in Jammy: Invalid Status in nvidia-graphics-drivers-470 source package in Jammy: Invalid Status in nvidia-graphics-drivers-470-server source package in Jammy: Invalid Status in nvidia-graphics-drivers-525 source package in Jammy: Invalid Status in nvidia-graphics-drivers-525-server source package in Jammy: Invalid Status in nvidia-graphics-drivers-390 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Mantic: Fix Released Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Mantic: Fix Released Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21, from /var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function ‘NV_GET_USER_PAGES_REMOTE’: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] 164 |return get_user_pages_remote(tsk, mm, start, nr_pages, flags, | ^~~ | | | struct task_struct * ... [Fix] Apply the attached fix. [How to test] Install (and build) the patched packet. [Regression potential] The fix is composed of two patches: 1) the first patch simply garbage collect a reference to a function that was never used but that had the API changed in Linux 6.5 - so, it's a trivial change. 2) the second patch actually reimplement part of the vma scanning that was removed in __get_user_pages_locked() in upstream commit b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas array from internal GUP functions" - here is where most likely any regression could be found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962572] Re: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y
As reported above, I tried deleting ../efivars/dump*, but even after a reboot, the ../vars/dump* directories remain. Worse, the ../efivars/dump* files returned. I repeated the deletion of ../efivars/dump* and again rebooted. On second reboot, those files are gone, along with the ../vars/dump* directories. If I had not removed tlp and acpi-call-dkms after that first boot, then rebooting may well have filled the NVRAM and bricked the machine! -- 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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: Confirmed Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1962572/+attachment/5564456/+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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1962572/+attachment/5564452/+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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1962572/+attachment/5564454/+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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1962572/+attachment/5564460/+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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1962572/+attachment/5564455/+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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1962572/+attachment/5564458/+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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1962572/+attachment/5564457/+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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1962572/+attachment/5564453/+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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] Re: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y
Is there a workaround right now for me to clear out the NVRAM dump files? -- 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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1962572/+attachment/5564459/+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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1962572/+attachment/5564448/+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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1962572/+attachment/5564445/+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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1962572/+attachment/5564446/+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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1962572/+attachment/5564449/+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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1962572/+attachment/5564450/+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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1962572/+attachment/5564451/+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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1962572/+attachment/5564447/+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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1962572/+attachment/556/+files/AudioDevicesInUse.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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1962572/+attachment/5564443/+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/1962572 Title: Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y Status in linux package in Ubuntu: New Bug description: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962572/+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 1962572] [NEW] Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y
Public bug reported: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the next boot. Some Thinkpads of the W530 vintage do not have a way to clear out that storage at post time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (389 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no intel_iommu=on quiet ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm btrbk cdrom debian-tor dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2436: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected focal ** Summary changed: - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y - Impossible to Delete UEFI Dump Files + Impossible to Delete UEFI Dump Files - CONFIG_EFIVAR_FS & CONFIG_EFI_VARS both =y ** Tags added: apport-collected focal ** Description changed: See this bug for where this issue appears: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+login I am seeing in the Arch UEFI documentation: UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI runtime variables using tools like /usr/bin/efibootmgr. The configuration option below has been added in kernel 3.10 and later. CONFIG_EFIVAR_FS=y UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled. CONFIG_EFI_VARS=n In Ubuntu 20.04, both of these are set =y. This appears to be the cause of my inability to delete /sys/firmware/efi/efivars/dump* variables. These variables are mirrored as directories of the same name in /sys/firmware/efi/vars/dump*. If I delete the files ../efivars/dump*, they reappear on reboot. - Systems have been bricked this way, when people thought they had cleared - out the variable storage, but had not, and then found it full on the - next boot. Some Thinkpads of the W530 vintage do not have a way to - clear out that storage at post time. + Systems have been bricked this way, when people thought they had cleared out the variable storage, but had not, and then found it full on the nex
[Kernel-packages] [Bug 1949247] Re: kernel: BUG: unable to handle page fault for address (5.4.0-89)
** Summary changed: - kernel: BUG: unable to handle page fault for address + kernel: BUG: unable to handle page fault for address (5.4.0-89) -- 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/1949247 Title: kernel: BUG: unable to handle page fault for address (5.4.0-89) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.3, kernel 5.4.0-89. - -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000
[Kernel-packages] [Bug 1949247] Re: kernel: BUG: unable to handle page fault for address
** Description changed: + Ubuntu 20.04.3, kernel 5.4.0-89. + - -- Support: http://www.ubuntu.com/support - -- + -- -- A start job for unit motd-news.service has finished successfully. - -- + -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: lightdm5230 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: lightdm5230 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-06
[Kernel-packages] [Bug 1908912] Re: "BUG: unable to handle page fault for address" 5.4.0-58-generic #64~18.04.1-Ubuntu
I'm on 20.04.3, kernel 5.4.0-89, with a similar problem: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949247 -- 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/1908912 Title: "BUG: unable to handle page fault for address" 5.4.0-58-generic #64~18.04.1-Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: mezimm00@m5:~$ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 mezimm00@m5:~$ apt-cache policy linux-image-5.4.0-58-generic linux-image-5.4.0-58-generic: Installed: 5.4.0-58.64~18.04.1 Candidate: 5.4.0-58.64~18.04.1 Version table: *** 5.4.0-58.64~18.04.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status Dec 20 08:59:56 m5 kernel: [144210.719252] BUG: unable to handle page fault for address: 0007fb39be0e Dec 20 08:59:56 m5 kernel: [144210.719320] #PF: supervisor read access in kernel mode Dec 20 08:59:56 m5 kernel: [144210.719358] #PF: error_code(0x) - not-present page Dec 20 08:59:56 m5 kernel: [144210.719395] PGD 0 P4D 0 Dec 20 08:59:56 m5 kernel: [144210.719420] Oops: [#1] SMP PTI Dec 20 08:59:56 m5 kernel: [144210.719449] CPU: 139 PID: 3081629 Comm: lsof Not tainted 5.4.0-58-generic #64~18.04.1-Ubuntu Dec 20 08:59:56 m5 kernel: [144210.719505] Hardware name: Dell Inc. PowerEdge R930/0T55KM, BIOS 2.8.1 01/02/2020 Dec 20 08:59:56 m5 kernel: [144210.719563] RIP: 0010:lock_get_status+0x221/0x380 Dec 20 08:59:56 m5 kernel: [144210.719600] Code: fd 7b de 91 4c 89 e7 e8 fd 30 fb ff 4d 85 ed 0f 84 de 00 00 00 49 8b 45 28 4d 8b 4d 40 44 89 f2 48 c7 c6 91 52 d7 91 4c 89 e7 <44> 8b 40 10 44 89 c1 41 81 e0 ff ff 0f 00 c1 e9 14 e8 c9 30 fb ff Dec 20 08:59:56 m5 kernel: [144210.719717] RSP: 0018:b731373efd98 EFLAGS: 00010286 Dec 20 08:59:56 m5 kernel: [144210.719755] RAX: 0007fb39bdfe RBX: 939c33a080d8 RCX: 0001 Dec 20 08:59:56 m5 kernel: [144210.719803] RDX: 0003b0a9 RSI: 91d75291 RDI: 938e2d796800 Dec 20 08:59:56 m5 kernel: [144210.719851] RBP: b731373efdc8 R08: 1000 R09: 93565c5a23b8 Dec 20 08:59:56 m5 kernel: [144210.719899] R10: b731373efe50 R11: 9394905b51d5 R12: 938e2d796800 Dec 20 08:59:56 m5 kernel: [144210.719948] R13: 934002945d90 R14: 0003b0a9 R15: 9390ce8a38a0 Dec 20 08:59:56 m5 kernel: [144210.719997] FS: 7ff9bcbb4040() GS:939c3fa8() knlGS: Dec 20 08:59:56 m5 kernel: [144210.720050] CS: 0010 DS: ES: CR0: 80050033 Dec 20 08:59:56 m5 kernel: [144210.720090] CR2: 0007fb39be0e CR3: 00e75d31a002 CR4: 001606e0 Dec 20 08:59:56 m5 kernel: [144210.720138] DR0: DR1: DR2: Dec 20 08:59:56 m5 kernel: [144210.720186] DR3: DR6: fffe0ff0 DR7: 0400 Dec 20 08:59:56 m5 kernel: [144210.720233] Call Trace: Dec 20 08:59:56 m5 kernel: [144210.720262] locks_show+0x83/0xc0 Dec 20 08:59:56 m5 kernel: [144210.720297] seq_read+0x2a4/0x420 Dec 20 08:59:56 m5 kernel: [144210.720330] proc_reg_read+0x3e/0x60 Dec 20 08:59:56 m5 kernel: [144210.720361] __vfs_read+0x1b/0x40 Dec 20 08:59:56 m5 kernel: [144210.721947] vfs_read+0x8e/0x130 Dec 20 08:59:56 m5 kernel: [144210.723479] ksys_read+0xa7/0xe0 Dec 20 08:59:56 m5 kernel: [144210.725009] __x64_sys_read+0x1a/0x20 Dec 20 08:59:56 m5 kernel: [144210.726545] do_syscall_64+0x57/0x190 Dec 20 08:59:56 m5 kernel: [144210.728064] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Dec 20 08:59:56 m5 kernel: [144210.729580] RIP: 0033:0x7ff9bc48e151 Dec 20 08:59:56 m5 kernel: [144210.731081] Code: fe ff ff 48 8d 3d 3f 9b 0a 00 48 83 ec 08 e8 66 4a 02 00 66 0f 1f 44 00 00 48 8d 05 91 08 2e 00 8b 00 85 c0 75 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 57 f3 c3 0f 1f 44 00 00 41 54 55 49 89 d4 53 Dec 20 08:59:56 m5 kernel: [144210.734225] RSP: 002b:7ffc9e915348 EFLAGS: 0246 ORIG_RAX: Dec 20 08:59:56 m5 kernel: [144210.735809] RAX: ffda RBX: 55f16fee7260 RCX: 7ff9bc48e151 Dec 20 08:59:56 m5 kernel: [144210.737396] RDX: 1000 RSI: 55f16fee8d80 RDI: 0003 Dec 20 08:59:56 m5 kernel: [144210.738947] RBP: 0d68 R08: 0001 R09: 55f16fee7340 Dec 20 08:59:56 m5 kernel: [144210.740456] R10: 7ff9bcbb4040 R11: 0246 R12: 7ff9bc765760 Dec 20 08:59:56 m5 kernel: [144210.741923] R13: 7ff9bc7662a0 R14: 55f16fee7260 R15: 0fff Dec 20 08:59:56 m5 kernel: [144210.743353] Modules linked in: ip6table_filter ip6_tables tcp_diag udp_diag inet_diag xt_REDIRECT ip_vs_rr xt_ipvs ip_vs xt
[Kernel-packages] [Bug 1949247] Re: kernel: BUG: unable to handle page fault for address
I just stumbled on what may be a similar problem, here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908912 -- 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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: Confirmed Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 A
[Kernel-packages] [Bug 1949247] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537113/+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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Archit
[Kernel-packages] [Bug 1949247] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537100/+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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Archit
[Kernel-packages] [Bug 1949247] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537110/+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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21
[Kernel-packages] [Bug 1949247] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537112/+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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Ar
[Kernel-packages] [Bug 1949247] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537111/+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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architectur
[Kernel-packages] [Bug 1949247] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537108/+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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0
[Kernel-packages] [Bug 1949247] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537104/+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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture:
[Kernel-packages] [Bug 1949247] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537102/+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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21
[Kernel-packages] [Bug 1949247] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537107/+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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21
[Kernel-packages] [Bug 1949247] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537105/+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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Archit
[Kernel-packages] [Bug 1949247] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537106/+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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architec
[Kernel-packages] [Bug 1949247] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537103/+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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Archit
[Kernel-packages] [Bug 1949247] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537101/+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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: a
[Kernel-packages] [Bug 1949247] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537109/+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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27
[Kernel-packages] [Bug 1949247] [NEW] kernel: BUG: unable to handle page fault for address
Public bug reported: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5230 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-06-02 (1245 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 003: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation
[Kernel-packages] [Bug 1924624] Re: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable
Perhaps this is related? That's my report, and I got rid of it by using the intel_iommu=on kernel parameter, but that introduced another error. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126 -- 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/1924624 Title: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe-5.8 package in Ubuntu: Confirmed Bug description: After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was suddenly extremely glitchy. Icons from the desktop flash through the browser, windows top bar gets distorted, all sort of glitches appear, parts of characters are missing in terminal, scrolling is inconsistent and the whole desktop becomes unusable. Under wayland the graphics are a bit more stable, but lots of glitches appear anyway, video reproduction in browser is stuttering and wobbly. Booting with previous kernel 5.8.0-48 seems to fix the issues. 5.8.0-50 is broken as well. this is the result of 'sudo lshw -c video' on my hp Elitebook 8470: *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:33 memory:d400-d43f memory:c000-cfff ioport:4000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+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 1925126] Re: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50
Discussion over at Arch led me to try adding the kernel parameter intel_iommu=on. https://bbs.archlinux.org/viewtopic.php?id=256520 That appears to have solved the problem (I hope I'm not speaking too soon), but now (as discussed in another Arch forum post) there's a new one: https://bbs.archlinux.org/viewtopic.php?id=228604 I also understand this causes power use to go up. $ dmesg -T | grep -i i915 [Mon Apr 19 23:57:41 2021] i915 :00:02.0: [drm] VT-d active for gfx access [Mon Apr 19 23:57:41 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 23:57:41 2021] i915 :00:02.0: [drm] DMAR active, disabling use of stolen memory [Mon Apr 19 23:57:41 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 23:57:41 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 23:57:41 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 23:57:42 2021] i915 :00:02.0: [drm] *ERROR* uncleared fifo underrun on pipe A [Mon Apr 19 23:57:42 2021] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun [Mon Apr 19 23:57:42 2021] i915 :00:02.0: [drm] *ERROR* uncleared pch fifo underrun on pch transcoder A [Mon Apr 19 23:57:42 2021] i915 :00:02.0: [drm] *ERROR* PCH transcoder A FIFO underrun [Mon Apr 19 23:57:42 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 23:59:47 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) -- 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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: com
[Kernel-packages] [Bug 1925126] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490019/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1
[Kernel-packages] [Bug 1925126] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490020/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/19251
[Kernel-packages] [Bug 1925126] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490013/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126
[Kernel-packages] [Bug 1925126] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490017/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug
[Kernel-packages] [Bug 1925126] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490012/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126
[Kernel-packages] [Bug 1925126] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490011/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+sub
[Kernel-packages] [Bug 1925126] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490016/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linu
[Kernel-packages] [Bug 1925126] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490018/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+s
[Kernel-packages] [Bug 1925126] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490014/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug
[Kernel-packages] [Bug 1925126] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490015/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+sou
[Kernel-packages] [Bug 1925126] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490010/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/19251
[Kernel-packages] [Bug 1925126] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490009/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+sub
[Kernel-packages] [Bug 1925126] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490005/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/19251
[Kernel-packages] [Bug 1925126] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490008/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/19251
[Kernel-packages] [Bug 1925126] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490007/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+b
[Kernel-packages] [Bug 1925126] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490006/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subsc
[Kernel-packages] [Bug 1925126] [NEW] Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50
Public bug reported: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome- terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected focal ** Tags added: apport-collected focal ** Description changed: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome- terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.
[Kernel-packages] [Bug 1830197] Re: e1000e driver - uploading slowed to a crawl.
** Package changed: linux (Ubuntu) => linux-hwe (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/1830197 Title: e1000e driver - uploading slowed to a crawl. Status in linux-hwe package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c InstallationDate: Installed on 2018-08-31 (264 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4284A94 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-50-generic root=UUID=36d8a469-5f40-46de-887d-90fbd0b4aa3b ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-50.54-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284A94 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn4284A94:pvrThinkPadW520:rvnLENOVO:rn4284A94:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W520 dmi.product.name: 4284A94 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+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 1830197] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1830197/+attachment/5265985/+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/1830197 Title: e1000e driver - uploading slowed to a crawl. Status in linux-hwe package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c InstallationDate: Installed on 2018-08-31 (264 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4284A94 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-50-generic root=UUID=36d8a469-5f40-46de-887d-90fbd0b4aa3b ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-50.54-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284A94 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn4284A94:pvrThinkPadW520:rvnLENOVO:rn4284A94:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W520 dmi.product.name: 4284A94 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+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 1830197] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1830197/+attachment/5265979/+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/1830197 Title: e1000e driver - uploading slowed to a crawl. Status in linux-hwe package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c InstallationDate: Installed on 2018-08-31 (264 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4284A94 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-50-generic root=UUID=36d8a469-5f40-46de-887d-90fbd0b4aa3b ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-50.54-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284A94 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn4284A94:pvrThinkPadW520:rvnLENOVO:rn4284A94:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W520 dmi.product.name: 4284A94 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+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 1830197] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1830197/+attachment/5265986/+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/1830197 Title: e1000e driver - uploading slowed to a crawl. Status in linux-hwe package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c InstallationDate: Installed on 2018-08-31 (264 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4284A94 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-50-generic root=UUID=36d8a469-5f40-46de-887d-90fbd0b4aa3b ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-50.54-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284A94 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn4284A94:pvrThinkPadW520:rvnLENOVO:rn4284A94:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W520 dmi.product.name: 4284A94 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+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 1830197] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1830197/+attachment/5265982/+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/1830197 Title: e1000e driver - uploading slowed to a crawl. Status in linux-hwe package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c InstallationDate: Installed on 2018-08-31 (264 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4284A94 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-50-generic root=UUID=36d8a469-5f40-46de-887d-90fbd0b4aa3b ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-50.54-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284A94 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn4284A94:pvrThinkPadW520:rvnLENOVO:rn4284A94:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W520 dmi.product.name: 4284A94 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+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 1830197] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1830197/+attachment/5265977/+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/1830197 Title: e1000e driver - uploading slowed to a crawl. Status in linux-hwe package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c InstallationDate: Installed on 2018-08-31 (264 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4284A94 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-50-generic root=UUID=36d8a469-5f40-46de-887d-90fbd0b4aa3b ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-50.54-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284A94 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn4284A94:pvrThinkPadW520:rvnLENOVO:rn4284A94:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W520 dmi.product.name: 4284A94 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+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 1830197] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1830197/+attachment/5265975/+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/1830197 Title: e1000e driver - uploading slowed to a crawl. Status in linux-hwe package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c InstallationDate: Installed on 2018-08-31 (264 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4284A94 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-50-generic root=UUID=36d8a469-5f40-46de-887d-90fbd0b4aa3b ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-50.54-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284A94 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn4284A94:pvrThinkPadW520:rvnLENOVO:rn4284A94:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W520 dmi.product.name: 4284A94 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+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 1830197] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1830197/+attachment/5265981/+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/1830197 Title: e1000e driver - uploading slowed to a crawl. Status in linux-hwe package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c InstallationDate: Installed on 2018-08-31 (264 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4284A94 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-50-generic root=UUID=36d8a469-5f40-46de-887d-90fbd0b4aa3b ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-50.54-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284A94 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn4284A94:pvrThinkPadW520:rvnLENOVO:rn4284A94:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W520 dmi.product.name: 4284A94 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+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 1830197] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1830197/+attachment/5265983/+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/1830197 Title: e1000e driver - uploading slowed to a crawl. Status in linux-hwe package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c InstallationDate: Installed on 2018-08-31 (264 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4284A94 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-50-generic root=UUID=36d8a469-5f40-46de-887d-90fbd0b4aa3b ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-50.54-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284A94 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn4284A94:pvrThinkPadW520:rvnLENOVO:rn4284A94:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W520 dmi.product.name: 4284A94 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+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 1830197] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1830197/+attachment/5265984/+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/1830197 Title: e1000e driver - uploading slowed to a crawl. Status in linux-hwe package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c InstallationDate: Installed on 2018-08-31 (264 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4284A94 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-50-generic root=UUID=36d8a469-5f40-46de-887d-90fbd0b4aa3b ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-50.54-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284A94 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn4284A94:pvrThinkPadW520:rvnLENOVO:rn4284A94:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W520 dmi.product.name: 4284A94 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+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 1830197] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1830197/+attachment/5265980/+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/1830197 Title: e1000e driver - uploading slowed to a crawl. Status in linux-hwe package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c InstallationDate: Installed on 2018-08-31 (264 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4284A94 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-50-generic root=UUID=36d8a469-5f40-46de-887d-90fbd0b4aa3b ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-50.54-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284A94 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn4284A94:pvrThinkPadW520:rvnLENOVO:rn4284A94:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W520 dmi.product.name: 4284A94 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+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 1830197] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1830197/+attachment/5265978/+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/1830197 Title: e1000e driver - uploading slowed to a crawl. Status in linux-hwe package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c InstallationDate: Installed on 2018-08-31 (264 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4284A94 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-50-generic root=UUID=36d8a469-5f40-46de-887d-90fbd0b4aa3b ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-50.54-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284A94 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn4284A94:pvrThinkPadW520:rvnLENOVO:rn4284A94:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W520 dmi.product.name: 4284A94 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+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 1830197] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1830197/+attachment/5265971/+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/1830197 Title: e1000e driver - uploading slowed to a crawl. Status in linux-hwe package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c InstallationDate: Installed on 2018-08-31 (264 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4284A94 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-50-generic root=UUID=36d8a469-5f40-46de-887d-90fbd0b4aa3b ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-50.54-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284A94 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn4284A94:pvrThinkPadW520:rvnLENOVO:rn4284A94:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W520 dmi.product.name: 4284A94 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+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 1830197] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1830197/+attachment/5265974/+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/1830197 Title: e1000e driver - uploading slowed to a crawl. Status in linux-hwe package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c InstallationDate: Installed on 2018-08-31 (264 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4284A94 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-50-generic root=UUID=36d8a469-5f40-46de-887d-90fbd0b4aa3b ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-50.54-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284A94 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn4284A94:pvrThinkPadW520:rvnLENOVO:rn4284A94:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W520 dmi.product.name: 4284A94 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+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 1830197] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1830197/+attachment/5265973/+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/1830197 Title: e1000e driver - uploading slowed to a crawl. Status in linux-hwe package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c InstallationDate: Installed on 2018-08-31 (264 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4284A94 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-50-generic root=UUID=36d8a469-5f40-46de-887d-90fbd0b4aa3b ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-50.54-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284A94 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn4284A94:pvrThinkPadW520:rvnLENOVO:rn4284A94:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W520 dmi.product.name: 4284A94 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+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 1830197] Re: e1000e driver - uploading slowed to a crawl.
apport information ** Tags added: apport-collected bionic ** Description changed: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.6 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: dev2052 F pulseaudio + CurrentDesktop: MATE + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c + InstallationDate: Installed on 2018-08-31 (264 days ago) + InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + MachineType: LENOVO 4284A94 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-50-generic root=UUID=36d8a469-5f40-46de-887d-90fbd0b4aa3b ro rootflags=subvol=@ quiet splash vt.handoff=1 + ProcVersionSignature: hostname 4.15.0-50.54-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-50-generic N/A + linux-backports-modules-4.15.0-50-generic N/A + linux-firmware 1.173.6 + Tags: bionic + Uname: Linux 4.15.0-50-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/20/2016 + dmi.bios.vendor: LENOVO + dmi.bios.version: 8BET63WW (1.43 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 4284A94 + dmi.board.vendor: LENOVO + dmi.board.version: Not Available + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Not Available + dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn4284A94:pvrThinkPadW520:rvnLENOVO:rn4284A94:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: + dmi.product.family: ThinkPad W520 + dmi.product.name: 4284A94 + dmi.product.version: ThinkPad W520 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1830197/+attachment/5265970/+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/1830197 Title: e1000e driver - uploading slowed to a crawl. Status in linux-hwe package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 1
[Kernel-packages] [Bug 1830197] Re: e1000e driver - uploading slowed to a crawl.
* The Thinkpad T530 has the same intel network hardware. (And correction, it gives me 1Gb down and ~ 0.5Gb up.) -- 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/1830197 Title: e1000e driver - uploading slowed to a crawl. Status in linux package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c InstallationDate: Installed on 2018-08-31 (264 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4284A94 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-50-generic root=UUID=36d8a469-5f40-46de-887d-90fbd0b4aa3b ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-50.54-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284A94 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn4284A94:pvrThinkPadW520:rvnLENOVO:rn4284A94:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W520 dmi.product.name: 4284A94 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830197/+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 1830197] [NEW] e1000e driver - uploading slowed to a crawl.
Public bug reported: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c InstallationDate: Installed on 2018-08-31 (264 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4284A94 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-50-generic root=UUID=36d8a469-5f40-46de-887d-90fbd0b4aa3b ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-50.54-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284A94 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn4284A94:pvrThinkPadW520:rvnLENOVO:rn4284A94:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W520 dmi.product.name: 4284A94 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-collected bionic driver e1000 intel -- 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/1830197 Title: e1000e driver - uploading slowed to a crawl. Status in linux package in Ubuntu: Incomplete Bug description: I have a Thinkpad T520 and a W520, both with the same ethernet device, Intel 82579LM. Running under Windows, speedtest reports ~1Gb up & down, so the hardware is good. Under Ubuntu 18.04, kernel 4.15.0-50, I get ~1Gb down but only ~4Mb (!) up. e1000e is version 3.2.6-K and e1000 is version 7.3.21-k8-NAPI. Note that I also have a Thinkpad T530 with those same versions of driver, and it gives me ~1Gb in both directions. I have tried a number of attempted solutions which have had no effect: ethtool -K eth0 gso off gro off tso off ethtool -K eth0 tx off rx off ethtool -G eth0 tx 256 rx 256 ethtool -G eth0 tx 8096 rx 8096 Turning off ASPM in BIOS and via the kernel parameter pcie_aspm=off Note that I also have a Dell Optiplex 980 with an 82578DM running CentOS wich had the same problem (4Mb up). Turning off ASPM in BIOS corrected the issue there. I also note that there is another issue with this driver that was never resolved: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377 Finally, I tried to install the most recent version of this e1000 and e1000e, but they do not compile under Ubuntu 18.04: https://sourceforge.net/p/e1000/bugs/643/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev2052 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7c310224-1fd2-472b-91a8-2d3f3001642c InstallationDate: Installed on 2018-08-31 (264 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver"
[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
Happening on attempted bootup of a Thinkpad W520, using a USB stick loaded with Ubuntu 17.10 installer. -- 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/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Status in linux package in Ubuntu: Triaged Bug description: I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will randomly freeze up, sometimes before the login screen, sometimes while I'm in the middle of using a program. This sometimes happens on the Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel 4.2.0-22. Important part of log: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112129] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112134] Modules linked in: rfcomm bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes video Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112183] CPU: 0 PID: 814 Comm: kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112184] Hardware name: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 07/09/2015 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112186] task: 88031146d400 ti: 88030e838000 task.ti: 88030e838000 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112188] RIP: 0010:[] [] __do_softirq+0x76/0x250 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112194] RSP: 0018:88031fc03f30 EFLAGS: 0202 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112196] RAX: 88030e83c000 RBX: RCX: 40400040 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112197] RDX: RSI: 613e RDI: 0380 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112198] RBP: 88031fc03f80 R08: 0029f8fa1411 R09: 88031fc169f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112199] R10: 0020 R11: 0004 R12: 88031fc169c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112201] R13: 88030df8e200 R14: R15: 0001 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112202] FS: 7f6c266ac880() GS:88031fc0() knlGS: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112203] CS: 0010 DS: ES: CR0: 80050033 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112205] CR2: 7ffef000bff8 CR3: 00030f368000 CR4: 000406f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112206] Stack: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112207] 404000401fc03f78 88030e83c000 0121 8803000a Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112209] 00021fc0d640 88031fc169c0 88030df8e200 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112211] 0001 88031fc03f90 81081d23 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112213] Call Trace: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112215] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112219] [] irq_exit+0xa3/0xb0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.11] [] smp_apic_timer_interrupt+0x42/0x50 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112225] [] apic_timer_interrupt+0x82/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112226] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112230] [] ? finish_task_switch+0x67/0x1c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112232] [] __schedule+0x36c/0x980 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112234] [] schedule+0x33/0x80 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112236] [] do_nanosleep+0x6f/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112239] [] hrtimer_nanosleep+0xdc/0x1f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112241] [] ? __hrtimer_init+0x90/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112243] [] ? do_nanosleep+0x5a/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112245] [] SyS_nanosleep+0x7a/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112247] [] entry_SYSCALL_64_fastpath+0x16/0x71 Dec 31 19:1
[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
*That's the Ubuntu Mate 17.10 installer. I get a repeated Call trace which ends with the line, "perf: interrupt took too long (8809 > 8338), lowering t_max_sample_rate to 22500. -- 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/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Status in linux package in Ubuntu: Triaged Bug description: I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will randomly freeze up, sometimes before the login screen, sometimes while I'm in the middle of using a program. This sometimes happens on the Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel 4.2.0-22. Important part of log: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112129] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112134] Modules linked in: rfcomm bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes video Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112183] CPU: 0 PID: 814 Comm: kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112184] Hardware name: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 07/09/2015 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112186] task: 88031146d400 ti: 88030e838000 task.ti: 88030e838000 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112188] RIP: 0010:[] [] __do_softirq+0x76/0x250 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112194] RSP: 0018:88031fc03f30 EFLAGS: 0202 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112196] RAX: 88030e83c000 RBX: RCX: 40400040 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112197] RDX: RSI: 613e RDI: 0380 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112198] RBP: 88031fc03f80 R08: 0029f8fa1411 R09: 88031fc169f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112199] R10: 0020 R11: 0004 R12: 88031fc169c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112201] R13: 88030df8e200 R14: R15: 0001 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112202] FS: 7f6c266ac880() GS:88031fc0() knlGS: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112203] CS: 0010 DS: ES: CR0: 80050033 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112205] CR2: 7ffef000bff8 CR3: 00030f368000 CR4: 000406f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112206] Stack: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112207] 404000401fc03f78 88030e83c000 0121 8803000a Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112209] 00021fc0d640 88031fc169c0 88030df8e200 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112211] 0001 88031fc03f90 81081d23 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112213] Call Trace: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112215] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112219] [] irq_exit+0xa3/0xb0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.11] [] smp_apic_timer_interrupt+0x42/0x50 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112225] [] apic_timer_interrupt+0x82/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112226] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112230] [] ? finish_task_switch+0x67/0x1c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112232] [] __schedule+0x36c/0x980 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112234] [] schedule+0x33/0x80 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112236] [] do_nanosleep+0x6f/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112239] [] hrtimer_nanosleep+0xdc/0x1f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112241] [] ? __hrtimer_init+0x90/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112243] [] ? do_nanosleep+0x5a/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112245] [] SyS_nanosleep+0x7a/0x90 Dec 31 19:13:12 COMPUTERNAME ke
[Kernel-packages] [Bug 1718047] Re: Kernel 4.4.0-93 Freezes on boot:splash/vt.handoff edit works; but debug fails
Right before requesting my LUKS password, while booting without splash and with $vt.handoff=7, I see these errors: Booting kernel: `7=7` invalid for parameter `vt.handoff' tpm tpm0: a TPM error (6) occurred attempting to read a pcr value drm:intel_set_pch_fifo_underrun_resporting [i915] *ERROR* uncleared pch fifo underrun on pch transcoder A drm:intel_pch_fifo_underrun_irq_handler [i915] *ERROR* PCH transcoder A FIFO underrun These errors are in the process that does allow me to boot, though. -- 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/1718047 Title: Kernel 4.4.0-93 Freezes on boot:splash/vt.handoff edit works;but debug fails Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-92.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and change $vt.handoff to "$vt.handoff=7". Even with these changes, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. Note (below): booting in recovery allows me to unlock the disks. Then choosing to continue with normal boot, leads to a blank grey screen. It appears frozen, but there is continuing disk activity for some long time. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718047/+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 1718047] Re: Kernel 4.4.0-93 Freezes on boot:splash/vt.handoff edit works; but debug fails
The problem is unchanged in 4.4.0-96. -- 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/1718047 Title: Kernel 4.4.0-93 Freezes on boot:splash/vt.handoff edit works;but debug fails Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-92.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and change $vt.handoff to "$vt.handoff=7". Even with these changes, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. Note (below): booting in recovery allows me to unlock the disks. Then choosing to continue with normal boot, leads to a blank grey screen. It appears frozen, but there is continuing disk activity for some long time. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718047/+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 1718047] Re: Kernel 4.4.0-93 Freezes on boot:splash/vt.handoff edit works; but debug fails
** Description changed: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-92.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and - changed $vt.handoff to "$vt.handoff=7". Even with these changes, adding + change $vt.handoff to "$vt.handoff=7". Even with these changes, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. Note (below): booting in recovery allows me to unlock the disks. Then choosing to continue with normal boot, leads to a blank grey screen. It appears frozen, but there is continuing disk activity for some long time. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO -- 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/1718047 Title: Kernel 4.4.0-93 Freezes on boot:splash/vt.handoff edit works;but debug fails Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-92.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and change $vt.handoff to "$vt.handoff=7". Even with these changes, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. Note (below): booting in recovery allows me to unlock the disks. Then choosing to continue with normal boot, leads to a blank grey screen. It appears frozen, but there is continuing disk activity for some long time. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignatur
[Kernel-packages] [Bug 1718047] Re: Kernel 4.4.0-93 Freezes on boot:splash/vt.handoff edit works; but debug fails
** Summary changed: - Kernel 4.4.0-93 - Suddenly freezing on boot. + Kernel 4.4.0-93 Freezes on boot:splash/vt.handoff edit works;but debug fails ** Description changed: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-92.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and - changed $vt.handoff to "$vt.handoff=7". Unfortunately, adding the - "debug" switch causes a freeze, though "debug=vc" boots. Also, for any - of the settings that cause a freeze, if I add "break=mountroot", I can - mount the LUKS disks by hand and continue with boot. + changed $vt.handoff to "$vt.handoff=7". Even with these changes, adding + the "debug" switch causes a freeze, though "debug=vc" boots. Also, for + any of the settings that cause a freeze, if I add "break=mountroot", I + can mount the LUKS disks by hand and continue with boot. Note (below): booting in recovery allows me to unlock the disks. Then choosing to continue with normal boot, leads to a blank grey screen. It appears frozen, but there is continuing disk activity for some long time. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO -- 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/1718047 Title: Kernel 4.4.0-93 Freezes on boot:splash/vt.handoff edit works;but debug fails Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-92.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and changed $vt.handoff to "$vt.handoff=7". Even with these changes, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. Note (below): booting in recovery allows me to unlock the disks. Then choosing to continue with normal boot, leads to a blank grey screen. It appears frozen, but there is continuing disk activity for some long time. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux
[Kernel-packages] [Bug 1718047] Re: Kernel 4.4.0-93 - Suddenly freezing on boot.
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears - with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-93.) My + with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-92.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). - I can boot via a text console if I remove the "splash" kernel switch and changed $vt.handoff to "$vt.handoff=7". Unfortunately, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. - --- + I can boot via a text console if I remove the "splash" kernel switch and + changed $vt.handoff to "$vt.handoff=7". Unfortunately, adding the + "debug" switch causes a freeze, though "debug=vc" boots. Also, for any + of the settings that cause a freeze, if I add "break=mountroot", I can + mount the LUKS disks by hand and continue with boot. + + Note (below): booting in recovery allows me to unlock the disks. Then + choosing to continue with normal boot, leads to a blank grey screen. It + appears frozen, but there is continuing disk activity for some long + time. + + --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: dev2272 F pulseaudio - /dev/snd/controlC1: dev2272 F pulseaudio - /dev/snd/controlC0: dev2272 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: dev2272 F pulseaudio + /dev/snd/controlC1: dev2272 F pulseaudio + /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: - 0 inteldrmfb - 1 nouveaufb + 0 inteldrmfb + 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: - linux-restricted-modules-4.4.0-93-generic N/A - linux-backports-modules-4.4.0-93-generic N/A - linux-firmware1.157.12 + linux-restricted-modules-4.4.0-93-generic N/A + linux-backports-modules-4.4.0-93-generic N/A + linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO -- 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/1718047 Title: Kernel 4.4.0-93 - Suddenly freezing on boot. Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-92.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and changed $vt.handoff to "$vt.handoff=7". Unfortunately, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. Note (below): booting in recovery allows me to unlock the disks. Then choosing to continue with normal boot, leads to a blank grey screen. It appears frozen, but there is continuing disk activity for some long time. --- ApportVersion: 2
[Kernel-packages] [Bug 1718047] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1718047/+attachment/4952531/+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/1718047 Title: Kernel 4.4.0-93 - Suddenly freezing on boot. Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-93.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and changed $vt.handoff to "$vt.handoff=7". Unfortunately, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718047/+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 1718047] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1718047/+attachment/4952520/+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/1718047 Title: Kernel 4.4.0-93 - Suddenly freezing on boot. Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-93.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and changed $vt.handoff to "$vt.handoff=7". Unfortunately, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718047/+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 1718047] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1718047/+attachment/4952528/+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/1718047 Title: Kernel 4.4.0-93 - Suddenly freezing on boot. Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-93.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and changed $vt.handoff to "$vt.handoff=7". Unfortunately, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718047/+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 1718047] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1718047/+attachment/4952525/+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/1718047 Title: Kernel 4.4.0-93 - Suddenly freezing on boot. Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-93.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and changed $vt.handoff to "$vt.handoff=7". Unfortunately, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718047/+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 1718047] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1718047/+attachment/4952530/+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/1718047 Title: Kernel 4.4.0-93 - Suddenly freezing on boot. Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-93.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and changed $vt.handoff to "$vt.handoff=7". Unfortunately, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718047/+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 1718047] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1718047/+attachment/4952523/+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/1718047 Title: Kernel 4.4.0-93 - Suddenly freezing on boot. Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-93.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and changed $vt.handoff to "$vt.handoff=7". Unfortunately, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718047/+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 1718047] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1718047/+attachment/4952529/+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/1718047 Title: Kernel 4.4.0-93 - Suddenly freezing on boot. Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-93.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and changed $vt.handoff to "$vt.handoff=7". Unfortunately, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718047/+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 1718047] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1718047/+attachment/4952519/+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/1718047 Title: Kernel 4.4.0-93 - Suddenly freezing on boot. Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-93.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and changed $vt.handoff to "$vt.handoff=7". Unfortunately, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718047/+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 1718047] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1718047/+attachment/4952526/+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/1718047 Title: Kernel 4.4.0-93 - Suddenly freezing on boot. Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-93.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and changed $vt.handoff to "$vt.handoff=7". Unfortunately, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718047/+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 1718047] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1718047/+attachment/4952522/+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/1718047 Title: Kernel 4.4.0-93 - Suddenly freezing on boot. Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-93.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and changed $vt.handoff to "$vt.handoff=7". Unfortunately, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718047/+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 1718047] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1718047/+attachment/4952527/+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/1718047 Title: Kernel 4.4.0-93 - Suddenly freezing on boot. Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-93.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and changed $vt.handoff to "$vt.handoff=7". Unfortunately, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718047/+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 1718047] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1718047/+attachment/4952521/+files/JournalErrors.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/1718047 Title: Kernel 4.4.0-93 - Suddenly freezing on boot. Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-93.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and changed $vt.handoff to "$vt.handoff=7". Unfortunately, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718047/+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 1718047] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1718047/+attachment/4952524/+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/1718047 Title: Kernel 4.4.0-93 - Suddenly freezing on boot. Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-93.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and changed $vt.handoff to "$vt.handoff=7". Unfortunately, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718047/+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 1718047] Re: Kernel 4.4.0-93 - Suddenly freezing on boot.
Alright, booting in recovery mode, and then "continuing with regular boot", leads to a freeze with a blank grey background. (Disc activity continues for a long time.) So, I am reporting against the kernel. ** 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/1718047 Title: Kernel 4.4.0-93 - Suddenly freezing on boot. Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04: has been working fine for a year and a half, now suddenly freezing on bootup, with a permanent spinning logo. The problem appears with the new (4.4.0-93) kernel. (Things were fine in 4.4.0-93.) My system has /boot on a USB and root on LUKS (along with a 2nd data disk on LUKS). I can boot via a text console if I remove the "splash" kernel switch and changed $vt.handoff to "$vt.handoff=7". Unfortunately, adding the "debug" switch causes a freeze, though "debug=vc" boots. Also, for any of the settings that cause a freeze, if I add "break=mountroot", I can mount the LUKS disks by hand and continue with boot. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dev2272 F pulseaudio /dev/snd/controlC1: dev2272 F pulseaudio /dev/snd/controlC0: dev2272 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-31 (475 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 23591L9 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@t530boot/vmlinuz-4.4.0-93-generic root=/username/mapper/luks.root ro rootflags=subvol=@ quiet vt.handoff=7=7 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-93-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA5WW (2.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 23591L9 dmi.board.vendor: LENOVO dmi.board.version: 0B98413 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn23591L9:pvrThinkPadT530:rvnLENOVO:rn23591L9:rvr0B98413Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23591L9 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718047/+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
