[Kernel-packages] [Bug 1898505] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1898505/+attachment/5419515/+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/1898505 Title: weird screen display Status in linux package in Ubuntu: Confirmed Bug description: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aradhana 1567 F pulseaudio /dev/snd/controlC0: aradhana 1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-08 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-03 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G531GT.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G531GT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG531GT.300:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnStrixG531GT_G531GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Strix dmi.product.name: Strix G531GT_G531GT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898505] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1898505/+attachment/5419514/+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/1898505 Title: weird screen display Status in linux package in Ubuntu: Confirmed Bug description: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aradhana 1567 F pulseaudio /dev/snd/controlC0: aradhana 1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-08 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-03 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G531GT.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G531GT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG531GT.300:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnStrixG531GT_G531GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Strix dmi.product.name: Strix G531GT_G531GT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898505] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1898505/+attachment/5419513/+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/1898505 Title: weird screen display Status in linux package in Ubuntu: Confirmed Bug description: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aradhana 1567 F pulseaudio /dev/snd/controlC0: aradhana 1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-08 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-03 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G531GT.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G531GT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG531GT.300:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnStrixG531GT_G531GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Strix dmi.product.name: Strix G531GT_G531GT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898505] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1898505/+attachment/5419512/+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/1898505 Title: weird screen display Status in linux package in Ubuntu: Confirmed Bug description: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aradhana 1567 F pulseaudio /dev/snd/controlC0: aradhana 1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-08 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-03 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G531GT.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G531GT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG531GT.300:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnStrixG531GT_G531GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Strix dmi.product.name: Strix G531GT_G531GT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898505] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1898505/+attachment/5419507/+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/1898505 Title: weird screen display Status in linux package in Ubuntu: Confirmed Bug description: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aradhana 1567 F pulseaudio /dev/snd/controlC0: aradhana 1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-08 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-03 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G531GT.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G531GT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG531GT.300:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnStrixG531GT_G531GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Strix dmi.product.name: Strix G531GT_G531GT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898505] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1898505/+attachment/5419508/+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/1898505 Title: weird screen display Status in linux package in Ubuntu: Confirmed Bug description: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aradhana 1567 F pulseaudio /dev/snd/controlC0: aradhana 1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-08 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-03 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G531GT.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G531GT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG531GT.300:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnStrixG531GT_G531GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Strix dmi.product.name: Strix G531GT_G531GT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898505] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1898505/+attachment/5419503/+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/1898505 Title: weird screen display Status in linux package in Ubuntu: Confirmed Bug description: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aradhana 1567 F pulseaudio /dev/snd/controlC0: aradhana 1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-08 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-03 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G531GT.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G531GT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG531GT.300:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnStrixG531GT_G531GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Strix dmi.product.name: Strix G531GT_G531GT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898505] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1898505/+attachment/5419509/+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/1898505 Title: weird screen display Status in linux package in Ubuntu: Confirmed Bug description: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aradhana 1567 F pulseaudio /dev/snd/controlC0: aradhana 1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-08 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-03 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G531GT.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G531GT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG531GT.300:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnStrixG531GT_G531GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Strix dmi.product.name: Strix G531GT_G531GT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898505] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1898505/+attachment/5419510/+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/1898505 Title: weird screen display Status in linux package in Ubuntu: Confirmed Bug description: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aradhana 1567 F pulseaudio /dev/snd/controlC0: aradhana 1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-08 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-03 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G531GT.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G531GT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG531GT.300:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnStrixG531GT_G531GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Strix dmi.product.name: Strix G531GT_G531GT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898505] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1898505/+attachment/5419506/+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/1898505 Title: weird screen display Status in linux package in Ubuntu: Confirmed Bug description: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aradhana 1567 F pulseaudio /dev/snd/controlC0: aradhana 1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-08 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-03 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G531GT.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G531GT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG531GT.300:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnStrixG531GT_G531GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Strix dmi.product.name: Strix G531GT_G531GT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898505] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1898505/+attachment/5419500/+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/1898505 Title: weird screen display Status in linux package in Ubuntu: Confirmed Bug description: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aradhana 1567 F pulseaudio /dev/snd/controlC0: aradhana 1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-08 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-03 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G531GT.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G531GT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG531GT.300:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnStrixG531GT_G531GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Strix dmi.product.name: Strix G531GT_G531GT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898505] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1898505/+attachment/5419501/+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/1898505 Title: weird screen display Status in linux package in Ubuntu: Confirmed Bug description: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aradhana 1567 F pulseaudio /dev/snd/controlC0: aradhana 1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-08 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-03 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G531GT.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G531GT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG531GT.300:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnStrixG531GT_G531GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Strix dmi.product.name: Strix G531GT_G531GT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898505] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1898505/+attachment/5419511/+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/1898505 Title: weird screen display Status in linux package in Ubuntu: Confirmed Bug description: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aradhana 1567 F pulseaudio /dev/snd/controlC0: aradhana 1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-08 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-03 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G531GT.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G531GT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG531GT.300:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnStrixG531GT_G531GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Strix dmi.product.name: Strix G531GT_G531GT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898505] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1898505/+attachment/5419505/+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/1898505 Title: weird screen display Status in linux package in Ubuntu: Confirmed Bug description: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aradhana 1567 F pulseaudio /dev/snd/controlC0: aradhana 1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-08 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-03 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G531GT.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G531GT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG531GT.300:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnStrixG531GT_G531GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Strix dmi.product.name: Strix G531GT_G531GT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898505] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1898505/+attachment/5419502/+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/1898505 Title: weird screen display Status in linux package in Ubuntu: Confirmed Bug description: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aradhana 1567 F pulseaudio /dev/snd/controlC0: aradhana 1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-08 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-03 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G531GT.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G531GT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG531GT.300:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnStrixG531GT_G531GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Strix dmi.product.name: Strix G531GT_G531GT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898505] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1898505/+attachment/5419504/+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/1898505 Title: weird screen display Status in linux package in Ubuntu: Confirmed Bug description: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aradhana 1567 F pulseaudio /dev/snd/controlC0: aradhana 1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-08 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-03 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G531GT.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G531GT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG531GT.300:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnStrixG531GT_G531GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Strix dmi.product.name: Strix G531GT_G531GT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898505] Re: weird screen display
apport information ** Tags added: apport-collected focal ** Description changed: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.9 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: aradhana 1567 F pulseaudio + /dev/snd/controlC0: aradhana 1567 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-09-08 (396 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device + Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse + Bus 001 Device 004: ID 8087:0aaa Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-48-generic N/A + linux-backports-modules-5.4.0-48-generic N/A + linux-firmware1.187.3 + Tags: focal + Uname: Linux 5.4.0-48-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-10-03 (4 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/19/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: G531GT.300 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: G531GT + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG531GT.300:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnStrixG531GT_G531GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG531GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: Strix + dmi.product.name: Strix G531GT_G531GT + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1898505/+attachment/5419499/+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/1898505 Title: weird screen display Status in linux package in Ubuntu: Confirmed Bug description: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aradhana 1567 F pulseaudio /dev/snd/controlC0: aradhana 1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-08 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 006: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. Strix G531GT_G531GT NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=e2ccc566-1c2a-4ccf-b96e-7666bb4ccaec ro nouveau.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-03 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: American
[Kernel-packages] [Bug 1830560] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1830560 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830560 Title: suspend Status in linux package in Ubuntu: Incomplete Bug description: This machine 16.04 fails to recover from suspend. Screen goes dark and no activity showing on HD Recovers OK after a hard restart with a bunch of "orphaned inodes" and functions properly. Seems to have occurred since an update. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.26 ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 Uname: Linux 4.4.0-148-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Sun May 26 14:49:41 2019 InstallationDate: Installed on 2016-12-02 (905 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
Pre-post upgrade domcapabilities diff now only adds EPYC-Rome as new type (as expected) As expected on my machine that isn't a usable type, but ok that way: EPYC-Rome root@g:~# grep Rome/usr/share/libvirt/cpu_map/index.xml root@g:~# ll /usr/share/libvirt/cpu_map/x86_EPYC-Rome.xml -rw-r--r-- 1 root root 2289 Oct 8 05:36 /usr/share/libvirt/cpu_map/x86_EPYC-Rome.xml Also I completed the SRU Template on the bug description here. Self-tests started on https://bileto.ubuntu.com/excuses/4303/groovy.html Merge Proposal on: https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/391963 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Fix Committed Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will only work if the target is updated as well. [Other Info] * This is the first build since glibc 2.32 arrived in groovy, hence we need to be careful of the fix done for bug 1892826. It has to be checked if the linking is fine after the rebuild. The workload still works in groovy despite 2.32 being present (I'd ahve expected it doesn't), so we will keep the revert as-is for now. To be sure that adds two tests that shall be done: - check the linking to point to libtirpc instead of glibc $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL Was pointing to glibc, does it still and if so does it work (see below)? - run the autopkgtest cases as the LXC tests would trigger an issue if there is one ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm -nographic $ qemu-system-x86_64 -cpu EPYC-v3 -machine
[Kernel-packages] [Bug 1830560] Re: suspend
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner According to https://wiki.ubuntu.com/Bugs/FindRightPackage#Suspend_and_Hibernate this issue should have been reported against the Ubuntu kernel so I'm reassigning. If this is still an issue then please provide any additional information that may be requested. ** 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/1830560 Title: suspend Status in linux package in Ubuntu: New Bug description: This machine 16.04 fails to recover from suspend. Screen goes dark and no activity showing on HD Recovers OK after a hard restart with a bunch of "orphaned inodes" and functions properly. Seems to have occurred since an update. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.26 ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 Uname: Linux 4.4.0-148-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Sun May 26 14:49:41 2019 InstallationDate: Installed on 2016-12-02 (905 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830560] [NEW] suspend
You have been subscribed to a public bug: This machine 16.04 fails to recover from suspend. Screen goes dark and no activity showing on HD Recovers OK after a hard restart with a bunch of "orphaned inodes" and functions properly. Seems to have occurred since an update. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.26 ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 Uname: Linux 4.4.0-148-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Sun May 26 14:49:41 2019 InstallationDate: Installed on 2016-12-02 (905 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade xenial -- suspend https://bugs.launchpad.net/bugs/1830560 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890639] Re: touchpad not working after login dell xps 13
** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890639 Title: touchpad not working after login dell xps 13 Status in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: My touchpad stops working after login. These are the props using xinput: Device 'DLL075B:01 06CB:76AF Touchpad': Device Enabled (148): 1 Coordinate Transformation Matrix (150): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Tapping Enabled (302): 1 libinput Tapping Enabled Default (303): 0 libinput Tapping Drag Enabled (304):1 libinput Tapping Drag Enabled Default (305):1 libinput Tapping Drag Lock Enabled (306): 0 libinput Tapping Drag Lock Enabled Default (307): 0 libinput Tapping Button Mapping Enabled (308): 1, 0 libinput Tapping Button Mapping Default (309): 1, 0 libinput Natural Scrolling Enabled (286): 1 libinput Natural Scrolling Enabled Default (287): 0 libinput Disable While Typing Enabled (310):1 libinput Disable While Typing Enabled Default (311):1 libinput Scroll Methods Available (288):1, 1, 0 libinput Scroll Method Enabled (289): 1, 0, 0 libinput Scroll Method Enabled Default (290): 1, 0, 0 libinput Click Methods Available (312): 1, 1 libinput Click Method Enabled (313):1, 0 libinput Click Method Enabled Default (314):1, 0 libinput Middle Emulation Enabled (315):0 libinput Middle Emulation Enabled Default (316):0 libinput Accel Speed (293): 0.00 libinput Accel Speed Default (294): 0.00 libinput Left Handed Enabled (298): 0 libinput Left Handed Enabled Default (299): 0 libinput Send Events Modes Available (271): 1, 1 libinput Send Events Mode Enabled (272):1, 0 libinput Send Events Mode Enabled Default (273):0, 0 Device Node (274): "/dev/input/event7" Device Product ID (275):1739, 30383 libinput Drag Lock Buttons (300): libinput Horizontal Scroll Enabled (301): 1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: uri2562 F pulseaudio /dev/snd/controlC0: uri2562 F pulseaudio CRDA: global country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS, AUTO-BW CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-20 (109 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 9360 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_xuq7gc@/vmlinuz-5.4.0-42-generic root=ZFS=rpool/ROOT/ubuntu_xuq7gc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-25 (103 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1890639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885730] Re: Please switch default, hwe, oem kernel flavours governor to CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that advanced userspace utilities such as game-mode can be
This bug was fixed in the package linux-raspi - 5.8.0-1003.6 --- linux-raspi (5.8.0-1003.6) groovy; urgency=medium * groovy/linux-raspi: 5.8.0-1003.6 -proposed tracker (LP: #1898142) * Please switch default, hwe, oem kernel flavours governor to CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that advanced userspace utilities such as game-mode can be later used to rev-up to to performance, or rev-down to powersave. (LP: #1885730) - [Config] raspi: Set the default CPU governor to ONDEMAND * groovy/linux-raspi: Upstream raspberrypi patchset 2020-09-16 (LP: #1896436) - Revert "raspberrypi-cpufreq: Only report integer pll divisor frequencies" - staging: vchiq_arm: children inherit DMA config - ARM: dts: 2711 DMA can address 36 bits - bcm2835-dma: Advertise the full DMA range - add CONFIG_CRYPTO_USER_API_HASH=m - configs: Adding remaining crypto API modules - configs: Restore missing cgroups to BCM2835-7 - ARM: dts: Add UART skip-init properties for U-boot - drm/vc4: Remove UIF from the list of modifiers returned by format_mod_supported - ARM: proc-v7: Force misalignment of early stmia - overlays: Fix sc16is75x overlays w.r.t. serdev - overlays: Delete spi0-hw-cs - overlays: Add maxtherm overlay for MAX6675/31855 - configs: add CONFIG_SENSORS_IIO_HWMON=m - dtoverlays: Add the iio_hwmon driver to correct ADC issues - dts: bcm2711: Disable DVP by default - config: Add USB gadget support to bcm2711 config - overlays: Regenerate upstream-pi4 - drm/vc4: Increase the number of planes per crtc in FKMS. - drm/vc4: Set the possible crtcs mask correctly for planes with FKMS - staging: vc04_services: codec: Fix incorrect buffer cleanup - staging: vc04_service: codec: Allow start_streaming to update the buffernum - staging: vc04_services: codec: Fix component enable/disable - configs: Add USB_GADGET=m to bcmrpi3_defconfig - update rpi-display-overlay.dts pins for 5.4 - dtoverlays: Add overlay for the PCA953x family of GPIO expanders - rtc: rv3028: Write BSM and TCE/TCR to EEPROM - rtc: rv3028: Refresh RAM on EEPROM write - dt/overlays: Add PiFace Digital Device Tree Overlay - configs: Regenerate defconfigs - configs: Restore CONFIG_CFG80211_WEXT=y - media: bcm2835: unicam: Select MEDIA_CONTROLLER and VIDEO_V4L2_SUBDEV_API - staging: media: rpivid: Select MEDIA_CONTROLLER and MEDIA_CONTROLLER_REQUEST_API - staging: vc04_services: codec: Select MEDIA_CONTROLLER - staging: vc04_services: isp: Select MEDIA_CONTROLLER - configs: Add CONFIG_UEVENT_HELPER=y - overlays: Updated MCP3008 compatible strings. - RESET_CONTROLLER needs to be activated to compile Broadcom BCM2835 clock support - ARM: dts: bcm2711: Enable support for DDR52 eMMC - staging: vc04_services: ISP: Fix dmabuf error check in S_CTRL - ARM: dts: bcm2708.dtsi: Don't delete the cpus node - configs: Add I2C_HID=m - configs: Add CONFIG_SPS30=m - configs: Enable upstream cpufreq driver for pi0/pi1 - ARM: dts: bcm2835: Use the L2 non-allocating alias - media: bcm2835-unicam: Drop WARN on uing direct cache alias - media: i2c: tc358743: Only allow supported pixel fmts in set_fmt - media: i2c: ov9281: Add support for 8 bit readout - overlays: Add spi0-1cs and spi0-2cs - ARM: dts: Add required USB power domain for XHCI - configs: Make the evdev module a built-in - configs: Include AppArmor support - overlays: Minor README correction - staging/fbtft: Add support for display variants - overlays: Add adafruit18 and sainsmart18 overlays - ARM: dts: Limit BT modem baud rate on 3B - configs: Enable CHACHA20POLY1305=m * Provide a raspi-nolpae kernel flavor (LP: #1896761) - [Packaging] raspi: Add new flavor raspi-nolpae for armhf - [Config] raspi: Disable LPAE and HIGHMEM and set VMSPLIT_2G=y * Enable irs1125 module (LP: #1893779) - [Config] raspi: Set VIDEO_IRS1125=m * Disable CONFIG_BRCM_TRACING (LP: #1893905) - [Config] raspi: Disable BRCM_TRACING * Miscellaneous Ubuntu changes - [Config] raspi: Update gcc and ld versions - [Packaging] raspi: Add raspi-nolpae flavor to etc/getabis - [Packaging] raspi: Skip ABI, modules and retpoline checks for raspi-nolpae flavor [ Ubuntu: 5.8.0-21.22 ] * groovy/linux: 5.8.0-21.22 -proposed tracker (LP: #1898150) * Packaging resync (LP: #1786013) - update dkms package versions * Fix broken e1000e device after S3 (LP: #1897755) - SAUCE: e1000e: Increase polling timeout on MDIC ready bit * EFA: add support for 0xefa1 devices (LP: #1896791) - RDMA/efa: Expose maximum TX doorbell batch - RDMA/efa: Expose minimum SQ size - RDMA/efa: User/kernel compatibility handshake mechanism - RDMA/efa: Add EFA 0xefa1 PCI ID * Groovy update: v5.8.13 upstream stable release (LP: #1898076) -
[Kernel-packages] [Bug 1896761] Re: Provide a raspi-nolpae kernel flavor
This bug was fixed in the package linux-raspi - 5.8.0-1003.6 --- linux-raspi (5.8.0-1003.6) groovy; urgency=medium * groovy/linux-raspi: 5.8.0-1003.6 -proposed tracker (LP: #1898142) * Please switch default, hwe, oem kernel flavours governor to CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that advanced userspace utilities such as game-mode can be later used to rev-up to to performance, or rev-down to powersave. (LP: #1885730) - [Config] raspi: Set the default CPU governor to ONDEMAND * groovy/linux-raspi: Upstream raspberrypi patchset 2020-09-16 (LP: #1896436) - Revert "raspberrypi-cpufreq: Only report integer pll divisor frequencies" - staging: vchiq_arm: children inherit DMA config - ARM: dts: 2711 DMA can address 36 bits - bcm2835-dma: Advertise the full DMA range - add CONFIG_CRYPTO_USER_API_HASH=m - configs: Adding remaining crypto API modules - configs: Restore missing cgroups to BCM2835-7 - ARM: dts: Add UART skip-init properties for U-boot - drm/vc4: Remove UIF from the list of modifiers returned by format_mod_supported - ARM: proc-v7: Force misalignment of early stmia - overlays: Fix sc16is75x overlays w.r.t. serdev - overlays: Delete spi0-hw-cs - overlays: Add maxtherm overlay for MAX6675/31855 - configs: add CONFIG_SENSORS_IIO_HWMON=m - dtoverlays: Add the iio_hwmon driver to correct ADC issues - dts: bcm2711: Disable DVP by default - config: Add USB gadget support to bcm2711 config - overlays: Regenerate upstream-pi4 - drm/vc4: Increase the number of planes per crtc in FKMS. - drm/vc4: Set the possible crtcs mask correctly for planes with FKMS - staging: vc04_services: codec: Fix incorrect buffer cleanup - staging: vc04_service: codec: Allow start_streaming to update the buffernum - staging: vc04_services: codec: Fix component enable/disable - configs: Add USB_GADGET=m to bcmrpi3_defconfig - update rpi-display-overlay.dts pins for 5.4 - dtoverlays: Add overlay for the PCA953x family of GPIO expanders - rtc: rv3028: Write BSM and TCE/TCR to EEPROM - rtc: rv3028: Refresh RAM on EEPROM write - dt/overlays: Add PiFace Digital Device Tree Overlay - configs: Regenerate defconfigs - configs: Restore CONFIG_CFG80211_WEXT=y - media: bcm2835: unicam: Select MEDIA_CONTROLLER and VIDEO_V4L2_SUBDEV_API - staging: media: rpivid: Select MEDIA_CONTROLLER and MEDIA_CONTROLLER_REQUEST_API - staging: vc04_services: codec: Select MEDIA_CONTROLLER - staging: vc04_services: isp: Select MEDIA_CONTROLLER - configs: Add CONFIG_UEVENT_HELPER=y - overlays: Updated MCP3008 compatible strings. - RESET_CONTROLLER needs to be activated to compile Broadcom BCM2835 clock support - ARM: dts: bcm2711: Enable support for DDR52 eMMC - staging: vc04_services: ISP: Fix dmabuf error check in S_CTRL - ARM: dts: bcm2708.dtsi: Don't delete the cpus node - configs: Add I2C_HID=m - configs: Add CONFIG_SPS30=m - configs: Enable upstream cpufreq driver for pi0/pi1 - ARM: dts: bcm2835: Use the L2 non-allocating alias - media: bcm2835-unicam: Drop WARN on uing direct cache alias - media: i2c: tc358743: Only allow supported pixel fmts in set_fmt - media: i2c: ov9281: Add support for 8 bit readout - overlays: Add spi0-1cs and spi0-2cs - ARM: dts: Add required USB power domain for XHCI - configs: Make the evdev module a built-in - configs: Include AppArmor support - overlays: Minor README correction - staging/fbtft: Add support for display variants - overlays: Add adafruit18 and sainsmart18 overlays - ARM: dts: Limit BT modem baud rate on 3B - configs: Enable CHACHA20POLY1305=m * Provide a raspi-nolpae kernel flavor (LP: #1896761) - [Packaging] raspi: Add new flavor raspi-nolpae for armhf - [Config] raspi: Disable LPAE and HIGHMEM and set VMSPLIT_2G=y * Enable irs1125 module (LP: #1893779) - [Config] raspi: Set VIDEO_IRS1125=m * Disable CONFIG_BRCM_TRACING (LP: #1893905) - [Config] raspi: Disable BRCM_TRACING * Miscellaneous Ubuntu changes - [Config] raspi: Update gcc and ld versions - [Packaging] raspi: Add raspi-nolpae flavor to etc/getabis - [Packaging] raspi: Skip ABI, modules and retpoline checks for raspi-nolpae flavor [ Ubuntu: 5.8.0-21.22 ] * groovy/linux: 5.8.0-21.22 -proposed tracker (LP: #1898150) * Packaging resync (LP: #1786013) - update dkms package versions * Fix broken e1000e device after S3 (LP: #1897755) - SAUCE: e1000e: Increase polling timeout on MDIC ready bit * EFA: add support for 0xefa1 devices (LP: #1896791) - RDMA/efa: Expose maximum TX doorbell batch - RDMA/efa: Expose minimum SQ size - RDMA/efa: User/kernel compatibility handshake mechanism - RDMA/efa: Add EFA 0xefa1 PCI ID * Groovy update: v5.8.13 upstream stable release (LP: #1898076) -
[Kernel-packages] [Bug 1896436] Re: groovy/linux-raspi: Upstream raspberrypi patchset 2020-09-16
This bug was fixed in the package linux-raspi - 5.8.0-1003.6 --- linux-raspi (5.8.0-1003.6) groovy; urgency=medium * groovy/linux-raspi: 5.8.0-1003.6 -proposed tracker (LP: #1898142) * Please switch default, hwe, oem kernel flavours governor to CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that advanced userspace utilities such as game-mode can be later used to rev-up to to performance, or rev-down to powersave. (LP: #1885730) - [Config] raspi: Set the default CPU governor to ONDEMAND * groovy/linux-raspi: Upstream raspberrypi patchset 2020-09-16 (LP: #1896436) - Revert "raspberrypi-cpufreq: Only report integer pll divisor frequencies" - staging: vchiq_arm: children inherit DMA config - ARM: dts: 2711 DMA can address 36 bits - bcm2835-dma: Advertise the full DMA range - add CONFIG_CRYPTO_USER_API_HASH=m - configs: Adding remaining crypto API modules - configs: Restore missing cgroups to BCM2835-7 - ARM: dts: Add UART skip-init properties for U-boot - drm/vc4: Remove UIF from the list of modifiers returned by format_mod_supported - ARM: proc-v7: Force misalignment of early stmia - overlays: Fix sc16is75x overlays w.r.t. serdev - overlays: Delete spi0-hw-cs - overlays: Add maxtherm overlay for MAX6675/31855 - configs: add CONFIG_SENSORS_IIO_HWMON=m - dtoverlays: Add the iio_hwmon driver to correct ADC issues - dts: bcm2711: Disable DVP by default - config: Add USB gadget support to bcm2711 config - overlays: Regenerate upstream-pi4 - drm/vc4: Increase the number of planes per crtc in FKMS. - drm/vc4: Set the possible crtcs mask correctly for planes with FKMS - staging: vc04_services: codec: Fix incorrect buffer cleanup - staging: vc04_service: codec: Allow start_streaming to update the buffernum - staging: vc04_services: codec: Fix component enable/disable - configs: Add USB_GADGET=m to bcmrpi3_defconfig - update rpi-display-overlay.dts pins for 5.4 - dtoverlays: Add overlay for the PCA953x family of GPIO expanders - rtc: rv3028: Write BSM and TCE/TCR to EEPROM - rtc: rv3028: Refresh RAM on EEPROM write - dt/overlays: Add PiFace Digital Device Tree Overlay - configs: Regenerate defconfigs - configs: Restore CONFIG_CFG80211_WEXT=y - media: bcm2835: unicam: Select MEDIA_CONTROLLER and VIDEO_V4L2_SUBDEV_API - staging: media: rpivid: Select MEDIA_CONTROLLER and MEDIA_CONTROLLER_REQUEST_API - staging: vc04_services: codec: Select MEDIA_CONTROLLER - staging: vc04_services: isp: Select MEDIA_CONTROLLER - configs: Add CONFIG_UEVENT_HELPER=y - overlays: Updated MCP3008 compatible strings. - RESET_CONTROLLER needs to be activated to compile Broadcom BCM2835 clock support - ARM: dts: bcm2711: Enable support for DDR52 eMMC - staging: vc04_services: ISP: Fix dmabuf error check in S_CTRL - ARM: dts: bcm2708.dtsi: Don't delete the cpus node - configs: Add I2C_HID=m - configs: Add CONFIG_SPS30=m - configs: Enable upstream cpufreq driver for pi0/pi1 - ARM: dts: bcm2835: Use the L2 non-allocating alias - media: bcm2835-unicam: Drop WARN on uing direct cache alias - media: i2c: tc358743: Only allow supported pixel fmts in set_fmt - media: i2c: ov9281: Add support for 8 bit readout - overlays: Add spi0-1cs and spi0-2cs - ARM: dts: Add required USB power domain for XHCI - configs: Make the evdev module a built-in - configs: Include AppArmor support - overlays: Minor README correction - staging/fbtft: Add support for display variants - overlays: Add adafruit18 and sainsmart18 overlays - ARM: dts: Limit BT modem baud rate on 3B - configs: Enable CHACHA20POLY1305=m * Provide a raspi-nolpae kernel flavor (LP: #1896761) - [Packaging] raspi: Add new flavor raspi-nolpae for armhf - [Config] raspi: Disable LPAE and HIGHMEM and set VMSPLIT_2G=y * Enable irs1125 module (LP: #1893779) - [Config] raspi: Set VIDEO_IRS1125=m * Disable CONFIG_BRCM_TRACING (LP: #1893905) - [Config] raspi: Disable BRCM_TRACING * Miscellaneous Ubuntu changes - [Config] raspi: Update gcc and ld versions - [Packaging] raspi: Add raspi-nolpae flavor to etc/getabis - [Packaging] raspi: Skip ABI, modules and retpoline checks for raspi-nolpae flavor [ Ubuntu: 5.8.0-21.22 ] * groovy/linux: 5.8.0-21.22 -proposed tracker (LP: #1898150) * Packaging resync (LP: #1786013) - update dkms package versions * Fix broken e1000e device after S3 (LP: #1897755) - SAUCE: e1000e: Increase polling timeout on MDIC ready bit * EFA: add support for 0xefa1 devices (LP: #1896791) - RDMA/efa: Expose maximum TX doorbell batch - RDMA/efa: Expose minimum SQ size - RDMA/efa: User/kernel compatibility handshake mechanism - RDMA/efa: Add EFA 0xefa1 PCI ID * Groovy update: v5.8.13 upstream stable release (LP: #1898076) -
[Kernel-packages] [Bug 1893779] Re: Enable irs1125 module
This bug was fixed in the package linux-raspi - 5.8.0-1003.6 --- linux-raspi (5.8.0-1003.6) groovy; urgency=medium * groovy/linux-raspi: 5.8.0-1003.6 -proposed tracker (LP: #1898142) * Please switch default, hwe, oem kernel flavours governor to CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that advanced userspace utilities such as game-mode can be later used to rev-up to to performance, or rev-down to powersave. (LP: #1885730) - [Config] raspi: Set the default CPU governor to ONDEMAND * groovy/linux-raspi: Upstream raspberrypi patchset 2020-09-16 (LP: #1896436) - Revert "raspberrypi-cpufreq: Only report integer pll divisor frequencies" - staging: vchiq_arm: children inherit DMA config - ARM: dts: 2711 DMA can address 36 bits - bcm2835-dma: Advertise the full DMA range - add CONFIG_CRYPTO_USER_API_HASH=m - configs: Adding remaining crypto API modules - configs: Restore missing cgroups to BCM2835-7 - ARM: dts: Add UART skip-init properties for U-boot - drm/vc4: Remove UIF from the list of modifiers returned by format_mod_supported - ARM: proc-v7: Force misalignment of early stmia - overlays: Fix sc16is75x overlays w.r.t. serdev - overlays: Delete spi0-hw-cs - overlays: Add maxtherm overlay for MAX6675/31855 - configs: add CONFIG_SENSORS_IIO_HWMON=m - dtoverlays: Add the iio_hwmon driver to correct ADC issues - dts: bcm2711: Disable DVP by default - config: Add USB gadget support to bcm2711 config - overlays: Regenerate upstream-pi4 - drm/vc4: Increase the number of planes per crtc in FKMS. - drm/vc4: Set the possible crtcs mask correctly for planes with FKMS - staging: vc04_services: codec: Fix incorrect buffer cleanup - staging: vc04_service: codec: Allow start_streaming to update the buffernum - staging: vc04_services: codec: Fix component enable/disable - configs: Add USB_GADGET=m to bcmrpi3_defconfig - update rpi-display-overlay.dts pins for 5.4 - dtoverlays: Add overlay for the PCA953x family of GPIO expanders - rtc: rv3028: Write BSM and TCE/TCR to EEPROM - rtc: rv3028: Refresh RAM on EEPROM write - dt/overlays: Add PiFace Digital Device Tree Overlay - configs: Regenerate defconfigs - configs: Restore CONFIG_CFG80211_WEXT=y - media: bcm2835: unicam: Select MEDIA_CONTROLLER and VIDEO_V4L2_SUBDEV_API - staging: media: rpivid: Select MEDIA_CONTROLLER and MEDIA_CONTROLLER_REQUEST_API - staging: vc04_services: codec: Select MEDIA_CONTROLLER - staging: vc04_services: isp: Select MEDIA_CONTROLLER - configs: Add CONFIG_UEVENT_HELPER=y - overlays: Updated MCP3008 compatible strings. - RESET_CONTROLLER needs to be activated to compile Broadcom BCM2835 clock support - ARM: dts: bcm2711: Enable support for DDR52 eMMC - staging: vc04_services: ISP: Fix dmabuf error check in S_CTRL - ARM: dts: bcm2708.dtsi: Don't delete the cpus node - configs: Add I2C_HID=m - configs: Add CONFIG_SPS30=m - configs: Enable upstream cpufreq driver for pi0/pi1 - ARM: dts: bcm2835: Use the L2 non-allocating alias - media: bcm2835-unicam: Drop WARN on uing direct cache alias - media: i2c: tc358743: Only allow supported pixel fmts in set_fmt - media: i2c: ov9281: Add support for 8 bit readout - overlays: Add spi0-1cs and spi0-2cs - ARM: dts: Add required USB power domain for XHCI - configs: Make the evdev module a built-in - configs: Include AppArmor support - overlays: Minor README correction - staging/fbtft: Add support for display variants - overlays: Add adafruit18 and sainsmart18 overlays - ARM: dts: Limit BT modem baud rate on 3B - configs: Enable CHACHA20POLY1305=m * Provide a raspi-nolpae kernel flavor (LP: #1896761) - [Packaging] raspi: Add new flavor raspi-nolpae for armhf - [Config] raspi: Disable LPAE and HIGHMEM and set VMSPLIT_2G=y * Enable irs1125 module (LP: #1893779) - [Config] raspi: Set VIDEO_IRS1125=m * Disable CONFIG_BRCM_TRACING (LP: #1893905) - [Config] raspi: Disable BRCM_TRACING * Miscellaneous Ubuntu changes - [Config] raspi: Update gcc and ld versions - [Packaging] raspi: Add raspi-nolpae flavor to etc/getabis - [Packaging] raspi: Skip ABI, modules and retpoline checks for raspi-nolpae flavor [ Ubuntu: 5.8.0-21.22 ] * groovy/linux: 5.8.0-21.22 -proposed tracker (LP: #1898150) * Packaging resync (LP: #1786013) - update dkms package versions * Fix broken e1000e device after S3 (LP: #1897755) - SAUCE: e1000e: Increase polling timeout on MDIC ready bit * EFA: add support for 0xefa1 devices (LP: #1896791) - RDMA/efa: Expose maximum TX doorbell batch - RDMA/efa: Expose minimum SQ size - RDMA/efa: User/kernel compatibility handshake mechanism - RDMA/efa: Add EFA 0xefa1 PCI ID * Groovy update: v5.8.13 upstream stable release (LP: #1898076) -
[Kernel-packages] [Bug 1893905] Re: Disable CONFIG_BRCM_TRACING
This bug was fixed in the package linux-raspi - 5.8.0-1003.6 --- linux-raspi (5.8.0-1003.6) groovy; urgency=medium * groovy/linux-raspi: 5.8.0-1003.6 -proposed tracker (LP: #1898142) * Please switch default, hwe, oem kernel flavours governor to CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that advanced userspace utilities such as game-mode can be later used to rev-up to to performance, or rev-down to powersave. (LP: #1885730) - [Config] raspi: Set the default CPU governor to ONDEMAND * groovy/linux-raspi: Upstream raspberrypi patchset 2020-09-16 (LP: #1896436) - Revert "raspberrypi-cpufreq: Only report integer pll divisor frequencies" - staging: vchiq_arm: children inherit DMA config - ARM: dts: 2711 DMA can address 36 bits - bcm2835-dma: Advertise the full DMA range - add CONFIG_CRYPTO_USER_API_HASH=m - configs: Adding remaining crypto API modules - configs: Restore missing cgroups to BCM2835-7 - ARM: dts: Add UART skip-init properties for U-boot - drm/vc4: Remove UIF from the list of modifiers returned by format_mod_supported - ARM: proc-v7: Force misalignment of early stmia - overlays: Fix sc16is75x overlays w.r.t. serdev - overlays: Delete spi0-hw-cs - overlays: Add maxtherm overlay for MAX6675/31855 - configs: add CONFIG_SENSORS_IIO_HWMON=m - dtoverlays: Add the iio_hwmon driver to correct ADC issues - dts: bcm2711: Disable DVP by default - config: Add USB gadget support to bcm2711 config - overlays: Regenerate upstream-pi4 - drm/vc4: Increase the number of planes per crtc in FKMS. - drm/vc4: Set the possible crtcs mask correctly for planes with FKMS - staging: vc04_services: codec: Fix incorrect buffer cleanup - staging: vc04_service: codec: Allow start_streaming to update the buffernum - staging: vc04_services: codec: Fix component enable/disable - configs: Add USB_GADGET=m to bcmrpi3_defconfig - update rpi-display-overlay.dts pins for 5.4 - dtoverlays: Add overlay for the PCA953x family of GPIO expanders - rtc: rv3028: Write BSM and TCE/TCR to EEPROM - rtc: rv3028: Refresh RAM on EEPROM write - dt/overlays: Add PiFace Digital Device Tree Overlay - configs: Regenerate defconfigs - configs: Restore CONFIG_CFG80211_WEXT=y - media: bcm2835: unicam: Select MEDIA_CONTROLLER and VIDEO_V4L2_SUBDEV_API - staging: media: rpivid: Select MEDIA_CONTROLLER and MEDIA_CONTROLLER_REQUEST_API - staging: vc04_services: codec: Select MEDIA_CONTROLLER - staging: vc04_services: isp: Select MEDIA_CONTROLLER - configs: Add CONFIG_UEVENT_HELPER=y - overlays: Updated MCP3008 compatible strings. - RESET_CONTROLLER needs to be activated to compile Broadcom BCM2835 clock support - ARM: dts: bcm2711: Enable support for DDR52 eMMC - staging: vc04_services: ISP: Fix dmabuf error check in S_CTRL - ARM: dts: bcm2708.dtsi: Don't delete the cpus node - configs: Add I2C_HID=m - configs: Add CONFIG_SPS30=m - configs: Enable upstream cpufreq driver for pi0/pi1 - ARM: dts: bcm2835: Use the L2 non-allocating alias - media: bcm2835-unicam: Drop WARN on uing direct cache alias - media: i2c: tc358743: Only allow supported pixel fmts in set_fmt - media: i2c: ov9281: Add support for 8 bit readout - overlays: Add spi0-1cs and spi0-2cs - ARM: dts: Add required USB power domain for XHCI - configs: Make the evdev module a built-in - configs: Include AppArmor support - overlays: Minor README correction - staging/fbtft: Add support for display variants - overlays: Add adafruit18 and sainsmart18 overlays - ARM: dts: Limit BT modem baud rate on 3B - configs: Enable CHACHA20POLY1305=m * Provide a raspi-nolpae kernel flavor (LP: #1896761) - [Packaging] raspi: Add new flavor raspi-nolpae for armhf - [Config] raspi: Disable LPAE and HIGHMEM and set VMSPLIT_2G=y * Enable irs1125 module (LP: #1893779) - [Config] raspi: Set VIDEO_IRS1125=m * Disable CONFIG_BRCM_TRACING (LP: #1893905) - [Config] raspi: Disable BRCM_TRACING * Miscellaneous Ubuntu changes - [Config] raspi: Update gcc and ld versions - [Packaging] raspi: Add raspi-nolpae flavor to etc/getabis - [Packaging] raspi: Skip ABI, modules and retpoline checks for raspi-nolpae flavor [ Ubuntu: 5.8.0-21.22 ] * groovy/linux: 5.8.0-21.22 -proposed tracker (LP: #1898150) * Packaging resync (LP: #1786013) - update dkms package versions * Fix broken e1000e device after S3 (LP: #1897755) - SAUCE: e1000e: Increase polling timeout on MDIC ready bit * EFA: add support for 0xefa1 devices (LP: #1896791) - RDMA/efa: Expose maximum TX doorbell batch - RDMA/efa: Expose minimum SQ size - RDMA/efa: User/kernel compatibility handshake mechanism - RDMA/efa: Add EFA 0xefa1 PCI ID * Groovy update: v5.8.13 upstream stable release (LP: #1898076) -
[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]
Corrupt lines, red flashing across the top bar: https://photos.app.goo.gl/TgYxkVHRnsrV5wCR9 I use Xorg, and almost exclusively see it on my external monitor. After locking the screen and having it locked for a while. Saw it once on the internal one in a week, but like daily on external. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896091 Title: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915] Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Bug description: I left my desktop (T480s thinkpad docked to ThinkVision P24h-10) unattended for a while, and then got the error message and now have funny lines on activity, e.g. red lines flashing on top of gnome-shell bar when switching windows, or white blocks/lines around typing text. This is the second or third time it happened, reboot fixes it until the error pops up again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-19-generic 5.8.0-19.20 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5052 F pulseaudio /dev/snd/controlC1: jak5052 F pulseaudio /dev/snd/pcmC1D0p: jak5052 F...m pulseaudio /dev/snd/controlC0: jak5052 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 19:14:11 2020 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (917 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-19-generic N/A linux-backports-modules-5.8.0-19-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 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: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:br1.42:efr1.20:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5052 F pulseaudio /dev/snd/controlC1: jak5052 F pulseaudio /dev/snd/pcmC1D0p: jak5052 F...m pulseaudio /dev/snd/controlC0: jak5052 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (917 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 RelatedPackageVersions: linux-restricted-modules-5.8.0-19-generic N/A linux-backports-modules-5.8.0-19-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not
[Kernel-packages] [Bug 1892288] Re: Comet Lake PCH-H RAID not support on Ubuntu20.04
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1892288
Title:
Comet Lake PCH-H RAID not support on Ubuntu20.04
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
Fix Released
Bug description:
[Impact]
Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
[Fix]
Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
[test]
[Regression Potential]
Low. Just add a PCI id for the sata/ahci raid.
== Original ==
As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
{ PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */
If Thinkstation P340 configured as RAID mode, It can not find any RAID volume
disk.
please update such support. Thanks.
Regards,
Jiqi.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1892288/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898786] Re: Issue with bcache bch_mca_scan causing huge IO wait
Hello Mauricio, That was also one of the conclusion we reached yesterday. I followed a wrong lead yesterday, after getting another more detailed output with klockstat. I'll update the description of the bug at the end, adding the bits I found. The system is not really having memory pressure but to confirm this, we resized the memory allocated to a VM on the server from 64GB to 44GB and looked into the shrinker behavior. It didn't change a thing, and the IO wait started to rise again. As for the IO load, I'm not sure, I would probably need to do a blktrace and register it (never did that, but I read that you can then passes the result to fio to reproduce a load) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898786 Title: Issue with bcache bch_mca_scan causing huge IO wait Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: Hello, In short, we faced an issue with a huge IO wait on a bionic Ubuntu 4.15.0-118.119-generic kernel. This is the full list of process and the kernel function they were stuck in [0]. The main issue can probably be summarized by this perf reports * first identify that the cpu are stuck in idle because of something[1] * second, see what kernel function seems to stuck the process kswapd0 and kswapd1 [2]. We could see that this seems to be the mutex_lock in the bch_mca_scan function [3]. After running the command: | sudo bash -c "echo 1 > /sys/fs/bcache/f1a1e8cb-3e6b-40ea-852e- 583c48d0c2b8/internal/btree_shrinker_disabled" The server started to respond normally and the IO wait dropped significantly Here is a trace of the bcache event related lock in the kernel obtained with some bpfcc-tools [4]. klockstat-bpfcc -c bch_ -i 5 -s 3 The trace has been run in parallel with the following command line echo "Shrinker disabled: $(date)"; sleep 60; echo "Enabling shrinker: $(date)"; echo 0 | sudo tee /sys/block/bcache0/bcache/cache/internal/btree_shrinker_disabled ; sleep 60; echo "Disabling shrinker: $(date)"; echo 1 | sudo tee /sys/block/bcache0/bcache/cache/internal/btree_shrinker_disabled; sleep 60; echo "End of test: $(date)" [0]: https://pastebin.ubuntu.com/p/QYXPdsMCWC/ [1]: https://pastebin.ubuntu.com/p/BFsvF7H54r/ [2]: https://pastebin.ubuntu.com/p/35qdsHYHf5/ [3]: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/drivers/md/bcache/btree.c?h=Ubuntu-4.15.0-118.119#n674 [4]: https://pastebin.ubuntu.com/p/qhyqP35fCw/ $ cat /proc/version_signature Ubuntu 4.15.0-118.119-generic 4.15.18 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-118-generic 4.15.0-118.119 ProcVersionSignature: User Name 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 10:04 seq crw-rw 1 root audio 116, 33 Sep 29 10:04 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Oct 6 20:36:18 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL380 G7 PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=c6ad1629-a506-4043-a339-6d57f0708d12 ro console=ttyS1,115200 nosplash RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.18 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-09-27 (375 days ago) dmi.bios.date: 05/05/2011 dmi.bios.vendor: HP dmi.bios.version: P67 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP67:bd05/05/2011:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL380 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Managed to make the touchpad work but gestures are not working. Got the PKGBUILD for 5.8.14 from the gitlab page and added the patch tried xf86-input-synaptics and xf86-input-libinput. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku:
[Kernel-packages] [Bug 1898786] Re: Issue with bcache bch_mca_scan causing huge IO wait
** Description changed: Hello, In short, we faced an issue with a huge IO wait on a bionic Ubuntu 4.15.0-118.119-generic kernel. This is the full list of process and the kernel function they were stuck in [0]. The main issue can probably be summarized by this perf reports * first identify that the cpu are stuck in idle because of something[1] * second, see what kernel function seems to stuck the process kswapd0 and kswapd1 [2]. We could see that this seems to be the mutex_lock in the bch_mca_scan function [3]. After running the command: | sudo bash -c "echo 1 > /sys/fs/bcache/f1a1e8cb-3e6b-40ea-852e- 583c48d0c2b8/internal/btree_shrinker_disabled" The server started to respond normally and the IO wait dropped significantly - [0]: https://pastebin.canonical.com/p/wYYKwHdRXk/ - [1]: https://pastebin.canonical.com/p/n2Tw57QyBC/ - [2]: https://pastebin.canonical.com/p/3QqFTfdHhX/ + [0]: https://pastebin.ubuntu.com/p/QYXPdsMCWC/ + [1]: https://pastebin.ubuntu.com/p/BFsvF7H54r/ + [2]: https://pastebin.ubuntu.com/p/35qdsHYHf5/ [3]: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/drivers/md/bcache/btree.c?h=Ubuntu-4.15.0-118.119#n674 $ cat /proc/version_signature Ubuntu 4.15.0-118.119-generic 4.15.18 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-118-generic 4.15.0-118.119 ProcVersionSignature: User Name 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 10:04 seq crw-rw 1 root audio 116, 33 Sep 29 10:04 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Oct 6 20:36:18 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL380 G7 PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=c6ad1629-a506-4043-a339-6d57f0708d12 ro console=ttyS1,115200 nosplash RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.18 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-09-27 (375 days ago) dmi.bios.date: 05/05/2011 dmi.bios.vendor: HP dmi.bios.version: P67 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP67:bd05/05/2011:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL380 G7 dmi.sys.vendor: HP ** Description changed: Hello, In short, we faced an issue with a huge IO wait on a bionic Ubuntu 4.15.0-118.119-generic kernel. This is the full list of process and the kernel function they were stuck in [0]. The main issue can probably be summarized by this perf reports * first identify that the cpu are stuck in idle because of something[1] * second, see what kernel function seems to stuck the process kswapd0 and kswapd1 [2]. We could see that this seems to be the mutex_lock in the bch_mca_scan function [3]. After running the command: | sudo bash -c "echo 1 > /sys/fs/bcache/f1a1e8cb-3e6b-40ea-852e- 583c48d0c2b8/internal/btree_shrinker_disabled" - The server started to respond normally and the IO wait dropped significantly + The server started to respond normally and the IO wait dropped + significantly + + Here is a trace of the bcache event related lock in the kernel obtained + with some bpfcc-tools [4]. + + klockstat-bpfcc -c bch_ -i 5 -s 3 + + The trace has been run in parallel with the following command line + + echo "Shrinker disabled: $(date)"; sleep 60; echo "Enabling shrinker: + $(date)"; echo 0 | sudo tee + /sys/block/bcache0/bcache/cache/internal/btree_shrinker_disabled ; sleep + 60; echo "Disabling shrinker: $(date)"; echo 1 | sudo tee + /sys/block/bcache0/bcache/cache/internal/btree_shrinker_disabled; sleep + 60; echo "End of test: $(date)" + + [0]: https://pastebin.ubuntu.com/p/QYXPdsMCWC/ [1]: https://pastebin.ubuntu.com/p/BFsvF7H54r/ [2]: https://pastebin.ubuntu.com/p/35qdsHYHf5/ [3]: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/drivers/md/bcache/btree.c?h=Ubuntu-4.15.0-118.119#n674 + [4]: https://pastebin.ubuntu.com/p/qhyqP35fCw/ $ cat /proc/version_signature Ubuntu 4.15.0-118.119-generic 4.15.18 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-118-generic 4.15.0-118.119 ProcVersionSignature: User Name
[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]
... so if mutter 3.38.1 does not resolve the problem, I would be interested to see the corruption in action. Probably with a video. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896091 Title: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915] Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Bug description: I left my desktop (T480s thinkpad docked to ThinkVision P24h-10) unattended for a while, and then got the error message and now have funny lines on activity, e.g. red lines flashing on top of gnome-shell bar when switching windows, or white blocks/lines around typing text. This is the second or third time it happened, reboot fixes it until the error pops up again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-19-generic 5.8.0-19.20 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5052 F pulseaudio /dev/snd/controlC1: jak5052 F pulseaudio /dev/snd/pcmC1D0p: jak5052 F...m pulseaudio /dev/snd/controlC0: jak5052 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 19:14:11 2020 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (917 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-19-generic N/A linux-backports-modules-5.8.0-19-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 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: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:br1.42:efr1.20:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5052 F pulseaudio /dev/snd/controlC1: jak5052 F pulseaudio /dev/snd/pcmC1D0p: jak5052 F...m pulseaudio /dev/snd/controlC0: jak5052 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (917 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 RelatedPackageVersions: linux-restricted-modules-5.8.0-19-generic N/A linux-backports-modules-5.8.0-19-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 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: None
[Kernel-packages] [Bug 1893711] Re: [hns3-0901]add hns3_gro_complete for HW GRO process
** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893711 Title: [hns3-0901]add hns3_gro_complete for HW GRO process Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: [Impact] kernel oops on hns3 driver when GRO is enabled. [Fix] Cherry-pick patches from upstream d474d88f8826 net: hns3: add hns3_gro_complete for HW GRO process a4d2cdcbb878 net: hns3: minor refactor for hns3_rx_checksum [Test] No known way to reproduce it in our lab. Regression test only. [Regression Potential] Patchset only affects hns3 driver. Minimal risk for other drivers and platform. Stress test on hns3 driver looks good and we also have positive feedback from different lab. Patches also in Ubuntu kernel since Eoan and no regression observed. [Bug Description] When a GRO packet is received by driver, the cwr field in the struct tcphdr needs to be checked to decide whether to set the SKB_GSO_TCP_ECN for skb_shinfo(skb)->gso_type. [Steps to Reproduce] 1.load PF driver 2.turn off GRO of stack, turn on HW GRO [Actual Results] [ 32.597752] bond-dcn: link status definitely up for interface enp189s0f0, 1 Mbps full duplex [1048422.589438] Unable to handle kernel paging request at virtual address 80605d0c [1048422.597506] Mem abort info: [1048422.600463] ESR = 0x9605 [1048422.603679] Exception class = DABT (current EL), IL = 32 bits [1048422.609747] SET = 0, FnV = 0 [1048422.612963] EA = 0, S1PTW = 0 [1048422.616265] Data abort info: [1048422.619309] ISV = 0, ISS = 0x0005 [1048422.623301] CM = 0, WnR = 0 [1048422.626431] swapper pgtable: 4k pages, 48-bit VAs, pgd = 96615bf4 [1048422.633360] [80605d0c] *pgd=205f6003, *pud= [1048422.640465] Internal error: Oops: 9605 [#1] SMP [1048422.645496] Modules linked in: bonding zfs(PO) zunicode(PO) zavl(PO) icp(PO) nls_iso8859_1 zcommon(PO) znvpair(PO) spl(O) joydev input_leds ipmi_ssif ipmi_si ipmi_devintf shpchp ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 xfs btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure hibmc_drm aes_ce_blk aes_ce_cipher ttm realtek crc32_ce drm_kms_helper crct10dif_ce syscopyarea ghash_ce hisi_sas_v3_hw sysfillrect sha2_ce sysimgblt hns3 nvme hisi_sas_main sha256_arm64 fb_sys_fops sha1_ce drm hclge libsas nvme_core ahci megaraid_sas hnae3 scsi_transport_sas libahci gpio_dwapb hid_generic [1048422.715911] usbhid hid aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [1048422.723192] Process swapper/22 (pid: 0, stack limit = 0xdc9798e5) [1048422.730122] CPU: 22 PID: 0 Comm: swapper/22 Tainted: P O 4.15.0-96-generic #97-Ubuntu [1048422.739297] Hardware name: Huawei TaiShan 200 (Model 2280)/BC82AMDDA, BIOS 1.35 04/30/2020 [1048422.747695] pstate: 8049 (Nzcv daif +PAN -UAO) [1048422.752641] pc : tcp_gro_complete+0x4c/0x80 [1048422.756988] lr : hns3_clean_rx_ring+0x63c/0x6f0 [hns3] [1048422.762274] sp : 09893d00 [1048422.765746] x29: 09893d00 x28: a05de384d900 [1048422.771207] x27: a05dc660c6c0 x26: a05dc7a6c280 [1048422.776668] x25: 0040 x24: a05dc7a4e000 [1048422.782130] x23: 0002 x22: [1048422.787590] x21: x20: [1048422.793051] x19: a05de384d900 x18: a3bf2a70 [1048422.798512] x17: a3b68698 x16: 08307aa0 [1048422.803973] x15: 0d920112ac4e x14: 0c96b6405c2a0a08 [1048422.809435] x13: 01011cc0f601 x12: 188058b201fc85fd [1048422.814896] x11: cd979f72c04ce5db x10: 2087e1db2087679d [1048422.820358] x9 : 0640004090cff807 x8 : 00450008f034d971 [1048422.825820] x7 : 1502726647903506 x6 : 0002 [1048422.831281] x5 : a05dc7ad0480 x4 : 0002 [1048422.836743] x3 : 805f5d00 x2 : 0060 [1048422.842203] x1 : 805f5f00 x0 : 80605cff [1048422.847665] Call trace: [1048422.850276] tcp_gro_complete+0x4c/0x80 [1048422.854274] hns3_clean_rx_ring+0x63c/0x6f0 [hns3] [1048422.859217] hns3_nic_common_poll+0x98/0x220 [hns3] [1048422.864247] net_rx_action+0x160/0x3d8 [1048422.868153]
[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]
Blocks/lines around areas of the screen that are changing may just be bug 1898080. ** Package changed: gnome-shell (Ubuntu) => mutter (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/1896091 Title: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915] Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Bug description: I left my desktop (T480s thinkpad docked to ThinkVision P24h-10) unattended for a while, and then got the error message and now have funny lines on activity, e.g. red lines flashing on top of gnome-shell bar when switching windows, or white blocks/lines around typing text. This is the second or third time it happened, reboot fixes it until the error pops up again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-19-generic 5.8.0-19.20 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5052 F pulseaudio /dev/snd/controlC1: jak5052 F pulseaudio /dev/snd/pcmC1D0p: jak5052 F...m pulseaudio /dev/snd/controlC0: jak5052 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 19:14:11 2020 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (917 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-19-generic N/A linux-backports-modules-5.8.0-19-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 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: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:br1.42:efr1.20:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5052 F pulseaudio /dev/snd/controlC1: jak5052 F pulseaudio /dev/snd/pcmC1D0p: jak5052 F...m pulseaudio /dev/snd/controlC0: jak5052 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (917 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 RelatedPackageVersions: linux-restricted-modules-5.8.0-19-generic N/A linux-backports-modules-5.8.0-19-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 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: None
[Kernel-packages] [Bug 1898903] Re: *-tools-common packages descriptions have typo "PGKVER"
** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Low ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Low ** Also affects: linux-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.4 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-hwe-5.4 (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: linux-hwe-5.4 (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-hwe-5.4 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-hwe-5.4 (Ubuntu Groovy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898903 Title: *-tools-common packages descriptions have typo "PGKVER" Status in linux package in Ubuntu: In Progress Status in linux-hwe-5.4 package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Status in linux-hwe-5.4 source package in Xenial: Invalid Status in linux source package in Bionic: In Progress Status in linux-hwe-5.4 source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux-hwe-5.4 source package in Focal: Invalid Status in linux source package in Groovy: In Progress Status in linux-hwe-5.4 source package in Groovy: Invalid Bug description: $ apt show linux-tools-common Description: Linux kernel version specific tools for version 4.15.0 This package provides the architecture independent parts for kernel version locked tools (such as perf and x86_energy_perf_policy) for version PGKVER. ^^ Seems to be true for all versions/flavors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898998] Re: BUG: kernel NULL pointer dereference, address: 000000000000002c
Discussed here: https://lore.kernel.org/linux-integrity/e1fdcccb-ca51-4aee-ac83-9cde995ea...@canonical.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898998 Title: BUG: kernel NULL pointer dereference, address: 002c Status in linux package in Ubuntu: Confirmed Bug description: Okt 07 20:45:43 jak-t480s kernel: BUG: kernel NULL pointer dereference, address: 002c Okt 07 20:45:43 jak-t480s kernel: #PF: supervisor read access in kernel mode Okt 07 20:45:43 jak-t480s kernel: #PF: error_code(0x) - not-present page Okt 07 20:45:43 jak-t480s kernel: PGD 0 P4D 0 Okt 07 20:45:43 jak-t480s kernel: Oops: [#3] SMP PTI Okt 07 20:45:43 jak-t480s kernel: CPU: 1 PID: 1763439 Comm: fwupd Tainted: P D W O 5.8.0-21-generic #22-Ubuntu Okt 07 20:45:43 jak-t480s kernel: Hardware name: LENOVO 20L8S02D00/20L8S02D00, BIOS N22ET65W (1.42 ) 06/04/2020 Okt 07 20:45:43 jak-t480s kernel: RIP: 0010:tpm2_bios_measurements_start+0x38/0x1f0 Okt 07 20:45:43 jak-t480s kernel: Code: 55 41 54 53 48 83 ec 30 4c 8b 16 65 48 8b 04 25 28 00 00 00 48 89 45 d0 48 8b 47 70 4c 8b a0 d0 06 00 00 48 8b 88 d8 06 00 00 <41> 8b 5c 24 1c 48 89 4d b0 48 89 d8 48 83 c3 20 4d 85 d2 75 31 4c Okt 07 20:45:43 jak-t480s kernel: RSP: 0018:ae1882593de8 EFLAGS: 00010286 Okt 07 20:45:43 jak-t480s kernel: RAX: 9eb8e2f8e000 RBX: RCX: 0010 Okt 07 20:45:43 jak-t480s kernel: RDX: 1000 RSI: 9eb458df5370 RDI: 9eb458df5348 Okt 07 20:45:43 jak-t480s kernel: RBP: ae1882593e40 R08: ce187f442ad0 R09: 9eb320efa300 Okt 07 20:45:43 jak-t480s kernel: R10: R11: 0002 R12: 0010 Okt 07 20:45:43 jak-t480s kernel: R13: 9eb458df5348 R14: 9eb458df5370 R15: 9eb458df5380 Okt 07 20:45:43 jak-t480s kernel: FS: 7f2974d35b00() GS:9eb8e744() knlGS: Okt 07 20:45:43 jak-t480s kernel: CS: 0010 DS: ES: CR0: 80050033 Okt 07 20:45:43 jak-t480s kernel: CR2: 002c CR3: 00041a232004 CR4: 003606e0 Okt 07 20:45:43 jak-t480s kernel: Call Trace: Okt 07 20:45:43 jak-t480s kernel: seq_read+0x95/0x470 Okt 07 20:45:43 jak-t480s kernel: ? security_file_permission+0x150/0x160 Okt 07 20:45:43 jak-t480s kernel: vfs_read+0xaa/0x190 Okt 07 20:45:43 jak-t480s kernel: ksys_read+0x67/0xe0 Okt 07 20:45:43 jak-t480s kernel: __x64_sys_read+0x1a/0x20 Okt 07 20:45:43 jak-t480s kernel: do_syscall_64+0x49/0xc0 Okt 07 20:45:43 jak-t480s kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Okt 07 20:45:43 jak-t480s kernel: RIP: 0033:0x7f2977f93cec Okt 07 20:45:43 jak-t480s kernel: Code: ec 28 48 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 f9 7c f8 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 34 44 89 c7 48 89 44 24 08 e8 4f 7d f8 ff 48 Okt 07 20:45:43 jak-t480s kernel: RSP: 002b:7ffc233bb840 EFLAGS: 0246 ORIG_RAX: Okt 07 20:45:43 jak-t480s kernel: RAX: ffda RBX: 560ac1a5da20 RCX: 7f2977f93cec Okt 07 20:45:43 jak-t480s kernel: RDX: 1000 RSI: 7ffc233bb940 RDI: 0010 Okt 07 20:45:43 jak-t480s kernel: RBP: 7f29780704c0 R08: R09: 560ac1a731d0 Okt 07 20:45:43 jak-t480s kernel: R10: 560ac1a6fdc0 R11: 0246 R12: 1000 Okt 07 20:45:43 jak-t480s kernel: R13: 7ffc233bb940 R14: 0d68 R15: 7f297806f8c0 Okt 07 20:45:43 jak-t480s kernel: Modules linked in: unix_diag snd_usb_audio snd_usbmidi_lib scsi_transport_iscsi acpi_call(O) veth ip6table_nat zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) nf_tables nfnetlink ccm rfcomm ipt_REJECT nf_reject_ipv4 xt_> Okt 07 20:45:43 jak-t480s kernel: snd_seq_midi ledtrig_audio elan_i2c ee1004 snd_pcm cfg80211 mei snd_seq_midi_event intel_pch_thermal snd_rawmidi ucsi_acpi typec_ucsi processor_thermal_device snd_seq intel_xhci_usb_role_switch intel_rapl_common roles intel_soc_dts_iosf typec snd_s> Okt 07 20:45:43 jak-t480s kernel: xhci_pci_renesas wmi video Okt 07 20:45:43 jak-t480s kernel: CR2: 002c Okt 07 20:45:43 jak-t480s kernel: ---[ end trace 78901de378649ad1 ]--- Okt 07 20:45:43 jak-t480s kernel: RIP: 0010:tpm2_bios_measurements_start+0x38/0x1f0 Okt 07 20:45:43 jak-t480s kernel: Code: 55 41 54 53 48 83 ec 30 4c 8b 16 65 48 8b 04 25 28 00 00 00 48 89 45 d0 48 8b 47 70 4c 8b a0 d0 06 00 00 48 8b 88 d8 06 00 00 <41> 8b 5c 24 1c 48 89 4d b0 48 89 d8 48 83 c3 20 4d 85 d2 75 31 4c Okt 07 20:45:43 jak-t480s kernel: RSP: 0018:ae1880903de8 EFLAGS: 00010286 Okt 07 20:45:43 jak-t480s kernel: RAX: 9eb8e2f8e000 RBX: RCX: 0010 Okt 07 20:45:43 jak-t480s kernel: RDX:
[Kernel-packages] [Bug 1898998] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898998 Title: BUG: kernel NULL pointer dereference, address: 002c Status in linux package in Ubuntu: Confirmed Bug description: Okt 07 20:45:43 jak-t480s kernel: BUG: kernel NULL pointer dereference, address: 002c Okt 07 20:45:43 jak-t480s kernel: #PF: supervisor read access in kernel mode Okt 07 20:45:43 jak-t480s kernel: #PF: error_code(0x) - not-present page Okt 07 20:45:43 jak-t480s kernel: PGD 0 P4D 0 Okt 07 20:45:43 jak-t480s kernel: Oops: [#3] SMP PTI Okt 07 20:45:43 jak-t480s kernel: CPU: 1 PID: 1763439 Comm: fwupd Tainted: P D W O 5.8.0-21-generic #22-Ubuntu Okt 07 20:45:43 jak-t480s kernel: Hardware name: LENOVO 20L8S02D00/20L8S02D00, BIOS N22ET65W (1.42 ) 06/04/2020 Okt 07 20:45:43 jak-t480s kernel: RIP: 0010:tpm2_bios_measurements_start+0x38/0x1f0 Okt 07 20:45:43 jak-t480s kernel: Code: 55 41 54 53 48 83 ec 30 4c 8b 16 65 48 8b 04 25 28 00 00 00 48 89 45 d0 48 8b 47 70 4c 8b a0 d0 06 00 00 48 8b 88 d8 06 00 00 <41> 8b 5c 24 1c 48 89 4d b0 48 89 d8 48 83 c3 20 4d 85 d2 75 31 4c Okt 07 20:45:43 jak-t480s kernel: RSP: 0018:ae1882593de8 EFLAGS: 00010286 Okt 07 20:45:43 jak-t480s kernel: RAX: 9eb8e2f8e000 RBX: RCX: 0010 Okt 07 20:45:43 jak-t480s kernel: RDX: 1000 RSI: 9eb458df5370 RDI: 9eb458df5348 Okt 07 20:45:43 jak-t480s kernel: RBP: ae1882593e40 R08: ce187f442ad0 R09: 9eb320efa300 Okt 07 20:45:43 jak-t480s kernel: R10: R11: 0002 R12: 0010 Okt 07 20:45:43 jak-t480s kernel: R13: 9eb458df5348 R14: 9eb458df5370 R15: 9eb458df5380 Okt 07 20:45:43 jak-t480s kernel: FS: 7f2974d35b00() GS:9eb8e744() knlGS: Okt 07 20:45:43 jak-t480s kernel: CS: 0010 DS: ES: CR0: 80050033 Okt 07 20:45:43 jak-t480s kernel: CR2: 002c CR3: 00041a232004 CR4: 003606e0 Okt 07 20:45:43 jak-t480s kernel: Call Trace: Okt 07 20:45:43 jak-t480s kernel: seq_read+0x95/0x470 Okt 07 20:45:43 jak-t480s kernel: ? security_file_permission+0x150/0x160 Okt 07 20:45:43 jak-t480s kernel: vfs_read+0xaa/0x190 Okt 07 20:45:43 jak-t480s kernel: ksys_read+0x67/0xe0 Okt 07 20:45:43 jak-t480s kernel: __x64_sys_read+0x1a/0x20 Okt 07 20:45:43 jak-t480s kernel: do_syscall_64+0x49/0xc0 Okt 07 20:45:43 jak-t480s kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Okt 07 20:45:43 jak-t480s kernel: RIP: 0033:0x7f2977f93cec Okt 07 20:45:43 jak-t480s kernel: Code: ec 28 48 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 f9 7c f8 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 34 44 89 c7 48 89 44 24 08 e8 4f 7d f8 ff 48 Okt 07 20:45:43 jak-t480s kernel: RSP: 002b:7ffc233bb840 EFLAGS: 0246 ORIG_RAX: Okt 07 20:45:43 jak-t480s kernel: RAX: ffda RBX: 560ac1a5da20 RCX: 7f2977f93cec Okt 07 20:45:43 jak-t480s kernel: RDX: 1000 RSI: 7ffc233bb940 RDI: 0010 Okt 07 20:45:43 jak-t480s kernel: RBP: 7f29780704c0 R08: R09: 560ac1a731d0 Okt 07 20:45:43 jak-t480s kernel: R10: 560ac1a6fdc0 R11: 0246 R12: 1000 Okt 07 20:45:43 jak-t480s kernel: R13: 7ffc233bb940 R14: 0d68 R15: 7f297806f8c0 Okt 07 20:45:43 jak-t480s kernel: Modules linked in: unix_diag snd_usb_audio snd_usbmidi_lib scsi_transport_iscsi acpi_call(O) veth ip6table_nat zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) nf_tables nfnetlink ccm rfcomm ipt_REJECT nf_reject_ipv4 xt_> Okt 07 20:45:43 jak-t480s kernel: snd_seq_midi ledtrig_audio elan_i2c ee1004 snd_pcm cfg80211 mei snd_seq_midi_event intel_pch_thermal snd_rawmidi ucsi_acpi typec_ucsi processor_thermal_device snd_seq intel_xhci_usb_role_switch intel_rapl_common roles intel_soc_dts_iosf typec snd_s> Okt 07 20:45:43 jak-t480s kernel: xhci_pci_renesas wmi video Okt 07 20:45:43 jak-t480s kernel: CR2: 002c Okt 07 20:45:43 jak-t480s kernel: ---[ end trace 78901de378649ad1 ]--- Okt 07 20:45:43 jak-t480s kernel: RIP: 0010:tpm2_bios_measurements_start+0x38/0x1f0 Okt 07 20:45:43 jak-t480s kernel: Code: 55 41 54 53 48 83 ec 30 4c 8b 16 65 48 8b 04 25 28 00 00 00 48 89 45 d0 48 8b 47 70 4c 8b a0 d0 06 00 00 48 8b 88 d8 06 00 00 <41> 8b 5c 24 1c 48 89 4d b0 48 89 d8 48 83 c3 20 4d 85 d2 75 31 4c Okt 07 20:45:43 jak-t480s kernel: RSP: 0018:ae1880903de8 EFLAGS: 00010286 Okt 07 20:45:43 jak-t480s kernel: RAX: 9eb8e2f8e000 RBX: RCX: 0010 Okt 07 20:45:43 jak-t480s kernel: RDX: 1000 RSI:
[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]
Also adding a gnome-shell task. This happens on 5.8.0-21-generic from proposed too, and restarting gnome-shell stops the corruptions, so it's possible this is a gnome issue. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896091 Title: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915] Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I left my desktop (T480s thinkpad docked to ThinkVision P24h-10) unattended for a while, and then got the error message and now have funny lines on activity, e.g. red lines flashing on top of gnome-shell bar when switching windows, or white blocks/lines around typing text. This is the second or third time it happened, reboot fixes it until the error pops up again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-19-generic 5.8.0-19.20 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5052 F pulseaudio /dev/snd/controlC1: jak5052 F pulseaudio /dev/snd/pcmC1D0p: jak5052 F...m pulseaudio /dev/snd/controlC0: jak5052 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 19:14:11 2020 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (917 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-19-generic N/A linux-backports-modules-5.8.0-19-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 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: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:br1.42:efr1.20:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5052 F pulseaudio /dev/snd/controlC1: jak5052 F pulseaudio /dev/snd/pcmC1D0p: jak5052 F...m pulseaudio /dev/snd/controlC0: jak5052 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (917 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 RelatedPackageVersions: linux-restricted-modules-5.8.0-19-generic N/A linux-backports-modules-5.8.0-19-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined
[Kernel-packages] [Bug 1898797] Re: [1006/183929.019360:ERROR:nacl_helper_linux.cc(308)]
Actually I did at https://bugs.chromium.org/p/chromium/issues/detail?id=1136411 as I see it too -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898797 Title: [1006/183929.019360:ERROR:nacl_helper_linux.cc(308)] Status in linux package in Ubuntu: Invalid Bug description: How? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-118-generic 4.15.0-118.119 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 2325 F pulseaudio /dev/snd/controlC1: robert 2325 F pulseaudio CurrentDesktop: MATE Date: Tue Oct 6 18:39:14 2020 InstallationDate: Installed on 2019-12-22 (289 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=ae6f5cdd-0c3b-48a9-8449-da1027511bec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
Now seeing your comment Markus, yeah I've seen the monitor fixup myself thanks. /me looks forward to live refreshing launchpad to not appear so ignorant to updates ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Fix Committed Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will only work if the target is updated as well. [Other Info] * This is the first build since glibc 2.32 arrived in groovy, hence we need to be careful of the fix done for bug 1892826. It has to be checked if the linking is fine after the rebuild. The workload still works in groovy despite 2.32 being present (I'd ahve expected it doesn't), so we will keep the revert as-is for now. To be sure that adds two tests that shall be done: - check the linking to point to libtirpc instead of glibc $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL Was pointing to glibc, does it still and if so does it work (see below)? - run the autopkgtest cases as the LXC tests would trigger an issue if there is one ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm -nographic $ qemu-system-x86_64 -cpu EPYC-v3 -machine pc-q35-focal,accel=kvm -nographic [Regression Potential] * This adds new CPU types to the list of known CPUs defining their name and features. Generally the changes are contained to those new types and only active when selected - and usually only selectable on such new machines. Therefore not a lot should change for other users. One thing thou, if a user selected an unversioned type (which in this case only can be "EPYC") by
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
+ same here 20.04 LTS clean install XPS9500 + MPOW336A -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898797] Re: [1006/183929.019360:ERROR:nacl_helper_linux.cc(308)]
The bug report title is the start of a chrome error message, and I can't see any bug in the dmesg output, so I don't see how this is a bug in the kernel. I suggest you open an issue on the Chrome bug tracker https://crbug.com/ for your Chrome issue. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898797 Title: [1006/183929.019360:ERROR:nacl_helper_linux.cc(308)] Status in linux package in Ubuntu: Invalid Bug description: How? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-118-generic 4.15.0-118.119 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 2325 F pulseaudio /dev/snd/controlC1: robert 2325 F pulseaudio CurrentDesktop: MATE Date: Tue Oct 6 18:39:14 2020 InstallationDate: Installed on 2019-12-22 (289 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=ae6f5cdd-0c3b-48a9-8449-da1027511bec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898998] [NEW] BUG: kernel NULL pointer dereference, address: 000000000000002c
Public bug reported: Okt 07 20:45:43 jak-t480s kernel: BUG: kernel NULL pointer dereference, address: 002c Okt 07 20:45:43 jak-t480s kernel: #PF: supervisor read access in kernel mode Okt 07 20:45:43 jak-t480s kernel: #PF: error_code(0x) - not-present page Okt 07 20:45:43 jak-t480s kernel: PGD 0 P4D 0 Okt 07 20:45:43 jak-t480s kernel: Oops: [#3] SMP PTI Okt 07 20:45:43 jak-t480s kernel: CPU: 1 PID: 1763439 Comm: fwupd Tainted: P D W O 5.8.0-21-generic #22-Ubuntu Okt 07 20:45:43 jak-t480s kernel: Hardware name: LENOVO 20L8S02D00/20L8S02D00, BIOS N22ET65W (1.42 ) 06/04/2020 Okt 07 20:45:43 jak-t480s kernel: RIP: 0010:tpm2_bios_measurements_start+0x38/0x1f0 Okt 07 20:45:43 jak-t480s kernel: Code: 55 41 54 53 48 83 ec 30 4c 8b 16 65 48 8b 04 25 28 00 00 00 48 89 45 d0 48 8b 47 70 4c 8b a0 d0 06 00 00 48 8b 88 d8 06 00 00 <41> 8b 5c 24 1c 48 89 4d b0 48 89 d8 48 83 c3 20 4d 85 d2 75 31 4c Okt 07 20:45:43 jak-t480s kernel: RSP: 0018:ae1882593de8 EFLAGS: 00010286 Okt 07 20:45:43 jak-t480s kernel: RAX: 9eb8e2f8e000 RBX: RCX: 0010 Okt 07 20:45:43 jak-t480s kernel: RDX: 1000 RSI: 9eb458df5370 RDI: 9eb458df5348 Okt 07 20:45:43 jak-t480s kernel: RBP: ae1882593e40 R08: ce187f442ad0 R09: 9eb320efa300 Okt 07 20:45:43 jak-t480s kernel: R10: R11: 0002 R12: 0010 Okt 07 20:45:43 jak-t480s kernel: R13: 9eb458df5348 R14: 9eb458df5370 R15: 9eb458df5380 Okt 07 20:45:43 jak-t480s kernel: FS: 7f2974d35b00() GS:9eb8e744() knlGS: Okt 07 20:45:43 jak-t480s kernel: CS: 0010 DS: ES: CR0: 80050033 Okt 07 20:45:43 jak-t480s kernel: CR2: 002c CR3: 00041a232004 CR4: 003606e0 Okt 07 20:45:43 jak-t480s kernel: Call Trace: Okt 07 20:45:43 jak-t480s kernel: seq_read+0x95/0x470 Okt 07 20:45:43 jak-t480s kernel: ? security_file_permission+0x150/0x160 Okt 07 20:45:43 jak-t480s kernel: vfs_read+0xaa/0x190 Okt 07 20:45:43 jak-t480s kernel: ksys_read+0x67/0xe0 Okt 07 20:45:43 jak-t480s kernel: __x64_sys_read+0x1a/0x20 Okt 07 20:45:43 jak-t480s kernel: do_syscall_64+0x49/0xc0 Okt 07 20:45:43 jak-t480s kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Okt 07 20:45:43 jak-t480s kernel: RIP: 0033:0x7f2977f93cec Okt 07 20:45:43 jak-t480s kernel: Code: ec 28 48 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 f9 7c f8 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 34 44 89 c7 48 89 44 24 08 e8 4f 7d f8 ff 48 Okt 07 20:45:43 jak-t480s kernel: RSP: 002b:7ffc233bb840 EFLAGS: 0246 ORIG_RAX: Okt 07 20:45:43 jak-t480s kernel: RAX: ffda RBX: 560ac1a5da20 RCX: 7f2977f93cec Okt 07 20:45:43 jak-t480s kernel: RDX: 1000 RSI: 7ffc233bb940 RDI: 0010 Okt 07 20:45:43 jak-t480s kernel: RBP: 7f29780704c0 R08: R09: 560ac1a731d0 Okt 07 20:45:43 jak-t480s kernel: R10: 560ac1a6fdc0 R11: 0246 R12: 1000 Okt 07 20:45:43 jak-t480s kernel: R13: 7ffc233bb940 R14: 0d68 R15: 7f297806f8c0 Okt 07 20:45:43 jak-t480s kernel: Modules linked in: unix_diag snd_usb_audio snd_usbmidi_lib scsi_transport_iscsi acpi_call(O) veth ip6table_nat zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) nf_tables nfnetlink ccm rfcomm ipt_REJECT nf_reject_ipv4 xt_> Okt 07 20:45:43 jak-t480s kernel: snd_seq_midi ledtrig_audio elan_i2c ee1004 snd_pcm cfg80211 mei snd_seq_midi_event intel_pch_thermal snd_rawmidi ucsi_acpi typec_ucsi processor_thermal_device snd_seq intel_xhci_usb_role_switch intel_rapl_common roles intel_soc_dts_iosf typec snd_s> Okt 07 20:45:43 jak-t480s kernel: xhci_pci_renesas wmi video Okt 07 20:45:43 jak-t480s kernel: CR2: 002c Okt 07 20:45:43 jak-t480s kernel: ---[ end trace 78901de378649ad1 ]--- Okt 07 20:45:43 jak-t480s kernel: RIP: 0010:tpm2_bios_measurements_start+0x38/0x1f0 Okt 07 20:45:43 jak-t480s kernel: Code: 55 41 54 53 48 83 ec 30 4c 8b 16 65 48 8b 04 25 28 00 00 00 48 89 45 d0 48 8b 47 70 4c 8b a0 d0 06 00 00 48 8b 88 d8 06 00 00 <41> 8b 5c 24 1c 48 89 4d b0 48 89 d8 48 83 c3 20 4d 85 d2 75 31 4c Okt 07 20:45:43 jak-t480s kernel: RSP: 0018:ae1880903de8 EFLAGS: 00010286 Okt 07 20:45:43 jak-t480s kernel: RAX: 9eb8e2f8e000 RBX: RCX: 0010 Okt 07 20:45:43 jak-t480s kernel: RDX: 1000 RSI: 9eb5311500a0 RDI: 9eb531150078 Okt 07 20:45:43 jak-t480s kernel: RBP: ae1880903e40 R08: ce187ec270e0 R09: 9eb7e1e62bc0 Okt 07 20:45:43 jak-t480s kernel: R10: R11: 0002 R12: 0010 Okt 07 20:45:43 jak-t480s kernel: R13: 9eb531150078 R14: 9eb5311500a0 R15: 9eb5311500b0 Okt 07 20:45:43 jak-t480s kernel: FS: 7f2974d35b00() GS:9eb8e744() knlGS: Okt 07
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
The issues of bug 1892826 seem resolved. I also have found what the problem here is, it comes down to: Oct 08 08:23:50 groovy-testEPYC libvirtd[2176]: XML error: failed to parse xml document '/usr/share/libvirt/cpu_map/x86_EPYC-Rome.xml' Which is right it isn't installed in my test build. But we don't explicitly list these files in the packaging: debian/libvirt0.install:5:usr/share/libvirt/cpu_map/* So I'd expect that this works, unless we have missed to install it in the upstream build system. Maybe since master has already switched to meson in 6.7 and are post: https://gitlab.com/libvirt/libvirt/-/commit/dfa2f42a046cce85d9c07869bd765dfbcaab2ab9 But we are on 6.6 we need a change to make this file available. So we need a replacement for (this is no reocket science, in fact it is as it was in the suggested debdiff already): --- a/src/cpu_map/meson.build +++ b/src/cpu_map/meson.build @@ -32,6 +32,7 @@ cpumap_data = [ 'x86_Dhyana.xml', 'x86_EPYC-IBPB.xml', 'x86_EPYC.xml', + 'x86_EPYC-Rome.xml', 'x86_features.xml', 'x86_Haswell-IBRS.xml', 'x86_Haswell-noTSX-IBRS.xml', But furthermore we will also need the following cleanup: https://gitlab.com/libvirt/libvirt/-/commit/3bf6f9fe22dfbd3c1dcc614b31f2f4fe8b71a2f2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Fix Committed Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will only work if the target is updated as well. [Other Info] * This is the first build since glibc 2.32 arrived in groovy, hence we need to be careful of the fix done for bug 1892826. It has to be checked if the linking is fine after the rebuild. The workload still works in groovy despite 2.32 being present (I'd ahve expected it doesn't), so we will keep the revert as-is for now. To be sure that adds two tests that shall be done: - check the linking to point to libtirpc instead of glibc $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL Was pointing to glibc, does it still and if so does it work (see below)? - run the autopkgtest cases as the LXC tests would trigger an issue if there is one ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
Note the fixup patch removing monitor flag: https://gitlab.com/libvirt/libvirt/-/commit/3bf6f9fe22dfbd3c1dcc614b31f2f4fe8b71a2f2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Fix Committed Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will only work if the target is updated as well. [Other Info] * This is the first build since glibc 2.32 arrived in groovy, hence we need to be careful of the fix done for bug 1892826. It has to be checked if the linking is fine after the rebuild. The workload still works in groovy despite 2.32 being present (I'd ahve expected it doesn't), so we will keep the revert as-is for now. To be sure that adds two tests that shall be done: - check the linking to point to libtirpc instead of glibc $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL Was pointing to glibc, does it still and if so does it work (see below)? - run the autopkgtest cases as the LXC tests would trigger an issue if there is one ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm -nographic $ qemu-system-x86_64 -cpu EPYC-v3 -machine pc-q35-focal,accel=kvm -nographic [Regression Potential] * This adds new CPU types to the list of known CPUs defining their name and features. Generally the changes are contained to those new types and only active when selected - and usually only selectable on such new machines. Therefore not a lot should change for other users. One thing thou, if a user selected an unversioned type (which in this case only can be "EPYC") by default it will pick the latest
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Affects me as well on Ubuntu 20.04 and DELL Latitude 5310 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895718] Re: Fix non-working NVMe after S3
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1895718 Title: Fix non-working NVMe after S3 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Status in linux-oem-5.6 source package in Groovy: Won't Fix Bug description: [Impact] KIOXIA NVMe has a 10% chance to stop working after S3. [Fix] Enable ACS quirk on Intel CML root port. [Test] With the patch applied, KIOXIA NVMe always works after S3. [Regression Potential] ACS works at hardware level, so I can't really assess the risk of regression. Since Intel confirmed CML also needs ACS quirk, we can only trust them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898988] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898988 Title: Random UI crashes Status in linux package in Ubuntu: Confirmed Bug description: I have had two spontaneous crashes in three days, with this in the syslog: Oct 8 09:19:57 alhazen kernel: [ 1532.621173] [ cut here ] Oct 8 09:19:57 alhazen kernel: [ 1532.621292] WARNING: CPU: 13 PID: 8346 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_resource.c:3194 dcn20_validate_bandwidth_fp+0x87/0xc0 [amdgpu] Oct 8 09:19:57 alhazen kernel: [ 1532.621301] Modules linked in: vhost_net vhost tap vhost_iotlb snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_counter nft_chain_nat nf_nat nf_connt rack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nf_tables nfnetlink bridge stp llc binfmt_misc nls_iso8859_1 amd64_edac_mod edac_mce_amd kvm_amd kvm snd_hda_codec_realtek rapl snd_hda_codec_generic eeepc_wmi ledtrig_audio serio_raw asus_wmi snd_hda_codec _hdmi sparse_keymap efi_pstore video wmi_bmof snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_seq_midi gspca_vc032x joydev snd_seq_midi_event uvcvideo gspca_zc3xx snd_rawmidi gspca_main snd_hwdep videobuf2_v malloc videobuf2_memops videobuf2_v4l2 input_leds k10temp videobuf2_common snd_pcm snd_seq snd_seq_device snd_timer snd ccp soundcore mac_hid sch_fq_codel cuse nct6775 hwmon_vid v4l2loopback(OE) videodev mc parport_pc ppdev lp parport ip_tables x_tabl es autofs4 dm_crypt uas usb_storage Oct 8 09:19:57 alhazen kernel: [ 1532.621333] hid_generic usbhid hid amdgpu iommu_v2 gpu_sched ttm crct10dif_pclmul mxm_wmi crc32_pclmul ghash_clmulni_intel drm_kms_helper aesni_intel syscopyarea sysfillrect crypto_simd sysimgblt cryptd fb_sys_fops glue_helper cec rc_core drm igb nvme ahci xhci_pci dca libahci i2c_piix4 xhci_pci_renesas i2c_algo_bit nvme_core wmi Oct 8 09:19:57 alhazen kernel: [ 1532.621348] CPU: 13 PID: 8346 Comm: kworker/13:3 Tainted: G OE 5.8.0-20-lowlatency #21-Ubuntu Oct 8 09:19:57 alhazen kernel: [ 1532.621349] Hardware name: System manufacturer System Product Name/PRIME X570-PRO, BIOS 2606 08/13/2020 Oct 8 09:19:57 alhazen kernel: [ 1532.621369] Workqueue: events drm_mode_rmfb_work_fn [drm] Oct 8 09:19:57 alhazen kernel: [ 1532.621478] RIP: 0010:dcn20_validate_bandwidth_fp+0x87/0xc0 [amdgpu] Oct 8 09:19:57 alhazen kernel: [ 1532.621480] Code: 24 a8 1e 00 00 75 29 31 d2 4c 89 e6 4c 89 ef f2 41 0f 11 84 24 d8 25 00 00 e8 05 fd ff ff 89 c2 41 22 94 24 a8 1e 00 00 75 26 <0f> 0b eb 02 75 cd 49 89 9c 24 d8 25 00 00 5b 41 5c 41 5d 5d c3 ba Oct 8 09:19:57 alhazen kernel: [ 1532.621483] RSP: 0018:b455875d3c18 EFLAGS: 00010246 Oct 8 09:19:57 alhazen kernel: [ 1532.621484] RAX: 0001 RBX: 40794000 RCX: 1153800d Oct 8 09:19:57 alhazen kernel: [ 1532.621485] RDX: RSI: fba65b79459e0f73 RDI: 000311a0 Oct 8 09:19:57 alhazen kernel: [ 1532.621486] RBP: b455875d3c30 R08: 9a9ab7be R09: 9a9ad0da Oct 8 09:19:57 alhazen kernel: [ 1532.621487] R10: 9a9abdb88000 R11: 00010001 R12: 9a9ab7be Oct 8 09:19:57 alhazen kernel: [ 1532.621487] R13: 9a9ad0da R14: 9a9ad3e37800 R15: 9a9ab7be Oct 8 09:19:57 alhazen kernel: [ 1532.621489] FS: () GS:9a9aeed4() knlGS: Oct 8 09:19:57 alhazen kernel: [ 1532.621490] CS: 0010 DS: ES: CR0: 80050033 Oct 8 09:19:57 alhazen kernel: [ 1532.621490] CR2: 7f43ac194850 CR3: 00036c80a000 CR4: 00340ee0 Oct 8 09:19:57 alhazen kernel: [ 1532.621491] Call Trace: Oct 8 09:19:57 alhazen kernel: [ 1532.621607] dcn20_validate_bandwidth+0x29/0x40 [amdgpu] Oct 8 09:19:57 alhazen kernel: [ 1532.621721] dc_validate_global_state+0x2f6/0x390 [amdgpu] Oct 8 09:19:57 alhazen kernel: [ 1532.621830] amdgpu_dm_atomic_check+0x87c/0x8a0 [amdgpu] Oct 8 09:19:57 alhazen kernel: [ 1532.621853] drm_atomic_check_only+0x1e9/0x360 [drm] Oct 8 09:19:57 alhazen kernel: [ 1532.621869] drm_atomic_commit+0x18/0x50 [drm] Oct 8 09:19:57 alhazen kernel: [ 1532.621884] atomic_remove_fb+0x25b/0x2d0 [drm] Oct 8 09:19:57 alhazen kernel: [ 1532.621900] drm_framebuffer_remove+0x5c/0xa0 [drm] Oct 8 09:19:57 alhazen kernel: [ 1532.621912] drm_mode_rmfb_work_fn+0x41/0x50 [drm] Oct 8 09:19:57 alhazen kernel: [ 1532.621917] process_one_work+0x1df/0x3d0 Oct 8 09:19:57 alhazen kernel: [ 1532.621921] worker_thread+0x205/0x350 Oct 8 09:19:57 alhazen kernel: [ 1532.621923] ? rescuer_thread+0x390/0x390 Oct 8 09:19:57 alhazen kernel: [ 1532.621924]
[Kernel-packages] [Bug 1892288] Re: Comet Lake PCH-H RAID not support on Ubuntu20.04
Koba and I got together to discuss and investigate the issue within this
week and last week. It seems to us that there is something wrong with
the OEM build because the issue can still be observed on OEM build after
upgrading the Kernel to 5.6.0.1029. Details are as follows.
# Stock Ubuntu & 5.6.0.1030-oem
- Test result: Issue cannot be observed. After configuring as RAID mode, the
system can boot into the desktop
# OEM build (amd64-X00-20200821-272) & 5.6.0.1030-oem
- Test result: Issue still can be observed. After configuring as RAID mode,
the system cannot boot into the desktop.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1892288
Title:
Comet Lake PCH-H RAID not support on Ubuntu20.04
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
Fix Released
Bug description:
[Impact]
Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
[Fix]
Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
[test]
[Regression Potential]
Low. Just add a PCI id for the sata/ahci raid.
== Original ==
As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
{ PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */
If Thinkstation P340 configured as RAID mode, It can not find any RAID volume
disk.
please update such support. Thanks.
Regards,
Jiqi.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1892288/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892288] Re: Comet Lake PCH-H RAID not support on Ubuntu20.04
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1892288
Title:
Comet Lake PCH-H RAID not support on Ubuntu20.04
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
Fix Released
Bug description:
[Impact]
Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
[Fix]
Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
[test]
[Regression Potential]
Low. Just add a PCI id for the sata/ahci raid.
== Original ==
As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
{ PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */
If Thinkstation P340 configured as RAID mode, It can not find any RAID volume
disk.
please update such support. Thanks.
Regards,
Jiqi.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1892288/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898988] Re: Random UI crashes
Since it is a graphics crash, this is probably relevant, too: 08:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev c5) 09:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch 0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5) 0a:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898988 Title: Random UI crashes Status in linux package in Ubuntu: New Bug description: I have had two spontaneous crashes in three days, with this in the syslog: Oct 8 09:19:57 alhazen kernel: [ 1532.621173] [ cut here ] Oct 8 09:19:57 alhazen kernel: [ 1532.621292] WARNING: CPU: 13 PID: 8346 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_resource.c:3194 dcn20_validate_bandwidth_fp+0x87/0xc0 [amdgpu] Oct 8 09:19:57 alhazen kernel: [ 1532.621301] Modules linked in: vhost_net vhost tap vhost_iotlb snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_counter nft_chain_nat nf_nat nf_connt rack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nf_tables nfnetlink bridge stp llc binfmt_misc nls_iso8859_1 amd64_edac_mod edac_mce_amd kvm_amd kvm snd_hda_codec_realtek rapl snd_hda_codec_generic eeepc_wmi ledtrig_audio serio_raw asus_wmi snd_hda_codec _hdmi sparse_keymap efi_pstore video wmi_bmof snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_seq_midi gspca_vc032x joydev snd_seq_midi_event uvcvideo gspca_zc3xx snd_rawmidi gspca_main snd_hwdep videobuf2_v malloc videobuf2_memops videobuf2_v4l2 input_leds k10temp videobuf2_common snd_pcm snd_seq snd_seq_device snd_timer snd ccp soundcore mac_hid sch_fq_codel cuse nct6775 hwmon_vid v4l2loopback(OE) videodev mc parport_pc ppdev lp parport ip_tables x_tabl es autofs4 dm_crypt uas usb_storage Oct 8 09:19:57 alhazen kernel: [ 1532.621333] hid_generic usbhid hid amdgpu iommu_v2 gpu_sched ttm crct10dif_pclmul mxm_wmi crc32_pclmul ghash_clmulni_intel drm_kms_helper aesni_intel syscopyarea sysfillrect crypto_simd sysimgblt cryptd fb_sys_fops glue_helper cec rc_core drm igb nvme ahci xhci_pci dca libahci i2c_piix4 xhci_pci_renesas i2c_algo_bit nvme_core wmi Oct 8 09:19:57 alhazen kernel: [ 1532.621348] CPU: 13 PID: 8346 Comm: kworker/13:3 Tainted: G OE 5.8.0-20-lowlatency #21-Ubuntu Oct 8 09:19:57 alhazen kernel: [ 1532.621349] Hardware name: System manufacturer System Product Name/PRIME X570-PRO, BIOS 2606 08/13/2020 Oct 8 09:19:57 alhazen kernel: [ 1532.621369] Workqueue: events drm_mode_rmfb_work_fn [drm] Oct 8 09:19:57 alhazen kernel: [ 1532.621478] RIP: 0010:dcn20_validate_bandwidth_fp+0x87/0xc0 [amdgpu] Oct 8 09:19:57 alhazen kernel: [ 1532.621480] Code: 24 a8 1e 00 00 75 29 31 d2 4c 89 e6 4c 89 ef f2 41 0f 11 84 24 d8 25 00 00 e8 05 fd ff ff 89 c2 41 22 94 24 a8 1e 00 00 75 26 <0f> 0b eb 02 75 cd 49 89 9c 24 d8 25 00 00 5b 41 5c 41 5d 5d c3 ba Oct 8 09:19:57 alhazen kernel: [ 1532.621483] RSP: 0018:b455875d3c18 EFLAGS: 00010246 Oct 8 09:19:57 alhazen kernel: [ 1532.621484] RAX: 0001 RBX: 40794000 RCX: 1153800d Oct 8 09:19:57 alhazen kernel: [ 1532.621485] RDX: RSI: fba65b79459e0f73 RDI: 000311a0 Oct 8 09:19:57 alhazen kernel: [ 1532.621486] RBP: b455875d3c30 R08: 9a9ab7be R09: 9a9ad0da Oct 8 09:19:57 alhazen kernel: [ 1532.621487] R10: 9a9abdb88000 R11: 00010001 R12: 9a9ab7be Oct 8 09:19:57 alhazen kernel: [ 1532.621487] R13: 9a9ad0da R14: 9a9ad3e37800 R15: 9a9ab7be Oct 8 09:19:57 alhazen kernel: [ 1532.621489] FS: () GS:9a9aeed4() knlGS: Oct 8 09:19:57 alhazen kernel: [ 1532.621490] CS: 0010 DS: ES: CR0: 80050033 Oct 8 09:19:57 alhazen kernel: [ 1532.621490] CR2: 7f43ac194850 CR3: 00036c80a000 CR4: 00340ee0 Oct 8 09:19:57 alhazen kernel: [ 1532.621491] Call Trace: Oct 8 09:19:57 alhazen kernel: [ 1532.621607] dcn20_validate_bandwidth+0x29/0x40 [amdgpu] Oct 8 09:19:57 alhazen kernel: [ 1532.621721] dc_validate_global_state+0x2f6/0x390 [amdgpu] Oct 8 09:19:57 alhazen kernel: [ 1532.621830] amdgpu_dm_atomic_check+0x87c/0x8a0 [amdgpu] Oct 8 09:19:57 alhazen kernel: [ 1532.621853] drm_atomic_check_only+0x1e9/0x360 [drm] Oct 8 09:19:57 alhazen kernel: [ 1532.621869] drm_atomic_commit+0x18/0x50 [drm] Oct 8 09:19:57 alhazen kernel: [ 1532.621884] atomic_remove_fb+0x25b/0x2d0 [drm] Oct 8 09:19:57 alhazen kernel: [ 1532.621900]
[Kernel-packages] [Bug 1898988] [NEW] Random UI crashes
Public bug reported: I have had two spontaneous crashes in three days, with this in the syslog: Oct 8 09:19:57 alhazen kernel: [ 1532.621173] [ cut here ] Oct 8 09:19:57 alhazen kernel: [ 1532.621292] WARNING: CPU: 13 PID: 8346 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_resource.c:3194 dcn20_validate_bandwidth_fp+0x87/0xc0 [amdgpu] Oct 8 09:19:57 alhazen kernel: [ 1532.621301] Modules linked in: vhost_net vhost tap vhost_iotlb snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_counter nft_chain_nat nf_nat nf_connt rack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nf_tables nfnetlink bridge stp llc binfmt_misc nls_iso8859_1 amd64_edac_mod edac_mce_amd kvm_amd kvm snd_hda_codec_realtek rapl snd_hda_codec_generic eeepc_wmi ledtrig_audio serio_raw asus_wmi snd_hda_codec _hdmi sparse_keymap efi_pstore video wmi_bmof snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_seq_midi gspca_vc032x joydev snd_seq_midi_event uvcvideo gspca_zc3xx snd_rawmidi gspca_main snd_hwdep videobuf2_v malloc videobuf2_memops videobuf2_v4l2 input_leds k10temp videobuf2_common snd_pcm snd_seq snd_seq_device snd_timer snd ccp soundcore mac_hid sch_fq_codel cuse nct6775 hwmon_vid v4l2loopback(OE) videodev mc parport_pc ppdev lp parport ip_tables x_tabl es autofs4 dm_crypt uas usb_storage Oct 8 09:19:57 alhazen kernel: [ 1532.621333] hid_generic usbhid hid amdgpu iommu_v2 gpu_sched ttm crct10dif_pclmul mxm_wmi crc32_pclmul ghash_clmulni_intel drm_kms_helper aesni_intel syscopyarea sysfillrect crypto_simd sysimgblt cryptd fb_sys_fops glue_helper cec rc_core drm igb nvme ahci xhci_pci dca libahci i2c_piix4 xhci_pci_renesas i2c_algo_bit nvme_core wmi Oct 8 09:19:57 alhazen kernel: [ 1532.621348] CPU: 13 PID: 8346 Comm: kworker/13:3 Tainted: G OE 5.8.0-20-lowlatency #21-Ubuntu Oct 8 09:19:57 alhazen kernel: [ 1532.621349] Hardware name: System manufacturer System Product Name/PRIME X570-PRO, BIOS 2606 08/13/2020 Oct 8 09:19:57 alhazen kernel: [ 1532.621369] Workqueue: events drm_mode_rmfb_work_fn [drm] Oct 8 09:19:57 alhazen kernel: [ 1532.621478] RIP: 0010:dcn20_validate_bandwidth_fp+0x87/0xc0 [amdgpu] Oct 8 09:19:57 alhazen kernel: [ 1532.621480] Code: 24 a8 1e 00 00 75 29 31 d2 4c 89 e6 4c 89 ef f2 41 0f 11 84 24 d8 25 00 00 e8 05 fd ff ff 89 c2 41 22 94 24 a8 1e 00 00 75 26 <0f> 0b eb 02 75 cd 49 89 9c 24 d8 25 00 00 5b 41 5c 41 5d 5d c3 ba Oct 8 09:19:57 alhazen kernel: [ 1532.621483] RSP: 0018:b455875d3c18 EFLAGS: 00010246 Oct 8 09:19:57 alhazen kernel: [ 1532.621484] RAX: 0001 RBX: 40794000 RCX: 1153800d Oct 8 09:19:57 alhazen kernel: [ 1532.621485] RDX: RSI: fba65b79459e0f73 RDI: 000311a0 Oct 8 09:19:57 alhazen kernel: [ 1532.621486] RBP: b455875d3c30 R08: 9a9ab7be R09: 9a9ad0da Oct 8 09:19:57 alhazen kernel: [ 1532.621487] R10: 9a9abdb88000 R11: 00010001 R12: 9a9ab7be Oct 8 09:19:57 alhazen kernel: [ 1532.621487] R13: 9a9ad0da R14: 9a9ad3e37800 R15: 9a9ab7be Oct 8 09:19:57 alhazen kernel: [ 1532.621489] FS: () GS:9a9aeed4() knlGS: Oct 8 09:19:57 alhazen kernel: [ 1532.621490] CS: 0010 DS: ES: CR0: 80050033 Oct 8 09:19:57 alhazen kernel: [ 1532.621490] CR2: 7f43ac194850 CR3: 00036c80a000 CR4: 00340ee0 Oct 8 09:19:57 alhazen kernel: [ 1532.621491] Call Trace: Oct 8 09:19:57 alhazen kernel: [ 1532.621607] dcn20_validate_bandwidth+0x29/0x40 [amdgpu] Oct 8 09:19:57 alhazen kernel: [ 1532.621721] dc_validate_global_state+0x2f6/0x390 [amdgpu] Oct 8 09:19:57 alhazen kernel: [ 1532.621830] amdgpu_dm_atomic_check+0x87c/0x8a0 [amdgpu] Oct 8 09:19:57 alhazen kernel: [ 1532.621853] drm_atomic_check_only+0x1e9/0x360 [drm] Oct 8 09:19:57 alhazen kernel: [ 1532.621869] drm_atomic_commit+0x18/0x50 [drm] Oct 8 09:19:57 alhazen kernel: [ 1532.621884] atomic_remove_fb+0x25b/0x2d0 [drm] Oct 8 09:19:57 alhazen kernel: [ 1532.621900] drm_framebuffer_remove+0x5c/0xa0 [drm] Oct 8 09:19:57 alhazen kernel: [ 1532.621912] drm_mode_rmfb_work_fn+0x41/0x50 [drm] Oct 8 09:19:57 alhazen kernel: [ 1532.621917] process_one_work+0x1df/0x3d0 Oct 8 09:19:57 alhazen kernel: [ 1532.621921] worker_thread+0x205/0x350 Oct 8 09:19:57 alhazen kernel: [ 1532.621923] ? rescuer_thread+0x390/0x390 Oct 8 09:19:57 alhazen kernel: [ 1532.621924] kthread+0x145/0x170 Oct 8 09:19:57 alhazen kernel: [ 1532.621926] ? kthread_create_on_node+0x60/0x60 Oct 8 09:19:57 alhazen kernel: [ 1532.621928] ret_from_fork+0x22/0x30 Oct 8 09:19:57 alhazen kernel: [ 1532.621929] ---[ end trace e76afab44e4cb434 ]--- First time the UI just locked up, but I could still switch to another console and restart things, today the screens just went black and I got a login
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
Test build in PPA: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4303 But there are some issues when checking for known models: Current: ... Skylake-Client-IBRS ... qemu64 ... New build: ... Something went wrong and broke any host-model or custom named CPU support. Need to debug what exactly happened. Furthermore as expected bug 1892826 provides some non-fun (updates about that there). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Fix Committed Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will only work if the target is updated as well. [Other Info] * This is the first build since glibc 2.32 arrived in groovy, hence we need to be careful of the fix done for bug 1892826. It has to be checked if the linking is fine after the rebuild. The workload still works in groovy despite 2.32 being present (I'd ahve expected it doesn't), so we will keep the revert as-is for now. To be sure that adds two tests that shall be done: - check the linking to point to libtirpc instead of glibc $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL Was pointing to glibc, does it still and if so does it work (see below)? - run the autopkgtest cases as the LXC tests would trigger an issue if there is one ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm -nographic $ qemu-system-x86_64 -cpu EPYC-v3 -machine pc-q35-focal,accel=kvm -nographic [Regression Potential] * This adds new CPU types to the list of known CPUs defining their name and features. Generally the changes
[Kernel-packages] [Bug 1895803] Re: uvcvideo: add mapping for HEVC payloads
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895803 Title: uvcvideo: add mapping for HEVC payloads Status in HWE Next: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Bug description: == Impact == Add mapping for HEVC so that uvcvideo can support the format. == Fixes == The commit "media: uvcvideo: Add mapping for HEVC payloads", which is already in the maintainer tree: https://patchwork.kernel.org/patch/11577395/ https://git.linuxtv.org/media_tree.git/commit/?id=40b222b56ea81aa636a4aa7a84939786369e726b For 4.15 we also need the "media: videodev2.h: Add v4l2 definition for HEVC" from mainline. == Regression Potential == Low since the patch only introduces a new format. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894895] Re: [linux-azure][hibernation] ]VM hangs after hibernation/resume if the VM has SRIOV NIC and has been deallocated
The fix is in the mainline kernel now: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19873eec7e13fda140a0ebc75d6664e57c00bfb1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1894895 Title: [linux-azure][hibernation] ]VM hangs after hibernation/resume if the VM has SRIOV NIC and has been deallocated Status in linux-azure package in Ubuntu: New Bug description: Description of problem: On Azure, if the VM is Stopped(deallocated) and later Started, the VF NIC's VMBus Instance GUID may change, and as a result hibernation/resume can hang forever. This happens to the latest stable release of the linux-azure 5.4.0-1023.23 kernel and the latest mainline linux kernel. How reproducible: 100% Steps to Reproduce: 1. Start a VM in Azure that supports Accelerated Networking, and enable hibernation properly (please refer to https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/comments/14 ) 2. Do hibernation from serial console # systemctl hibernate 4. After the VM state changes to "Stopped", click "Stop" button from Azure portal to change the VM state to Stopped(deallocated) 5. Wait for some time (e.g. 10 minutes? 1 hour?), and click the "Start" button to start the VM, and then check the boot-up process from the serial console. Actual results: Can not boot up. VM hangs after resume. Starting Resume from hibernation us…6c7-2c0c-491e-adcf-b625d69faf76... [ 19.822747] PM: resume from hibernation [ 19.836693] Freezing user space processes ... (elapsed 0.003 seconds) done. [ 19.846968] OOM killer disabled. [ 19.850236] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 20.542934] PM: Using 1 thread(s) for decompression [ 20.548250] PM: Loading and decompressing image data (559580 pages)... [ 22.844964] PM: Image loading progress: 0% [ 28.131327] PM: Image loading progress: 10% [ 32.346480] PM: Image loading progress: 20% [ 37.453971] PM: Image loading progress: 30% [ 40.834525] PM: Image loading progress: 40% [ 42.980629] PM: Image loading progress: 50% [ 44.342959] PM: Image loading progress: 60% [ 45.506197] PM: Image loading progress: 70% [ 46.800445] PM: Image loading progress: 80% [ 48.010185] PM: Image loading progress: 90% [ 49.045671] PM: Image loading done [ 49.050419] PM: Read 2238320 kbytes in 28.48 seconds (78.59 MB/s) [ 49.074198] printk: Suspending console(s) (use no_console_suspend to debug) (The VM hangs here forever) BUG FIX: A workaround patch is available and is being reviewed: https://lkml.org/lkml/2020/9/4/1270 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1894895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894893] Re: [linux-azure][hibernation] GPU device no longer working after resume from hibernation in NV6 VM size
The fix is in the PCI tree now: "PCI: hv: Fix hibernation in case interrupts are not re-create" ( https://git.kernel.org/pub/scm/linux/kernel/git/lpieralisi/pci.git/commit/?h=pci/hv=915cff7f38c5e4d47f187f8049245afc2cb3e503 ) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1894893 Title: [linux-azure][hibernation] GPU device no longer working after resume from hibernation in NV6 VM size Status in linux-azure package in Ubuntu: New Bug description: There are failed logs after resume from hibernation in NV6 (GPU passthrough size) VM in Azure: [ 1432.153730] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() failed: 0x5 [ 1432.167910] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() failed: 0x5 This happens to the latest stable release of the linux-azure 5.4.0-1023.23 kernel and the latest mainline linux kernel. How reproducible: 100% Steps to Reproduce: 1. Start a Standard_NV6 VM in Azure and enable hibernation properly (please refer to https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/comments/14 ) E.g. here I create a Generation-1 Ubuntu 20.04 Standard NV6_Promo (6 vcpus, 56 GiB memory) VM in East US 2. 2. Make sure the in-kernel open-source nouveau driver is loaded, or blacklist the nouveau driver and install the official Nvidia GPU driver (please follow https://docs.microsoft.com/en-us/azure/virtual- machines/linux/n-series-driver-setup : "Install GRID drivers on NV or NVv3-series VMs" -- the most important step to run the "./NVIDIA- Linux-x86_64-grid.run".) 3. Run hibernation from serial console # systemctl hibernate 4. After hibernation finishes, start VM and check dmesg # dmesg|grep fail Actual results: [ 1432.153730] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() failed: 0x5 [ 1432.167910] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() failed: 0x5 And /proc/interrupts shows that the GPU interrupts are no longer happening. Expected results: No failed logs, and the GPU interrupt should still happen after hibernation. BUG FIX: I made a fix here: https://lkml.org/lkml/2020/9/4/1268. Without the patch, we see the error "hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() failed: 0x5" during hibernation when the VM has the Nvidia GPU driver loaded, and after hibernation the GPU driver can no longer receive any MSI/MSI-X interrupts when we check /proc/interrupts. With the patch, we should no longer see the error, and the GPU driver should still receive interrupts after hibernation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1894893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
** Description changed: [Impact] * CPU definitions are added to libvirt as these CPUs are known -and added to qemu for execution. + and added to qemu for execution. And due to that over time some are considered missing in -former releases. + former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions -(no control flow changes) + (no control flow changes) [Test Case] - * Check if it has an EPYC-Rome entry in -/usr/share/libvirt/cpu_map/index.xml and the file included -there exists. + * Check if it has an EPYC-Rome entry in + /usr/share/libvirt/cpu_map/index.xml and the file included + there exists. - * Define a guest like: - - EPYC-Rome - -You can only "really" start this on a system with the -matching HW. But even on others it will change from: - error: internal error: Unknown CPU model EPYC-Rome -to being unable to start for some features missing. + * Define a guest like: + + EPYC-Rome + + You can only "really" start this on a system with the + matching HW. But even on others it will change from: + error: internal error: Unknown CPU model EPYC-Rome + to being unable to start for some features missing. - * libvirt probes a system if a named cpu can be used, after the -fix this should include EPYC-Rome -$ virsh domcapabilities | grep EPYC - EPYC-IBPB - EPYC + * libvirt probes a system if a named cpu can be used, after the + fix this should include EPYC-Rome + $ virsh domcapabilities | grep EPYC + EPYC-IBPB + EPYC [Regression Potential] - * Usually these type additions are safe unless they add control flow -changes (e.g. to handle yet unknown types of registers or such) but -that isn't the case here. -A regression if any is to be expected on systems that are close to the -newly added type(s). Those will after the update be detected as such -if e.g. host-model is used. If then running on a mixed cluster of -updated/non-updated systems migrations will only work if the target is -updated as well. + * Usually these type additions are safe unless they add control flow + changes (e.g. to handle yet unknown types of registers or such) but + that isn't the case here. + A regression if any is to be expected on systems that are close to the + newly added type(s). Those will after the update be detected as such + if e.g. host-model is used. If then running on a mixed cluster of + updated/non-updated systems migrations will only work if the target is + updated as well. [Other Info] - - * This is the first build since glibc 2.32 arrived in groovy, hence we -need to revert the revert done for bug 1892826. It has to be checked -if the linking is fine afterwards. That adds two tests that shall be -done. -- check the linking to point to libtirpc instead of glibc - $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL -- run the autopkgtest cases as the LXC tests would trigger an issue if - there is one + * This is the first build since glibc 2.32 arrived in groovy, hence we + need to be careful of the fix done for bug 1892826. +It has to be checked if the linking is fine after the rebuild. +The workload still works in groovy despite 2.32 being present (I'd ahve +expected it doesn't), so we will keep the revert as-is for now. +To be sure that adds two tests that shall be done: + - check the linking to point to libtirpc instead of glibc + $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL + Was pointing to glibc, does it still and if so does it work (see + below)? + - run the autopkgtest cases as the LXC tests would trigger an issue if + there is one ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor
[Kernel-packages] [Bug 1888001] Re: Focal minimal cloud image: failed to apply kernel variables
*** This bug is a duplicate of bug 1866149 *** https://bugs.launchpad.net/bugs/1866149 ** This bug has been marked a duplicate of bug 1866149 CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888001 Title: Focal minimal cloud image: failed to apply kernel variables Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Overview --- It appears the Focal minimal images have always shipped with a failing systemd unit: "systemd-sysctl.service" with the error "Couldn't write '4194304' to 'kernel/pid_max': Invalid argument" Expected results --- $ sudo systemctl list-units --failed --no-legend # Return no failed units Actual results --- $ sudo systemctl list-units --failed --no-legend systemd-sysctl.service loaded failed failed Apply Kernel Variables From the journal: Jul 20 12:18:53 ubuntu systemd[1]: systemd-sysctl.service: Main process exit ed, code=exited, status=1/FAILURE Jul 20 12:18:53 ubuntu systemd[1]: systemd-sysctl.service: Faile d with result 'exit-code'. Jul 20 12:18:53 ubuntu systemd[1]: Failed to start Apply Kernel Variables. Jul 20 12:18:53 ubuntu systemd-sysctl[135]: Couldn't write '4194304' to 'ker nel/pid_max': Invalid argument Steps to reproduce --- $ wget https://cloud-images.ubuntu.com/daily/server/minimal/releases/focal/release/ubuntu-20.04-minimal-cloudimg-amd64.img $ multipass launch file:///$(pwd)/ubuntu-20.04-minimal-cloudimg-amd64.img --name=focal-minimal $ multipass exec focal-minimal -- sudo systemctl list-units --failed --no-legend --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1018-kvm root=PARTUUID=4a94aad5-09c7-46a5-aa33-f2f2e03254e7 ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 5.4.0-1018.18-kvm 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-1018-kvm N/A linux-backports-modules-5.4.0-1018-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1018-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1888001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/391963 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Fix Committed Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will only work if the target is updated as well. [Other Info] * This is the first build since glibc 2.32 arrived in groovy, hence we need to revert the revert done for bug 1892826. It has to be checked if the linking is fine afterwards. That adds two tests that shall be done. - check the linking to point to libtirpc instead of glibc $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL - run the autopkgtest cases as the LXC tests would trigger an issue if there is one ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm -nographic $ qemu-system-x86_64 -cpu EPYC-v3 -machine pc-q35-focal,accel=kvm -nographic [Regression Potential] * This adds new CPU types to the list of known CPUs defining their name and features. Generally the changes are contained to those new types and only active when selected - and usually only selectable on such new machines. Therefore not a lot should change for other users. One thing thou, if a user selected an unversioned type (which in this case only can be "EPYC") by default it will pick the latest subversion that applies. In this case the behavior will change and pick EPYC-v3 after the fix. But this is the whole purpose of versioned (stay as is) and unversioned (move with updates) CPU types - so that should be ok. The EPYC-Rome type
[Kernel-packages] [Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model
** Description changed: + [Impact] + + * CPU definitions are added to libvirt as these CPUs are known +and added to qemu for execution. + And due to that over time some are considered missing in +former releases. + + * To really benefit from the new features of these chips + they have to be known, therefore new type additions done by + upstream should be backported if they generally apply and do + not depend on SRU-critical changes. + + * This backports three upstream fixes that just add definitions +(no control flow changes) + + [Test Case] + + * Check if it has an EPYC-Rome entry in +/usr/share/libvirt/cpu_map/index.xml and the file included +there exists. + + * Define a guest like: + + EPYC-Rome + +You can only "really" start this on a system with the +matching HW. But even on others it will change from: + error: internal error: Unknown CPU model EPYC-Rome +to being unable to start for some features missing. + + * libvirt probes a system if a named cpu can be used, after the +fix this should include EPYC-Rome +$ virsh domcapabilities | grep EPYC + EPYC-IBPB + EPYC + + [Regression Potential] + + * Usually these type additions are safe unless they add control flow +changes (e.g. to handle yet unknown types of registers or such) but +that isn't the case here. +A regression if any is to be expected on systems that are close to the +newly added type(s). Those will after the update be detected as such +if e.g. host-model is used. If then running on a mixed cluster of +updated/non-updated systems migrations will only work if the target is +updated as well. + + [Other Info] + + * This is the first build since glibc 2.32 arrived in groovy, hence we +need to revert the revert done for bug 1892826. It has to be checked +if the linking is fine afterwards. That adds two tests that shall be +done. +- check the linking to point to libtirpc instead of glibc + $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL +- run the autopkgtest cases as the LXC tests would trigger an issue if + there is one + + + + ## Qemu SRU ## [Impact] - * CPU definitions are added to qemu as these CPUs are known. -And due to that over time are missing in former releases. + * CPU definitions are added to qemu as these CPUs are known. + And due to that over time are missing in former releases. - * To really benefit from the new features of these chips -they have to be known, therefore new type additions done by -upstream should be backported if they generally apply and do -not depend on SRU-critical changes. + * To really benefit from the new features of these chips + they have to be known, therefore new type additions done by + upstream should be backported if they generally apply and do + not depend on SRU-critical changes. - * This backports two upstream fixes that just add definitions (no -control flow changes) + * This backports two upstream fixes that just add definitions (no + control flow changes) [Test Case] - * Probe qemu for the known CPU types (works on all HW) -$ qemu-system-x86_64 -cpu ? | grep EPYC -Focal without fix: -x86 EPYC (alias configured by machine type) -x86 EPYC-IBPB (alias of EPYC-v2) -x86 EPYC-v1 AMD EPYC Processor -x86 EPYC-v2 AMD EPYC Processor (with IBPB) -Focal with fix also adds: -x86 EPYC-Rome (alias configured by machine type) -x86 EPYC-Rome-v1 AMD EPYC-Rome Processor -x86 EPYC-v3 AMD EPYC Processor + * Probe qemu for the known CPU types (works on all HW) + $ qemu-system-x86_64 -cpu ? | grep EPYC + Focal without fix: + x86 EPYC (alias configured by machine type) + x86 EPYC-IBPB (alias of EPYC-v2) + x86 EPYC-v1 AMD EPYC Processor + x86 EPYC-v2 AMD EPYC Processor (with IBPB) + Focal with fix also adds: + x86 EPYC-Rome (alias configured by machine type) + x86 EPYC-Rome-v1 AMD EPYC-Rome Processor + x86 EPYC-v3 AMD EPYC Processor - * Given such HW is available start a KVM guest using those new types -Since we don't have libvirt support (yet) do so directly in qemu -commandline like (bootloader is enough) -$ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm -nographic -$ qemu-system-x86_64 -cpu EPYC-v3 -machine pc-q35-focal,accel=kvm -nographic + * Given such HW is available start a KVM guest using those new types + Since we don't have libvirt support (yet) do so directly in qemu + commandline like (bootloader is enough) +
[Kernel-packages] [Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model
libvirt changes accepted: https://www.redhat.com/archives/libvir-list/2020-October/msg00493.html And became https://gitlab.com/libvirt/libvirt/-/commit/e06590f1708a599286f3ee3690b3dc50ee525d40 https://gitlab.com/libvirt/libvirt/-/commit/f941639f86f4bc66c106eb1291f1b58cf9e24680 https://gitlab.com/libvirt/libvirt/-/commit/736b8637f691242fd688cf726d22f79d0eb300d3 These mostly apply as-is and one with minimal delta. They are SRUable and therefore not much of an FF problem, but might be stalled a bit. We need to be a bit extra careful for the rebuild with glibc 2.32 due to bug 1892826. But I'll test that ahead of the final upload to groovy. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Fix Committed Bug description: ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm -nographic $ qemu-system-x86_64 -cpu EPYC-v3 -machine pc-q35-focal,accel=kvm -nographic [Regression Potential] * This adds new CPU types to the list of known CPUs defining their name and features. Generally the changes are contained to those new types and only active when selected - and usually only selectable on such new machines. Therefore not a lot should change for other users. One thing thou, if a user selected an unversioned type (which in this case only can be "EPYC") by default it will pick the latest subversion that applies. In this case the behavior will change and pick EPYC-v3 after the fix. But this is the whole purpose of versioned (stay as is) and unversioned (move with updates) CPU types - so that should be ok. The EPYC-Rome type didn't exist in Focal before, so it can't "change" for users. [Other Info] * Depends on the new kernel 5.4.0-49 or later (Currently in focal-proposed) --- Qemu in focal has already support for most (except amd-stibp) flags of this model. Please backport the following patches: https://github.com/qemu/qemu/commit/a16e8dbc043720abcb37fc7dca313e720b4e0f0c https://github.com/qemu/qemu/commit/143c30d4d346831a09e59e9af45afdca0331e819 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
