[Kernel-packages] [Bug 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend)
Oh I didn't realize Ubuntu 20.04 has a version of libc that's a little too old for that. You will need to try an older kernel version that's still newer than the 5.8.0 that caused this bug. Maybe try: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.56/amd64/ Also the "invalid signature" problem I think is caused by Secure Boot. Try disabling Secure Boot in your BIOS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) Status in linux-hwe-5.8 package in Ubuntu: Incomplete Bug description: System freezes after I close the lid on the laptop and leave it closed overnight. It doesn't respond to any key presses or mouse clicks including Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the "suspend" screen showing but mostly it's just black. The Power settings -Dim screen when inactive = yes Blank screen = never Wifi and Bluetooth can be turned off to save power = yes Automatic suspend on battery power = yes Power button action = Power off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 22 17:34:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87cf] InstallationDate: Installed on 2021-06-30 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15-ef1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2021 dmi.bios.release: 15.34 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.19 dmi.modalias: dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-ef1xxx dmi.product.sku: 27A48UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1937321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935785] Re: Failed resume: radeon
seems to work now. ** Changed in: linux (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/1935785 Title: Failed resume: radeon Status in linux package in Ubuntu: Invalid Bug description: My laptop used to be able to suspend and resume fine, on 20.04 and earlier. I recently upgraded to 20.10, and noticed that it was failing to resume, but I didn't look into it much because I also noticed that I could upgrade to 21.04. Same issue. I ran journalctl -b -l -kand noticed an error with radeon failing to resume. But, I'm not sure if that is the correct command. I was suggested to run journalctl -b -1, and that doesn't show any errors at the end. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan1243 F pulseaudio /dev/snd/controlC1: dan1243 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Jul 11 18:46:53 2021 InstallationDate: Installed on 2020-04-01 (466 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude E6540 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=fb680a18-f11e-44e5-91db-015c28c61227 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-07-11 (0 days ago) dmi.bios.date: 09/03/2013 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0CYT5F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/03/2013:br4.6:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.sku: Latitude E6540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935785/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend)
That failed when I rebooted: Error:/boot/vmlunz-5.13.7-051307-generic has invalid signature Error: you need to load the kernel first Press any key to continue Pressing a key takes me back to the Grub screen and I can select 5.11.0-25 to reboot the system I don't think I did anything wrong, but I received the following errors when I installed them: dpkg: dependency problems prevent configuration of linux-headers-5.13.7-051307-generic: linux-headers-5.13.7-051307-generic depends on libc6 (>= 2.33); however: Version of libc6:amd64 on system is 2.31-0ubuntu9.2. dpkg: error processing package linux-headers-5.13.7-051307-generic (--install): dependency problems - leaving unconfigured -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) Status in linux-hwe-5.8 package in Ubuntu: Incomplete Bug description: System freezes after I close the lid on the laptop and leave it closed overnight. It doesn't respond to any key presses or mouse clicks including Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the "suspend" screen showing but mostly it's just black. The Power settings -Dim screen when inactive = yes Blank screen = never Wifi and Bluetooth can be turned off to save power = yes Automatic suspend on battery power = yes Power button action = Power off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 22 17:34:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87cf] InstallationDate: Installed on 2021-06-30 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15-ef1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2021 dmi.bios.release: 15.34 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.19 dmi.modalias: dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-ef1xxx dmi.product.sku: 27A48UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1937321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gke/5.4.0.1051.61)
All autopkgtests for the newly accepted linux-meta-gke (5.4.0.1051.61) for focal have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-gke [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] Fw: [Bug 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend)
Can I use "apt upgrade" to refresh libc6? Duane - Forwarded Message - From: Duane Palmer To: Daniel van Vugt <1937...@bugs.launchpad.net>Sent: Thursday, August 5, 2021, 11:35:10 PM CDTSubject: Fw: [Bug 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend) Can I use the Grub editor and comment out the 5.13.7-053107 kernel? Duane - Forwarded Message - From: Duane Palmer To: Daniel van Vugt <1937...@bugs.launchpad.net>Sent: Thursday, August 5, 2021, 11:29:09 PM CDTSubject: Re: [Bug 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend) That failed when I rebooted: Error:/boot/vmlunz-5.13.7-051307-generic has invalid signatureError: you need to load the kernel firstPress any key to continuePressing a key takes me back to the Grub screen and I can select 5.11.0-25 to reboot the system I don't think I did anything wrong, but I received the following errors when I installed them: dpkg: dependency problems prevent configuration of linux-headers-5.13.7-051307-generic: linux-headers-5.13.7-051307-generic depends on libc6 (>= 2.33); however: Version of libc6:amd64 on system is 2.31-0ubuntu9.2. dpkg: error processing package linux-headers-5.13.7-051307-generic (--install): dependency problems - leaving unconfigured Duane On Thursday, August 5, 2021, 9:30:47 PM CDT, Daniel van Vugt <1937...@bugs.launchpad.net> wrote: Yes we do need to make this process easier for people. 1. Download these four files: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.7/amd64/linux- headers-5.13.7-051307-generic_5.13.7-051307.202107310732_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.7/amd64/linux- headers-5.13.7-051307_5.13.7-051307.202107310732_all.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.7/amd64/linux- image- unsigned-5.13.7-051307-generic_5.13.7-051307.202107310732_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.7/amd64/linux- modules-5.13.7-051307-generic_5.13.7-051307.202107310732_amd64.deb 2. Install them all at once: sudo dpkg -i linux*.deb 3. Reboot. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1937321/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) Status in linux-hwe-5.8 package in Ubuntu: Incomplete Bug description: System freezes after I close the lid on the laptop and leave it closed overnight. It doesn't respond to any key presses or mouse clicks including Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the "suspend" screen showing but mostly it's just black. The Power settings -Dim screen when inactive = yes Blank screen = never Wifi and Bluetooth can be turned off to save power = yes Automatic suspend on battery power = yes Power button action = Power off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 22 17:34:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87cf] InstallationDate: Installed on 2021-06-30 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15-ef1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2021 dmi.bios.release: 15.34 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.19 dmi.chassis.type: 10
[Kernel-packages] Fw: [Bug 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend)
Can I use the Grub editor and comment out the 5.13.7-053107 kernel? Duane - Forwarded Message - From: Duane Palmer To: Daniel van Vugt <1937...@bugs.launchpad.net>Sent: Thursday, August 5, 2021, 11:29:09 PM CDTSubject: Re: [Bug 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend) That failed when I rebooted: Error:/boot/vmlunz-5.13.7-051307-generic has invalid signatureError: you need to load the kernel firstPress any key to continuePressing a key takes me back to the Grub screen and I can select 5.11.0-25 to reboot the system I don't think I did anything wrong, but I received the following errors when I installed them: dpkg: dependency problems prevent configuration of linux-headers-5.13.7-051307-generic: linux-headers-5.13.7-051307-generic depends on libc6 (>= 2.33); however: Version of libc6:amd64 on system is 2.31-0ubuntu9.2. dpkg: error processing package linux-headers-5.13.7-051307-generic (--install): dependency problems - leaving unconfigured Duane On Thursday, August 5, 2021, 9:30:47 PM CDT, Daniel van Vugt <1937...@bugs.launchpad.net> wrote: Yes we do need to make this process easier for people. 1. Download these four files: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.7/amd64/linux- headers-5.13.7-051307-generic_5.13.7-051307.202107310732_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.7/amd64/linux- headers-5.13.7-051307_5.13.7-051307.202107310732_all.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.7/amd64/linux- image- unsigned-5.13.7-051307-generic_5.13.7-051307.202107310732_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.7/amd64/linux- modules-5.13.7-051307-generic_5.13.7-051307.202107310732_amd64.deb 2. Install them all at once: sudo dpkg -i linux*.deb 3. Reboot. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1937321/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) Status in linux-hwe-5.8 package in Ubuntu: Incomplete Bug description: System freezes after I close the lid on the laptop and leave it closed overnight. It doesn't respond to any key presses or mouse clicks including Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the "suspend" screen showing but mostly it's just black. The Power settings -Dim screen when inactive = yes Blank screen = never Wifi and Bluetooth can be turned off to save power = yes Automatic suspend on battery power = yes Power button action = Power off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 22 17:34:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87cf] InstallationDate: Installed on 2021-06-30 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15-ef1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2021 dmi.bios.release: 15.34 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.19 dmi.modalias: dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook
Re: [Kernel-packages] [Bug 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend)
That failed when I rebooted: Error:/boot/vmlunz-5.13.7-051307-generic has invalid signatureError: you need to load the kernel firstPress any key to continuePressing a key takes me back to the Grub screen and I can select 5.11.0-25 to reboot the system I don't think I did anything wrong, but I received the following errors when I installed them: dpkg: dependency problems prevent configuration of linux-headers-5.13.7-051307-generic: linux-headers-5.13.7-051307-generic depends on libc6 (>= 2.33); however: Version of libc6:amd64 on system is 2.31-0ubuntu9.2. dpkg: error processing package linux-headers-5.13.7-051307-generic (--install): dependency problems - leaving unconfigured Duane On Thursday, August 5, 2021, 9:30:47 PM CDT, Daniel van Vugt <1937...@bugs.launchpad.net> wrote: Yes we do need to make this process easier for people. 1. Download these four files: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.7/amd64/linux- headers-5.13.7-051307-generic_5.13.7-051307.202107310732_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.7/amd64/linux- headers-5.13.7-051307_5.13.7-051307.202107310732_all.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.7/amd64/linux- image- unsigned-5.13.7-051307-generic_5.13.7-051307.202107310732_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.7/amd64/linux- modules-5.13.7-051307-generic_5.13.7-051307.202107310732_amd64.deb 2. Install them all at once: sudo dpkg -i linux*.deb 3. Reboot. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1937321/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) Status in linux-hwe-5.8 package in Ubuntu: Incomplete Bug description: System freezes after I close the lid on the laptop and leave it closed overnight. It doesn't respond to any key presses or mouse clicks including Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the "suspend" screen showing but mostly it's just black. The Power settings -Dim screen when inactive = yes Blank screen = never Wifi and Bluetooth can be turned off to save power = yes Automatic suspend on battery power = yes Power button action = Power off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 22 17:34:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87cf] InstallationDate: Installed on 2021-06-30 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15-ef1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2021 dmi.bios.release: 15.34 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.19 dmi.modalias: dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-ef1xxx dmi.product.sku: 27A48UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core:
[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working
@Nicholas, Could you please help to provide: $ sudo dmidecode -s bios-version $ lspci -nnv -s 00:1f.4 | grep Subsystem $ evtest # when you press brightness key FWIK, it seems like the HP common issue if your system is preload with windows from HP factory then install the Linux distro. Since HP has a hotkey application which setting the EC to enter a special mode for this application (EC will send the different keycode). After you reinstall to other OS, the EC still in the special mode. Thus, the keycode might wrong in your system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822581 Title: HP 1030 G3 fn-keys not working Status in linux package in Ubuntu: Invalid Bug description: Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn key combinations are only working partially. What works: Volume up/down/mute, Airplane mode What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator lights I already tried solutions regarding editing the Kernel Parameter acpi_osi in the grub config but can not get the keys to work. In case of screen brightness changing it using the desktop slider works. But it seems, that the keypress isn't recognized at all. Neither xev nor acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone muting (fn+f8). Running showkey -k results in a keycode 465 pressed and released event for all three key combinations. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: udev 239-7ubuntu10.10 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Apr 1 14:22:47 2019 InstallationDate: Installed on 2019-03-30 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: HP HP EliteBook x360 1030 G3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2019 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.06.00 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.38.00 dmi.chassis.asset.tag: 5CD8427YK5 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook x360 dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 4QZ13ES#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848746] Re: Refresh rate change requests to 40Hz are "adjusted" back to 60Hz
Hi Cameron, I didn't go upstream yet. I suppose upstream bugs should be filed to the Intel Open Source Technology Center (https://01.org/), but I'm not sure. Or maybe to the Linux kernel since it's an in-tree module after all... From what I understand, the Intel module fails to switch to anything else than the refreshing rate that's on the preferred (i.e. first mentioned on EDID) DTD. However, it seems to me the first DTD usually has the highest refresh rate, which makes your problem strange. Could that mean the 60 Hz DTD is the preferred one on your laptop's panel, despite it being able to go up to 135 Hz ? Also, are you sure you're using true Xorg, not Xorg on Wayland ? Bcos on any readings on the latter would be mostly irrelevant as they don't necessary reflect the reality (Xorg on Wayland being only a compatibility layer). From what I've seen, when asking for a reduced refresh rate, even if it fails, Wayland seems to try to near the target refresh rate by syncing frames to a factor of the effective refresh rate. That's why on a previous post, when trying to get 60Hz on my 144Hz-capable monitor, I was getting 72 fps with glxgears... But in your case of trying to get 135 from an effective 60, Wayland surely can't do this trick. Anyway, you can get the EDID from sysfs easily. On my current config, mine is in /sys/class/drm/card0-eDP-1/edid. You should have something similar. To quicky decode the EDID, you can use edid-decode (from the edid-decode package), most basically like this : edid-decode /sys/class/drm/card0-eDP-1/edid Then you can create a modified, hex-edited EDID file, with the two DTDs swapped, put it somewhere under the /lib/firmware directory and add the following in a file inside /etc/modprobe.d : options drm edid_firmware=eDP-1:mydir/myedid.bin eDP-1 is your connector name, for me it's eDP-1 but for you it can be something else. You can also omit "eDP-1:", in which case the EDID will apply to all connectors. While I didn't check myself, I suppose it will be a problem if you plug your laptop on an external monitor. Also, if the module is loaded while the system is still on the initramfs, it won't work since your modified EDID won't be there, hence you will have to add it with an initramfs hook in /etc/initramfs-tools/hooks. The file should look like this : --- File starts after this line - #!/bin/sh PREREQ="" prereqs () { echo "$PREREQ" } case "$1" in prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions copy_file edid /lib/firmware/mydir/myedid.bin - File ends before this line - Make the file belong to root:root and mode 555 (readable/executable by all). You should then update your initramfs with update-initramfs -u (to update the initramfs for the current running kernel) or update-initramfs -u -k all (to update for all installed kernels, or you can specify a kernel). And reboot... Hope this helps ! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848746 Title: Refresh rate change requests to 40Hz are "adjusted" back to 60Hz Status in linux package in Ubuntu: Confirmed Bug description: Dear Launchpad readers, Changes to a 40Hz-based mode are adjusted back to a 60Hz display mode by KMS, as can be seen in the logs with the drm.debug=4 option : oct. 18 16:27:24 NovHak-P2 kernel: [drm:intel_dump_pipe_config [i915]] requested mode: oct. 18 16:27:24 NovHak-P2 kernel: [drm:drm_mode_debug_printmodeline [drm]] Modeline 0:"" 0 92450 1920 1968 2000 2080 1080 1083 1088 0x0 0x9 oct. 18 16:27:24 NovHak-P2 kernel: [drm:intel_dump_pipe_config [i915]] adjusted mode: oct. 18 16:27:24 NovHak-P2 kernel: [drm:drm_mode_debug_printmodeline [drm]] Modeline 0:"1920x1080" 60 140490 1920 1972 2007 2094 1080 1083 1089 1118 0x48 0x9 I managed to have 40Hz through EDID modification, swapping the two DTDs it contains, one being 60Hz, the other 40Hz, hence placing the 40Hz DTD first, but then it remains sticked to 40Hz and unable to switch to a 60Hz mode. I suppose the bug is i915-related rather than Xorg-related, since the modelines seem correctly sent for KMS. I can provide additional information if needed. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.32.33 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: olivier 12097 F pulseaudio /dev/snd/controlC0: olivier 12097 F pulseaudio /dev/snd/controlC1: olivier 12097 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 18 16:43:01 2019 InstallationDate: Installed on 2019-09-22 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" -
[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working
Same issue with the brightness keys on the HP Elite Dragonfly G2, even on kernel 5.13. Seems like a firmware bug, but may have something to do with the HP WMI keycode driver. Really annoying and not at all good for such an expensive product. This needs to be fixed, it affects most of HP's new business laptops. Could someone describe how to do the power reset please? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822581 Title: HP 1030 G3 fn-keys not working Status in linux package in Ubuntu: Invalid Bug description: Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn key combinations are only working partially. What works: Volume up/down/mute, Airplane mode What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator lights I already tried solutions regarding editing the Kernel Parameter acpi_osi in the grub config but can not get the keys to work. In case of screen brightness changing it using the desktop slider works. But it seems, that the keypress isn't recognized at all. Neither xev nor acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone muting (fn+f8). Running showkey -k results in a keycode 465 pressed and released event for all three key combinations. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: udev 239-7ubuntu10.10 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Apr 1 14:22:47 2019 InstallationDate: Installed on 2019-03-30 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: HP HP EliteBook x360 1030 G3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2019 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.06.00 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.38.00 dmi.chassis.asset.tag: 5CD8427YK5 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook x360 dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 4QZ13ES#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939045] Re: Extend ANDROID_BINDER_DEVICES
@alexhung Sure, xnox told me to report the bugs here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939045 Title: Extend ANDROID_BINDER_DEVICES Status in linux package in Ubuntu: New Bug description: Would it be possible to extend ANDROID_BINDER_DEVICES to 'binder,hwbinder,vndbinder,anbox-binder,anbox-hwbinder,anbox- vndbinder' for Waydroid (a new alternative to Anbox) to work OOTB on Ubuntu without having to recompile the kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939046] Re: Enable CONFIG_SW_SYNC_USER
@alexhung Sure, xnox told me to report the bugs here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939046 Title: Enable CONFIG_SW_SYNC_USER Status in linux package in Ubuntu: New Bug description: Would it be possible to enable SYNC_USER for Waydroid (a new alternative to Anbox) to work OOTB on Ubuntu without having to recompile the kernel? Related to #1939045. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930903] Re: Frequent kernel oops related to nvidia / nv_drm_master_set
** Tags added: oem-priority originate-from-1939083 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930903 Title: Frequent kernel oops related to nvidia / nv_drm_master_set Status in OEM Priority Project: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: After upgrading yesterday from ubuntu 20 to 21.04 my machine now exhibits frequent involuntary restarts, related to a kernel oops of the form Jun 3 10:48:32 zotac kernel: [ 20.464926] RIP: 0010:nv_drm_master_set+0x27/0x30 [nvidia_drm] [...] Jun 3 10:48:32 zotac kernel: [ 20.464958] Call Trace: Jun 3 10:48:32 zotac kernel: [ 20.464964] drm_new_set_master+0x7e/0x100 [drm] Jun 3 10:48:32 zotac kernel: [ 20.464994] drm_master_open+0x6e/0xa0 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465017] drm_open+0xf8/0x250 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465044] drm_stub_open+0xba/0x140 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465070] chrdev_open+0xf7/0x220 Jun 3 10:48:32 zotac kernel: [ 20.465075] ? cdev_device_add+0x90/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465078] do_dentry_open+0x156/0x370 Jun 3 10:48:32 zotac kernel: [ 20.465081] vfs_open+0x2d/0x30 Jun 3 10:48:32 zotac kernel: [ 20.465084] do_open+0x1c3/0x340 Jun 3 10:48:32 zotac kernel: [ 20.465087] path_openat+0x10a/0x1d0 Jun 3 10:48:32 zotac kernel: [ 20.465090] do_filp_open+0x8c/0x130 Jun 3 10:48:32 zotac kernel: [ 20.465093] ? __check_object_size+0x1c/0x20 Jun 3 10:48:32 zotac kernel: [ 20.465096] do_sys_openat2+0x9b/0x150 Jun 3 10:48:32 zotac kernel: [ 20.465099] __x64_sys_openat+0x56/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465102] do_syscall_64+0x38/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465105] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 3 10:48:32 zotac kernel: [ 20.465108] RIP: 0033:0x7fe6ea270954 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jun 4 17:00:45 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-18-generic, x86_64: installed nvidia, 460.80, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] [19da:2438] InstallationDate: Installed on 2020-05-09 (391 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: NA ZBOX-ER51070 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=4e73512b-1846-4fe4-87d1-079bbaae2a1a ro quiet splash crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Default string dmi.board.name: ZBOX-ER51070 dmi.board.vendor: NA dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd04/25/2019:br5.12:svnNA:pnZBOX-ER51070:pvrDefaultstring:rvnNA:rnZBOX-ER51070:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZBOX-ER51070 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: NA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Kernel-packages] [Bug 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend)
Yes we do need to make this process easier for people. 1. Download these four files: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.7/amd64/linux- headers-5.13.7-051307-generic_5.13.7-051307.202107310732_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.7/amd64/linux- headers-5.13.7-051307_5.13.7-051307.202107310732_all.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.7/amd64/linux- image- unsigned-5.13.7-051307-generic_5.13.7-051307.202107310732_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.7/amd64/linux- modules-5.13.7-051307-generic_5.13.7-051307.202107310732_amd64.deb 2. Install them all at once: sudo dpkg -i linux*.deb 3. Reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) Status in linux-hwe-5.8 package in Ubuntu: Incomplete Bug description: System freezes after I close the lid on the laptop and leave it closed overnight. It doesn't respond to any key presses or mouse clicks including Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the "suspend" screen showing but mostly it's just black. The Power settings -Dim screen when inactive = yes Blank screen = never Wifi and Bluetooth can be turned off to save power = yes Automatic suspend on battery power = yes Power button action = Power off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 22 17:34:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87cf] InstallationDate: Installed on 2021-06-30 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15-ef1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2021 dmi.bios.release: 15.34 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.19 dmi.modalias: dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-ef1xxx dmi.product.sku: 27A48UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1937321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend)
How do I install these files, I'm not that conversant with Linux. Duane On Thursday, August 5, 2021, 7:33:24 PM CDT, Daniel van Vugt <1937...@bugs.launchpad.net> wrote: This is a bug in the kernel that ships with Ubuntu 20.04 so you need a newer one. Try this: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.7/amd64/ -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1937321/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) Status in linux-hwe-5.8 package in Ubuntu: Incomplete Bug description: System freezes after I close the lid on the laptop and leave it closed overnight. It doesn't respond to any key presses or mouse clicks including Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the "suspend" screen showing but mostly it's just black. The Power settings -Dim screen when inactive = yes Blank screen = never Wifi and Bluetooth can be turned off to save power = yes Automatic suspend on battery power = yes Power button action = Power off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 22 17:34:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87cf] InstallationDate: Installed on 2021-06-30 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15-ef1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2021 dmi.bios.release: 15.34 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.19 dmi.modalias: dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-ef1xxx dmi.product.sku: 27A48UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1937321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938999] Re: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock
nouveau is used instead of nvidia-driver. external display highly depends on nvidia gpu. Could you try 5.13/5.14 kernel? Or 5.13 with nvidia-driver? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938999 Title: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock Status in linux package in Ubuntu: Confirmed Bug description: I have two external displays chained via Display port connected to the ThinkPad Thunderbolt 3 Dock. They are working with kernel 5.8.0-63 but not with the new 5.11.0-25 kernel. I could reproduce this behavior several times for both kernels, as follows: I booted up with disconnected dock, logged in, then I connected it, disconnected it, and connected it again. With the 5.11.0-25 kernel the external displays go black; the main screen turns off and on several times. Sometimes the main screen remains working, but UI is lagging. I'm attaching the logs. Two separate boots for each variant are marked 'a'/'b'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
It happened to me too ** Attachment added: "Crash log of amdgpu driver" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+attachment/5516220/+files/amdgu_crash.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939071] Re: Dual screen not working
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1939071 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939071 Title: Dual screen not working Status in linux package in Ubuntu: New Bug description: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Dual screen issue with kernel family 5.11. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939071] [NEW] Dual screen not working
Public bug reported: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Dual screen issue with kernel family 5.11. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1939071/+attachment/5516205/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939071 Title: Dual screen not working Status in linux package in Ubuntu: New Bug description: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Dual screen issue with kernel family 5.11. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
This bug is related to https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1928244 https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1912811 Kernel 5.13 can be compiled in one of the two ways: 1. Use dwarves 1.21, which needs Ubuntu 21.04 and breaks installation for older systems 2. Disable CONFIG_DEBUG_INFO_BTF, thus allowing it to be compiled with older toolchains and thus, for older Ubuntu releases. I believe the sensible approach would be to temporarily follow the second option until a better solution is found as proposed in 1912811. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923284] Re: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test / vmx_hlt_with_rvi_test fails with timeout on Bionic
** Tags added: sru-20210719 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923284 Title: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test / vmx_hlt_with_rvi_test fails with timeout on Bionic Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Bug description: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test fails with timeout on Bionic 4.15.0-141.145 host rizzo this failed on the previous version of bionic 4.15.0-140.144 as well, so not a regression. vmx_host_state_area has an error before giving timeout: 04/10 01:29:18 DEBUG| utils:0153| [stderr] KVM: entry failed, hardware error 0x8021 04/10 01:29:18 DEBUG| utils:0153| [stderr] 04/10 01:29:18 DEBUG| utils:0153| [stderr] If you're running a guest on an Intel machine without unrestricted mode 04/10 01:29:18 DEBUG| utils:0153| [stderr] support, the failure can be most likely due to the guest entering an invalid 04/10 01:29:18 DEBUG| utils:0153| [stderr] state for Intel VT. For example, the guest maybe running in big real mode 04/10 01:29:18 DEBUG| utils:0153| [stderr] which is not supported on less recent Intel processors. 04/10 01:29:18 DEBUG| utils:0153| [stderr] 04/10 01:29:47 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 21956 (timeout) 04/10 01:29:47 DEBUG| utils:0153| [stdout] FAIL vmx_host_state_area (timeout; duration=30) vmx_intr_window_test / vmx_nmi_window_test shows passing until the timeout: 28. 04/10 01:29:49 DEBUG| utils:0153| [stdout] PASS: interrupt-window: active, RFLAGS.IF = 0: Activity state (0) is 'ACTIVE' 29. 04/10 01:30:19 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 22161 (timeout) 30. 04/10 01:30:19 DEBUG| utils:0153| [stdout] FAIL vmx_intr_window_test (timeout; duration=30) 31. 04/10 01:30:19 ERROR| test:0414| Exception escaping from test: -- 26. 04/10 01:30:24 DEBUG| utils:0153| [stdout] PASS: NMI-window: active, blocking by NMI: #UD handler executed once (actual 1 times) 27. 04/10 01:30:53 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 22570 (timeout) 28. 04/10 01:30:53 DEBUG| utils:0153| [stdout] FAIL vmx_nmi_window_test (timeout; duration=30) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917616] Re: vmx test from ubuntu_kvm_unit_tests failed on Bionic/Focal
seeing on H/kvm 5.11.0-1013.14 ** Tags added: hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917616 Title: vmx test from ubuntu_kvm_unit_tests failed on Bionic/Focal Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Bug description: Appearing in bionic 5.4.0-67.75~18.04.1 affecting lowlatency and hwe flavors. 2538. 02/25 00:10:11 DEBUG| utils:0153| [stdout] Unhandled exception 13 #GP at ip 004071a3 2539. 02/25 00:10:11 DEBUG| utils:0153| [stdout] error_code= rflags=00010006 cs=0008 2540. 02/25 00:10:11 DEBUG| utils:0153| [stdout] rax=0078 rcx=0809 rdx= rbx=0009 2541. 02/25 00:10:11 DEBUG| utils:0153| [stdout] rbp=0047efdf rsi=0042568d rdi=0042568d 2542. 02/25 00:10:11 DEBUG| utils:0153| [stdout] r8=000a r9=03f8 r10=000d r11= 2543. 02/25 00:10:11 DEBUG| utils:0153| [stdout] r12= r13= r14=00403dcc r15= 2544. 02/25 00:10:11 DEBUG| utils:0153| [stdout] cr0=80010031 cr2=e000 cr3=00477000 cr4=2020 2545. 02/25 00:10:11 DEBUG| utils:0153| [stdout] cr8=0007 2546. 02/25 00:10:11 DEBUG| utils:0153| [stdout] STACK: @4071a3 40170b 4004dd 2547. 02/25 00:10:11 DEBUG| utils:0153| [stdout] FAIL vmx 2548. 02/25 00:10:11 ERROR| test:0414| Exception escaping from test: 2549. Traceback (most recent call last): 2550. File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec 2551. _call_test_function(self.execute, *p_args, **p_dargs) 2552. File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function 2553. return func(*args, **dargs) 2554. File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute 2555. postprocess_profiled_run, args, dargs) 2556. File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once 2557. self.run_once(*args, **dargs) 2558. File "/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py", line 80, in run_once 2559. raise error.TestError("Test failed for {}".format(test_name)) 2560. TestError: Test failed for vmx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1917616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831449] Re: memory in ubuntu_kvm_unit_tests fails (clflushopt / clwb ABSENT)
** Tags added: sru-20210719 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1831449 Title: memory in ubuntu_kvm_unit_tests fails (clflushopt / clwb ABSENT) Status in ubuntu-kernel-tests: Triaged Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Bug description: Need to run this on oracle manually to get the full output: TESTNAME=memory TIMEOUT=90s ACCEL= ./x86/run x86/memory.flat -smp 1 -cpu host FAIL memory (8 tests, 2 unexpected failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939045] Re: Extend ANDROID_BINDER_DEVICES
You may want to send emails to Ubuntu kernel team (see https://lists.ubuntu.com/mailman/listinfo/kernel-team) for discussions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939045 Title: Extend ANDROID_BINDER_DEVICES Status in linux package in Ubuntu: New Bug description: Would it be possible to extend ANDROID_BINDER_DEVICES to 'binder,hwbinder,vndbinder,anbox-binder,anbox-hwbinder,anbox- vndbinder' for Waydroid (a new alternative to Anbox) to work OOTB on Ubuntu without having to recompile the kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939046] Re: Enable CONFIG_SW_SYNC_USER
You may want to send emails to Ubuntu kernel team (see https://lists.ubuntu.com/mailman/listinfo/kernel-team) for discussions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939046 Title: Enable CONFIG_SW_SYNC_USER Status in linux package in Ubuntu: New Bug description: Would it be possible to enable SYNC_USER for Waydroid (a new alternative to Anbox) to work OOTB on Ubuntu without having to recompile the kernel? Related to #1939045. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939052] Re: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939052 Title: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2 Status in linux package in Ubuntu: New Bug description: All 3 models need the appropriate HDA verbs sent to properly initialize the sound hardware. Additionally, the Legion 15IMHG05 needs automute disabled otherwise speaker output will not return after removing headphones. The good news is that I have working patches for all 3. However, the 13s Gen2 reportedly has some weirdness on the volume control. I don't have this model of laptop so there's not a lot I can do. It seems tuning the volume up and down using the keys on the keyboard can jump the volume up and down in large increments. Volume adjustments via a GUI do not have this issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hiryu 7243 F pulseaudio /dev/snd/controlC0: hiryu 7243 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 5 10:17:57 2021 InstallationDate: Installed on 2021-04-23 (104 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82K6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 bluetooth.disable_ertm acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2021 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: H1CN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ITHg6 dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrH1CN33WW:bd07/18/2021:br1.33:efr1.33:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6: dmi.product.family: Legion 7 16ITHg6 dmi.product.name: 82K6 dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6 dmi.product.version: Legion 7 16ITHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939052] Re: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2
Hi Cameron, Thanks for sharing your work. For patches to be merged into Ubuntu kernel, patches need to be backport by sending SRU to ubuntu kernel team: kernel-team at lists.ubuntu.com with specific format. This allows reviews from broader audiences. An example will be like https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938689 Cover letter: https://lists.ubuntu.com/archives/kernel-team/2021-August/122890.html Patch: https://lists.ubuntu.com/archives/kernel-team/2021-August/122891.html Note: subject's "UBUNTU: SAUCE:" is needed for patches aren't in mainline kernel, and bug link should be included in both cover letter and patch description. Details can be found @ https://wiki.ubuntu.com/StableReleaseUpdates#Procedure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939052 Title: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2 Status in linux package in Ubuntu: New Bug description: All 3 models need the appropriate HDA verbs sent to properly initialize the sound hardware. Additionally, the Legion 15IMHG05 needs automute disabled otherwise speaker output will not return after removing headphones. The good news is that I have working patches for all 3. However, the 13s Gen2 reportedly has some weirdness on the volume control. I don't have this model of laptop so there's not a lot I can do. It seems tuning the volume up and down using the keys on the keyboard can jump the volume up and down in large increments. Volume adjustments via a GUI do not have this issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hiryu 7243 F pulseaudio /dev/snd/controlC0: hiryu 7243 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 5 10:17:57 2021 InstallationDate: Installed on 2021-04-23 (104 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82K6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 bluetooth.disable_ertm acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2021 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: H1CN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ITHg6 dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrH1CN33WW:bd07/18/2021:br1.33:efr1.33:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6: dmi.product.family: Legion 7 16ITHg6 dmi.product.name: 82K6 dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6 dmi.product.version: Legion 7 16ITHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924588] Re: P2P mode doesn't work in qla2xxx
It should be fixed in 5.4.0-74.83: https://launchpad.net/ubuntu/+source/linux/5.4.0-74.83 By pulling upstream v5.4.114 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926493): Revert "scsi: qla2xxx: Retry PLOGI on FC-NVMe PRLI failure" Revert "scsi: qla2xxx: Fix stuck login session using prli_pend_timer" scsi: qla2xxx: Dual FCP-NVMe target port support scsi: qla2xxx: Fix device connect issues in P2P configuration scsi: qla2xxx: Retry PLOGI on FC-NVMe PRLI failure scsi: qla2xxx: Add a shadow variable to hold disc_state history of fcport ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924588 Title: P2P mode doesn't work in qla2xxx Status in linux package in Ubuntu: Fix Released Bug description: Link to a patch series to the stable: https://www.spinics.net/lists/stable/msg458515.html QLogic FC adapters don't work in direct mode on focal (at least QLE2692, and QLE2694, QLE2742 are affected): [ 266.821659] qla2xxx [:05:00.0]-3874:3: ELS_DCMD PLOGI sent, hdl=1a, loopid=0, to port_id 02 from port_id 01 [ 266.822926] qla2xxx [:05:00.0]-583f:3: ELS IOCB Done -Driver ELS logo error hdl=1a comp_status=0x0 error subcode 1=0x0 error subcode 2=0x0 total_byte=0x74 [ 266.822933] qla2xxx [:05:00.0]-3872:3: ELS_DCMD ELS done rc 0 hdl=1a, portid=02 21:00:34:80:0d:74:14:d2 [ 266.822937] qla2xxx [:05:00.0]-2918:3: qla_handle_els_plogi_done 1764 21:00:34:80:0d:74:14:d2 post PRLI [ 266.822965] qla2xxx [:05:00.0]-291b:3: Async-prli - 21:00:34:80:0d:74:14:d2 hdl=0, loopid=0 portid=02 retries=29 nvme. [ 266.823008] qla2xxx [:05:00.0]-5837:3: Async-prli failed - 21:00:34:80:0d:74:14:d2 hdl=1b portid=02 comp=31 iop0=18 iop1=b. [ 266.823011] qla2xxx [:05:00.0]-2929:3: qla2x00_async_prli_sp_done 21:00:34:80:0d:74:14:d2 res 0 [ 266.823014] qla2xxx [:05:00.0]-2918:3: qla24xx_handle_prli_done_event 1934 21:00:34:80:0d:74:14:d2 post NVMe prli [ 266.823019] qla2xxx [:05:00.0]-e801:3: Scheduling sess a438982b for deletion 21:00:34:80:0d:74:14:d2 [ 266.823031] qla2xxx [:05:00.0]-290a:3: qlt_unreg_sess sess a438982b for deletion 21:00:34:80:0d:74:14:d2 [ 266.823039] qla2xxx [:05:00.0]-f884:3: qlt_free_session_done: se_sess / sess a438982b from port 21:00:34:80:0d:74:14:d2 loop_id 0x00 s_id 00:00:02 logout 1 keep 0 els_logo 0 [ 266.823043] qla2xxx [:05:00.0]-f886:3: qlt_free_session_done: waiting for sess a438982b logout [ 266.823066] qla2xxx [:05:00.0]-2870:3: Async-logout - hdl=0 loop-id=0 portid=02 21:00:34:80:0d:74:14:d2. [ 266.823087] qla2xxx [:05:00.0]-5836:3: Async-logout complete - 21:00:34:80:0d:74:14:d2 hdl=1c portid=02 iop0=0. [ 266.823093] qla2xxx [:05:00.0]-f893:3: qlt_logo_completion_handler: se_sess / sess a438982b from port 21:00:34:80:0d:74:14:d2 loop_id 0x00 s_id 00:00:02 LOGO failed: 0x0 [ 266.928413] qla2xxx [:05:00.0]-f887:3: qlt_free_session_done: sess a438982b logout completed [ 266.931754] qla2xxx [:05:00.0]-f89a:3: se_sess / sess a438982b port 21:00:34:80:0d:74:14:d2 is gone, no own PLOGI pending (ref=-1) The snippet above shows that qla2xxx is trying to send NVMe PRLI instead of FCP PRLI to FCP target and link connection doesn't succeed. The same bug exists in linux-stable since 5.4.69. P2P worked until 5.4.69 but issue_lip was broken and link was not recovered after issue_lip. We have triaged the issue and found a way to fix it by backporting and properly merging upstream patches and will send a series to linux- stable shortly. (https://www.spinics.net/lists/stable/msg458515.html) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-71-generic 5.4.0-71.79 ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101 Uname: Linux 5.4.0-71-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-71-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip Date: Thu Apr 15 15:43:55 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU
[Kernel-packages] [Bug 1939055] Re: package linux-headers-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to install/upgrade: installed linux-headers-5.11.0-25-generic package post-installation script s
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939055 Title: package linux-headers-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to install/upgrade: installed linux-headers-5.11.0-25-generic package post-installation script subprocess returned error exit status 1 Status in linux-hwe-5.11 package in Ubuntu: New Bug description: I have absolutely no idea what is happening and why the system prompts me to send a report. But if it helps someone, then here are my logs. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 5 14:34:05 2021 ErrorMessage: installed linux-headers-5.11.0-25-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-04-13 (114 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to install/upgrade: installed linux-headers-5.11.0-25-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939055] [NEW] package linux-headers-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to install/upgrade: installed linux-headers-5.11.0-25-generic package post-installation script
Public bug reported: I have absolutely no idea what is happening and why the system prompts me to send a report. But if it helps someone, then here are my logs. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 5 14:34:05 2021 ErrorMessage: installed linux-headers-5.11.0-25-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-04-13 (114 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to install/upgrade: installed linux-headers-5.11.0-25-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939055 Title: package linux-headers-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to install/upgrade: installed linux-headers-5.11.0-25-generic package post-installation script subprocess returned error exit status 1 Status in linux-hwe-5.11 package in Ubuntu: New Bug description: I have absolutely no idea what is happening and why the system prompts me to send a report. But if it helps someone, then here are my logs. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 5 14:34:05 2021 ErrorMessage: installed linux-headers-5.11.0-25-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-04-13 (114 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to install/upgrade: installed linux-headers-5.11.0-25-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848746] Re: Refresh rate change requests to 40Hz are "adjusted" back to 60Hz
Unsure if this is related, but I'm seeing the same issue with both the 21.04 vendor kernel and 5.13.8. I have a 165 Hz screen, and the Intel iGPU will only run it at 60 Hz. If I switch to the discrete Nvidia GPU in the BIOS, I get 165 Hz and I'm able to switch to 60 Hz. First I switch from "165 Hz" to 60: Aug 5 10:59:12 ukyo kernel: [ 247.263181] [drm:drm_mode_debug_printmodeline [drm]] Modeline "": 60 282670 2560 2608 2640 2720 1600 1603 1609 1732 0x0 0x9 Aug 5 10:59:12 ukyo kernel: [ 247.263307] [drm:drm_mode_debug_printmodeline [drm]] Modeline "2560x1600": 60 282670 2560 2608 2640 2720 1600 1603 1609 1732 0x48 0x9 Aug 5 10:59:12 ukyo kernel: [ 247.263521] [drm:drm_mode_debug_printmodeline [drm]] Modeline "2560x1600": 60 282670 2560 2608 2640 2720 1600 1603 1609 1732 0x40 0x9 Then I attempt to switch from 60 Hz to 165 Hz: Aug 5 10:59:22 ukyo kernel: [ 257.078950] [drm:drm_mode_debug_printmodeline [drm]] Modeline "": 165 777340 2560 2608 2640 2720 1600 1603 1609 1732 0x0 0xa Aug 5 10:59:22 ukyo kernel: [ 257.079075] [drm:drm_mode_debug_printmodeline [drm]] Modeline "2560x1600": 60 282670 2560 2608 2640 2720 1600 1603 1609 1732 0x48 0x9 Aug 5 10:59:22 ukyo kernel: [ 257.079266] [drm:drm_mode_debug_printmodeline [drm]] Modeline "2560x1600": 60 282670 2560 2608 2640 2720 1600 1603 1609 1732 0x40 0x9 I've tried adding a custom modeline to Xorg to work around this. It sees the modeline, but it doesn't do anything. I'll try the EDID hack. If the Nvidia driver is able to do it, probably something wrong with the EDID parsing if the EDID hack works? My previous laptop (which I replaced just 2 days ago) didn't have this problem. However, it was a i7 10875h with a 144 Hz screen. The new laptop is a Tigerlake 11980HK. Maybe it's the difference in refresh rate or my case of a bug with the newer iGPU? I'll research to see if any of my monitor outputs go through the Intel GPU and I can test against one of my 144 Hz external monitors. Oliver, If you file the bug upstream or already have, can you please share the link? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848746 Title: Refresh rate change requests to 40Hz are "adjusted" back to 60Hz Status in linux package in Ubuntu: Confirmed Bug description: Dear Launchpad readers, Changes to a 40Hz-based mode are adjusted back to a 60Hz display mode by KMS, as can be seen in the logs with the drm.debug=4 option : oct. 18 16:27:24 NovHak-P2 kernel: [drm:intel_dump_pipe_config [i915]] requested mode: oct. 18 16:27:24 NovHak-P2 kernel: [drm:drm_mode_debug_printmodeline [drm]] Modeline 0:"" 0 92450 1920 1968 2000 2080 1080 1083 1088 0x0 0x9 oct. 18 16:27:24 NovHak-P2 kernel: [drm:intel_dump_pipe_config [i915]] adjusted mode: oct. 18 16:27:24 NovHak-P2 kernel: [drm:drm_mode_debug_printmodeline [drm]] Modeline 0:"1920x1080" 60 140490 1920 1972 2007 2094 1080 1083 1089 1118 0x48 0x9 I managed to have 40Hz through EDID modification, swapping the two DTDs it contains, one being 60Hz, the other 40Hz, hence placing the 40Hz DTD first, but then it remains sticked to 40Hz and unable to switch to a 60Hz mode. I suppose the bug is i915-related rather than Xorg-related, since the modelines seem correctly sent for KMS. I can provide additional information if needed. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.32.33 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: olivier 12097 F pulseaudio /dev/snd/controlC0: olivier 12097 F pulseaudio /dev/snd/controlC1: olivier 12097 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 18 16:43:01 2019 InstallationDate: Installed on 2019-09-22 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Notebook P17SM-A ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=788f8a5e-9667-4cfb-abf4-bc76ebcb86bb ro quiet splash mtrr_spare_reg_nr=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: P17SM-A dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: To Be Filled By O.E.M.
[Kernel-packages] [Bug 1939053] Re: Impish update: v5.13.8 upstream stable release
** Changed in: linux (Ubuntu Impish) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939053 Title: Impish update: v5.13.8 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.13.8 upstream stable release from git://git.kernel.org/ selftest: fix build error in tools/testing/selftests/vm/userfaultfd.c pipe: make pipe writes always wake up readers fs/ext2: Avoid page_address on pages returned by ext2_get_page btrfs: fix lost inode on log replay after mix of fsync, rename and inode eviction btrfs: fix rw device counting in __btrfs_free_extra_devids btrfs: mark compressed range uptodate only if all bio succeed Revert "ACPI: resources: Add checks for ACPI IRQ override" ACPI: DPTF: Fix reading of attributes x86/kvm: fix vcpu-id indexed array sizes KVM: add missing compat KVM_CLEAR_DIRTY_LOG ocfs2: fix zero out valid data ocfs2: issue zeroout to EOF blocks mm: memcontrol: fix blocking rstat function called from atomic cgroup1 thresholding code mm/memcg: fix NULL pointer dereference in memcg_slab_free_hook() can: j1939: j1939_xtp_rx_dat_one(): fix rxtimer value between consecutive TP.DT to 750ms can: raw: raw_setsockopt(): fix raw_rcv panic for sock UAF can: peak_usb: pcan_usb_handle_bus_evt(): fix reading rxerr/txerr values can: mcba_usb_start(): add missing urb->transfer_dma initialization can: usb_8dev: fix memory leak can: ems_usb: fix memory leak can: esd_usb2: fix memory leak alpha: register early reserved memory in memblock HID: wacom: Re-enable touch by default for Cintiq 24HDT / 27QHDT net: stmmac: add est_irq_status callback function for GMAC 4.10 and 5.10 NIU: fix incorrect error return, missed in previous revert drm/amd/display: ensure dentist display clock update finished in DCN20 drm/amdgpu: Check pmops for desired suspend state drm/amdgpu: Avoid printing of stack contents on firmware load error drm/amdgpu: Fix resource leak on probe error path blk-iocost: fix operation ordering in iocg_wake_fn() nfc: nfcsim: fix use after free during module unload io_uring: fix io_prep_async_link locking io_uring: don't block level reissue off completion path io_uring: fix poll requests leaking second poll entries cfg80211: Fix possible memory leak in function cfg80211_bss_update RDMA/bnxt_re: Fix stats counters platform/x86: amd-pmc: Fix command completion code platform/x86: amd-pmc: Fix SMU firmware reporting mechanism platform/x86: amd-pmc: Fix missing unlock on error in amd_pmc_send_cmd() RDMA/rxe: Fix memory leak in error path code netfilter: nf_tables: fix audit memory leak in nf_tables_commit bpf: Fix OOB read when printing XDP link fdinfo mac80211: fix enabling 4-address mode on a sta vif after assoc netfilter: conntrack: adjust stop timestamp to real expiry value netfilter: nft_nat: allow to specify layer 4 protocol NAT only i40e: Fix logic of disabling queues i40e: Fix firmware LLDP agent related warning i40e: Fix queue-to-TC mapping on Tx i40e: Fix log TC creation failure when max num of queues is exceeded tipc: fix implicit-connect for SYN+ tipc: fix sleeping in tipc accept routine net: Set true network header for ECN decapsulation net: dsa: mv88e6xxx: silently accept the deletion of VID 0 too loop: reintroduce global lock for safe loop_validate_file() traversal net: qrtr: fix memory leaks ionic: make all rx_mode work threadsafe ionic: catch no ptp support earlier ionic: remove intr coalesce update from napi ionic: fix up dim accounting for tx and rx ionic: count csum_none when offload enabled can: mcp251xfd: mcp251xfd_irq(): stop timestamping worker in case error in IRQ tipc: do not write skb_shinfo frags when doing decrytion octeontx2-pf: Fix interface down flag on error octeontx2-pf: Dont enable backpressure on LBK links net: phy: broadcom: re-add check for PHY_BRCM_DIS_TXCRXC_NOENRGY on the BCM54811 PHY mlx4: Fix missing error code in mlx4_load_one() drm/panel: panel-simple: Fix proper bpc for ytc700tlag_05_201c drm/i915/bios: Fix ports mask KVM: x86: Check the right feature bit for MSR_KVM_ASYNC_PF_ACK access net: llc: fix skb_over_panic drm/msm/dpu: Fix sm8250_mdp register length drm/msm/dp: use dp_ctrl_off_link_stream during
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi2/4.15.0.1094.92)
All autopkgtests for the newly accepted linux-meta-raspi2 (4.15.0.1094.92) for bionic have finished running. The following regressions have been reported in tests triggered by the package: rtl8821ce/5.5.2.1-0ubuntu3~18.04.1 (armhf) dpdk/unknown (arm64) asic0x/unknown (arm64) nat-rtsp/unknown (arm64) zfs-linux/unknown (arm64) r8168/8.045.08-2ubuntu1 (armhf) ddcci-driver-linux/unknown (arm64) xtables-addons/unknown (arm64) fwts/unknown (arm64) wireguard-linux-compat/unknown (arm64) rtl8812au/unknown (arm64) lime-forensics/unknown (arm64) adv-17v35x/unknown (arm64) glibc/unknown (arm64) lttng-modules/unknown (arm64) snapd/unknown (arm64) spl-linux/unknown (arm64) r8168/unknown (arm64) langford/unknown (arm64) systemd/unknown (arm64) west-chamber/unknown (arm64) acpi-call/unknown (arm64) langford/0.0.20130228-5ubuntu1 (armhf) dm-writeboost/unknown (arm64) ktap/unknown (arm64) rtl8821ce/unknown (arm64) bbswitch/unknown (arm64) v4l2loopback/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-raspi2 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939053] [NEW] Impish update: v5.13.8 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.13.8 upstream stable release from git://git.kernel.org/ selftest: fix build error in tools/testing/selftests/vm/userfaultfd.c pipe: make pipe writes always wake up readers fs/ext2: Avoid page_address on pages returned by ext2_get_page btrfs: fix lost inode on log replay after mix of fsync, rename and inode eviction btrfs: fix rw device counting in __btrfs_free_extra_devids btrfs: mark compressed range uptodate only if all bio succeed Revert "ACPI: resources: Add checks for ACPI IRQ override" ACPI: DPTF: Fix reading of attributes x86/kvm: fix vcpu-id indexed array sizes KVM: add missing compat KVM_CLEAR_DIRTY_LOG ocfs2: fix zero out valid data ocfs2: issue zeroout to EOF blocks mm: memcontrol: fix blocking rstat function called from atomic cgroup1 thresholding code mm/memcg: fix NULL pointer dereference in memcg_slab_free_hook() can: j1939: j1939_xtp_rx_dat_one(): fix rxtimer value between consecutive TP.DT to 750ms can: raw: raw_setsockopt(): fix raw_rcv panic for sock UAF can: peak_usb: pcan_usb_handle_bus_evt(): fix reading rxerr/txerr values can: mcba_usb_start(): add missing urb->transfer_dma initialization can: usb_8dev: fix memory leak can: ems_usb: fix memory leak can: esd_usb2: fix memory leak alpha: register early reserved memory in memblock HID: wacom: Re-enable touch by default for Cintiq 24HDT / 27QHDT net: stmmac: add est_irq_status callback function for GMAC 4.10 and 5.10 NIU: fix incorrect error return, missed in previous revert drm/amd/display: ensure dentist display clock update finished in DCN20 drm/amdgpu: Check pmops for desired suspend state drm/amdgpu: Avoid printing of stack contents on firmware load error drm/amdgpu: Fix resource leak on probe error path blk-iocost: fix operation ordering in iocg_wake_fn() nfc: nfcsim: fix use after free during module unload io_uring: fix io_prep_async_link locking io_uring: don't block level reissue off completion path io_uring: fix poll requests leaking second poll entries cfg80211: Fix possible memory leak in function cfg80211_bss_update RDMA/bnxt_re: Fix stats counters platform/x86: amd-pmc: Fix command completion code platform/x86: amd-pmc: Fix SMU firmware reporting mechanism platform/x86: amd-pmc: Fix missing unlock on error in amd_pmc_send_cmd() RDMA/rxe: Fix memory leak in error path code netfilter: nf_tables: fix audit memory leak in nf_tables_commit bpf: Fix OOB read when printing XDP link fdinfo mac80211: fix enabling 4-address mode on a sta vif after assoc netfilter: conntrack: adjust stop timestamp to real expiry value netfilter: nft_nat: allow to specify layer 4 protocol NAT only i40e: Fix logic of disabling queues i40e: Fix firmware LLDP agent related warning i40e: Fix queue-to-TC mapping on Tx i40e: Fix log TC creation failure when max num of queues is exceeded tipc: fix implicit-connect for SYN+ tipc: fix sleeping in tipc accept routine net: Set true network header for ECN decapsulation net: dsa: mv88e6xxx: silently accept the deletion of VID 0 too loop: reintroduce global lock for safe loop_validate_file() traversal net: qrtr: fix memory leaks ionic: make all rx_mode work threadsafe ionic: catch no ptp support earlier ionic: remove intr coalesce update from napi ionic: fix up dim accounting for tx and rx ionic: count csum_none when offload enabled can: mcp251xfd: mcp251xfd_irq(): stop timestamping worker in case error in IRQ tipc: do not write skb_shinfo frags when doing decrytion octeontx2-pf: Fix interface down flag on error octeontx2-pf: Dont enable backpressure on LBK links net: phy: broadcom: re-add check for PHY_BRCM_DIS_TXCRXC_NOENRGY on the BCM54811 PHY mlx4: Fix missing error code in mlx4_load_one() drm/panel: panel-simple: Fix proper bpc for ytc700tlag_05_201c drm/i915/bios: Fix ports mask KVM: x86: Check the right feature bit for MSR_KVM_ASYNC_PF_ACK access net: llc: fix skb_over_panic drm/msm/dpu: Fix sm8250_mdp register length drm/msm/dp: use dp_ctrl_off_link_stream during PHY compliance test run drm/msm/dp: Initialize the INTF_CONFIG register KVM: selftests: Fix missing break in dirty_log_perf_test arg parsing bpf, sockmap: Zap ingress queues after stopping strparser net/mlx5: Fix flow table chaining net/mlx5e: Disable Rx ntuple offload for uplink representor net/mlx5: E-Switch, Set destination vport vhca id only when merged eswitch is supported net/mlx5: E-Switch, handle devcom events only for ports on the same device net/mlx5e: RX, Avoid possible data corruption when relaxed ordering and LRO combined net/mlx5e: Add NETIF_F_HW_TC
[Kernel-packages] [Bug 1939052] Re: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2
This is the patch for the 13s gen2 with the aforementioned issue relating to volume adjustments using the keyboard function keys. ** Patch added: "Cegion-13s-gen2-sound-0.0.9-003.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939052/+attachment/5516172/+files/linux-5.12-legion-13s-gen2-sound-0.0.9-003.patch ** Bug watch added: Linux Kernel Bug Tracker #208555 https://bugzilla.kernel.org/show_bug.cgi?id=208555 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939052 Title: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2 Status in linux package in Ubuntu: New Bug description: All 3 models need the appropriate HDA verbs sent to properly initialize the sound hardware. Additionally, the Legion 15IMHG05 needs automute disabled otherwise speaker output will not return after removing headphones. The good news is that I have working patches for all 3. However, the 13s Gen2 reportedly has some weirdness on the volume control. I don't have this model of laptop so there's not a lot I can do. It seems tuning the volume up and down using the keys on the keyboard can jump the volume up and down in large increments. Volume adjustments via a GUI do not have this issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hiryu 7243 F pulseaudio /dev/snd/controlC0: hiryu 7243 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 5 10:17:57 2021 InstallationDate: Installed on 2021-04-23 (104 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82K6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 bluetooth.disable_ertm acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2021 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: H1CN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ITHg6 dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrH1CN33WW:bd07/18/2021:br1.33:efr1.33:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6: dmi.product.family: Legion 7 16ITHg6 dmi.product.name: 82K6 dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6 dmi.product.version: Legion 7 16ITHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939052] Re: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2
All patches apply against all of 5.13.x so far (with the latest being 5.13.8). This is a duplicate of https://bugzilla.kernel.org/show_bug.cgi?id=208555 Happy to improve these patches to a point where they could be included.I'm posting this here, because I'm an Ubuntu user and I'd like to see this work merged in. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939052 Title: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2 Status in linux package in Ubuntu: New Bug description: All 3 models need the appropriate HDA verbs sent to properly initialize the sound hardware. Additionally, the Legion 15IMHG05 needs automute disabled otherwise speaker output will not return after removing headphones. The good news is that I have working patches for all 3. However, the 13s Gen2 reportedly has some weirdness on the volume control. I don't have this model of laptop so there's not a lot I can do. It seems tuning the volume up and down using the keys on the keyboard can jump the volume up and down in large increments. Volume adjustments via a GUI do not have this issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hiryu 7243 F pulseaudio /dev/snd/controlC0: hiryu 7243 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 5 10:17:57 2021 InstallationDate: Installed on 2021-04-23 (104 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82K6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 bluetooth.disable_ertm acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2021 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: H1CN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ITHg6 dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrH1CN33WW:bd07/18/2021:br1.33:efr1.33:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6: dmi.product.family: Legion 7 16ITHg6 dmi.product.name: 82K6 dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6 dmi.product.version: Legion 7 16ITHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939052] Re: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2
This is the patch for the Lenovo Yoga 7 14ITL5. ** Patch added: "linux-5.12-legion-sound-yoga-14ITL5-0.0.9-002.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939052/+attachment/5516171/+files/linux-5.12-legion-sound-yoga-14ITL5-0.0.9-002.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939052 Title: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2 Status in linux package in Ubuntu: New Bug description: All 3 models need the appropriate HDA verbs sent to properly initialize the sound hardware. Additionally, the Legion 15IMHG05 needs automute disabled otherwise speaker output will not return after removing headphones. The good news is that I have working patches for all 3. However, the 13s Gen2 reportedly has some weirdness on the volume control. I don't have this model of laptop so there's not a lot I can do. It seems tuning the volume up and down using the keys on the keyboard can jump the volume up and down in large increments. Volume adjustments via a GUI do not have this issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hiryu 7243 F pulseaudio /dev/snd/controlC0: hiryu 7243 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 5 10:17:57 2021 InstallationDate: Installed on 2021-04-23 (104 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82K6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 bluetooth.disable_ertm acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2021 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: H1CN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ITHg6 dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrH1CN33WW:bd07/18/2021:br1.33:efr1.33:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6: dmi.product.family: Legion 7 16ITHg6 dmi.product.name: 82K6 dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6 dmi.product.version: Legion 7 16ITHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939052] [NEW] No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2
Public bug reported: All 3 models need the appropriate HDA verbs sent to properly initialize the sound hardware. Additionally, the Legion 15IMHG05 needs automute disabled otherwise speaker output will not return after removing headphones. The good news is that I have working patches for all 3. However, the 13s Gen2 reportedly has some weirdness on the volume control. I don't have this model of laptop so there's not a lot I can do. It seems tuning the volume up and down using the keys on the keyboard can jump the volume up and down in large increments. Volume adjustments via a GUI do not have this issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hiryu 7243 F pulseaudio /dev/snd/controlC0: hiryu 7243 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 5 10:17:57 2021 InstallationDate: Installed on 2021-04-23 (104 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82K6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 bluetooth.disable_ertm acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2021 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: H1CN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ITHg6 dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrH1CN33WW:bd07/18/2021:br1.33:efr1.33:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6: dmi.product.family: Legion 7 16ITHg6 dmi.product.name: 82K6 dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6 dmi.product.version: Legion 7 16ITHg6 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Patch added: "linux-5.12-sound-legion-15imhg05-0.0.9-legion-001.patch" https://bugs.launchpad.net/bugs/1939052/+attachment/5516149/+files/linux-5.12-sound-legion-15imhg05-0.0.9-legion-001.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939052 Title: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2 Status in linux package in Ubuntu: New Bug description: All 3 models need the appropriate HDA verbs sent to properly initialize the sound hardware. Additionally, the Legion 15IMHG05 needs automute disabled otherwise speaker output will not return after removing headphones. The good news is that I have working patches for all 3. However, the 13s Gen2 reportedly has some weirdness on the volume control. I don't have this model of laptop so there's not a lot I can do. It seems tuning the volume up and down using the keys on the keyboard can jump the volume up and down in large increments. Volume adjustments via a GUI do not have this issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hiryu 7243 F pulseaudio /dev/snd/controlC0: hiryu 7243 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 5 10:17:57 2021 InstallationDate: Installed on 2021-04-23 (104 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82K6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 bluetooth.disable_ertm acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware
[Kernel-packages] [Bug 1938886] Re: rrr:no dh_strip or strip loose setuid bit
This bug was fixed in the package debhelper - 13.3.4ubuntu2 --- debhelper (13.3.4ubuntu2) impish; urgency=medium * objcopy/strip changed in 2.36.1, not keeping file attributes of the original file. Work around that in dh_strip to write to a temporary file, copying attributes, cat'ing this to the original file, copying attributes again to keep the original attributes. LP: #1938886 -- Dimitri John Ledkov Wed, 04 Aug 2021 19:23:25 +0100 ** Changed in: debhelper (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938886 Title: rrr:no dh_strip or strip loose setuid bit Status in bash package in Ubuntu: Invalid Status in binutils package in Ubuntu: New Status in dash package in Ubuntu: Invalid Status in debhelper package in Ubuntu: Fix Released Status in debugedit package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: New Bug description: Over at https://launchpadlibrarian.net/550715513/buildlog_ubuntu- hirsute-amd64.virtualbox_6.1.22-dfsg-2~ubuntu1.21.04.2_BUILDING.txt.gz I have rebuilt an earlier version of virtualbox, that sets Rules- Requires-Root: no and added extra ls statements to find where/when/why setuid bits are getting lost after fixperms. make[1]: Leaving directory '/<>' debian/rules override_dh_strip make[1]: Entering directory '/<>' ls -latr debian/virtualbox/usr/lib/virtualbox/VBoxSDL -rwsr-sr-x 1 buildd buildd 406808 Jul 29 14:34 debian/virtualbox/usr/lib/virtualbox/VBoxSDL ... dh_strip --dbgsym-migration='virtualbox-dbg' debugedit: debian/virtualbox/usr/lib/virtualbox/VBoxSDL.so: Unknown DWARF DW_FORM_0x1f20 a7cf3c43c8b18c3261d2d4737a475bf730ad1554 ls -latr debian/virtualbox/usr/lib/virtualbox/VBoxSDL -rwxr-xr-x 1 buildd buildd 166208 Jul 29 14:35 debian/virtualbox/usr/lib/virtualbox/VBoxSDL It seems to me that either dh_strip or something it calls (strip, debugedit) looses the setuid permission in hirsute and up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1938886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939046] [NEW] Enable CONFIG_SW_SYNC_USER
Public bug reported: Would it be possible to enable SYNC_USER for Waydroid (a new alternative to Anbox) to work OOTB on Ubuntu without having to recompile the kernel? Related to #1939045. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939046 Title: Enable CONFIG_SW_SYNC_USER Status in linux package in Ubuntu: New Bug description: Would it be possible to enable SYNC_USER for Waydroid (a new alternative to Anbox) to work OOTB on Ubuntu without having to recompile the kernel? Related to #1939045. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939045] [NEW] Extend ANDROID_BINDER_DEVICES
Public bug reported: Would it be possible to extend ANDROID_BINDER_DEVICES to 'binder,hwbinder,vndbinder,anbox-binder,anbox-hwbinder,anbox-vndbinder' for Waydroid (a new alternative to Anbox) to work OOTB on Ubuntu without having to recompile the kernel? ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939045 Title: Extend ANDROID_BINDER_DEVICES Status in linux package in Ubuntu: New Bug description: Would it be possible to extend ANDROID_BINDER_DEVICES to 'binder,hwbinder,vndbinder,anbox-binder,anbox-hwbinder,anbox- vndbinder' for Waydroid (a new alternative to Anbox) to work OOTB on Ubuntu without having to recompile the kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829983] Re: memcg_stat from controllers test suite in LTP failed
** Tags added: sru-20210719 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829983 Title: memcg_stat from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: memcg_stat_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_stat_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 1 TINFO: Running memcg_process --shm -k 3 -s 135168 memcg_stat_test 1 TINFO: Warming up pid: 31352 memcg_stat_test 1 TINFO: Process is still here after warm up: 31352 memcg_stat_test 1 TPASS: cache is 135168 as expected memcg_stat_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_stat_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 2 TINFO: Running memcg_process --mmap-file -s 135168 memcg_stat_test 2 TINFO: Warming up pid: 31380 memcg_stat_test 2 TINFO: Process is still here after warm up: 31380 memcg_stat_test 2 TPASS: mapped_file is 135168 as expected memcg_stat_test 3 TINFO: Starting test 3 sh: echo: I/O error memcg_stat_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 3 TINFO: Running memcg_process --mmap-lock1 -s 4096 memcg_stat_test 3 TINFO: Warming up pid: 31409 memcg_stat_test 3 TINFO: Process is still here after warm up: 31409 memcg_stat_test 3 TPASS: unevictable is 4096 as expected memcg_stat_test 4 TINFO: Starting test 4 sh: echo: I/O error memcg_stat_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 4 TINFO: Running memcg_process --mmap-lock2 -s 4096 memcg_stat_test 4 TINFO: Warming up pid: 31434 memcg_stat_test 4 TINFO: Process is still here after warm up: 31434 memcg_stat_test 4 TPASS: unevictable is 4096 as expected memcg_stat_test 5 TINFO: Starting test 5 sh: echo: I/O error memcg_stat_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 5 TPASS: hierarchical_memory_limit is 4096 as expected memcg_stat_test 6 TINFO: Starting test 6 sh: echo: I/O error memcg_stat_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed sh: echo: I/O error memcg_stat_test 6 TFAIL: hierarchical_memory_limit is 4096, 8192 expected memcg_stat_test 7 TINFO: Starting test 7 sh: echo: I/O error memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 7 TCONF: mem+swap is not enabled memcg_stat_test 7 TINFO: Starting test 8 sh: echo: I/O error memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 7 TCONF: mem+swap is not enabled tag=memcg_stat stime=1558504742 dur=4 exit=exited stat=33 core=no cu=16 cs=10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 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: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:17:43 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version:
[Kernel-packages] [Bug 1845919] Re: memcg_failcnt in mm from ubuntu_ltp failed on B 4.15
The same issue seems to be happening with memcg_move_charge_at_immigrat on hirsute/linux 5.11. tag=memcg_max_usage_in_bytes stime=1626909193 dur=5 exit=exited stat=0 core startup='Wed Jul 21 23:13:18 2021' memcg_move_charge_at_immigrate_test 1 TINFO: timeout per run is 0h 5m 0s [...] memcg_move_charge_at_immigrate_test 3 TINFO: Test move file memcg_move_charge_at_immigrate_test 3 TINFO: Running memcg_process --mmap-anon --shm --mmap-file -s 135168 memcg_move_charge_at_immigrate_test 3 TINFO: Warming up pid: 762538 memcg_move_charge_at_immigrate_test 3 TINFO: Process is still here after warm up: 762538 memcg_move_charge_at_immigrate_test 3 TBROK: timed out on memory.usage_in_bytes memcg_move_charge_at_immigrate_test 3 TINFO: AppArmor enabled, this may affect test results memcg_move_charge_at_immigrate_test 3 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) memcg_move_charge_at_immigrate_test 3 TINFO: loaded AppArmor profiles: none -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1845919 Title: memcg_failcnt in mm from ubuntu_ltp failed on B 4.15 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Bug description: Issue found on node amaura, with Bionic 4.15 AMD64: tag=memcg_test_3 stime=1569410880 dur=0 exit=exited stat=0 core=no cu=9 cs=17 startup='Wed Sep 25 11:28:01 2019' memcg_failcnt 1 TINFO: Starting test 1 sh: echo: I/O error memcg_failcnt 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_failcnt 1 TINFO: Running memcg_process --mmap-anon -s 8192 memcg_failcnt 1 TBROK: timeouted on memory.usage_in_bytes tag=memcg_failcnt stime=1569410881 dur=10 exit=exited stat=2 core=no cu=9 cs=2 Probably a test case issue, it needs to be investigated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938845] Re: Legion 7 16ITHg6 - Touchpad undetected
I applied the diff to 5.13.8... and it worked! Thank you!! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938845 Title: Legion 7 16ITHg6 - Touchpad undetected Status in linux package in Ubuntu: New Bug description: I received my Lenovo Legion 7i 16ITHg6 laptop today. The touchpad seems to be entirely undetected. I've attached the contents of /proc/bus/input/devices as devices.txt. No touchpad device is shown. USB mice work. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hiryu 7344 F pulseaudio /dev/snd/controlC0: hiryu 7344 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Aug 3 20:05:13 2021 InstallationDate: Installed on 2021-04-23 (103 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82K6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash nvidia-drm.modeset=1 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 bluetooth.disable_ertm acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2021 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: H1CN26WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ITHg6 dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvrH1CN26WW:bd05/22/2021:br1.26:efr1.26:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6: dmi.product.family: Legion 7 16ITHg6 dmi.product.name: 82K6 dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6 dmi.product.version: Legion 7 16ITHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939035] [NEW] memory.usage_in_bytes from ubuntu_ltp.controllers.memcg_subgroup_charge times out in Hirsute 5.11
Public bug reported: memory.usage_in_bytes from ubuntu_ltp.controllers.memcg_subgroup_charge times out when running with hirsute/linux 5.11. startup='Mon Jul 19 15:17:41 2021' memcg_subgroup_charge 1 TINFO: timeout per run is 0h 5m 0s memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 1 TINFO: Test that group and subgroup have no relationship memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 270336 memcg_subgroup_charge 1 TINFO: Warming up pid: 443417 memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 443417 memcg_subgroup_charge 1 TBROK: timed out on memory.usage_in_bytes memcg_subgroup_charge 1 TINFO: AppArmor enabled, this may affect test results memcg_subgroup_charge 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) memcg_subgroup_charge 1 TINFO: loaded AppArmor profiles: none Summary: passed 0 failed 0 broken 1 skipped 0 warnings 0 tag=memcg_subgroup_charge stime=1626707861 dur=11 exit=exited stat=2 core=no cu=19 cs=12 This is not a regression as it already failed on previous releases. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Tags: 5.11 hirsute sru-20210719 ** Tags added: 5.11 hirsute sru-20210719 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) 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/1939035 Title: memory.usage_in_bytes from ubuntu_ltp.controllers.memcg_subgroup_charge times out in Hirsute 5.11 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Hirsute: New Bug description: memory.usage_in_bytes from ubuntu_ltp.controllers.memcg_subgroup_charge times out when running with hirsute/linux 5.11. startup='Mon Jul 19 15:17:41 2021' memcg_subgroup_charge 1 TINFO: timeout per run is 0h 5m 0s memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 1 TINFO: Test that group and subgroup have no relationship memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 270336 memcg_subgroup_charge 1 TINFO: Warming up pid: 443417 memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 443417 memcg_subgroup_charge 1 TBROK: timed out on memory.usage_in_bytes memcg_subgroup_charge 1 TINFO: AppArmor enabled, this may affect test results memcg_subgroup_charge 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) memcg_subgroup_charge 1 TINFO: loaded AppArmor profiles: none Summary: passed 0 failed 0 broken 1 skipped 0 warnings 0 tag=memcg_subgroup_charge stime=1626707861 dur=11 exit=exited stat=2 core=no cu=19 cs=12 This is not a regression as it already failed on previous releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934175] Re: Kernel oops due to uninitialized list on kernfs (kernfs_kill_sb)
** Tags removed: verification-needed-bionic ** Tags added: bionic 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/1934175 Title: Kernel oops due to uninitialized list on kernfs (kernfs_kill_sb) Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] * We had a recent report of a kernel crash due to a NULL pointer dereference in a Bionic 4.15 derivative kernel, as per the following log collected: [...] [537105.767348] SLUB: Unable to allocate memory on node -1, gfp=0x14000c0(GFP_KERNEL) [...] [537105.767368] BUG: unable to handle kernel NULL pointer dereference at 0008 [537105.11] IP: kernfs_kill_sb+0x31/0x70 [537105.783582] PGD 0 P4D 0 [537105.787844] Oops: 0002 [#1] SMP PTI [...] RIP: 0010:kernfs_kill_sb+0x31/0x70 RSP: 0018:b90aec1afd00 EFLAGS: 00010286 RAX: RBX: 9fdbd567d900 RCX: a0143885ae01 RDX: RSI: a0143885ae00 RDI: a2937c40 RBP: b90aec1afd10 R08: a0150b581510 R09: 0001814d R10: b90aec1afcd8 R11: 0100 R12: a01436e43000 R13: a01436e43000 R14: R15: 9fdbd567d900 FS: 7fe41a615b80() GS:a01afea4() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0008 CR3: 007dfe3cc003 CR4: 003606e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: sysfs_kill_sb+0x1f/0x40 deactivate_locked_super+0x48/0x80 kernfs_mount_ns+0x1eb/0x230 sysfs_mount+0x66/0xc0 mount_fs+0x37/0x160 ? alloc_vfsmnt+0x1b3/0x230 vfs_kern_mount.part.24+0x5d/0x110 do_mount+0x5ed/0xce0 [...] * The following detailed call stack plus the disassembly help to understand the cause of the issue: mount_fs() --sysfs_mount() kernfs_mount_ns() --deactivate_locked_super() sysfs_kill_sb() --kernfs_kill_sb() The below disassembly of kernfs_kill_sb() clarifies exactly the issue: 812f46e0 : [ ... prologue ...] 48 8b 9f 08 04 00 00mov0x408(%rdi),%rbx # %rbx = kernfs_super_info *info = sb->s_fs_info 49 89 fcmov%rdi,%r12 # %r12 = super_block *sb 48 c7 c7 40 7c 53 82mov$0x82537c40,%rdi # %rdi = _mutex (global) 812f46f9: R_X86_64_32S kernfs_mutex e8 ee da 67 00 callq 819721f0 # mutex_lock(_mutex); [...] 48 8b 53 18 mov0x18(%rbx),%rdx # %rdx = info->node 48 8b 43 20 mov0x20(%rbx),%rax # based on splat, RAX == 0x0 [info->head.prev] 48 89 42 08 mov%rax,0x8(%rdx) # <- OOPS [tried to assign next->prev = prev, see __list_del()] 48 89 10mov%rdx,(%rax) 48 b8 00 01 00 00 00movabs $0xdead0100,%rax # node->next = LIST_POISON1 [...] * The fix for this issue comes from upstream commit 82382acec0c9 ("kernfs: deal with kernfs_fill_super() failures"); this commit is a very trivial fix that adds an INIT_LIST_HEAD(>node) in kernfs_mount_ns(), making the list prev/next pointers valid since the beginning. Unfortunately this commit wasn't CCed to stable email when sent, so it wasn't automatically picked up by Ubuntu kernel; now it was properly submitted to stable list [0]. * Along with this fix, we found another commit (7b745a4e4051) which is a small/simple fix to correlated code, that also should have been sent to 4.14.y stable branch, but for some reason wasn't. Since both commits were accepted in linux-stable, we are hereby proposing the backport for Ubuntu kernel 4.15. [0] https://lore.kernel.org/stable/20210622210622.9925-1-gpicc...@canonical.com/ [Test Case] * We don't have a real test case, although low-memory condition or an artificial kprobe reproducer could easily trigger the issue. * We booted a qemu virtual machine with a kernel containing both patches with no issues. [Where problems could occur] * The likelihood of issues are low, specially due to the fact both patches are very simple and they are on upstream kernel for more than 3 years (and were quickly accepted in 4.14.y stable branch last week). * With that sad, the second patch could potentially introduce issues with super_block references - I honestly cannot conceive any issues potentially caused by patch 1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934175/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933518] Re: Update SmartPQI driver
Jeff Lane, someone from Microchip should verify whether the Focal hwe-5.11 (5.11.0-26.28_20.04.1) and Hirsute (5.11.0-26.28) kernels from proposed fix the issue. ** Changed in: linux (Ubuntu Hirsute) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933518 Title: Update SmartPQI driver Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Won't Fix Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] Improves support in SmartPQI for most recent controllers [Fixes] All are in mainline currently and cleanly cherry pick into Hirsute. c64aab41c5e1 scsi: smartpqi: Remove unused functions 5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static checker issue 667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045 75fbeacca3ad scsi: smartpqi: Add new PCI IDs 43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from hibernation d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs 18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets 55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and target_port_protocols ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf() 3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues 66f1c2b40270 scsi: smartpqi: Update device scan operations 2790cd4d3f6a scsi: smartpqi: Update OFA management 5be9db069d3f scsi: smartpqi: Update RAID bypass handling 9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown 37f3318199ce scsi: smartpqi: Synchronize device resets with mutex 4ccc354bac14 scsi: smartpqi: Update soft reset management for OFA 06b41e0d1800 scsi: smartpqi: Update event handler 7a84a821f194 scsi: smartpqi: Add support for wwid ae0c189db4f1 scsi: smartpqi: Remove timeouts from internal cmds 99a12b487f19 scsi: smartpqi: Disable WRITE SAME for HBA NVMe disks 5be746d7d74b scsi: smartpqi: Add host level stream detection enable c7ffedb3a774 scsi: smartpqi: Add stream detection 583891c9e509 scsi: smartpqi: Align code with oob driver 598bef8d7942 scsi: smartpqi: Add support for long firmware version f6cc2a774aa7 scsi: smartpqi: Add support for BMIC sense feature cmd and feature bits 7a012c23c7a7 scsi: smartpqi: Add support for RAID1 writes 6702d2c40f31 scsi: smartpqi: Add support for RAID5 and RAID6 writes 1a22bc4bee22 scsi: smartpqi: Refactor scatterlist code 281a817f232e scsi: smartpqi: Refactor aio submission code 2708a25643ab scsi: smartpqi: Add support for new product ids b622a601a13a scsi: smartpqi: Correct request leakage during reset operations c6d3ee209b9e scsi: smartpqi: Use host-wide tag space The patches they provided only apply the hunk that applies to the SmartPQI driver. This commit was a much wider commit that removes references to MODULE_SUPPORTED_DEVICE in many drivers across the kernel. 6417f03132a6 module: remove never implemented MODULE_SUPPORTED_DEVICE [Testing] On machines equipped with SmartPQI SCSI controller: 1. reboot tests 2. insmod/rmmod tests 3. fio testing: no performance regressions [Regression Risk] Patchset changes only smartpqi driver so regression is limited to systems equipped with this SCSI device. On such SmartPQI-equipped systems the patchset can cause data corruption, data loss or unavailability of SCSI storage and boot failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927749] Re: ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8
** Tags removed: verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927749 Title: ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8 Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Invalid Status in linux-aws source package in Focal: Fix Released Status in linux source package in Groovy: Won't Fix Status in linux-aws source package in Groovy: Won't Fix Status in linux source package in Hirsute: Fix Released Status in linux-aws source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Status in linux-aws source package in Impish: Fix Released Bug description: [Impact] arm64 only focal/aws 5.8.0-1031.33~20.04.1-aws and 5.8.0-1032.34~20.04.1-aws - regression. Works fine on previous Focal cycle (5.8.0-1028.30~20.04.3-aws) and current Groovy 5.8. 12. 05/06 07:01:39 DEBUG| utils:0153| [stdout] TAP version 13 13. 05/06 07:01:39 DEBUG| utils:0153| [stdout] 1..1 14. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 15. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 16. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 17. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 18. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 19. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check [PASS] 20. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 21. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 22. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 23. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct functions against tracers [UNRESOLVED] 24. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] 25. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - add/remove kprobe events [PASS] 26. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - add/remove synthetic events [PASS] 27. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event - selective clear (compatibility) [PASS] 28. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [13] Generic dynamic event - generic clear event [PASS] 29. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with event level files [PASS] 30. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [15] event tracing - restricts events based on pid notrace filtering [FAIL] 31. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [16] event tracing - restricts events based on pid [PASS] 32. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [17] event tracing - enable/disable with subsystem level files [PASS] 33. 05/06 07:01:46 DEBUG| utils:0153| [stdout] # [18] event tracing - enable/disable with top level files [PASS] [Test Plan] * Run ftrace test from kernel selftests. [Where problems could occur] * Only kernel selftests should be affected. * ftrace test can have false positives or negatives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933518] Re: Update SmartPQI driver
** Changed in: linux (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933518 Title: Update SmartPQI driver Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Won't Fix Status in linux source package in Hirsute: Fix Released Bug description: [Impact] Improves support in SmartPQI for most recent controllers [Fixes] All are in mainline currently and cleanly cherry pick into Hirsute. c64aab41c5e1 scsi: smartpqi: Remove unused functions 5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static checker issue 667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045 75fbeacca3ad scsi: smartpqi: Add new PCI IDs 43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from hibernation d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs 18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets 55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and target_port_protocols ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf() 3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues 66f1c2b40270 scsi: smartpqi: Update device scan operations 2790cd4d3f6a scsi: smartpqi: Update OFA management 5be9db069d3f scsi: smartpqi: Update RAID bypass handling 9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown 37f3318199ce scsi: smartpqi: Synchronize device resets with mutex 4ccc354bac14 scsi: smartpqi: Update soft reset management for OFA 06b41e0d1800 scsi: smartpqi: Update event handler 7a84a821f194 scsi: smartpqi: Add support for wwid ae0c189db4f1 scsi: smartpqi: Remove timeouts from internal cmds 99a12b487f19 scsi: smartpqi: Disable WRITE SAME for HBA NVMe disks 5be746d7d74b scsi: smartpqi: Add host level stream detection enable c7ffedb3a774 scsi: smartpqi: Add stream detection 583891c9e509 scsi: smartpqi: Align code with oob driver 598bef8d7942 scsi: smartpqi: Add support for long firmware version f6cc2a774aa7 scsi: smartpqi: Add support for BMIC sense feature cmd and feature bits 7a012c23c7a7 scsi: smartpqi: Add support for RAID1 writes 6702d2c40f31 scsi: smartpqi: Add support for RAID5 and RAID6 writes 1a22bc4bee22 scsi: smartpqi: Refactor scatterlist code 281a817f232e scsi: smartpqi: Refactor aio submission code 2708a25643ab scsi: smartpqi: Add support for new product ids b622a601a13a scsi: smartpqi: Correct request leakage during reset operations c6d3ee209b9e scsi: smartpqi: Use host-wide tag space The patches they provided only apply the hunk that applies to the SmartPQI driver. This commit was a much wider commit that removes references to MODULE_SUPPORTED_DEVICE in many drivers across the kernel. 6417f03132a6 module: remove never implemented MODULE_SUPPORTED_DEVICE [Testing] On machines equipped with SmartPQI SCSI controller: 1. reboot tests 2. insmod/rmmod tests 3. fio testing: no performance regressions [Regression Risk] Patchset changes only smartpqi driver so regression is limited to systems equipped with this SCSI device. On such SmartPQI-equipped systems the patchset can cause data corruption, data loss or unavailability of SCSI storage and boot failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927749] Re: ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8
** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Krzysztof Kozlowski (krzk) ** Changed in: linux-aws (Ubuntu Focal) Status: New => Fix Released ** Changed in: linux-aws (Ubuntu Focal) Assignee: (unassigned) => Krzysztof Kozlowski (krzk) ** Changed in: linux-aws (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: linux-aws (Ubuntu Groovy) Assignee: (unassigned) => Krzysztof Kozlowski (krzk) ** Changed in: linux-aws (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: linux-aws (Ubuntu Hirsute) Assignee: (unassigned) => Krzysztof Kozlowski (krzk) ** Changed in: linux-aws (Ubuntu Impish) Status: New => Fix Released ** Changed in: linux-aws (Ubuntu Impish) Assignee: (unassigned) => Krzysztof Kozlowski (krzk) ** Changed in: linux-aws (Ubuntu Groovy) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Groovy) Status: Fix Released => Won't Fix ** Changed in: linux-aws (Ubuntu Groovy) Status: Fix Released => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927749 Title: ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8 Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Invalid Status in linux-aws source package in Focal: Fix Released Status in linux source package in Groovy: Won't Fix Status in linux-aws source package in Groovy: Won't Fix Status in linux source package in Hirsute: Fix Released Status in linux-aws source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Status in linux-aws source package in Impish: Fix Released Bug description: [Impact] arm64 only focal/aws 5.8.0-1031.33~20.04.1-aws and 5.8.0-1032.34~20.04.1-aws - regression. Works fine on previous Focal cycle (5.8.0-1028.30~20.04.3-aws) and current Groovy 5.8. 12. 05/06 07:01:39 DEBUG| utils:0153| [stdout] TAP version 13 13. 05/06 07:01:39 DEBUG| utils:0153| [stdout] 1..1 14. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 15. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 16. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 17. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 18. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 19. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check [PASS] 20. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 21. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 22. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 23. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct functions against tracers [UNRESOLVED] 24. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] 25. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - add/remove kprobe events [PASS] 26. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - add/remove synthetic events [PASS] 27. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event - selective clear (compatibility) [PASS] 28. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [13] Generic dynamic event - generic clear event [PASS] 29. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with event level files [PASS] 30. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [15] event tracing - restricts events based on pid notrace filtering [FAIL] 31. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [16] event tracing - restricts events based on pid [PASS] 32. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [17] event tracing - enable/disable with subsystem level files [PASS] 33. 05/06 07:01:46 DEBUG| utils:0153| [stdout] # [18] event tracing - enable/disable with top level files [PASS] [Test Plan] * Run ftrace test from kernel selftests. [Where problems could occur] * Only kernel selftests should be affected. * ftrace test can have false positives or negatives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831043] Re: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D
bionic/azure 4.15.0-1122.135 and bionic/azure-fips 4.15.0-2034.38, only on Azure instance Standard_D48_v3 has a slightly different error message: 04:06:33 DEBUG| [stdout] move_pages12.c:274: TINFO: Free RAM 194497904 kB 04:06:33 DEBUG| [stdout] move_pages12.c:292: TINFO: Increasing 2048kB hugepages pool on node 0 to 4 04:06:33 DEBUG| [stdout] move_pages12.c:302: TINFO: Increasing 2048kB hugepages pool on node 1 to 4 04:06:33 DEBUG| [stdout] move_pages12.c:218: TINFO: Allocating and freeing 4 hugepages on node 0 04:06:33 DEBUG| [stdout] move_pages12.c:218: TINFO: Allocating and freeing 4 hugepages on node 1 04:06:33 DEBUG| [stdout] move_pages12.c:208: TPASS: Bug not reproduced 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:106: TFAIL: madvise failed: ENOMEM (12) 04:06:33 DEBUG| [stdout] move_pages12.c:142: TFAIL: move_pages failed: EINVAL (22) ** Tags added: fips-test sru-20210719 -- 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/1831043 Title: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-azure source package in Bionic: New Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Bug description: This is a new test case landed 8 days ago, but we already have the patch in B, and it looks like this is not failing across all the nodes: move_pages12.c:114: FAIL: move_pages failed: ENOMEM <<>> tag=move_pages12 stime=1559209337 cmdline="move_pages12" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s move_pages12.c:235: INFO: Free RAM 31883452 kB move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:169: PASS: Bug not reproduced move_pages12.c:114: FAIL: move_pages failed: ENOMEM move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL:
[Kernel-packages] [Bug 1821903] Re: svm in ubuntu_kvm_unit_tests failed on 3.13 / 4.4 / 4.15
Found on bionic/ibm-gt 4.15.0-1098.108 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821903 Title: svm in ubuntu_kvm_unit_tests failed on 3.13 / 4.4 / 4.15 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Incomplete Status in linux-signed-lts-xenial source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux-signed-lts-xenial source package in Xenial: Invalid Status in linux source package in Cosmic: Won't Fix Status in linux-signed-lts-xenial source package in Cosmic: Invalid Bug description: This svm test timeouted on T-3.13 failed on T-4.4 with: root@gonzo:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests# TESTNAME=svm TIMEOUT=90s ACCEL= ./x86/run x86/svm.flat -smp 2 -cpu qemu64,+svm timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/svm.flat -smp 2 -cpu qemu64,+svm # -initrd /tmp/tmp.PDi0UKyCcl enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 466000 cr4 = 20 PASS: null PASS: vmrun PASS: ioio PASS: vmrun intercept check PASS: cr3 read intercept PASS: cr3 read nointercept PASS: cr3 read intercept emulate PASS: dr intercept check PASS: msr intercept check PASS: mode_switch PASS: asid_zero PASS: sel_cr0_bug FAIL: tsc_adjust Latency VMRUN : max: 80562 min: 19763 avg: 20374 Latency VMEXIT: max: 83146 min: 20193 avg: 20834 PASS: latency_run_exit Latency VMLOAD: max: 38298 min: 4619 avg: 4838 Latency VMSAVE: max: 32870 min: 4637 avg: 4809 Latency STGI: max: 55478 min: 3846 avg: 3923 Latency CLGI: max: 67473 min: 3379 avg: 3437 PASS: latency_svm_insn SUMMARY: 15 tests, 1 unexpected failures ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-143-generic 4.4.0-143.169~14.04.2 ProcVersionSignature: User Name 4.4.0-143.169~14.04.2-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Wed Mar 27 11:00:42 2019 SourcePackage: linux-signed-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939024] [NEW] linux-azure Enable CONFIG_RT_GROUP_SCHED
Public bug reported: SRU Justification [Impact] Microsoft has requested that CONFIG_RT_GROUP_SCHED be enabled. This option has no discernible runtime impact in the default case. As quoted from research performed by Colin King, "I ran some synthetic stress-ng throughput and latency tests with and without CONFIG_RT_GROUP_SCHED on CONFIG_RT_GROUP_SCHED. I don't see enough variation in the throughput or latency to warrant any concern about enabling this option. We have quite a bit of small jitter on the results, but overall the kernel results are similar enough to make me feel OK to enable this option for Focal." [Test Case] Microsoft has tested this option using kernels at https://kernel.ubuntu.com/~rtg/azure-rt-group-sched-sf00314473/. The customer requesting this config option verified that it satisfied their requirements. Microsft also determined that there were no performance regressions for the default case, i.e., when no RT priority threads were created. [Where things could go awry] Adding options to the scheduler could impact work loads that we have yet to observe. [Other Info] SF: 00314473 ** Affects: linux-azure (Ubuntu) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: New ** Affects: linux-azure (Ubuntu Focal) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: New ** Affects: linux-azure (Ubuntu Hirsute) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: New ** Affects: linux-azure (Ubuntu Impish) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: New ** Also affects: linux-azure (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Hirsute) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Impish) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1939024 Title: linux-azure Enable CONFIG_RT_GROUP_SCHED Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Focal: New Status in linux-azure source package in Hirsute: New Status in linux-azure source package in Impish: New Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_RT_GROUP_SCHED be enabled. This option has no discernible runtime impact in the default case. As quoted from research performed by Colin King, "I ran some synthetic stress-ng throughput and latency tests with and without CONFIG_RT_GROUP_SCHED on CONFIG_RT_GROUP_SCHED. I don't see enough variation in the throughput or latency to warrant any concern about enabling this option. We have quite a bit of small jitter on the results, but overall the kernel results are similar enough to make me feel OK to enable this option for Focal." [Test Case] Microsoft has tested this option using kernels at https://kernel.ubuntu.com/~rtg/azure-rt-group-sched-sf00314473/. The customer requesting this config option verified that it satisfied their requirements. Microsft also determined that there were no performance regressions for the default case, i.e., when no RT priority threads were created. [Where things could go awry] Adding options to the scheduler could impact work loads that we have yet to observe. [Other Info] SF: 00314473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1939024/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821903] Re: svm in ubuntu_kvm_unit_tests failed on 3.13 / 4.4 / 4.15
Found on bionic/fips 4.15.0-1068.77 (and previous: 4.15.0-1067.76) ** Tags added: fips-test sru-20210719 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821903 Title: svm in ubuntu_kvm_unit_tests failed on 3.13 / 4.4 / 4.15 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Incomplete Status in linux-signed-lts-xenial source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux-signed-lts-xenial source package in Xenial: Invalid Status in linux source package in Cosmic: Won't Fix Status in linux-signed-lts-xenial source package in Cosmic: Invalid Bug description: This svm test timeouted on T-3.13 failed on T-4.4 with: root@gonzo:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests# TESTNAME=svm TIMEOUT=90s ACCEL= ./x86/run x86/svm.flat -smp 2 -cpu qemu64,+svm timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/svm.flat -smp 2 -cpu qemu64,+svm # -initrd /tmp/tmp.PDi0UKyCcl enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 466000 cr4 = 20 PASS: null PASS: vmrun PASS: ioio PASS: vmrun intercept check PASS: cr3 read intercept PASS: cr3 read nointercept PASS: cr3 read intercept emulate PASS: dr intercept check PASS: msr intercept check PASS: mode_switch PASS: asid_zero PASS: sel_cr0_bug FAIL: tsc_adjust Latency VMRUN : max: 80562 min: 19763 avg: 20374 Latency VMEXIT: max: 83146 min: 20193 avg: 20834 PASS: latency_run_exit Latency VMLOAD: max: 38298 min: 4619 avg: 4838 Latency VMSAVE: max: 32870 min: 4637 avg: 4809 Latency STGI: max: 55478 min: 3846 avg: 3923 Latency CLGI: max: 67473 min: 3379 avg: 3437 PASS: latency_svm_insn SUMMARY: 15 tests, 1 unexpected failures ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-143-generic 4.4.0-143.169~14.04.2 ProcVersionSignature: User Name 4.4.0-143.169~14.04.2-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Wed Mar 27 11:00:42 2019 SourcePackage: linux-signed-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929831] Re: cifs: On cifs_reconnect, resolve the hostname again
I am tagging this verification done. MSFT has been using this patch set in the Azure derivative kernel for several weeks and have confirmed it fixes the issue. ** 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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1929831 Title: cifs: On cifs_reconnect, resolve the hostname again Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: Fix Released Status in linux source package in Groovy: Won't Fix Status in linux-azure source package in Groovy: Won't Fix Bug description: SRU Justification [Impact] The Microsoft CIFS team is requesting below patch to be backported for 5.4 Azure tuned kernel https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4e456b30f78c429b183db420e23b26cde7e03a78 A customer is encountering the bug fixed by this patch. [Fix] 7d397a034d5c45528c7bdf7fc3752c4793029cce cifs: rename reconn_inval_dfs_target() 7d6535b720421d58886d5590ffc3617d359aa871 cifs: Simplify reconnect code when dfs upcall is enabled 4e456b30f78c429b183db420e23b26cde7e03a78 cifs: On cifs_reconnect, resolve the hostname again. The first 2 patches are scaffolding to make the backport simpler. the 3rd patch is the bug fix. [Test Plan] The test kernel at https://launchpad.net/~timg- tpi/+archive/ubuntu/cifs-reconnect-sf00309672 has been found to fix the issue. [Where problems could occur] This could perturb CIFS connections in new and different ways. [Other Info] https://canonical.my.salesforce.com/5004K05pQNG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917616] Re: vmx test from ubuntu_kvm_unit_tests failed on Bionic/Focal
Found on bionic/azure-4.15 4.15.0-1122.135 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917616 Title: vmx test from ubuntu_kvm_unit_tests failed on Bionic/Focal Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Bug description: Appearing in bionic 5.4.0-67.75~18.04.1 affecting lowlatency and hwe flavors. 2538. 02/25 00:10:11 DEBUG| utils:0153| [stdout] Unhandled exception 13 #GP at ip 004071a3 2539. 02/25 00:10:11 DEBUG| utils:0153| [stdout] error_code= rflags=00010006 cs=0008 2540. 02/25 00:10:11 DEBUG| utils:0153| [stdout] rax=0078 rcx=0809 rdx= rbx=0009 2541. 02/25 00:10:11 DEBUG| utils:0153| [stdout] rbp=0047efdf rsi=0042568d rdi=0042568d 2542. 02/25 00:10:11 DEBUG| utils:0153| [stdout] r8=000a r9=03f8 r10=000d r11= 2543. 02/25 00:10:11 DEBUG| utils:0153| [stdout] r12= r13= r14=00403dcc r15= 2544. 02/25 00:10:11 DEBUG| utils:0153| [stdout] cr0=80010031 cr2=e000 cr3=00477000 cr4=2020 2545. 02/25 00:10:11 DEBUG| utils:0153| [stdout] cr8=0007 2546. 02/25 00:10:11 DEBUG| utils:0153| [stdout] STACK: @4071a3 40170b 4004dd 2547. 02/25 00:10:11 DEBUG| utils:0153| [stdout] FAIL vmx 2548. 02/25 00:10:11 ERROR| test:0414| Exception escaping from test: 2549. Traceback (most recent call last): 2550. File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec 2551. _call_test_function(self.execute, *p_args, **p_dargs) 2552. File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function 2553. return func(*args, **dargs) 2554. File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute 2555. postprocess_profiled_run, args, dargs) 2556. File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once 2557. self.run_once(*args, **dargs) 2558. File "/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py", line 80, in run_once 2559. raise error.TestError("Test failed for {}".format(test_name)) 2560. TestError: Test failed for vmx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1917616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931325] Re: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15
Found on bionic/azure-4.15 4.15.0-1122.135 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931325 Title: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15 Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Bug description: [Impact] Test case cfs_bandwidth01 in LTP sched test suite is a reproducer of a CFS unthrottle_cfs_rq() issue (fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning). This test triggers a warning on our 4.15 kernel: LTP: starting cfs_bandwidth01 (cfs_bandwidth01 -i 5) [ cut here ] rq->tmp_alone_branch != >leaf_cfs_rq_list WARNING: CPU: 0 PID: 0 at /build/linux-fYK9kF/linux-4.15.0/kernel/sched/fair.c:393 unthrottle_cfs_rq+0x16f/0x200 Modules linked in: input_leds joydev serio_raw mac_hid qemu_fw_cfg kvm_intel kvm irqbypass sch_fq_codel binfmt_misc ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear cirrus ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse virtio_blk pata_acpi floppy virtio_net i2c_piix4 CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-144-generic #148-Ubuntu Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 RIP: 0010:unthrottle_cfs_rq+0x16f/0x200 RSP: 0018:989ebfc03e80 EFLAGS: 00010082 RAX: RBX: 989eb4c6ac00 RCX: RDX: 0005 RSI: acb63c4d RDI: 0046 RBP: 989ebfc03ea8 R08: 00af39e61b33 R09: acb63c20 R10: R11: 0001 R12: 989eb57fe400 R13: 989ebfc21900 R14: 0001 R15: 0001 FS: () GS:989ebfc0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 55593258d618 CR3: 7a044000 CR4: 06f0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: distribute_cfs_runtime+0xc3/0x110 sched_cfs_period_timer+0xff/0x220 ? sched_cfs_slack_timer+0xd0/0xd0 __hrtimer_run_queues+0xdf/0x230 hrtimer_interrupt+0xa0/0x1d0 smp_apic_timer_interrupt+0x6f/0x140 apic_timer_interrupt+0x90/0xa0 RIP: 0010:native_safe_halt+0x12/0x20 RSP: 0018:ac603e28 EFLAGS: 0246 ORIG_RAX: ff11 RAX: abbc9280 RBX: RCX: RDX: RSI: RDI: RBP: ac603e28 R08: 00af39850067 R09: 989e73749d00 R10: R11: 7fff R12: R13: R14: R15: ? __sched_text_end+0x1/0x1 default_idle+0x20/0x100 arch_cpu_idle+0x15/0x20 default_idle_call+0x23/0x30 do_idle+0x172/0x1f0 cpu_startup_entry+0x73/0x80 rest_init+0xae/0xb0 start_kernel+0x4dc/0x500 x86_64_start_reservations+0x24/0x26 x86_64_start_kernel+0x74/0x77 secondary_startup_64+0xa5/0xb0 Code: 50 09 00 00 49 39 85 60 09 00 00 74 68 80 3d 3a 6e 54 01 00 75 5f 31 db 48 c7 c7 c0 3d 2d ac c6 05 28 6e 54 01 01 e8 11 36 fc ff <0f> 0b 48 85 db 74 43 49 8b 85 78 09 00 00 49 39 85 70 09 00 00 ---[ end trace b6b9a70bc2945c0c ]--- [Fix] Base on the test case description, we will need these fixes: * fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning * b34cb07dde7c23 sched/fair: Fix enqueue_task_fair() warning some more * 39f23ce07b9355 sched/fair: Fix unthrottle_cfs_rq() for leaf_cfs_rq list * 6d4d22468dae3d sched/fair: Reorder enqueue/dequeue_task_fair path * 5ab297bab98431 sched/fair: Fix reordering of enqueue/dequeue_task_fair() Backport needed for Bionic since we're missing some new variables / coding style changes introduced in the following commits (and their corresponding fixes): * 97fb7a0a8944bd sched: Clean up and harmonize the coding style of the scheduler code base * 9f68395333ad7f sched/pelt: Add a new runnable average signal * 6212437f0f6043 sched/fair: Fix runnable_avg for throttled cfs * 43e9f7f231e40e sched/fair: Start tracking SCHED_IDLE tasks count in cfs_rq I have also searched in the upstream tree to see if there is any other commit claim to be a fix of these but didn't see any. [Test] Test kernel can be found here: https://people.canonical.com/~phlin/kernel/lp-1931325-cfs_bandwidth01/ With these patches applied, the test can pass without triggering this warning.
[Kernel-packages] [Bug 1932029] Re: Support builtin revoked certificates
** Description changed: [Impact] Upstream linux kernel now supports configuring built-in revoked certificates for the .blacklist keyring. Add support in our kernel configuration to have built-in revoked certificates. Revoke UEFI amd64 & arm64 2012 signing certificate. Under UEFI Secureboot with lockdown, shim may attempt to communicate revoked certificates to the kernel and depending on how good EFI firmware is, this may or may not succeed. By having these built-in, it will be prohibited to kexec file_load older kernels that were signed with now revoked certificates, however one boots. [Test Plan] * Boot kernel directly, or just with grub, and without shim * Check that $ sudo keyctl list %:.blacklist Contains assymetric 2012 key. [Where problems could occur] * Derivative and per-arch kernels may need to revoke different keys, thus this should be evaluated on per arch & flavour basis as to which keys to revoke. [Other Info] * In theory, this only needs to be revoked on amd64 and arm64, but empty revocation list is not allowed by the kernel configury, thus at the moment revoking 2012 UEFI cert for all architectures. + + * an ubuntu kernel team regression test is being added to assert that expected revoked certificates have been revoked + see https://lists.ubuntu.com/archives/kernel-team/2021-August/122986.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932029 Title: Support builtin revoked certificates Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Hirsute: New Bug description: [Impact] Upstream linux kernel now supports configuring built-in revoked certificates for the .blacklist keyring. Add support in our kernel configuration to have built-in revoked certificates. Revoke UEFI amd64 & arm64 2012 signing certificate. Under UEFI Secureboot with lockdown, shim may attempt to communicate revoked certificates to the kernel and depending on how good EFI firmware is, this may or may not succeed. By having these built-in, it will be prohibited to kexec file_load older kernels that were signed with now revoked certificates, however one boots. [Test Plan] * Boot kernel directly, or just with grub, and without shim * Check that $ sudo keyctl list %:.blacklist Contains assymetric 2012 key. [Where problems could occur] * Derivative and per-arch kernels may need to revoke different keys, thus this should be evaluated on per arch & flavour basis as to which keys to revoke. [Other Info] * In theory, this only needs to be revoked on amd64 and arm64, but empty revocation list is not allowed by the kernel configury, thus at the moment revoking 2012 UEFI cert for all architectures. * an ubuntu kernel team regression test is being added to assert that expected revoked certificates have been revoked see https://lists.ubuntu.com/archives/kernel-team/2021-August/122986.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938998] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1938998/+attachment/5516114/+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/1938998 Title: Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Incomplete Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938998] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1938998/+attachment/5516115/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938998 Title: Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Incomplete Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938998] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1938998/+attachment/5516108/+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/1938998 Title: Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Incomplete Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938998] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1938998/+attachment/5516111/+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/1938998 Title: Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Incomplete Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938998] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1938998/+attachment/5516105/+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/1938998 Title: Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Incomplete Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938998] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1938998/+attachment/5516102/+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/1938998 Title: Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Incomplete Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938998] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1938998/+attachment/5516109/+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/1938998 Title: Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Incomplete Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938998] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1938998/+attachment/5516112/+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/1938998 Title: Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Incomplete Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938998] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1938998/+attachment/5516103/+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/1938998 Title: Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Incomplete Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938998] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1938998/+attachment/5516104/+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/1938998 Title: Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Incomplete Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938998] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1938998/+attachment/5516113/+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/1938998 Title: Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Incomplete Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938998] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1938998/+attachment/5516106/+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/1938998 Title: Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Incomplete Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938998] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1938998/+attachment/5516110/+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/1938998 Title: Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Incomplete Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938998] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1938998/+attachment/5516107/+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/1938998 Title: Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Incomplete Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938998] Re: Update to mesa and xorg-server causes Cinnamon desktop to not render properly
apport information ** Tags added: apport-collected ulyssa ** Description changed: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 - Restoring the system from backup, and then upgrading but omitting the - above two updates and restarting, the system behaves as expected. It's - not immediately clear which of these packages is causing the problem. + Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.18 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: vinay 1218 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 20.1 + InstallationDate: Installed on 2021-01-30 (187 days ago) + InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 + IwConfig: + lono wireless extensions. + + ens33 no wireless extensions. + + tailscale0 no wireless extensions. + Lsusb: + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub + Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Lsusb-t: + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M + |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M + MachineType: VMware, Inc. VMware Virtual Platform + Package: linux (not installed) + ProcFB: 0 svgadrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash + ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-80-generic N/A + linux-backports-modules-5.4.0-80-generic N/A + linux-firmware1.187.15 + RfKill: + + Tags: ulyssa + Uname: Linux 5.4.0-80-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/20/2014 + dmi.bios.vendor: Phoenix Technologies LTD + dmi.bios.version: 6.00 + dmi.board.name: 440BX Desktop Reference Platform + dmi.board.vendor: Intel Corporation + dmi.board.version: None + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 1 + dmi.chassis.vendor: No Enclosure + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: + dmi.product.name: VMware Virtual Platform + dmi.product.version: None + dmi.sys.vendor: VMware, Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1938998/+attachment/5516101/+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/1938998 Title: Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Incomplete Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip
[Kernel-packages] [Bug 1937926] Re: Realtek 8821C PCIe Wifi driver problem, wifi speed very slow on connecting to 2.4ghz network.
Can you share result of the following command when you're suffering very slow wifi speed? 1. iw dev wlan0 link 2. iw dev wlan0 get power_save Please let me know if the command "iw dev wlan0 set power_save off" can do any help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937926 Title: Realtek 8821C PCIe Wifi driver problem, wifi speed very slow on connecting to 2.4ghz network. Status in linux package in Ubuntu: New Bug description: I am using the Realtek 8821C PCIE Wifi driver that is provided in the Additional drivers app of Ubuntu. When I connect to a 2.4 ghz network, the internet speed is very slow, it rarely goes above 4mbps. But the driver works fine when connected to a 5ghz network, easily reaching speeds of over 80mbps. I don't think it is a problem of my wifi router because in Windows OS running on the same laptop, I mostly get speeds of around 40mbps when connected to the 2.4 ghz network. 1. What is the full computer model number? Ans: HP Laptop 15s-eq0500AU. 2. If you update your BIOS to the newest version following the guide here, does this change anything? Ans: No. 3. Regarding your wireless Access Point (WAP): 3c. What wireless connection type are you using (802.11ac, 802.11n 150/300, 802.11g, etc.)? Ans: 802.11n 3d. If you switch to a different wireless type (802.11g or 802.11n if you are using 802.11g) does this change anything? Ans: Yes, in the 5ghz 802.11ac type, the speed is very normally very good. 3f. In order to understand the wireless environment your WAP is working in, please provide the output of the following terminal command: sudo iw dev wlan0 scan | grep -i "ds parameter set" Ans: [sudo] password for soumadeepsarkar1: command failed: No such device (-19) Output of sudo iw dev wlo1 scan | grep -i "ds parameter set" DS Parameter set: channel 11 DS Parameter set: channel 149 DS Parameter set: channel 149 DS Parameter set: channel 11 DS Parameter set: channel 2 DS Parameter set: channel 6 DS Parameter set: channel 10 DS Parameter set: channel 1 DS Parameter set: channel 7 DS Parameter set: channel 13 DS Parameter set: channel 1 DS Parameter set: channel 1 DS Parameter set: channel 4 DS Parameter set: channel 3 DS Parameter set: channel 10 3g. What encryption type are you using (ex. WEP, WPA2-PSK, etc.)? Ans: WPA2-PSK 3o. What frequency are you using (2.4GHz, 5GHz, etc.)? Ans: 2.4 GHz 3p. If you change frequency does it change anything? Ans: Yes, speed is good in 5ghz 4. Does another wireless device tested with the WAP have the same problem as the hardware you initially reported with? Ans: No. 5. What is the distance of the wireless device from the WAP? Ans: 6 metre 6. What is the number and type of obstructions between your device and the WAP? Ans: 2 6a. If you bring the device close to the WAP and eliminate obstructions, does this change anything? Ans: No 7. Does the issue occur with different WAPs? Ans: Yes 8. Is it a regression (i.e. did the problem happen in a prior Ubuntu release)? If so, what release specifically did it last work with? If you do not know, could you please test for this in the earliest release of Ubuntu that is supported as per Ubuntu Releases? Ans: I don't know if it is a regression and I cannot test for this in another release of Ubuntu. 9. Does this problem occur in the newest mainline kernel following https://wiki.ubuntu.com/Kernel/MainlineBuilds? Please mention what specific version of the mainline kernel you tested with in your report. Ans: Kernel version: 5.11.0-25-generic ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: soumadeepsarkar1 1797 F pulseaudio /dev/snd/controlC0: soumadeepsarkar1 1797 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 25 10:11:55 2021 InstallationDate: Installed on 2021-07-02 (23 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15s-eq0xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=2d1ce438-fd55-446d-8d61-e2d579055204 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware
[Kernel-packages] [Bug 1938998] Re: Update to mesa and xorg-server causes Cinnamon desktop to not render properly
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1938998 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Please note: `ubuntu-bug`, `apport` & bug reporting tools are provided with Ubuntu by default, many require manual addition for some releases of downstream OSes based on Ubuntu (eg. Linux Mint). You should check with your distribution first. ** Package changed: ubuntu => linux (Ubuntu) ** 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/1938998 Title: Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Incomplete Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938998] [NEW] Update to mesa and xorg-server causes Cinnamon desktop to not render properly
You have been subscribed to a public bug: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Update to mesa and xorg-server causes Cinnamon desktop to not render properly https://bugs.launchpad.net/bugs/1938998 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 1937893] Re: [HP Pavilion x360 Convertible] Touchscreen Misbehaving After Upgrading to Ubuntu 21.04
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1937893 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937893 Title: [HP Pavilion x360 Convertible] Touchscreen Misbehaving After Upgrading to Ubuntu 21.04 Status in linux package in Ubuntu: New Bug description: I just upgraded from Ubuntu 20.10 to 21.04. After the upgrade, the touchscreen of my laptop has started registering random touch events when no touch input is actually being given by the user. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 24 12:54:15 2021 DistUpgraded: 2021-07-07 09:51:26,066 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81a9] InstallationDate: Installed on 2020-10-10 (286 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Pavilion x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=58c17d38-5a4a-455c-a288-fffc3bd115a2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-07-07 (17 days ago) dmi.bios.date: 06/25/2018 dmi.bios.release: 15.35 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81A9 dmi.board.vendor: HP dmi.board.version: 57.53 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 57.53 dmi.modalias: dmi:bvnInsyde:bvrF.35:bd06/25/2018:br15.35:efr57.53:svnHP:pnHPPavilionx360Convertible:pvrType1ProductConfigId:rvnHP:rn81A9:rvr57.53:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion x360 Convertible dmi.product.sku: Z4Q51PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938999] Re: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1938999 Title: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock Status in linux package in Ubuntu: Confirmed Bug description: I have two external displays chained via Display port connected to the ThinkPad Thunderbolt 3 Dock. They are working with kernel 5.8.0-63 but not with the new 5.11.0-25 kernel. I could reproduce this behavior several times for both kernels, as follows: I booted up with disconnected dock, logged in, then I connected it, disconnected it, and connected it again. With the 5.11.0-25 kernel the external displays go black; the main screen turns off and on several times. Sometimes the main screen remains working, but UI is lagging. I'm attaching the logs. Two separate boots for each variant are marked 'a'/'b'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938408] Re: EHL board does not support soft reboot
Patches are ready and under review. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1938408 Title: EHL board does not support soft reboot Status in intel: New Status in linux-intel package in Ubuntu: In Progress Bug description: [Summary]Telling the EHL board to reboot from within Ubuntu causes it to hang, forcing you to do a hard reboot. [Steps to reproduce] 1. Open terminal window. 2. $ reboot [Expected result] System should gracefullyl reboot. [Actual result] Screen goes blank except for a cursor. System does not reboot. You must hard reboot (pull the plug) [Failure rate]100% [Additional information] CID: 202105-29063 SKU: system-manufacturer: Intel Corporation system-product-name: Elkhart Lake Embedded Platform bios-version: EHLSFWI1.R00.2091.A00.2002250754 CPU: Genuine Intel(R) CPU @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] kernel-version: 5.11.0-1009-intel To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938413] Re: Shutdown hangs on EHL board
Patches are ready and under review. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1938413 Title: Shutdown hangs on EHL board Status in intel: New Status in linux-intel package in Ubuntu: In Progress Bug description: [Summary]Go to Power -> Shutdown and the screen goes blank, but the system does not shut down. You cannot recover and have to perform a hard reboot. [Steps to reproduce] 1. Boot up Ubuntu 2. Power -> Shutdown (click ok) [Expected result] System should cleanly shut down. [Actual result] Screen blanks with a blinking cursor, the system does not shut down, the fan is still on. System is unresponsive, forcing you to do a hard reset. [Failure rate]100% [Additional information] CID: 20215-29063 SKU: system-manufacturer: Intel Corporation system-product-name: Elkhart Lake Embedded Platform bios-version: EHLSFWI1.R00.2091.A00.2002250754 CPU: Genuine Intel(R) CPU @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] kernel-version: 5.11.0-1009-intel [Stage] Device froze, issue reported and logs collected right after a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938413] Re: Shutdown hangs on EHL board
Regarding comment #7, No need to revert the patch in this case Test passed (5/5) by disabling CONFIG_PINCTRL_ELKHARTLAKE and remove the kernel module. I will upload a new kernel for testing later. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1938413 Title: Shutdown hangs on EHL board Status in intel: New Status in linux-intel package in Ubuntu: In Progress Bug description: [Summary]Go to Power -> Shutdown and the screen goes blank, but the system does not shut down. You cannot recover and have to perform a hard reboot. [Steps to reproduce] 1. Boot up Ubuntu 2. Power -> Shutdown (click ok) [Expected result] System should cleanly shut down. [Actual result] Screen blanks with a blinking cursor, the system does not shut down, the fan is still on. System is unresponsive, forcing you to do a hard reset. [Failure rate]100% [Additional information] CID: 20215-29063 SKU: system-manufacturer: Intel Corporation system-product-name: Elkhart Lake Embedded Platform bios-version: EHLSFWI1.R00.2091.A00.2002250754 CPU: Genuine Intel(R) CPU @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] kernel-version: 5.11.0-1009-intel [Stage] Device froze, issue reported and logs collected right after a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA
** Attachment added: "powertop-5.13.0+.html" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5515994/+files/powertop-5.13.0+.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912057 Title: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA Status in linux package in Ubuntu: Incomplete Bug description: After boot the idle power consumption is around 2.3 W but after suspend it is 4.7 W. The measurement is 5-10 min after boot/resume - looking at "top" to see system was idle. This is consistent - I have tried more that 10 times. BIOS is updated to latest version. I have checked power consumption with external meter - and confirmed that it is higher. I have attached output of: sudo powertop -t 60 -r --html=before.html (and after) I have noticed that Package C-state 6 is reached before suspend but not after. I expect that idle power consumption after suspend should be the same as before. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-38-generic 5.8.0-38.43 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hjh1448 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 15:49:32 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2021-01-03 (13 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425JA_UX425JA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=6296ce1c-eec8-4302-beb1-b4a228780075 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425JA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425JA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425JA.304:bd10/28/2020:br5.14:efr3.4:svnASUSTeKCOMPUTERINC.:pnZenBookUX425JA_UX425JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425JA_UX425JA 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/1912057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA
Kai-Heng, I have tried kernel 5.13.0+ from #73. Power consumption is the same and NVMe has ASPM L1 enabled both before and after suspend/resume. I have been running the kernel for a few hours now and also done some suspend/resume and it seems to work fine. I have attached dmesg and powertop output. ** Attachment added: "dmesg_5.13.0+.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5515993/+files/dmesg_5.13.0+.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/1912057 Title: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA Status in linux package in Ubuntu: Incomplete Bug description: After boot the idle power consumption is around 2.3 W but after suspend it is 4.7 W. The measurement is 5-10 min after boot/resume - looking at "top" to see system was idle. This is consistent - I have tried more that 10 times. BIOS is updated to latest version. I have checked power consumption with external meter - and confirmed that it is higher. I have attached output of: sudo powertop -t 60 -r --html=before.html (and after) I have noticed that Package C-state 6 is reached before suspend but not after. I expect that idle power consumption after suspend should be the same as before. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-38-generic 5.8.0-38.43 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hjh1448 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 15:49:32 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2021-01-03 (13 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425JA_UX425JA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=6296ce1c-eec8-4302-beb1-b4a228780075 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425JA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425JA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425JA.304:bd10/28/2020:br5.14:efr3.4:svnASUSTeKCOMPUTERINC.:pnZenBookUX425JA_UX425JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425JA_UX425JA 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/1912057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938912] Re: Bad Linux ARM64 Image magic
** Also affects: linux-raspi-5.4 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-raspi-5.4 (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux-raspi-5.4 (Ubuntu) Status: New => Invalid ** Changed in: linux-raspi-5.4 (Ubuntu Bionic) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-raspi-5.4 (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1938912 Title: Bad Linux ARM64 Image magic Status in linux-raspi-5.4 package in Ubuntu: Invalid Status in linux-raspi-5.4 source package in Bionic: Fix Committed Bug description: [Impact] On all pi devices we are testing (rpi3, 3b+, cm3, rpi4, etc...) when refreshing the kernel snap to the 5.4 kernel in 18-pi (r333), it fails to boot. Here's the serial log on the failed boot from one of those devices: Hit any key to stop autoboot: 0 WARNING at /build/u-boot-GPcj9K/u-boot-2019.07+dfsg/drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()! WARNING at /build/u-boot-GPcj9K/u-boot-2019.07+dfsg/drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()! switch to partitions #0, OK mmc0(part 0) is current device LOADBOOTENV Running uenvcmd ... ENVCMD Saving Environment to FAT... OK 8624908 bytes read in 367 ms (22.4 MiB/s) 3947036 bytes read in 171 ms (22 MiB/s) 67581 bytes read in 22 ms (2.9 MiB/s) Bad Linux ARM64 Image magic! Armhf seems to be booting just fine after the refresh. [Test Case] See above. [Where Problems Could Occur] The worst that can probably happen is that the device won't boot, which is the current behavior. Well, since the kernel image is bigger I guess we could run out of disk space on the vfat partition... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi-5.4/+bug/1938912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938999] [NEW] External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock
Public bug reported: I have two external displays chained via Display port connected to the ThinkPad Thunderbolt 3 Dock. They are working with kernel 5.8.0-63 but not with the new 5.11.0-25 kernel. I could reproduce this behavior several times for both kernels, as follows: I booted up with disconnected dock, logged in, then I connected it, disconnected it, and connected it again. With the 5.11.0-25 kernel the external displays go black; the main screen turns off and on several times. Sometimes the main screen remains working, but UI is lagging. I'm attaching the logs. Two separate boots for each variant are marked 'a'/'b'. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "logs_2021-08-05.zip" https://bugs.launchpad.net/bugs/1938999/+attachment/5515989/+files/logs_2021-08-05.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938999 Title: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock Status in linux package in Ubuntu: New Bug description: I have two external displays chained via Display port connected to the ThinkPad Thunderbolt 3 Dock. They are working with kernel 5.8.0-63 but not with the new 5.11.0-25 kernel. I could reproduce this behavior several times for both kernels, as follows: I booted up with disconnected dock, logged in, then I connected it, disconnected it, and connected it again. With the 5.11.0-25 kernel the external displays go black; the main screen turns off and on several times. Sometimes the main screen remains working, but UI is lagging. I'm attaching the logs. Two separate boots for each variant are marked 'a'/'b'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
Here is the kernel and the backported patch https://kernel.ubuntu.com/~ikepanhc/lp1932117/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: New Status in kunpeng920 ubuntu-18.04-hwe series: New Status in kunpeng920 ubuntu-20.04 series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910813] Re: Error when install libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb
Ubuntu 21.10 bug fixed. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1910813 Title: Error when install libnvidia- compute-390_390.141-0ubuntu0.20.10.1_amd64.deb Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: Preparing to unpack ... / libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb ... Unpacking libnvidia-compute-390: amd64 (390.141-0ubuntu0.20.10.1) ... dpkg: error processing archive /var/cache/apt/archives/libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb (--unpack): trying to overwrite the generic "/etc/OpenCL/vendors/nvidia.icd" which is different from other instances of the libnvidia-compute-390: amd64 package dpkg-deb: error: insert subprocess was interrupted by signal (Broken pipe) Errors occurred while processing the following packets: /var/cache/apt/archives/libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb E: subprocess / usr / bin / dpkg returned error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libnvidia-compute-390 (not installed) ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 8 23:10:43 2021 InstallationDate: Installed on 2020-11-01 (68 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=ru TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1910813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917709] Re: Ubuntu tries to read blu-ray when boot from ssd and gives I/O error
Ubuntu 21.10 bug is present. ** Tags added: impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917709 Title: Ubuntu tries to read blu-ray when boot from ssd and gives I/O error Status in linux package in Ubuntu: Confirmed Bug description: kernel: sd 14:0:0:0: [sdd] No Caching mode page found kernel: sd 14:0:0:0: [sdd] Assuming drive cache: write through kernel: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295100, async page read kernel: Buffer I/O error on dev sr0, logical block 2295101, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179392 op 0x0:(READ) flags 0x80700 phys_seg 17 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9179904 op 0x0:(READ) flags 0x80700 phys_seg 13 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9180096 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295024, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180100 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295025, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180392 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295098, async page read kernel: Buffer I/O error on dev sr0, logical block 2295099, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180376 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295094, async page read kernel: Buffer I/O error on dev sr0, logical block 2295095, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179648 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9179776 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2294944, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179780 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2294945, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180368 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295092, async page read kernel: Buffer I/O error on dev sr0, logical block 2295093, async page read systemd[1]: Failed unmounting /cdrom. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.10.0-14-generic 5.10.0-14.15 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ubuntu-mate 5498 F pulseaudio /dev/snd/controlC0: ubuntu-mate 5498 F pulseaudio /dev/snd/controlC1: ubuntu-mate 5498 F pulseaudio CasperMD5CheckResult: unknown CasperVersion: 1.458 Date: Thu Mar 4 06:07:11 2021 IwConfig: lono wireless extensions. eno1 no wireless extensions. LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hipp" - Alpha amd64 (20210304) MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed maybe-ubiquity quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to:
[Kernel-packages] [Bug 1900391] Re: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Ubuntu 21.10 bug is present. ** Tags added: impish ** Tags added: groovy ** Tags removed: focal ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1900391 Title: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled Status in linux package in Ubuntu: Confirmed Bug description: [4.589406] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled [4.589410] EDAC sbridge: Couldn't find mci handler [4.589411] EDAC sbridge: Failed to register device with error -19. but x79 doesn't have ecc ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-23-generic 5.8.0-23.24 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat2032 F pulseaudio /dev/snd/controlC0: navycat2032 F pulseaudio /dev/snd/controlC1: navycat2032 F pulseaudio CasperMD5CheckResult: skip Date: Mon Oct 19 10:19:05 2020 InstallationDate: Installed on 2020-10-07 (11 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-23-generic N/A linux-backports-modules-5.8.0-23-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900391/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900388] Re: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Ubuntu 21.10 bug is present. ** Tags added: impish ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: 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/1900388 Title: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Status in linux package in Ubuntu: Confirmed Bug description: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 PIONEER BD-RW BDR-205 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-23-generic 5.8.0-23.24 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat2032 F pulseaudio /dev/snd/controlC0: navycat2032 F pulseaudio /dev/snd/controlC1: navycat2032 F pulseaudio CasperMD5CheckResult: skip Date: Mon Oct 19 10:11:53 2020 InstallationDate: Installed on 2020-10-07 (11 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-23-generic N/A linux-backports-modules-5.8.0-23-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934110] Re: ubuntu-host driver lacks lseek ops
Removing focal tag as this SRU does not apply to focal, it does not have this driver. ** Tags removed: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934110 Title: ubuntu-host driver lacks lseek ops Status in linux package in Ubuntu: In Progress Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Fix Committed Bug description: [ SRU Justification ][GROOVY][HIRSUTE][IMPISH] == Impact == The ubuntu-host driver lacks procfs lseek ops and lseeking on the procfs esm-token file will jump to a NULL address causing the following splat: 942.470568] BUG: kernel NULL pointer dereference, address: [ 942.471157] #PF: supervisor instruction fetch in kernel mode [ 942.471724] #PF: error_code(0x0010) - not-present page [ 942.472297] PGD 0 P4D 0 [ 942.472867] Oops: 0010 [#1] SMP PTI [ 942.473435] CPU: 2 PID: 5661 Comm: stress-ng Not tainted 5.13.0-9-generic #9 [ 942.474012] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 [ 942.474599] RIP: 0010:0x0 [ 942.475194] Code: Unable to access opcode bytes at RIP 0xffd6. [ 942.475792] RSP: 0018:aacf80ff7eb8 EFLAGS: 00010246 [ 942.476383] RAX: RBX: 9eaa8a175240 RCX: 0001 [ 942.476986] RDX: RSI: RDI: 9eaa838d5800 [ 942.477600] RBP: aacf80ff7ed0 R08: 4000 R09: 0004 [ 942.478203] R10: 0002 R11: R12: [ 942.478800] R13: R14: ffea R15: 9eaa838d5800 [ 942.479399] FS: 7f998d487f00() GS:9eaaffc8() knlGS: [ 942.480006] CS: 0010 DS: ES: CR0: 80050033 [ 942.480607] CR2: ffd6 CR3: 00010a774002 CR4: 00370ee0 [ 942.481219] DR0: DR1: DR2: [ 942.481855] DR3: DR6: fffe0ff0 DR7: 0400 [ 942.482458] Call Trace: [ 942.483052] proc_reg_llseek+0x4e/0x80 [ 942.483646] ? __fdget_pos+0x43/0x50 [ 942.484234] ksys_lseek+0x84/0xc0 [ 942.484815] __x64_sys_lseek+0x1a/0x20 [ 942.485412] do_syscall_64+0x61/0xb0 [ 942.485966] ? asm_exc_page_fault+0x8/0x30 [ 942.486476] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 942.486994] RIP: 0033:0x7f998d5c1cdb [ 942.487512] Code: ff ff c3 0f 1f 40 00 48 8b 15 89 81 0d 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb ba 0f 1f 00 f3 0f 1e fa b8 08 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 59 81 0d 00 f7 d8 [ 942.488593] RSP: 002b:7ffdf61c5328 EFLAGS: 0246 ORIG_RAX: 0008 [ 942.489148] RAX: ffda RBX: RCX: 7f998d5c1cdb [ 942.489710] RDX: RSI: RDI: 0004 [ 942.490252] RBP: 0004 R08: 01785e4740dd R09: 562dbebb9e50 [ 942.490801] R10: 7ffdf61c5300 R11: 0246 R12: 7ffdf61c63f0 [ 942.491354] R13: 7ffdf61c53f0 R14: 0003 R15: 01e9 == Fix == Add the default_llseek ops: diff --git a/ubuntu/ubuntu-host/ubuntu-host.c b/ubuntu/ubuntu-host/ubuntu-host.c index 1abd402..a4c0636 100644 --- a/ubuntu/ubuntu-host/ubuntu-host.c +++ b/ubuntu/ubuntu-host/ubuntu-host.c @@ -38,6 +38,8 @@ static ssize_t esm_token_write(struct file *f, const char __user *buf, static const struct proc_ops esm_token_fops = { .proc_read = esm_token_read, .proc_write = esm_token_write, + .proc_lseek = default_llseek, + }; == Test plan == modrobe ubuntu-host stress-ng --procfs 0 -t 60 without the fix we hit the splat. With the fix it's OK. == Where problems could occur == This one liner adds the missing proc_lseek op. It is hard to see where it can cause a regression since it affects the driver no other way. I doubt any code is relying on the current semantics of lseek not working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934110] Re: ubuntu-host driver lacks lseek ops
Tested on Hirsute 5.11.0-26-generic, no crash observed, marking as verified. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934110 Title: ubuntu-host driver lacks lseek ops Status in linux package in Ubuntu: In Progress Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Fix Committed Bug description: [ SRU Justification ][GROOVY][HIRSUTE][IMPISH] == Impact == The ubuntu-host driver lacks procfs lseek ops and lseeking on the procfs esm-token file will jump to a NULL address causing the following splat: 942.470568] BUG: kernel NULL pointer dereference, address: [ 942.471157] #PF: supervisor instruction fetch in kernel mode [ 942.471724] #PF: error_code(0x0010) - not-present page [ 942.472297] PGD 0 P4D 0 [ 942.472867] Oops: 0010 [#1] SMP PTI [ 942.473435] CPU: 2 PID: 5661 Comm: stress-ng Not tainted 5.13.0-9-generic #9 [ 942.474012] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 [ 942.474599] RIP: 0010:0x0 [ 942.475194] Code: Unable to access opcode bytes at RIP 0xffd6. [ 942.475792] RSP: 0018:aacf80ff7eb8 EFLAGS: 00010246 [ 942.476383] RAX: RBX: 9eaa8a175240 RCX: 0001 [ 942.476986] RDX: RSI: RDI: 9eaa838d5800 [ 942.477600] RBP: aacf80ff7ed0 R08: 4000 R09: 0004 [ 942.478203] R10: 0002 R11: R12: [ 942.478800] R13: R14: ffea R15: 9eaa838d5800 [ 942.479399] FS: 7f998d487f00() GS:9eaaffc8() knlGS: [ 942.480006] CS: 0010 DS: ES: CR0: 80050033 [ 942.480607] CR2: ffd6 CR3: 00010a774002 CR4: 00370ee0 [ 942.481219] DR0: DR1: DR2: [ 942.481855] DR3: DR6: fffe0ff0 DR7: 0400 [ 942.482458] Call Trace: [ 942.483052] proc_reg_llseek+0x4e/0x80 [ 942.483646] ? __fdget_pos+0x43/0x50 [ 942.484234] ksys_lseek+0x84/0xc0 [ 942.484815] __x64_sys_lseek+0x1a/0x20 [ 942.485412] do_syscall_64+0x61/0xb0 [ 942.485966] ? asm_exc_page_fault+0x8/0x30 [ 942.486476] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 942.486994] RIP: 0033:0x7f998d5c1cdb [ 942.487512] Code: ff ff c3 0f 1f 40 00 48 8b 15 89 81 0d 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb ba 0f 1f 00 f3 0f 1e fa b8 08 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 59 81 0d 00 f7 d8 [ 942.488593] RSP: 002b:7ffdf61c5328 EFLAGS: 0246 ORIG_RAX: 0008 [ 942.489148] RAX: ffda RBX: RCX: 7f998d5c1cdb [ 942.489710] RDX: RSI: RDI: 0004 [ 942.490252] RBP: 0004 R08: 01785e4740dd R09: 562dbebb9e50 [ 942.490801] R10: 7ffdf61c5300 R11: 0246 R12: 7ffdf61c63f0 [ 942.491354] R13: 7ffdf61c53f0 R14: 0003 R15: 01e9 == Fix == Add the default_llseek ops: diff --git a/ubuntu/ubuntu-host/ubuntu-host.c b/ubuntu/ubuntu-host/ubuntu-host.c index 1abd402..a4c0636 100644 --- a/ubuntu/ubuntu-host/ubuntu-host.c +++ b/ubuntu/ubuntu-host/ubuntu-host.c @@ -38,6 +38,8 @@ static ssize_t esm_token_write(struct file *f, const char __user *buf, static const struct proc_ops esm_token_fops = { .proc_read = esm_token_read, .proc_write = esm_token_write, + .proc_lseek = default_llseek, + }; == Test plan == modrobe ubuntu-host stress-ng --procfs 0 -t 60 without the fix we hit the splat. With the fix it's OK. == Where problems could occur == This one liner adds the missing proc_lseek op. It is hard to see where it can cause a regression since it affects the driver no other way. I doubt any code is relying on the current semantics of lseek not working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934809] Re: Backport support for AMD SMU statistics
** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1934809 Title: Backport support for AMD SMU statistics Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Impish: New Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] AMD RN and CZN SOC can collect extra debugging data for s0i3. This information is useful for finding problems with IP blocks not going into correct states. [Fix] The following patch series adds support for these stats and will be included in 5.14. https://patchwork.kernel.org/project/platform-driver-x86/patch/20210629084803.248498-2-shyam-sundar@amd.com/ [Test] Check for extra debugfs files on amd platform. Verify that s0i3 shows successful enter (counter increases to non-zero). [Where problems could occur] The code is only used on amd platforms in s2idle. It would be specific to those platforms and cases (where it is adding support for debugging). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
Thanks Dann. Build the kernel and I can confirm that is the fix. Let me review it once again before sending it out. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: New Status in kunpeng920 ubuntu-18.04-hwe series: New Status in kunpeng920 ubuntu-20.04 series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933627] Re: HUGETLBFS is disabled
The kernel in proposed looks good: $ uname -a Linux rpi-3b-rev1d2-62e2 5.11.0-1016-raspi #17-Ubuntu SMP PREEMPT Thu Jul 29 15:33:06 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux $ hugeadm --pool-list Size Minimum Current Maximum Default 65536000 2097152000* 33554432000 1073741824000 $ sudo dmesg | grep -i huge [0.170664] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.170729] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages [0.170767] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [0.170804] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages [ 14.441925] systemd[1]: Mounting Huge Pages File System... [ 14.804603] systemd[1]: Mounted Huge Pages File System. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi-unstable in Ubuntu. https://bugs.launchpad.net/bugs/1933627 Title: HUGETLBFS is disabled Status in linux-raspi package in Ubuntu: Fix Committed Status in linux-raspi-unstable package in Ubuntu: Fix Committed Status in linux-raspi source package in Hirsute: Fix Committed Status in linux-raspi-unstable source package in Impish: Fix Committed Bug description: [Impact] Huge pages can't be managed via hugeadm which requires hugetlbfs. [Test Case] $ hugeadm --pool-list hugeadm:ERROR: kernel does not support huge pages With fix: $ hugeadm --pool-list Size Minimum Current Maximum Default 65536000 2097152000* 33554432000 1073741824000 [Fix] Enable CONFIG_HUGETLBFS [Regression Potential] This config enables code that is disabled by default. However, there is minimal stub code running at boot so problems would most likely show up as splats during boot or later on when hugetlbfs is explicitly mounted by systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1933627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
the patch is in the linux-next, and just sent the patch to ubuntu 5.11 and 5.13 generic kernels. ** Description changed: - No audio/mic from internal speakers/build in microphone running Ubuntu - 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will - work. Tried suggestions from Dell XPS 17 (9700) but this is the new - model and fixes do not work. Currently running 21.04 with proposed. + This patch is for soundwire audio, and only ubuntu 5.11-generic + and later kernels support soundwire audio driver, so this patch is not + sent to groovy and focal kernels. + + For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM + project, it is not urgent to merge this patch to OEM kenrels, after + the patch is in the hirsute and impish kernels, the oem kernels will + have this patch when syncing with generic kernels. + + [Impact] + On the Dell XPS 17 (9710) machine, the audio card is not detected when + booting hirsute or impish kernels. So the audio doesn't work on this + machine with ubuntu linux 21.04 or 21.10. + + [Fix] + Backport a upstream patch, this will set the correct codec config + for this machine: rt711 for headset, dual rt1308 for spks and rt715 + for internal mic. + + [Test] + Booting up with the patched kernel, the audio card is detected, test + internal speaker and internal mic, all work well, plug a headset, + the headphone and external mic work well too. + + + [Where problems could occur] + This change only applis to the Dell machines with the + DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the + regression, it will make the audio (speaker, internal mic and headset) + can't work anymore on the Dell machine with that PRODUCT_SKU, but this + possibility is very low, and we tested the patch on the machine, so + far no regression is found. + + + No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone
[Kernel-packages] [Bug 1925261] Re: memory leak on AWS kernels when using docker
Hi Paul, Thank you for coming back to us. I will ask my colleagues that work with the AWS kernels to look at this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1925261 Title: memory leak on AWS kernels when using docker Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Focal: New Bug description: Ever since the "ubuntu-bionic-18.04-amd64-server-20200729" EC2 Ubuntu AMI was released which has the "5.3.0-1032-aws" kernel we have been hitting a 100% repro memory leak that causes our app that is running under docker to be OOM killed. The scenario is that we have an app running in a docker container and it occasionally catches a crash happening within itself and when that happens it creates another process which triggers a gdb dump of that parent app. Normally this works fine but under these specific kernels it causes the memory usage to grow and grow until it hits the maximum allowed memory for the container at which point the container is killed. I have tested using several of the latest available Ubuntu AMIs including the latest "ubuntu-bionic-18.04-amd64-server-20210415" which has the "5.4.0-1045-aws" kernel and the bug still exists. I also tested a bunch of the mainline kernels and found the fix was introduced for this memory leak in the v5.9-rc4 kernel (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9-rc4/CHANGES). Do you all have any idea if or when that set of changes will be backported into a supported kernel for Ubuntu 18.04 or 20.04? Release we are running: root@:~# lsb_release -rd Description: Ubuntu 18.04.5 LTS Release: 18.04 Docker / containerd.io versions: - containerd.io: 1.4.4-1 - docker-ce: 5:20.10.5~3-0~ubuntu-bionic Latest supported kernel I tried which still sees the memory leak: root@hostname:~# apt-cache policy linux-aws linux-aws: Installed: 5.4.0.1045.27 Candidate: 5.4.0.1045.27 Version table: *** 5.4.0.1045.27 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1007.7 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Thanks, Paul To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1925261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Also affects: linux (Ubuntu Impish) Importance: Low Status: Confirmed ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Hui Wang (hui.wang) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935850] [NEW] Dell XPS 17 (9710) PCI/internal sound card not detected
You have been subscribed to a public bug: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug hirsute -- Dell XPS 17 (9710) PCI/internal sound card not detected https://bugs.launchpad.net/bugs/1935850 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 1938947] Re: [Ubuntu 21.10] Additional fix for s390-tools 2.17.0 - libkmipclient
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Also affects: s390-tools-signed (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: s390-tools (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Foundations Team (canonical-foundations) ** Changed in: ubuntu-z-systems 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/1938947 Title: [Ubuntu 21.10] Additional fix for s390-tools 2.17.0 - libkmipclient Status in Ubuntu on IBM z Systems: Triaged Status in s390-tools package in Ubuntu: New Status in s390-tools-signed package in Ubuntu: New Bug description: == Comment: #0 - Ingo Franzki - 2021-08-02 08:08:41 == A problem has been identified in the the libkmipclient component of s390-tools 2.17.0. Please include the following commit on top of v2.17.0: https://github.com/ibm-s390-linux/s390-tools/commit/d2a4a8b0f3f24a19bd0363b5a4f264b50ac4a885 "libkmipclient: Fix parsing of hex values for XML and JSON encoding" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1938947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp