[Kernel-packages] [Bug 1863574] Re: Update mpt3sas Driver to 33.100.00.00 for Ubuntu 20.04
** Changed in: linux (Ubuntu Focal) Status: Fix Released => 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/1863574 Title: Update mpt3sas Driver to 33.100.00.00 for Ubuntu 20.04 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Confirmed Bug description: [IMPACT] This is a feature request to update the mpt3sas driver in focal to latest version 33.100.00.00 in Ubuntu 20.04. This will allow users to use fixes and enhancements that landed upstream in 5.6. For this reason, Broadcom and Dell have requested that we pull these patches to update the mpt3sas driver to the current upstream version. [FIXES] The following commit ID's from Broadcom that whould be cherry-picked form mainline commit c53cf10ef6d9faeee9baa1fab824139c6f10a134 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c53cf10ef6d9faeee9baa1fab824139c6f10a134 commit c50ed99cd56ee725d9e14dffec8e8f1641b8ca30 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c50ed99cd56ee725d9e14dffec8e8f1641b8ca30 commit c6bdb6a10892d1130638a5e28d1523a813e45d5e https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c6bdb6a10892d1130638a5e28d1523a813e45d5e commit 5b061980e362820894d7d884370b37005bed23ec https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=5b061980e362820894d7d884370b37005bed23ec commit c59777189433621392f6f5c82ecfc62f00a1232d https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c59777189433621392f6f5c82ecfc62f00a1232d commit fce0aa08792b3ae725395fa25d44507dee0b603b https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=fce0aa08792b3ae725395fa25d44507dee0b603b commit e8c2307e6a690db9aaff84153b2857c5c4dfd969 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=e8c2307e6a690db9aaff84153b2857c5c4dfd969 commit 36c6c7f75b0998f5a4b5c79cbb94ee1ab4ee35c0 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=36c6c7f75b0998f5a4b5c79cbb94ee1ab4ee35c0 commit d3f623ae8e0323ca434ee9029100312a8be37773 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=d3f623ae8e0323ca434ee9029100312a8be37773 commit 1ade26b616cc2da0b7277a97e3799c99bae0655b https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=1ade26b616cc2da0b7277a97e3799c99bae0655b commit ee560e7bbab0c10cf3f0e71997fbc354ab2ee5cb https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=ee560e7bbab0c10cf3f0e71997fbc354ab2ee5cb commit 5bb2f743cdaa6da618e77a6aab5c38b46072365b https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=5bb2f743cdaa6da618e77a6aab5c38b46072365b commit 3524a38e594dd5f090cbc3226e5f47cb4067fac7 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=3524a38e594dd5f090cbc3226e5f47cb4067fac7 commit d8b2625f4699a36b1753d87e96b0c50a4531c065 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=d8b2625f4699a36b1753d87e96b0c50a4531c065 commit 9e64fd1e65f72d229f96fcf390576e772770a01c https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=9e64fd1e65f72d229f96fcf390576e772770a01c commit 77fd4f2c88bf83205a21f9ca49fdcc0c7868dba9 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=77fd4f2c88bf83205a21f9ca49fdcc0c7868dba9 commit b06ff10249036eec74fa8565503ac40d0ee92213 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=b06ff10249036eec74fa8565503ac40d0ee92213 commit 29f571f8b4cc652cae9244630f714a610549d301 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=29f571f8b4cc652cae9244630f714a610549d301 commit a8a6cbcd038de4ee3722c17edd7a4d84ce423f7d https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=a8a6cbcd038de4ee3722c17edd7a4d84ce423f7d commit a066f4c31359d07b1a2c5144b4b9a29901365fd0 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=a066f4c31359d07b1a2c5144b4b9a29901365fd0 commit dd180e4eedfd85b80020a6fd566601f4765a9d69 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=dd180e4eedfd85b80020a6fd566601f4765a9d69 commit 08e7378ee331a803cfdd91c512a3dea040f1da79 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=08e7378ee331a803cfdd91c512a3dea040f1da79 commit 764f472ba4a7a0c18107ebfbe1a9f1f5f5a1e411
[Kernel-packages] [Bug 1901731] Re: Lenovo Yoga Slim 7 Touchpad Not Detected
*** This bug is a duplicate of bug 1899913 *** https://bugs.launchpad.net/bugs/1899913 ** This bug has been marked a duplicate of bug 1899913 touchpad not detected Lenovo Yoga Slim 7 14IIL05 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901731 Title: Lenovo Yoga Slim 7 Touchpad Not Detected Status in linux package in Ubuntu: Confirmed Bug description: I recently bought a new Yoga Slim 7 and installed ubuntu in it. but unfortunately the touchpad is not working. I tried everything on the internet but it doesn't seem to work, any fix for this? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aradhana 1368 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 27 23:19:40 2020 InstallationDate: Installed on 2020-10-27 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 82A1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=b42f40f9-4f6c-4381-adb7-01cdeeabf0d5 ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN27WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55726 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDHCN27WW:bd05/22/2020:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws
Also the touchpad issue is bug 1899913. ** Tags added: regression-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. 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: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO 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/1937072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899913] Re: touchpad not detected Lenovo Yoga Slim 7 14IIL05
** Summary changed: - touchpad not detected lenovo yoga slim + touchpad not detected Lenovo Yoga Slim 7 14IIL05 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899913 Title: touchpad not detected Lenovo Yoga Slim 7 14IIL05 Status in linux package in Ubuntu: Confirmed Bug description: I have installed ubuntu 20.04 in lenovo yoga slim 7i, the touchpad is not getting detected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-51-generic 5.4.0-51.56 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: puneethchanda 1338 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 13:58:50 2020 InstallationDate: Installed on 2020-10-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 82A1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-51-generic root=UUID=c1f15954-8464-48af-bba3-e2d5152112cc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-51-generic N/A linux-backports-modules-5.4.0-51-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN27WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDHCN27WW:bd05/22/2020:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937296] Re: Kernel Hang During "Loading initial ramdisk..."
I was wanting to assign to https://launchpad.net/~system76 but I couldn't figure out how to do that. Says I can only assign to myself when I try. :( ** Also affects: system76 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/1937296 Title: Kernel Hang During "Loading initial ramdisk..." Status in System76: New Status in linux package in Ubuntu: Incomplete Bug description: This is specific to the System 76 PPA. linux-image-5.11.0-7614-generic boots with no problems. ``` % uname -a Linux system76-pc 5.11.0-7614-generic #15~1622578982~20.04~383c0a9~dev-Ubuntu SMP Wed Jun 2 00:50:47 U x86_64 x86_64 x86_64 GNU/Linux ``` linux-image-5.11.0-7620-generic hangs at "Loading initial ramdisk...". This is true in recovery mode as well. /etc/os-release: ``` NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal ``` Hardware is Serval: ``` System Information Manufacturer: System76 Product Name: Serval Version: serw11-b UUID: 6c5bfa80-9b7c--- Wake-up Type: Power Switch ``` All packages / firmware is up-to-date, and EFI was updated a couple of months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1937296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937072] Re: [Ice Lake] Incomplete screen redraws
This post seems to confirm your model of laptop has issues with PSR on Linux: https://www.reddit.com/r/archlinux/comments/jzhwmv/graphical_glitches_on_arch_running_kde_520_on_new/ so the workaround should be: i915.enable_psr=0 But please confirm. ** Summary changed: - [Ice Lake] Incomplete screen redraws + [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws ** No longer affects: mutter (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. 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: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO 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/1937072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937072] Re: [Ice Lake] Incomplete screen redraws
It looks like this might be a Panel Self Refresh bug. PSR was disabled in Ubuntu 20.04 but seems to be enabled (sometimes) in newer Ubuntu releases. So please try disabling it by adding a kernel parameter: i915.enable_psr=0 ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: mutter (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/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. 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: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO 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/1937072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929340] Re: Black screen ubuntu hirsute live usb
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929340 Title: Black screen ubuntu hirsute live usb Status in linux package in Ubuntu: Expired Bug description: My computer cannot start Ubuntu Hirsute Hippo (21.04). The grub selection appears, but then a black screen appears reading endlessly. Radeon HD 3000 RS780L To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937296] Re: Kernel Hang During "Loading initial ramdisk..."
It doesn't look like a Ubuntu kernel, can you please report the bug to system76? ** 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/1937296 Title: Kernel Hang During "Loading initial ramdisk..." Status in linux package in Ubuntu: Incomplete Bug description: This is specific to the System 76 PPA. linux-image-5.11.0-7614-generic boots with no problems. ``` % uname -a Linux system76-pc 5.11.0-7614-generic #15~1622578982~20.04~383c0a9~dev-Ubuntu SMP Wed Jun 2 00:50:47 U x86_64 x86_64 x86_64 GNU/Linux ``` linux-image-5.11.0-7620-generic hangs at "Loading initial ramdisk...". This is true in recovery mode as well. /etc/os-release: ``` NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal ``` Hardware is Serval: ``` System Information Manufacturer: System76 Product Name: Serval Version: serw11-b UUID: 6c5bfa80-9b7c--- Wake-up Type: Power Switch ``` All packages / firmware is up-to-date, and EFI was updated a couple of months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755999] Re: Reproducible hang in generic/430 with xfstest from upstream
generic/430 still hung on ubuntu 18.04 on azure, kernel version is 5.4.0-1055-azure, file system type is xfs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755999 Title: Reproducible hang in generic/430 with xfstest from upstream Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Triaged Status in xfsprogs package in Ubuntu: New Status in linux source package in Bionic: New Status in xfsprogs source package in Bionic: New Bug description: While testing the latest xfstest from upstream, the generic/430 test will hang, no matter using ext4/xfs/btrfs. It looks like this issue was caused by the following command to copy beyond the file: /usr/sbin/xfs_io -i -f -c "copy_range -s 4000 -l 2000 /home/ubuntu/test/test-430/file" "/home/ubuntu/test/test-430/beyond" The copied file will have a correct MD5 as expected. e68d4a150c4e42f4f9ea3ffe4c9cf4ed beyond But the command will never return. The file size of test-430/file is 5000, so a copy_range call with source offset 4000 with length 1000 works, but > 1000 does not. Steps: 1. Deploy a node with Bionic (should have a /dev/sdb available for the test) 2. Run: sudo apt-get install git python-minimal -y git clone --depth=1 https://github.com/Cypresslin/autotest-client-tests.git -b kteam-xfstest-upstream git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests 3. Run the test with the following command: AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ (The test suite can be built manually, but it's easier to do this with autotest framework) To run this test solely after the test partition has been creation on /dev/sdb: mkdir /home/ubuntu/test cd autotest/client/tmp/xfstests/src/xfstests-bld/xfstests-dev sudo su export TEST_DIR=/home/ubuntu/test export TEST_DEV=/dev/sdb1 ./check generic/430 Tested with the latest mainline kernel, 4.16.0-041600rc5-generic, and the bug still exist. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 [modified: boot/vmlinuz-4.15.0-10-generic] ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1148 F pulseaudio /dev/snd/controlC1: ubuntu 1148 F pulseaudio Date: Thu Mar 15 14:24:46 2018 InstallationDate: Installed on 2018-03-15 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. Dell Precision M3800 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=d1980d27-9063-4d92-aa10-1fb240453d8d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/14/2014:svnDellInc.:pnDellPrecisionM3800:pvrA07:rvnDellInc.:rnDellPrecisionM3800:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1755999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936452] Re: [SRU][F/H/I] Add MT7921 wifi fw
** Tags added: oem-priority originate-from-1928170 sutton -- 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/1936452 Title: [SRU][F/H/I] Add MT7921 wifi fw Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Hirsute: New Status in linux-firmware source package in Impish: New Bug description: SRU justification: [Impact] No support for MT7921 wifi card. [Fix] MT7921 needs both driver and firmware, driver is almost ready, add firmware first, then get driver bug fixed later. [Test] Verified on hardware, cold boot system wifi works fine. Reboot make it fail, but I will fix it in SRU of kernel patch. After that, it works fine. [Where problems could occur] The MT7921 wifi may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937169] Re: [SRU][OEM-5.13/U] Add support of Foxconn bluetooth 0xe0cd on MT7921
** Tags added: oem-priority originate-from-1928170 sutton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937169 Title: [SRU][OEM-5.13/U] Add support of Foxconn bluetooth 0xe0cd on MT7921 Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Bug description: SRU justification: [Impact] Another Foxconn bluetooth device on MT7921 doesn't load driver. [Fix] MT7921 bluetooth needs both driver and firmware, firmware is SRUed. Add ID in btusb. Due to the project schedule, this patch is not applied by upstream, SRU it for oem-5.13 kernel and Unstable as SAUCE. [Test] Verified on hardware, bluetooth works fine with headset and phone. [Where problems could occur] The MT7921 BT may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934647] Re: [HP Pavilion Gaming Laptop 15-dk0xxx] Black screen at login using 5.8.0-59, but 5.8.0-43 and 5.12.14 work fine
** Package changed: linux (Ubuntu) => linux-hwe-5.8 (Ubuntu) -- 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/1934647 Title: [HP Pavilion Gaming Laptop 15-dk0xxx] Black screen at login using 5.8.0-59, but 5.8.0-43 and 5.12.14 work fine Status in linux-hwe-5.8 package in Ubuntu: Confirmed Bug description: If I choose nvidia driver, then the screen is black and I cannot log in. To log in, I need to delete all nvidia files. After that, the xorg is selected and I can log in. But I cannot edit brightness. I can hardly see anything on the screen. The battery is draining very badly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1934647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937072] Re: Incomplete screen redraws
** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Summary changed: - Incomplete screen redraws + [Ice Lake] Incomplete screen redraws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: [Ice Lake] Incomplete screen redraws Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. 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: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO 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/1937072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934548] Re: RISC-V: Illegal instruction
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-riscv (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1934548 Title: RISC-V: Illegal instruction Status in Ubuntu: Confirmed Status in linux-riscv package in Ubuntu: Confirmed Bug description: When booting the Ubuntu Server image on the SiFive HiFive Unmatched I am getting the following error. The last known working version was 1012. The issue is being tracked on the SiFive forums at https://forums.sifive.com/t/u-boot-says-unhandled-exception-illegal-instruction/4898 ``` Starting kernel ... [0.00] Linux version 5.11.0-1014-generic (buildd@riscv64-qemu-lcy01-084) (gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #14-Ubuntu SMP Wed Jun 30 17:56:50 UTC 2021 (Ubuntu 5.11.0-1014.14-generic 5.11.22) [0.00] OF: fdt: Ignoring memory range 0x8000 - 0x8020 [0.00] earlycon: sifive0 at MMIO 0x1001 (options '') [0.00] printk: bootconsole [sifive0] enabled [0.00] efi: UEFI not found. [0.00] Initial ramdisk at: 0x(ptrval) (183422976 bytes) [0.00] cma: Reserved 32 MiB at 0xfe00 [0.00] Zone ranges: [0.00] DMA32[mem 0x8020-0x] [0.00] Normal [mem 0x0001-0x00047fff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x8020-0x00047fff] [0.00] Initmem setup node 0 [mem 0x8020-0x00047fff] [0.00] DMA32 zone: 512 pages in unavailable ranges [0.00] SBI specification v0.2 detected [0.00] SBI implementation ID=0x1 Version=0x9 [0.00] SBI v0.2 TIME extension detected [0.00] SBI v0.2 IPI extension detected [0.00] SBI v0.2 RFENCE extension detected [0.00] software IO TLB: mapped [mem 0xfa00-0xfe00] (64MB) [0.00] SBI v0.2 HSM extension detected [0.00] CPU with hartid=0 is not available [0.00] CPU with hartid=0 is not available [0.00] riscv: ISA extensions acdfim [0.00] riscv: ELF capabilities acdfim [0.00] percpu: Embedded 26 pages/cpu s69272 r8192 d29032 u106496 [0.00] Built 1 zonelists, mobility grouping on. Total pages: 4128264 [0.00] Kernel command line: root=/dev/nvme0n1p1 ro earlycon [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [0.00] Sorting __ex_table... [0.00] mem auto-init: stack:off, heap alloc:on, heap free:off [0.00] Memory: 16165452K/16775168K available (9854K kernel code, 5763K rwdata, 8192K rodata, 2519K init, 997K bss, 576948K reserved, 32768K cma-reserved) [0.00] random: get_random_u64 called from kmem_cache_open+0x36/0x338 with crng_init=0 [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] ftrace: allocating 38893 entries in 152 pages [0.00] Oops - illegal instruction [#1] [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 5.11.0-1014-generic #14-Ubuntu [0.00] epc: ffe0920e ra : ffe09384 sp : ffe001803d30 [0.00] gp : ffe001a14240 tp : ffe00180f440 t0 : ffe07fe38000 [0.00] t1 : ffe0019cd338 t2 : s0 : ffe001803d70 [0.00] s1 : a0 : ffe095aa a1 : 0001 [0.00] a2 : 0002 a3 : a4 : [0.00] a5 : a6 : 0004 a7 : 52464e43 [0.00] s2 : 0002 s3 : 0001 s4 : [0.00] s5 : s6 : s7 : [0.00] s8 : ffe001a170c0 s9 : 0001 s10: 0001 [0.00] s11: fffcc5d0 t3 : 0068 t4 : 000b [0.00] t5 : ffe0019cd3e0 t6 : ffe001803cd8 [0.00] status: 00020100 badaddr: 0513f187 cause: 0002 [0.00] ---[ end trace f67eb9af4d8d492b ]--- [0.00] Kernel panic - not syncing: Attempted to kill the idle task! [0.00] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]--- ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1934548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1934548] Re: RISC-V: Illegal instruction
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1934548 Title: RISC-V: Illegal instruction Status in Ubuntu: Confirmed Status in linux-riscv package in Ubuntu: Confirmed Bug description: When booting the Ubuntu Server image on the SiFive HiFive Unmatched I am getting the following error. The last known working version was 1012. The issue is being tracked on the SiFive forums at https://forums.sifive.com/t/u-boot-says-unhandled-exception-illegal-instruction/4898 ``` Starting kernel ... [0.00] Linux version 5.11.0-1014-generic (buildd@riscv64-qemu-lcy01-084) (gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #14-Ubuntu SMP Wed Jun 30 17:56:50 UTC 2021 (Ubuntu 5.11.0-1014.14-generic 5.11.22) [0.00] OF: fdt: Ignoring memory range 0x8000 - 0x8020 [0.00] earlycon: sifive0 at MMIO 0x1001 (options '') [0.00] printk: bootconsole [sifive0] enabled [0.00] efi: UEFI not found. [0.00] Initial ramdisk at: 0x(ptrval) (183422976 bytes) [0.00] cma: Reserved 32 MiB at 0xfe00 [0.00] Zone ranges: [0.00] DMA32[mem 0x8020-0x] [0.00] Normal [mem 0x0001-0x00047fff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x8020-0x00047fff] [0.00] Initmem setup node 0 [mem 0x8020-0x00047fff] [0.00] DMA32 zone: 512 pages in unavailable ranges [0.00] SBI specification v0.2 detected [0.00] SBI implementation ID=0x1 Version=0x9 [0.00] SBI v0.2 TIME extension detected [0.00] SBI v0.2 IPI extension detected [0.00] SBI v0.2 RFENCE extension detected [0.00] software IO TLB: mapped [mem 0xfa00-0xfe00] (64MB) [0.00] SBI v0.2 HSM extension detected [0.00] CPU with hartid=0 is not available [0.00] CPU with hartid=0 is not available [0.00] riscv: ISA extensions acdfim [0.00] riscv: ELF capabilities acdfim [0.00] percpu: Embedded 26 pages/cpu s69272 r8192 d29032 u106496 [0.00] Built 1 zonelists, mobility grouping on. Total pages: 4128264 [0.00] Kernel command line: root=/dev/nvme0n1p1 ro earlycon [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [0.00] Sorting __ex_table... [0.00] mem auto-init: stack:off, heap alloc:on, heap free:off [0.00] Memory: 16165452K/16775168K available (9854K kernel code, 5763K rwdata, 8192K rodata, 2519K init, 997K bss, 576948K reserved, 32768K cma-reserved) [0.00] random: get_random_u64 called from kmem_cache_open+0x36/0x338 with crng_init=0 [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] ftrace: allocating 38893 entries in 152 pages [0.00] Oops - illegal instruction [#1] [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 5.11.0-1014-generic #14-Ubuntu [0.00] epc: ffe0920e ra : ffe09384 sp : ffe001803d30 [0.00] gp : ffe001a14240 tp : ffe00180f440 t0 : ffe07fe38000 [0.00] t1 : ffe0019cd338 t2 : s0 : ffe001803d70 [0.00] s1 : a0 : ffe095aa a1 : 0001 [0.00] a2 : 0002 a3 : a4 : [0.00] a5 : a6 : 0004 a7 : 52464e43 [0.00] s2 : 0002 s3 : 0001 s4 : [0.00] s5 : s6 : s7 : [0.00] s8 : ffe001a170c0 s9 : 0001 s10: 0001 [0.00] s11: fffcc5d0 t3 : 0068 t4 : 000b [0.00] t5 : ffe0019cd3e0 t6 : ffe001803cd8 [0.00] status: 00020100 badaddr: 0513f187 cause: 0002 [0.00] ---[ end trace f67eb9af4d8d492b ]--- [0.00] Kernel panic - not syncing: Attempted to kill the idle task! [0.00] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]--- ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1934548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1937324] [NEW] hang booting kernel after software reboot
Public bug reported: After issuing a software reboot, the machine hangs at a black screen after the grub prompt, before the kernel boots. This lasts at least five minutes, with the processor fans spun all the way up. If I remove quiet and nosplash there is no text, the screen is completely black. I have tried various reboot= options but it behaves the same way (when it reboots--some of those options do not reboot at all). If I add acpi=off it will boot reliably, but with acpi=ht the same problem occurs. Once at the black screen, I can press the reset button, and after going through grub, the machine boots successfully. It also boots successfully on a cold boot. I am using UEFI, but I had the same problem with BIOS boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-63-generic 5.8.0-63.71~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 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 22 20:51:41 2021 InstallationDate: Installed on 2021-07-18 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1937324 Title: hang booting kernel after software reboot Status in linux-signed-hwe-5.8 package in Ubuntu: New Bug description: After issuing a software reboot, the machine hangs at a black screen after the grub prompt, before the kernel boots. This lasts at least five minutes, with the processor fans spun all the way up. If I remove quiet and nosplash there is no text, the screen is completely black. I have tried various reboot= options but it behaves the same way (when it reboots--some of those options do not reboot at all). If I add acpi=off it will boot reliably, but with acpi=ht the same problem occurs. Once at the black screen, I can press the reset button, and after going through grub, the machine boots successfully. It also boots successfully on a cold boot. I am using UEFI, but I had the same problem with BIOS boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-63-generic 5.8.0-63.71~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 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 22 20:51:41 2021 InstallationDate: Installed on 2021-07-18 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1937324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932163] Re: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** No longer affects: linux-hwe-5.11 (Ubuntu) ** No longer affects: linux-hwe-5.11 (Ubuntu Focal) ** No longer affects: linux-hwe-5.11 (Ubuntu Hirsute) -- 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/1932163 Title: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in evdi package in Ubuntu: Fix Released Status in evdi source package in Focal: Confirmed Status in evdi source package in Hirsute: Confirmed Bug description: [Impact] focal users running latest hwe kernel, version 5.11, won't be able to use evdi-dkms. [Test case] Built evdi dkms and loaded the evdi module on 5.4, 5.8 and 5.11 kernels. [Potential regression] DisplayLink devices will stop working. -- This is a scripted bug report about ADT failures while running evdi tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/e/evdi/20210611_210228_7f0da@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/e/evdi/20210612_122245_bd52e@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/e/evdi/20210611_210028_038f3@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/e/evdi/20210611_205902_3dc65@/log.gz [Other] NB! dkms ftbfs fixes must be built in security, such that after SRU process in -proposed & -updates it can be copied into -security pocket too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Hardware compatibility means that I need 5.11 and up, but this was keeping me from getting newer kernels with up to date security. I am kinda shocked that it is apparently being ignored by devs. Thanks to tuxinvader, as builds on that ppa seem to work well with mint. -- You 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 1931254] Re: Google Confidential Compute fails to boot with shim version 1.47
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1931254 Title: Google Confidential Compute fails to boot with shim version 1.47 Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Bug description: # Overview Hirsute and Impish daily builds are currently not booting on Google Confidential Compute. Confidential compute is Google's platform that enables the use of Secure Encrypted Virtualization extension via AMD EPYC CPUs. Booting an image with version 1.45 works, but once upgraded to 1.47, the VM no longer boots, and instead the kernel panics. Launching the image with secure boot, but without confidential compute works as expected. # Expected result The system is able to reboot after the upgrade. # Actual result Kernel panic: https://paste.ubuntu.com/p/mHrvVc6qBc/ # Steps to reproduce Launch a VM in GCE with confidential compute enabled with a serial v20210511a or later and look at the serial log for the kernel panic. Example CLI command to launch a VM: $ gcloud beta compute instances create $USER-confidential-testing --zone=us-west1-b --machine-type=n2d-standard-2 --image=daily- ubuntu-2104-hirsute-v20210511a --image-project=ubuntu-os-cloud-devel --confidential-compute --maintenance-policy=TERMINATE The last known good working image is daily- ubuntu-2104-hirsute-v20210510. The upgrade that fails is when shim signed is updated from 1.46+15.4-0ubuntu1 to 1.47+15.4-0ubuntu2 # Logs & notes * 20210510 manifest (good): https://paste.ubuntu.com/p/QjnMPcJj7G/ * 20210511a manifest (bad): https://paste.ubuntu.com/p/PvJQwRXHcG/ * diff between manifests: https://paste.ubuntu.com/p/4nJtGxqGn7/ * serial logs of failed boot: https://paste.ubuntu.com/p/mHrvVc6qBc/ # Cause: shim changed the memory type for pages reserved for EFI runtime services, from EfiRuntimeServicesData to EfiBootServicesData. Memory reserved for EFI runtime/boot services must be remapped as encrypted in the kernel (during boot) if SEV (secure encrypted virtualization) is enabled. The original kernel implementation of ioremap only correctly mapped the region as encrypted for EfiRuntimeServicesData regions, so when shim changed the type to EfiBootServicesData the kernel bug was exposed Note that this affects all 5.11 kernels not just gcp. It is possible that gcp is the only cloud that uses sev currently (for "Confidential Computing"). # Fix: Both EfiRuntimeServicesData and EfiBootServicesData must be mapped as encrypted if SEV is active, as per: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8d651ee9c71bb12fc0c8eb2786b66cbe5aa3e43b # Test Without the fix applied, confirmed that I was able to reproduce the issue described here (complete failure to boot, kernel panic) With fix, confirmed no issues booting # Regression potential The fix could potentially cause boot failures, if a memory region is marked encrypted when it shouldn't be. I assume in that case it would cause a panic similar to the one seen here for this bug: general protection fault, probably for non-canonical address 0x314836c31124d346: [#1] SMP NOPTI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927866] Re: Root filesystem becomes readonly frequenty freezing system
For anybody coming across this thread. I was not able to get this to a closure. I returned the laptop :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927866 Title: Root filesystem becomes readonly frequenty freezing system Status in linux package in Ubuntu: Confirmed Bug description: I have a brand new Lenovo Ideapad Flex 5.14 which came with Windows 10 and I have installed Ubuntu 21.04 with dual boot. I am running into this problem where the root filesystem becomes readonly and the system freezes with a screen full of errors shown about unable to write to filesystem. I booted into a live boot usb and did fsck and e2fsck but did not see any errors there. I read online that this could be because of io errors but smartctl and fsck does not show any errors So I was wondering if this could be a bug vs a hardward issue. Please let me know if you need any further information from the system. = = fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: WDC PC SN530 SDBPMPZ-512G-1101 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E8803E28-C4F7-4FA5-9B6D-0F3CAB7027A5 Device StartEnd Sectors Size Type /dev/nvme0n1p1 2048 534527532480 260M EFI System /dev/nvme0n1p2534528 567295 3276816M Microsoft reserved /dev/nvme0n1p3567296 199446527 198879232 94.8G Microsoft basic data /dev/nvme0n1p4 998166528 1000214527 2048000 1000M Windows recovery environmen /dev/nvme0n1p5 199446528 203352063 3905536 1.9G Linux filesystem /dev/nvme0n1p6 203352064 219353087 16001024 7.6G Linux swap /dev/nvme0n1p7 219353088 414664703 195311616 93.1G Linux filesystem /dev/nvme0n1p8 414664704 998166527 583501824 278.2G Microsoft basic data = = smartctl -a /dev/nvme0 smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.11.0-16-generic] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: WDC PC SN530 SDBPMPZ-512G-1101 Serial Number: 205135806243 Firmware Version: 21160001 PCI Vendor/Subsystem ID:0x15b7 IEEE OUI Identifier:0x001b44 Total NVM Capacity: 512,110,190,592 [512 GB] Unallocated NVM Capacity: 0 Controller ID: 1 NVMe Version: 1.4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 512,110,190,592 [512 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64:001b44 8b484daff7 Local Time is: Sun May 9 12:45:05 2021 EDT Firmware Updates (0x14):2 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg Maximum Data Transfer Size: 128 Pages Warning Comp. Temp. Threshold: 80 Celsius Critical Comp. Temp. Threshold: 85 Celsius Namespace 1 Features (0x02):NA_Fields Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 3.50W2.10W -0 0 0 00 0 1 + 2.40W1.60W -0 0 0 00 0 2 + 1.90W1.50W -0 0 0 00 0 3 - 0.0250W --3 3 3 3 3900 11000 4 - 0.0050W --4 4 4 4 5000 39000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 2 1 -4096 0 1 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature:35 Celsius Available Spare:100% Available Spare Threshold: 10% Percentage Used:0% Data Units Read:624,535 [319 GB] Data Units Written: 526,042 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power On Hours: 76
[Kernel-packages] [Bug 1895855] Re: FFE: support for NVIDIA runtimepm (hybrid gfx)
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1895855 Title: FFE: support for NVIDIA runtimepm (hybrid gfx) Status in OEM Priority Project: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Released Bug description: The work that went into ubuntu-drivers-common and nvidia-prime is meant to enable RTD3 support on Intel/NVIDIA or AMD/NVIDIA hybrid systems, introduced by the NVIDIA 450 driver series. This allows the supported systems to make use of the integrated GPU (Intel or AMD) and to keep the discrete NVIDIA GPU powered down until needed. While powered down, the NVIDIA GPU can still detect any events, should external displays be plugged in. This brings hybrid graphics on Linux on par with Windows. Only the supported GPUs will be able to benefit from this change. This is why NVIDIA provides a hardware database (included in the nvidia packages), which gpu-manager can now parse. The ubuntu-drivers tool relies on that detection to enable this new feature when installing the NVIDIA driver. Another improvement is the ability of ubuntu-drivers to detect LTSB (Long term support branch), NFB (New feature branch), Legacy, Beta flags, which the NVIDIA drivers can have, and make informed detection choices. This work also includes a number of bug fixes reported on errors.ubuntu.com. Requirements: The new ubuntu-drivers-common: The new nvidia-prime: Changes to the NVIDIA drivers: To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1895855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933716] Re: Black screen on boot after stable update
*** This bug is a duplicate of bug 1934647 *** https://bugs.launchpad.net/bugs/1934647 ** This bug has been marked a duplicate of bug 1934647 [HP Pavilion Gaming Laptop 15-dk0xxx] Black screen at login using 5.8.0-59, but 5.8.0-43 and 5.12.14 work fine -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933716 Title: Black screen on boot after stable update Status in linux package in Ubuntu: Confirmed Bug description: After kernel update from 5.11.0-18-generic to 5.11.0-22-generic system boots into black screen. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 1374 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 26 11:55:00 2021 InstallationDate: Installed on 2021-05-02 (55 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Pavilion Laptop 15-eg0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9625a19f-eeea-4a92-ab4b-1549d4950f3b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2021 dmi.bios.release: 15.12 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 87CB dmi.board.vendor: HP dmi.board.version: 34.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 34.27 dmi.modalias: dmi:bvnInsyde:bvrF.12:bd03/17/2021:br15.12:efr34.27:svnHP:pnHPPavilionLaptop15-eg0xxx:pvrType1ProductConfigId:rvnHP:rn87CB:rvr34.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eg0xxx dmi.product.sku: 2Q2T4EA#AKD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934647] Re: [HP Pavilion Gaming Laptop 15-dk0xxx] Black screen at login using 5.8.0-59, but 5.8.0-43 and 5.12.14 work fine
I have HP Proobook 450 and also have this problem. It is not in Nvidia driver cause i have internal intel gpu. when i plug external monitor as secondary monitor - i see ubuntu banner and after login blindly i may do what i want on second screen but internal notebook monitor black. kernel 5.11.0-22 and 5.11.0-25 have this problem as well. for now i downgrade kernel to 5.8.0-55 and i'm waiting for bug fixes -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934647 Title: [HP Pavilion Gaming Laptop 15-dk0xxx] Black screen at login using 5.8.0-59, but 5.8.0-43 and 5.12.14 work fine Status in linux package in Ubuntu: Confirmed Bug description: If I choose nvidia driver, then the screen is black and I cannot log in. To log in, I need to delete all nvidia files. After that, the xorg is selected and I can log in. But I cannot edit brightness. I can hardly see anything on the screen. The battery is draining very badly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937312] Re: package linux-modules-nvidia-460-5.8.0-63-generic 5.8.0-63.71~20.04.1 failed to install/upgrade: installed linux-modules-nvidia-460-5.8.0-63-generic package post-in
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1937312 Title: package linux-modules-nvidia-460-5.8.0-63-generic 5.8.0-63.71~20.04.1 failed to install/upgrade: installed linux-modules- nvidia-460-5.8.0-63-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules-hwe-5.8 package in Ubuntu: New Bug description: nuts ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-modules-nvidia-460-5.8.0-63-generic 5.8.0-63.71~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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Jul 22 16:37:06 2021 ErrorMessage: installed linux-modules-nvidia-460-5.8.0-63-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-02-19 (153 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: linux-restricted-modules-hwe-5.8 Title: package linux-modules-nvidia-460-5.8.0-63-generic 5.8.0-63.71~20.04.1 failed to install/upgrade: installed linux-modules-nvidia-460-5.8.0-63-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-restricted-modules-hwe-5.8/+bug/1937312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937312] [NEW] package linux-modules-nvidia-460-5.8.0-63-generic 5.8.0-63.71~20.04.1 failed to install/upgrade: installed linux-modules-nvidia-460-5.8.0-63-generic package post-
Public bug reported: nuts ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-modules-nvidia-460-5.8.0-63-generic 5.8.0-63.71~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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Jul 22 16:37:06 2021 ErrorMessage: installed linux-modules-nvidia-460-5.8.0-63-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-02-19 (153 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: linux-restricted-modules-hwe-5.8 Title: package linux-modules-nvidia-460-5.8.0-63-generic 5.8.0-63.71~20.04.1 failed to install/upgrade: installed linux-modules-nvidia-460-5.8.0-63-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1937312 Title: package linux-modules-nvidia-460-5.8.0-63-generic 5.8.0-63.71~20.04.1 failed to install/upgrade: installed linux-modules- nvidia-460-5.8.0-63-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules-hwe-5.8 package in Ubuntu: New Bug description: nuts ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-modules-nvidia-460-5.8.0-63-generic 5.8.0-63.71~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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Jul 22 16:37:06 2021 ErrorMessage: installed linux-modules-nvidia-460-5.8.0-63-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-02-19 (153 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: linux-restricted-modules-hwe-5.8 Title: package linux-modules-nvidia-460-5.8.0-63-generic 5.8.0-63.71~20.04.1 failed to install/upgrade: installed linux-modules-nvidia-460-5.8.0-63-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-restricted-modules-hwe-5.8/+bug/1937312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934910] Re: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux-hwe-5.4/5.4.0-79.88~18.04.1
This bug was fixed in the package zfs-linux - 0.7.5-1ubuntu16.12 --- zfs-linux (0.7.5-1ubuntu16.12) bionic; urgency=medium * Improve scrub testing in kernel-smoke-test-scrub (LP: #1934910) On some slower small memory systems we need to check until resilvering has completed. The most reliably method is to poll on a scrub until it finishes successfully. Give up after ~15 minutes and flag a failure if the scrub can't start or complete successfully. -- Colin Ian King Thu, 8 Jul 2021 08:51:21 +0100 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1934910 Title: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux- hwe-5.4/5.4.0-79.88~18.04.1 Status in linux-hwe-5.4 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Released Status in linux-hwe-5.4 source package in Bionic: New Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Focal: Fix Released Status in zfs-linux source package in Groovy: Fix Released Status in zfs-linux source package in Hirsute: Fix Released Status in zfs-linux source package in Impish: Fix Released Bug description: == zfs-linux SRU == IMPISH, HIRSUTE, GROOVY, FOCAL, BIONIC, XENIAL [Impact] The zfs debian scrub test sometimes times out on slower test systems because scrub can take a while to complete and the scrub test can time out. The test needs some more intelligence to detect this and a longer time out for slower systems. The fix now polls the scrub completion more thoroughly and increases timeout to 15 minutes. [Test Plan] Run the test with autopkgtest on slow file systems. With the fix the test has longer timeout and will pass rather than fail with a timeout. e.g. autopkgtest zfs-linux_2.0.3-8ubuntu5.dsc -- null [Where problems could occur] The timeout is hard coded to 15 minutes. This should be enough for slow devices with the small ZFS volume set used by this test. However, it may still fail if the backing store is really slow. However, we don't want the test to be blocked indefinitely waiting for a timeout, so a 15 minute scrub timeout seems to be long enough to be more than reasonable. Any longer and it's highly likely that the scrub has hung. [Other Info] This test is almost identical to the same scrub test run from the kernel team autotest zfs smoke test, so it has been exercised regularly and is known to reliably. - This is a scripted bug report about ADT failures while running zfs-linux tests for linux-hwe-5.4/5.4.0-79.88~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343_3aa5c@/log.gz This is a similar issue as reported on bug 1885289, which was fixed on autotest-client-tests ubuntu_zfs_smoke_test. However, the ADT tests don't use autotest, the test script run comes from the zfs-linux dkms source package, debian/tests/kernel-smoke-test-scrub. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1934910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934910] Re: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux-hwe-5.4/5.4.0-79.88~18.04.1
This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu30 --- zfs-linux (0.6.5.6-0ubuntu30) xenial; urgency=medium * Improve scrub testing in kernel-smoke-test-scrub (LP: #1934910) On some slower small memory systems we need to check until resilvering has completed. The most reliably method is to poll on a scrub until it finishes successfully. Give up after ~15 minutes and flag a failure if the scrub can't start or complete successfully. -- Colin Ian King Thu, 8 Jul 2021 08:51:21 +0100 ** Changed in: zfs-linux (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1934910 Title: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux- hwe-5.4/5.4.0-79.88~18.04.1 Status in linux-hwe-5.4 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Released Status in linux-hwe-5.4 source package in Bionic: New Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Focal: Fix Released Status in zfs-linux source package in Groovy: Fix Released Status in zfs-linux source package in Hirsute: Fix Released Status in zfs-linux source package in Impish: Fix Released Bug description: == zfs-linux SRU == IMPISH, HIRSUTE, GROOVY, FOCAL, BIONIC, XENIAL [Impact] The zfs debian scrub test sometimes times out on slower test systems because scrub can take a while to complete and the scrub test can time out. The test needs some more intelligence to detect this and a longer time out for slower systems. The fix now polls the scrub completion more thoroughly and increases timeout to 15 minutes. [Test Plan] Run the test with autopkgtest on slow file systems. With the fix the test has longer timeout and will pass rather than fail with a timeout. e.g. autopkgtest zfs-linux_2.0.3-8ubuntu5.dsc -- null [Where problems could occur] The timeout is hard coded to 15 minutes. This should be enough for slow devices with the small ZFS volume set used by this test. However, it may still fail if the backing store is really slow. However, we don't want the test to be blocked indefinitely waiting for a timeout, so a 15 minute scrub timeout seems to be long enough to be more than reasonable. Any longer and it's highly likely that the scrub has hung. [Other Info] This test is almost identical to the same scrub test run from the kernel team autotest zfs smoke test, so it has been exercised regularly and is known to reliably. - This is a scripted bug report about ADT failures while running zfs-linux tests for linux-hwe-5.4/5.4.0-79.88~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343_3aa5c@/log.gz This is a similar issue as reported on bug 1885289, which was fixed on autotest-client-tests ubuntu_zfs_smoke_test. However, the ADT tests don't use autotest, the test script run comes from the zfs-linux dkms source package, debian/tests/kernel-smoke-test-scrub. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1934910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934910] Re: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux-hwe-5.4/5.4.0-79.88~18.04.1
This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu12.11 --- zfs-linux (0.8.3-1ubuntu12.11) focal; urgency=medium * Improve scrub testing in kernel-smoke-test-scrub (LP: #1934910) On some slower small memory systems we need to check until resilvering has completed. The most reliably method is to poll on a scrub until it finishes successfully. Give up after ~15 minutes and flag a failure if the scrub can't start or complete successfully. -- Colin Ian King Thu, 8 Jul 2021 08:51:21 +0100 ** Changed in: zfs-linux (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1934910 Title: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux- hwe-5.4/5.4.0-79.88~18.04.1 Status in linux-hwe-5.4 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Released Status in linux-hwe-5.4 source package in Bionic: New Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Focal: Fix Released Status in zfs-linux source package in Groovy: Fix Released Status in zfs-linux source package in Hirsute: Fix Released Status in zfs-linux source package in Impish: Fix Released Bug description: == zfs-linux SRU == IMPISH, HIRSUTE, GROOVY, FOCAL, BIONIC, XENIAL [Impact] The zfs debian scrub test sometimes times out on slower test systems because scrub can take a while to complete and the scrub test can time out. The test needs some more intelligence to detect this and a longer time out for slower systems. The fix now polls the scrub completion more thoroughly and increases timeout to 15 minutes. [Test Plan] Run the test with autopkgtest on slow file systems. With the fix the test has longer timeout and will pass rather than fail with a timeout. e.g. autopkgtest zfs-linux_2.0.3-8ubuntu5.dsc -- null [Where problems could occur] The timeout is hard coded to 15 minutes. This should be enough for slow devices with the small ZFS volume set used by this test. However, it may still fail if the backing store is really slow. However, we don't want the test to be blocked indefinitely waiting for a timeout, so a 15 minute scrub timeout seems to be long enough to be more than reasonable. Any longer and it's highly likely that the scrub has hung. [Other Info] This test is almost identical to the same scrub test run from the kernel team autotest zfs smoke test, so it has been exercised regularly and is known to reliably. - This is a scripted bug report about ADT failures while running zfs-linux tests for linux-hwe-5.4/5.4.0-79.88~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343_3aa5c@/log.gz This is a similar issue as reported on bug 1885289, which was fixed on autotest-client-tests ubuntu_zfs_smoke_test. However, the ADT tests don't use autotest, the test script run comes from the zfs-linux dkms source package, debian/tests/kernel-smoke-test-scrub. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1934910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934910] Re: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux-hwe-5.4/5.4.0-79.88~18.04.1
This bug was fixed in the package zfs-linux - 0.8.4-1ubuntu11.3 --- zfs-linux (0.8.4-1ubuntu11.3) groovy; urgency=medium * Improve scrub testing in kernel-smoke-test-scrub (LP: #1934910) On some slower small memory systems we need to check until resilvering has completed. The most reliably method is to poll on a scrub until it finishes successfully. Give up after ~15 minutes and flag a failure if the scrub can't start or complete successfully. -- Colin Ian King Thu, 8 Jul 2021 08:51:21 +0100 ** Changed in: zfs-linux (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1934910 Title: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux- hwe-5.4/5.4.0-79.88~18.04.1 Status in linux-hwe-5.4 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Released Status in linux-hwe-5.4 source package in Bionic: New Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Focal: Fix Released Status in zfs-linux source package in Groovy: Fix Released Status in zfs-linux source package in Hirsute: Fix Released Status in zfs-linux source package in Impish: Fix Released Bug description: == zfs-linux SRU == IMPISH, HIRSUTE, GROOVY, FOCAL, BIONIC, XENIAL [Impact] The zfs debian scrub test sometimes times out on slower test systems because scrub can take a while to complete and the scrub test can time out. The test needs some more intelligence to detect this and a longer time out for slower systems. The fix now polls the scrub completion more thoroughly and increases timeout to 15 minutes. [Test Plan] Run the test with autopkgtest on slow file systems. With the fix the test has longer timeout and will pass rather than fail with a timeout. e.g. autopkgtest zfs-linux_2.0.3-8ubuntu5.dsc -- null [Where problems could occur] The timeout is hard coded to 15 minutes. This should be enough for slow devices with the small ZFS volume set used by this test. However, it may still fail if the backing store is really slow. However, we don't want the test to be blocked indefinitely waiting for a timeout, so a 15 minute scrub timeout seems to be long enough to be more than reasonable. Any longer and it's highly likely that the scrub has hung. [Other Info] This test is almost identical to the same scrub test run from the kernel team autotest zfs smoke test, so it has been exercised regularly and is known to reliably. - This is a scripted bug report about ADT failures while running zfs-linux tests for linux-hwe-5.4/5.4.0-79.88~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343_3aa5c@/log.gz This is a similar issue as reported on bug 1885289, which was fixed on autotest-client-tests ubuntu_zfs_smoke_test. However, the ADT tests don't use autotest, the test script run comes from the zfs-linux dkms source package, debian/tests/kernel-smoke-test-scrub. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1934910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934910] Re: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux-hwe-5.4/5.4.0-79.88~18.04.1
This bug was fixed in the package zfs-linux - 2.0.2-1ubuntu5.1 --- zfs-linux (2.0.2-1ubuntu5.1) hirsute; urgency=medium * Improve scrub testing in kernel-smoke-test-scrub (LP: #1934910) On some slower small memory systems we need to check until resilvering has completed. The most reliably method is to poll on a scrub until it finishes successfully. Give up after ~15 minutes and flag a failure if the scrub can't start or complete successfully. -- Colin Ian King Thu, 8 Jul 2021 08:51:21 +0100 ** Changed in: zfs-linux (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: zfs-linux (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1934910 Title: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux- hwe-5.4/5.4.0-79.88~18.04.1 Status in linux-hwe-5.4 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Released Status in linux-hwe-5.4 source package in Bionic: New Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Focal: Fix Released Status in zfs-linux source package in Groovy: Fix Released Status in zfs-linux source package in Hirsute: Fix Released Status in zfs-linux source package in Impish: Fix Released Bug description: == zfs-linux SRU == IMPISH, HIRSUTE, GROOVY, FOCAL, BIONIC, XENIAL [Impact] The zfs debian scrub test sometimes times out on slower test systems because scrub can take a while to complete and the scrub test can time out. The test needs some more intelligence to detect this and a longer time out for slower systems. The fix now polls the scrub completion more thoroughly and increases timeout to 15 minutes. [Test Plan] Run the test with autopkgtest on slow file systems. With the fix the test has longer timeout and will pass rather than fail with a timeout. e.g. autopkgtest zfs-linux_2.0.3-8ubuntu5.dsc -- null [Where problems could occur] The timeout is hard coded to 15 minutes. This should be enough for slow devices with the small ZFS volume set used by this test. However, it may still fail if the backing store is really slow. However, we don't want the test to be blocked indefinitely waiting for a timeout, so a 15 minute scrub timeout seems to be long enough to be more than reasonable. Any longer and it's highly likely that the scrub has hung. [Other Info] This test is almost identical to the same scrub test run from the kernel team autotest zfs smoke test, so it has been exercised regularly and is known to reliably. - This is a scripted bug report about ADT failures while running zfs-linux tests for linux-hwe-5.4/5.4.0-79.88~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343_3aa5c@/log.gz This is a similar issue as reported on bug 1885289, which was fixed on autotest-client-tests ubuntu_zfs_smoke_test. However, the ADT tests don't use autotest, the test script run comes from the zfs-linux dkms source package, debian/tests/kernel-smoke-test-scrub. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1934910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934910] Update Released
The verification of the Stable Release Update for zfs-linux has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1934910 Title: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux- hwe-5.4/5.4.0-79.88~18.04.1 Status in linux-hwe-5.4 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Released Status in linux-hwe-5.4 source package in Bionic: New Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Focal: Fix Released Status in zfs-linux source package in Groovy: Fix Released Status in zfs-linux source package in Hirsute: Fix Released Status in zfs-linux source package in Impish: Fix Released Bug description: == zfs-linux SRU == IMPISH, HIRSUTE, GROOVY, FOCAL, BIONIC, XENIAL [Impact] The zfs debian scrub test sometimes times out on slower test systems because scrub can take a while to complete and the scrub test can time out. The test needs some more intelligence to detect this and a longer time out for slower systems. The fix now polls the scrub completion more thoroughly and increases timeout to 15 minutes. [Test Plan] Run the test with autopkgtest on slow file systems. With the fix the test has longer timeout and will pass rather than fail with a timeout. e.g. autopkgtest zfs-linux_2.0.3-8ubuntu5.dsc -- null [Where problems could occur] The timeout is hard coded to 15 minutes. This should be enough for slow devices with the small ZFS volume set used by this test. However, it may still fail if the backing store is really slow. However, we don't want the test to be blocked indefinitely waiting for a timeout, so a 15 minute scrub timeout seems to be long enough to be more than reasonable. Any longer and it's highly likely that the scrub has hung. [Other Info] This test is almost identical to the same scrub test run from the kernel team autotest zfs smoke test, so it has been exercised regularly and is known to reliably. - This is a scripted bug report about ADT failures while running zfs-linux tests for linux-hwe-5.4/5.4.0-79.88~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343_3aa5c@/log.gz This is a similar issue as reported on bug 1885289, which was fixed on autotest-client-tests ubuntu_zfs_smoke_test. However, the ADT tests don't use autotest, the test script run comes from the zfs-linux dkms source package, debian/tests/kernel-smoke-test-scrub. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1934910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937296] [NEW] Kernel Hang During "Loading initial ramdisk..."
Public bug reported: This is specific to the System 76 PPA. linux-image-5.11.0-7614-generic boots with no problems. ``` % uname -a Linux system76-pc 5.11.0-7614-generic #15~1622578982~20.04~383c0a9~dev-Ubuntu SMP Wed Jun 2 00:50:47 U x86_64 x86_64 x86_64 GNU/Linux ``` linux-image-5.11.0-7620-generic hangs at "Loading initial ramdisk...". This is true in recovery mode as well. /etc/os-release: ``` NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal ``` Hardware is Serval: ``` System Information Manufacturer: System76 Product Name: Serval Version: serw11-b UUID: 6c5bfa80-9b7c--- Wake-up Type: Power Switch ``` All packages / firmware is up-to-date, and EFI was updated a couple of months ago. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: system76 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937296 Title: Kernel Hang During "Loading initial ramdisk..." Status in linux package in Ubuntu: New Bug description: This is specific to the System 76 PPA. linux-image-5.11.0-7614-generic boots with no problems. ``` % uname -a Linux system76-pc 5.11.0-7614-generic #15~1622578982~20.04~383c0a9~dev-Ubuntu SMP Wed Jun 2 00:50:47 U x86_64 x86_64 x86_64 GNU/Linux ``` linux-image-5.11.0-7620-generic hangs at "Loading initial ramdisk...". This is true in recovery mode as well. /etc/os-release: ``` NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal ``` Hardware is Serval: ``` System Information Manufacturer: System76 Product Name: Serval Version: serw11-b UUID: 6c5bfa80-9b7c--- Wake-up Type: Power Switch ``` All packages / firmware is up-to-date, and EFI was updated a couple of months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937291] [NEW] no sound on alc294 asus rog laptop
Public bug reported: Built-in speakers don't work. Bluetooth work okeyish, but the volume is very low. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-63-generic 5.8.0-63.71~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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Thu Jul 22 19:30:07 2021 InstallationDate: Installed on 2021-06-19 (32 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1937291 Title: no sound on alc294 asus rog laptop Status in linux-signed-hwe-5.8 package in Ubuntu: New Bug description: Built-in speakers don't work. Bluetooth work okeyish, but the volume is very low. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-63-generic 5.8.0-63.71~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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Thu Jul 22 19:30:07 2021 InstallationDate: Installed on 2021-06-19 (32 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1937291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937072] Re: Incomplete screen redraws
List of things I have to Inform you what I have tested.I am Computer Science student but new to linux so I have tested many things. 1. I have used both x-org and nvidia GPU. After fresh installation and on reboot I got into many problem my touchpad and brightness controller were not working and screen glitch so i fixed my brightness and touchpad using ubuntu community posts. But glitch were all same I have tried many solution but not solved. so I posted ubuntu-bug. 2. I have changed setting from bios to disable NVIDIA but glitch problem not solved. And on using NVIDIA Driver there were not glitch performance were perfectly fine but on restart i got stucked on boot menu screen were blank so i ran into recovery and change my driver to x-org intel. 3. Before bug submission I have tested around 10 popular linux distro all were having same problem screen glitches. 4. only two distro have not occoured a display glitch problem one was ubuntu 20.04 LTS and ubuntu budgie 21.04 but that distro causes same touchpad and brightness controll problem that was so frustating. So I came to conclusion that my intel driver is buggy and on reboot my device alwaay fail to recognise touchpad and display 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/1937072 Title: Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. 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: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO 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/1937072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] Re: GPF in rtl2832
https://wiki.ubuntu.com/Kernel/MainlineBuilds You can remove the kernel after testing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects
Hi, This bug is back on kernel 5.11.2 and 5.7.0 except even worse. Now the touchpad doesn't even get recognized. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937264] Re: CIFS: Improve DFS caching
Test kernels at https://launchpad.net/~timg-tpi/+archive/ubuntu/cifs- dfs-cache-lp1937264 -- 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/1937264 Title: CIFS: Improve DFS caching Status in linux-azure package in Ubuntu: New Bug description: SRU Justification [Impact] The Microsoft CIFS team is requesting to ensure these 5 patches are made available with 5.11 Azure tuned kernel https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=6efa994e35a402ae4ae2161b6439c94b64816cee https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=cdc3363065aba2711e51019b3d5787f044f8a133 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=507345b5ae6a57b7ecd7550ff39282ed20de7b8d https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=50630b3f1ada0bf412d3f28e73bac310448d9d6f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=506c1da44fee32ba1d3a70413289ad58c772bba6 [Test Plan] Connect to a Windows DFS share [Where problems could occur] The CIFS connection could fail. [Other Info] https://canonical.my.salesforce.com/5004K05r0uT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1937264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937269] Re: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build
** Description changed: Crash dialog show up on reboot right after kernel update + reinstalling using: apt purge nvidia-driver-460 # enforce a fresh install apt install nvidia-driver-460 + + Besides the crash dialog, I did not notice any problems so far; e.g. no + visual impact, nvidia utils launch as usual showing information, etc... + + - - - - - - - - - - - - - + ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-460 460.91.03-0ubuntu0.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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-59-generic Date: Wed Jul 21 08:14:54 2021 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-460:460.91.03-0ubuntu0.20.04.1:clang: error: unsupported option '-dumpspecs' InstallationDate: Installed on 2021-05-27 (55 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.91.03-0ubuntu0.20.04.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: nvidia-graphics-drivers-460 Title: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1937269 Title: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: Crash dialog show up on reboot right after kernel update + reinstalling using: apt purge nvidia-driver-460 # enforce a fresh install apt install nvidia-driver-460 Besides the crash dialog, I did not notice any problems so far; e.g. no visual impact, nvidia utils launch as usual showing information, etc... - - - - - - - - - - - - - ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-460 460.91.03-0ubuntu0.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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-59-generic Date: Wed Jul 21 08:14:54 2021 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-460:460.91.03-0ubuntu0.20.04.1:clang: error: unsupported option '-dumpspecs' InstallationDate: Installed on 2021-05-27 (55 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.91.03-0ubuntu0.20.04.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: nvidia-graphics-drivers-460 Title: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build 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-460/+bug/1937269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937068] Re: "BUG: non-zero pgtables_bytes on freeing mm: 16384" errors during boot on bionic/linux s390x
*** This bug is a duplicate of bug 1937276 *** https://bugs.launchpad.net/bugs/1937276 Marking as duplicate as bug 1937276, which has more info about the root cause. ** This bug has been marked a duplicate of bug 1937276 log_check test in ubuntu_boot will erroneously get error on manually provisioned systems -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937068 Title: "BUG: non-zero pgtables_bytes on freeing mm: 16384" errors during boot on bionic/linux s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: [Impact] When booting bionic/linux 4.15.0-152.159 on a s390x machine there's a lot of the following error message on the kernel log: BUG: non-zero pgtables_bytes on freeing mm: 16384 This error doesn't seem to happen on every boot. I could trace this happening as far back as 4.15.0-143.147, but this could be older as I don't have test results for older releases. This is similar to bug 1840046, which was supposedly fixed by an upstream stable patch around Sep/2019. [Test case] Boot bionic/linux on a s390x system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1937068/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937264] Re: CIFS: Improve DFS caching
** Description changed: SRU Justification [Impact] - The Microsoft CIFS team is requesting to ensure these 4 patches are made + The Microsoft CIFS team is requesting to ensure these 5 patches are made available with 5.11 Azure tuned kernel + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=6efa994e35a402ae4ae2161b6439c94b64816cee https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=cdc3363065aba2711e51019b3d5787f044f8a133 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=507345b5ae6a57b7ecd7550ff39282ed20de7b8d https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=50630b3f1ada0bf412d3f28e73bac310448d9d6f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=506c1da44fee32ba1d3a70413289ad58c772bba6 [Test Plan] Connect to a Windows DFS share [Where problems could occur] The CIFS connection could fail. [Other Info] https://canonical.my.salesforce.com/5004K05r0uT -- 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/1937264 Title: CIFS: Improve DFS caching Status in linux-azure package in Ubuntu: New Bug description: SRU Justification [Impact] The Microsoft CIFS team is requesting to ensure these 5 patches are made available with 5.11 Azure tuned kernel https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=6efa994e35a402ae4ae2161b6439c94b64816cee https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=cdc3363065aba2711e51019b3d5787f044f8a133 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=507345b5ae6a57b7ecd7550ff39282ed20de7b8d https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=50630b3f1ada0bf412d3f28e73bac310448d9d6f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=506c1da44fee32ba1d3a70413289ad58c772bba6 [Test Plan] Connect to a Windows DFS share [Where problems could occur] The CIFS connection could fail. [Other Info] https://canonical.my.salesforce.com/5004K05r0uT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1937264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] Re: GPF in rtl2832
I would love to be helpful - but i don't really know how to do that and then get back to the kernel I'm on. I don't even know if all my stuff (virtualbox, nvidia, etc) will work with it. Sorry not trying to be dumb, just not done that before. is there an easy way to do that? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932163] Re: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
1.9.1-1ubuntu4~21.04.1 supersedes 1.9.1-1ubuntu3~21.04.1 to fix adt failure on s390x. -- 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/1932163 Title: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in evdi package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Confirmed Status in evdi source package in Focal: Confirmed Status in linux-hwe-5.11 source package in Focal: Confirmed Status in evdi source package in Hirsute: Confirmed Status in linux-hwe-5.11 source package in Hirsute: Confirmed Bug description: [Impact] focal users running latest hwe kernel, version 5.11, won't be able to use evdi-dkms. [Test case] Built evdi dkms and loaded the evdi module on 5.4, 5.8 and 5.11 kernels. [Potential regression] DisplayLink devices will stop working. -- This is a scripted bug report about ADT failures while running evdi tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/e/evdi/20210611_210228_7f0da@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/e/evdi/20210612_122245_bd52e@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/e/evdi/20210611_210028_038f3@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/e/evdi/20210611_205902_3dc65@/log.gz [Other] NB! dkms ftbfs fixes must be built in security, such that after SRU process in -proposed & -updates it can be copied into -security pocket too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937269] Re: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build
** Tags removed: need-duplicate-check -- 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/1937269 Title: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: Crash dialog show up on reboot right after kernel update + reinstalling using: apt purge nvidia-driver-460 # enforce a fresh install apt install nvidia-driver-460 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-460 460.91.03-0ubuntu0.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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-59-generic Date: Wed Jul 21 08:14:54 2021 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-460:460.91.03-0ubuntu0.20.04.1:clang: error: unsupported option '-dumpspecs' InstallationDate: Installed on 2021-05-27 (55 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.91.03-0ubuntu0.20.04.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: nvidia-graphics-drivers-460 Title: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build 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-460/+bug/1937269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
I can confirm that nvidia 470.57.02 and linux 5.11.0-25-generic is working with displayport on my system, all monitors, one on hdmi, two on displayport and the internal lcd on the laptop, come up correctly without crash -- 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/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-465 package in Ubuntu: Triaged Bug description: I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute Jun 03 16:26:57 willow kernel: Oops: [#1] SMP PTI Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P OE 5.11.0-18-generic #19-Ubuntu Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019 Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 R09: 8e318220acb8 Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 R12: 0400 Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 R15: 0800 Jun 03 16:26:57 willow kernel: FS: 7f5807f38a40() GS:8e3466dc() knlGS: Jun 03 16:26:57 willow kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 CR4: 003706e0 Jun 03 16:26:57 willow kernel: DR0: DR1: DR2: Jun 03 16:26:57 willow kernel: DR3: DR6: fffe0ff0 DR7: 0400 Jun 03 16:26:57 willow kernel: Call Trace: Jun 03 16:26:57 willow kernel: ? _nv015556rm+0x7fd/0x1020 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv027155rm+0x22c/0x4f0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017787rm+0x303/0x5e0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017789rm+0xe1/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv022829rm+0xed/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv023065rm+0x30/0x60 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv000704rm+0x16da/0x22b0 [nvidia] Jun 03 16:26:57 willow kernel: ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 03 16:26:57 willow kernel: ? nv_open_device+0x122/0x8e0 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_open+0x2b7/0x560 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_frontend_open+0x58/0xa0 [nvidia] Jun 03 16:26:57 willow kernel: ? chrdev_open+0xf7/0x220 Jun 03 16:26:57 willow kernel: ? cdev_device_add+0x90/0x90 Jun 03 16:26:57 willow kernel: ? do_dentry_open+0x156/0x370 Jun 03 16:26:57 willow kernel: ? vfs_open+0x2d/0x30 Jun 03 16:26:57 willow kernel: ? do_open+0x1c3/0x340 Jun 03 16:26:57 willow kernel: ? path_openat+0x10a/0x1d0 Jun 03 16:26:57 willow kernel: ? do_filp_open+0x8c/0x130 Jun 03 16:26:57 willow kernel: ? __check_object_size+0x1c/0x20 Jun 03 16:26:57 willow kernel: ? do_sys_openat2+0x9b/0x150 Jun 03 16:26:57 willow kernel: ? __x64_sys_openat+0x56/0x90 Jun 03 16:26:57 willow kernel: ? do_syscall_64+0x38/0x90 Jun 03 16:26:57 willow kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) > Jun 03 16:26:57 willow kernel: sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c> Jun 03 16:26:57 willow kernel: CR2: 0170 Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]--- Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow
[Kernel-packages] [Bug 1937269] [NEW] nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build
Public bug reported: Crash dialog show up on reboot right after kernel update + reinstalling using: apt purge nvidia-driver-460 # enforce a fresh install apt install nvidia-driver-460 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-460 460.91.03-0ubuntu0.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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-59-generic Date: Wed Jul 21 08:14:54 2021 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-460:460.91.03-0ubuntu0.20.04.1:clang: error: unsupported option '-dumpspecs' InstallationDate: Installed on 2021-05-27 (55 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.91.03-0ubuntu0.20.04.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: nvidia-graphics-drivers-460 Title: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal ** Description changed: - Crash dialog show up right after kernel update + reinstalling using: + Crash dialog show up on reboot right after kernel update + reinstalling + using: apt purge nvidia-driver-460 # enforce a fresh install apt install nvidia-driver-460 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-460 460.91.03-0ubuntu0.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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-59-generic Date: Wed Jul 21 08:14:54 2021 Dependencies: - + DuplicateSignature: dkms:nvidia-kernel-source-460:460.91.03-0ubuntu0.20.04.1:clang: error: unsupported option '-dumpspecs' InstallationDate: Installed on 2021-05-27 (55 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.91.03-0ubuntu0.20.04.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 + dpkg 1.19.7ubuntu3 + apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1937269 Title: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: Crash dialog show up on reboot right after kernel update + reinstalling using: apt purge nvidia-driver-460 # enforce a fresh install apt install nvidia-driver-460 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-460 460.91.03-0ubuntu0.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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-59-generic Date: Wed Jul 21 08:14:54 2021 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-460:460.91.03-0ubuntu0.20.04.1:clang: error: unsupported option '-dumpspecs' InstallationDate: Installed on 2021-05-27 (55 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.91.03-0ubuntu0.20.04.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: nvidia-graphics-drivers-460 Title: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build 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-460/+bug/1937269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935846] Re: Sony Dualshock 4 usb dongle crashes the whole system
Hello All! Please also apply the patch for the 5.8.0-63-generic series. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935846 Title: Sony Dualshock 4 usb dongle crashes the whole system Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Won't Fix Bug description: [Impact] Sony Dualshock 4 controller crashes systems. This is the result of a divide by zero when the driver processes requests from Steam and returns invalid data. More details are in the patch description. [Fix] Check whether data is valid and retry up to 3 times if needed. [Test Case] Tested by the bug reporter of LP:1935846. No more crashes after applying this patch. [Where problems could occur] None. The patch checks whether data is valid and retry 3 times before return -EILSEQ if it still fails. == Original descriptions == The hid-sony driver has custom DS4 connect/disconnect logic for the DS4 dongle, which is a USB dongle acting as a proxy to Bluetooth connected DS4. The connect/disconnect logic works fine generally, however not in conjunction with Steam. Steam implements its own DS4 driver using hidraw. Both hid-sony and Steam are issuing their own HID requests and are racing each other during DS4 dongle connect/disconnect resulting in a kernel crash in hid-sony. The problem is that upon a DS4 connect to the dongle, hid-sony kicks of 'ds4_get_calibration_data' from within its dongle hotplug code. The calibration code issues raw HID feature report for reportID 0x02. When Steam is running, it issues a feature report for reportID 0x12 typically just prior to hid-sony requesting feature reportID 0x02. The result is that 'ds4_get_calibration_data' receives the data Steam requested as that's the HID report returing first. Currently this results in it processing invalid data, which ultimately results in a divide by zero upon a future 'dualshock4_parse_report'. The solution for now is to check within 'ds4_get_calibration_data' to check if we received data for the feature report we issued and if not retry. Please consider to add this patch to Ubuntu LTS kernels. Commit: https://github.com/torvalds/linux/commit/f5dc93b7875bcb8be77baa792cc9432aaf65365b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935846/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937264] [NEW] CIFS: Improve DFS caching
Public bug reported: SRU Justification [Impact] The Microsoft CIFS team is requesting to ensure these 4 patches are made available with 5.11 Azure tuned kernel https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=cdc3363065aba2711e51019b3d5787f044f8a133 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=507345b5ae6a57b7ecd7550ff39282ed20de7b8d https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=50630b3f1ada0bf412d3f28e73bac310448d9d6f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=506c1da44fee32ba1d3a70413289ad58c772bba6 [Test Plan] Connect to a Windows DFS share [Where problems could occur] The CIFS connection could fail. [Other Info] https://canonical.my.salesforce.com/5004K05r0uT ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1937264 Title: CIFS: Improve DFS caching Status in linux-azure package in Ubuntu: New Bug description: SRU Justification [Impact] The Microsoft CIFS team is requesting to ensure these 4 patches are made available with 5.11 Azure tuned kernel https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=cdc3363065aba2711e51019b3d5787f044f8a133 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=507345b5ae6a57b7ecd7550ff39282ed20de7b8d https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=50630b3f1ada0bf412d3f28e73bac310448d9d6f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=506c1da44fee32ba1d3a70413289ad58c772bba6 [Test Plan] Connect to a Windows DFS share [Where problems could occur] The CIFS connection could fail. [Other Info] https://canonical.my.salesforce.com/5004K05r0uT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1937264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937252] Re: e1000e: add handshake with the Intel CSME to support S0ix
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/linux-staging, version 5.13.0-9009.10+staging.3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937252 Title: e1000e: add handshake with the Intel CSME to support S0ix Status in HWE Next: New Status in linux package in Ubuntu: New 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.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: Intel is doing some improvement for the Corp ME + S0ix support. Currently, this patch series have been landed in nextdev, net-next tree. e1000e: Additional PHY power saving in S0ix https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=3ad3e28cb203309fb29022dea41cd65df0583632 e1000e: Add polling mechanism to indicate CSME DPG exit https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=ef407b86d3cc7ab7ad37658c1c7a094cb8f3b6b4 e1000e: Add handshake with the CSME to support S0ix https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=3e55d231716ea361b1520b801c6778c4c48de102 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937252] Re: e1000e: add handshake with the Intel CSME to support S0ix
** Summary changed: - Add handshake with the Intel CSME to support S0ix + e1000e: add handshake with the Intel CSME to support S0ix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937252 Title: e1000e: add handshake with the Intel CSME to support S0ix Status in HWE Next: New Status in linux package in Ubuntu: New 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.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: Intel is doing some improvement for the Corp ME + S0ix support. Currently, this patch series have been landed in nextdev, net-next tree. e1000e: Additional PHY power saving in S0ix https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=3ad3e28cb203309fb29022dea41cd65df0583632 e1000e: Add polling mechanism to indicate CSME DPG exit https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=ef407b86d3cc7ab7ad37658c1c7a094cb8f3b6b4 e1000e: Add handshake with the CSME to support S0ix https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=3e55d231716ea361b1520b801c6778c4c48de102 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937252] [NEW] e1000e: add handshake with the Intel CSME to support S0ix
Public bug reported: Intel is doing some improvement for the Corp ME + S0ix support. Currently, this patch series have been landed in nextdev, net-next tree. e1000e: Additional PHY power saving in S0ix https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=3ad3e28cb203309fb29022dea41cd65df0583632 e1000e: Add polling mechanism to indicate CSME DPG exit https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=ef407b86d3cc7ab7ad37658c1c7a094cb8f3b6b4 e1000e: Add handshake with the CSME to support S0ix https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=3e55d231716ea361b1520b801c6778c4c48de102 ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1937234 somerville ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Tags added: oem-priority originate-from-1937234 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937252 Title: e1000e: add handshake with the Intel CSME to support S0ix Status in HWE Next: New Status in linux package in Ubuntu: New 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.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: Intel is doing some improvement for the Corp ME + S0ix support. Currently, this patch series have been landed in nextdev, net-next tree. e1000e: Additional PHY power saving in S0ix https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=3ad3e28cb203309fb29022dea41cd65df0583632 e1000e: Add polling mechanism to indicate CSME DPG exit https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=ef407b86d3cc7ab7ad37658c1c7a094cb8f3b6b4 e1000e: Add handshake with the CSME to support S0ix https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=3e55d231716ea361b1520b801c6778c4c48de102 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools
** Also affects: opa-ff (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/1215411 Title: libcpupower.so is not installed from linux-tools Status in cpufreqd package in Ubuntu: Confirmed Status in gkrellm2-cpufreq package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in opa-ff package in Ubuntu: New Bug description: The patch for bug 1158668 installs cpupower_$(abi_version) command- line tool as well as libcpupower.so.$(abi_version). This isn't particularly suitable for projects that previously used libcpufreq and intend to migrate to libcpupower, because the libcpupower.so symlink is no longer installed. The command-line tools can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/1215411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936452] Re: [SRU][F/H/I] Add MT7921 wifi fw
SRU v3: * https://lists.ubuntu.com/archives/kernel-team/2021-July/122623.html (f) * https://lists.ubuntu.com/archives/kernel-team/2021-July/122624.html (h) * https://lists.ubuntu.com/archives/kernel-team/2021-July/122625.html (i) -- 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/1936452 Title: [SRU][F/H/I] Add MT7921 wifi fw Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Hirsute: New Status in linux-firmware source package in Impish: New Bug description: SRU justification: [Impact] No support for MT7921 wifi card. [Fix] MT7921 needs both driver and firmware, driver is almost ready, add firmware first, then get driver bug fixed later. [Test] Verified on hardware, cold boot system wifi works fine. Reboot make it fail, but I will fix it in SRU of kernel patch. After that, it works fine. [Where problems could occur] The MT7921 wifi may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937004] Re: Add additional Mediatek MT7921 WiFi/BT device IDs
SRU v2: * https://lists.ubuntu.com/archives/kernel-team/2021-July/122628.html (oem-5.13, h) * https://lists.ubuntu.com/archives/kernel-team/2021-July/122636.html (u) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937004 Title: Add additional Mediatek MT7921 WiFi/BT device IDs Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] Some Mediatek MT7921 Bluetooth doesn't work out of box. [Fix] One ID for Lite-On was included in upstream, but we need two additional more from different vendors. [Test Case] With firmware from bug 1936452, this will bring up MT7921 Bluetooth. Check BD address from output of `hciconfig`. [Where problems could occur] This brings up new devices that wasn't working. After being up and running, we may face some other runtime issue, e.g. power consumption. == original bug description == Mediatek MT7921 has been added to mainline kernel & firmware. Firmware part is being handled by bug 1936452, and WiFi fw loading failure in bug 1936790. This issue will focus on backport/add device IDs for MT7921: * Bus 001 Device 004: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device * Bus 002 Device 003: ID 13d3:3567 IMC Networks linux$ git log --graph --oneline korg/master -- \ drivers/bluetooth/ \ drivers/net/wireless/mediatek/mt76/mt7921/ linux-firmware$ git log --graph --oneline korg/master -- \ mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin \ mediatek/WIFI_RAM_CODE_MT7961_1.bin \ mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin * a7882719 linux-firmware: update frimware for mediatek bluetooth chip (MT7921) * 2fd5139f linux-firmware: update firmware for MT7921 WiFi device to 20210612122753 * 42a66e5b linux-firmware: update firmware for MT7921 WiFi device * 58fb90a0 linux-firmware: add frimware for mediatek bluetooth chip (MT7921) * 391fd50d linux-firmware: add firmware for MT7921 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1278 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X135 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-05 (16 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 192f:0616 Avago Technologies, Pte. ADNS-5700 Optical Mouse Controller (5-button) Bus 001 Device 002: ID 03f0:344a HP, Inc HP USB Slim Keyboard Bus 001 Device 004: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3910 Package: linux-firmware 1.187.15+staging.9 [origin: LP-PPA-vicamo-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9009-oem root=UUID=6ae05750-3063-48a4-92af-626f62ff75fc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9009.10+staging.2-oem 5.13.0 RelatedPackageVersions: linux-restricted-modules-5.13.0-9009-oem N/A linux-backports-modules-5.13.0-9009-oem N/A linux-firmware 1.187.15+staging.9 Tags: third-party-packages focal Uname: Linux 5.13.0-9009-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/12/2021 dmi.bios.release: 0.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.8.22 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.8.22:bd07/12/2021:br0.8:svnDellInc.:pnInspiron3910:pvr:sku0AD3:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: Inspiron 3910 dmi.product.sku: 0AD3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1937249] [NEW] package libnvidia-compute-460 460.91.03-0ubuntu0.20.04.1 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/i386-linux-gnu/libnvidia-compi
Public bug reported: It just didn't install and presented the error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-460 460.91.03-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jul 22 08:12:35 2021 ErrorMessage: não pode copiar dados extráidos para './usr/lib/i386-linux-gnu/libnvidia-compiler.so.460.91.03' para '/usr/lib/i386-linux-gnu/libnvidia-compiler.so.460.91.03.dpkg-new': fim de ficheiro ou stream inesperado InstallationDate: Installed on 2020-12-07 (226 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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: nvidia-graphics-drivers-460 Title: package libnvidia-compute-460 460.91.03-0ubuntu0.20.04.1 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/i386-linux-gnu/libnvidia-compiler.so.460.91.03' para '/usr/lib/i386-linux-gnu/libnvidia-compiler.so.460.91.03.dpkg-new': fim de ficheiro ou stream inesperado UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (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 nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1937249 Title: package libnvidia-compute-460 460.91.03-0ubuntu0.20.04.1 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/i386-linux-gnu/libnvidia-compiler.so.460.91.03' para '/usr/lib/i386-linux-gnu/libnvidia-compiler.so.460.91.03.dpkg-new': fim de ficheiro ou stream inesperado Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: It just didn't install and presented the error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-460 460.91.03-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jul 22 08:12:35 2021 ErrorMessage: não pode copiar dados extráidos para './usr/lib/i386-linux-gnu/libnvidia-compiler.so.460.91.03' para '/usr/lib/i386-linux-gnu/libnvidia-compiler.so.460.91.03.dpkg-new': fim de ficheiro ou stream inesperado InstallationDate: Installed on 2020-12-07 (226 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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: nvidia-graphics-drivers-460 Title: package libnvidia-compute-460 460.91.03-0ubuntu0.20.04.1 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/i386-linux-gnu/libnvidia-compiler.so.460.91.03' para '/usr/lib/i386-linux-gnu/libnvidia-compiler.so.460.91.03.dpkg-new': fim de ficheiro ou stream inesperado 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-460/+bug/1937249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Changed in: ubuntu-kernel-tests Status: In Progress => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: In Progress => 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/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:
[Kernel-packages] [Bug 1923162] Proposed package removed from archive
The version of u-boot in the proposed pocket of Hirsute that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. ** Changed in: u-boot (Ubuntu Hirsute) Status: Won't Fix => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: Fix Released Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Focal: Invalid Status in u-boot source package in Focal: Fix Committed Status in u-boot-menu source package in Focal: Fix Committed Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: Confirmed Status in u-boot-menu source package in Hirsute: Fix Released Bug description: [Impact] * u-boot may crash when attempting to boot extlinux.conf which specifies fdtdir; the given u-boot config doesn't specify a dtb filename to load; autodetection tries to make one up using $soc & $board variables; and if one or both of them are not set (as it is the case for qemu) it would crash. Fix this crash by doing validation / checking when quering for $soc & $board variables in autodetectionn. [Test Plan] * Use qemu & uboot produced by the build that fixes this bug report properly and attempt to boot hirsute's riscv64+unmatched image. * It should boot correctly without a crash / qemu backtrace. [Where problems could occur] * This patch is bein upstreamed. If one is using external uboot (i.e. provided by some other vendor) it may still crash when trying to boot Ubuntu's riscv64 rootfs or cloud image. [Other Info] * Patch is being reviewed upstream https://lists.denx.de/pipermail/u-boot/2021-May/449176.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923162] Proposed package removed from archive
The version of u-boot in the proposed pocket of Hirsute that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. ** Changed in: u-boot (Ubuntu Hirsute) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: Fix Released Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Focal: Invalid Status in u-boot source package in Focal: Fix Committed Status in u-boot-menu source package in Focal: Fix Committed Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: Confirmed Status in u-boot-menu source package in Hirsute: Fix Released Bug description: [Impact] * u-boot may crash when attempting to boot extlinux.conf which specifies fdtdir; the given u-boot config doesn't specify a dtb filename to load; autodetection tries to make one up using $soc & $board variables; and if one or both of them are not set (as it is the case for qemu) it would crash. Fix this crash by doing validation / checking when quering for $soc & $board variables in autodetectionn. [Test Plan] * Use qemu & uboot produced by the build that fixes this bug report properly and attempt to boot hirsute's riscv64+unmatched image. * It should boot correctly without a crash / qemu backtrace. [Where problems could occur] * This patch is bein upstreamed. If one is using external uboot (i.e. provided by some other vendor) it may still crash when trying to boot Ubuntu's riscv64 rootfs or cloud image. [Other Info] * Patch is being reviewed upstream https://lists.denx.de/pipermail/u-boot/2021-May/449176.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923162] Re: riscv64 images fail to boot in qemu
Per my discussion with Dimitri on IRC, I'm switching the tag to verification-failed for hirsute again and then proceeding with dropping the hirsute-proposed u-boot package. ** Tags removed: verification-needed-hirsute ** Tags added: verification-failed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: Fix Released Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Focal: Invalid Status in u-boot source package in Focal: Fix Committed Status in u-boot-menu source package in Focal: Fix Committed Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: Confirmed Status in u-boot-menu source package in Hirsute: Fix Released Bug description: [Impact] * u-boot may crash when attempting to boot extlinux.conf which specifies fdtdir; the given u-boot config doesn't specify a dtb filename to load; autodetection tries to make one up using $soc & $board variables; and if one or both of them are not set (as it is the case for qemu) it would crash. Fix this crash by doing validation / checking when quering for $soc & $board variables in autodetectionn. [Test Plan] * Use qemu & uboot produced by the build that fixes this bug report properly and attempt to boot hirsute's riscv64+unmatched image. * It should boot correctly without a crash / qemu backtrace. [Where problems could occur] * This patch is bein upstreamed. If one is using external uboot (i.e. provided by some other vendor) it may still crash when trying to boot Ubuntu's riscv64 rootfs or cloud image. [Other Info] * Patch is being reviewed upstream https://lists.denx.de/pipermail/u-boot/2021-May/449176.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923162] Proposed package removed from archive
The version of u-boot in the proposed pocket of Hirsute that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: Fix Released Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Focal: Invalid Status in u-boot source package in Focal: Fix Committed Status in u-boot-menu source package in Focal: Fix Committed Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: Confirmed Status in u-boot-menu source package in Hirsute: Fix Released Bug description: [Impact] * u-boot may crash when attempting to boot extlinux.conf which specifies fdtdir; the given u-boot config doesn't specify a dtb filename to load; autodetection tries to make one up using $soc & $board variables; and if one or both of them are not set (as it is the case for qemu) it would crash. Fix this crash by doing validation / checking when quering for $soc & $board variables in autodetectionn. [Test Plan] * Use qemu & uboot produced by the build that fixes this bug report properly and attempt to boot hirsute's riscv64+unmatched image. * It should boot correctly without a crash / qemu backtrace. [Where problems could occur] * This patch is bein upstreamed. If one is using external uboot (i.e. provided by some other vendor) it may still crash when trying to boot Ubuntu's riscv64 rootfs or cloud image. [Other Info] * Patch is being reviewed upstream https://lists.denx.de/pipermail/u-boot/2021-May/449176.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936673] Re: BUG: kernel NULL pointer dereference, address: 0000000000000000
The security fixed Kernel # cat /proc/version_signature Ubuntu 5.4.0-80.90-generic 5.4.124 from focal-security also fixes the problem. Greetings, Lars -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936673 Title: BUG: kernel NULL pointer dereference, address: Status in linux package in Ubuntu: Confirmed Bug description: Hi Kernelguys, after updating my kernel from 5.4.0-74.83-generic to 5.4.0-77.86 I get a kernelpanic when putting load onto my NFSv4.1 mount. About the System: I run a Galera Cluster on a VMWare VM with data stored on a NetApp system with NFSv4.1: # grep nfs4 /proc/mounts server:/GALERANFS_MUC_2_LOG /GALERANFS_MUC_LOG nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 nfs-server-ip:/GALERANFS_MUC_2_BACKUP /GALERANFS_MUC_BACKUP nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 nfs-server-ip:/GALERANFS_MUC_2_DATA /GALERANFS_MUC_DATA nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 The panic I get when I give a little load on the NFS mount with my mariadb-server is: Jul 16 15:26:10 maria2021-muc-2 systemd[1]: Starting MariaDB 10.5.11 database server... Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.549355] BUG: kernel NULL pointer dereference, address: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.551391] #PF: supervisor read access in kernel mode Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.553377] #PF: error_code(0x) - not-present page Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.555350] PGD 0 P4D 0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.557268] Oops: [#7] SMP PTI Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.559186] CPU: 0 PID: 44171 Comm: mysqld Tainted: P DO 5.4.0-77-generic #86-Ubuntu Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.560644] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.17369862.B64.2012240522 12/24/2020 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.562497] RIP: 0010:pnfs_mark_matching_lsegs_return+0x108/0x150 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.563447] Code: 01 f0 80 4b 40 08 49 8b 06 4c 89 f3 4c 39 75 d0 75 9d 8b 45 bc 85 c0 75 3b 48 8b 4d c8 48 8b 41 38 48 8d 51 38 48 39 c2 74 23 <41> 8b 34 24 48 8b 7d c8 44 89 fa e8 88 e3 ff ff 31 c0 48 83 c4 20 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.565380] RSP: 0018:a6e91c113d68 EFLAGS: 00010283 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.566361] RAX: 95e263669540 RBX: 95e263669268 RCX: 95e263669240 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.567364] RDX: 95e263669278 RSI: 95e263669540 RDI: 95e263669240 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.568358] RBP: a6e91c113db0 R08: 0064 R09: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.569356] R10: 95e24b0ed480 R11: 003d R12: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.570355] R13: 95e263669278 R14: 95e263669268 R15: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.571353] FS: 7f5d988cf800() GS:95e277a0() knlGS: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.572340] CS: 0010 DS: ES: CR0: 80050033 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.573317] CR2: CR3: 0002229a2003 CR4: 001606f0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.574289] Call Trace: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.575260] _pnfs_return_layout+0x118/0x230 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.576272] ? nfs_inode_detach_delegation+0x29/0x70 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.577244] nfs4_evict_inode+0x70/0x80 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.578205] evict+0xd2/0x1b0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.579174] iput+0x148/0x210 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.580104] do_unlinkat+0x1c5/0x2d0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.581014] __x64_sys_unlink+0x23/0x30 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.581905] do_syscall_64+0x57/0x190 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.582763] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.583615] RIP: 0033:0x7f5d98b78e3b Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.584429] Code: f0 ff ff 73 01 c3 48 8b 0d 52 80 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 84 00 00 00 00 00
[Kernel-packages] [Bug 1937220] Re: ubuntu_ltp.memcg_subgroup_charge fails on focal/linux on ppc64el Power9
** Tags added: 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/1937220 Title: ubuntu_ltp.memcg_subgroup_charge fails on focal/linux on ppc64el Power9 Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux source package in Bionic: Won't Fix Status in linux source package in Focal: Won't Fix Bug description: [Impact] memcg_subgroup_charge from ubuntu_ltp is failing on ppc64el (only with Power9) with focal/linux 5.4.0-81.91. 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 4325376 memcg_subgroup_charge 1 TINFO: Warming up pid: 530613 memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 530613 memcg_subgroup_charge 1 TFAIL: rss is 2949120, 4325376 expected memcg_subgroup_charge 1 TPASS: rss is 0 as expected memcg_subgroup_charge 2 TINFO: Running memcg_process --mmap-anon -s 4325376 memcg_subgroup_charge 2 TINFO: Warming up pid: 530633 memcg_subgroup_charge 2 TINFO: Process is still here after warm up: 530633 memcg_subgroup_charge 2 TFAIL: rss is 3997696, 4325376 expected memcg_subgroup_charge 2 TPASS: rss is 0 as expected memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 4325376 memcg_subgroup_charge 3 TINFO: Warming up pid: 530653 memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 530653 memcg_subgroup_charge 3 TFAIL: rss is 2883584, 4325376 expected memcg_subgroup_charge 3 TPASS: rss is 0 as expected memcg_subgroup_charge 4 TINFO: AppArmor enabled, this may affect test results memcg_subgroup_charge 4 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) memcg_subgroup_charge 4 TINFO: loaded AppArmor profiles: none Summary: passed 3 failed 3 broken 0 skipped 0 warnings 0 There has been some major changed on the testcase, so it's not clear if this is a test case issue or a kernel regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1937220/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935583] Re: Kernel panic on Bionic 5.4.0-47-generic
Hi Merlin, Thanks for the information. I will look into it. And can you provide us more information please? e.g. firmware ver, output of `lspci -vvnn`, what kind of operation you use to reproduce this issue. Thanks a lot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935583 Title: Kernel panic on Bionic 5.4.0-47-generic Status in kunpeng920: In Progress Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] Stack overflow in Kunpeng 920 32cores server, cause system reboot in production environment every month [Steps to Reproduce] 1)I cannot reproduce coz its a low-probability event [Actual Results] [1474521.296779] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.323300] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.349890] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.376451] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.411383] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.438042] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.455965] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.481140] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.508051] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.534519] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.561541] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.565243] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.596849] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.623516] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.659077] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.677128] Kernel panic - not syncing: corrupted stack end detected inside scheduler [1474521.685108] CPU: 7 PID: 5387 Comm: query_event Kdump: loaded Tainted: G OE 5.4.0-47-generic #51~18.04.1-Ubuntu [1474521.686201] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.689690] Unable to handle kernel paging request at virtual address 8027ce43b007 [1474521.689693] Mem abort info: [1474521.689695] ESR = 0x9605 [1474521.689698] EC = 0x25: DABT (current EL), IL = 32 bits [1474521.689700] SET = 0, FnV = 0 [1474521.689702] EA = 0, S1PTW = 0 [1474521.689703] Data abort info: [1474521.689705] ISV = 0, ISS = 0x0005 [1474521.689706] CM = 0, WnR = 0 [1474521.689710] swapper pgtable: 4k pages, 48-bit VAs, pgdp=014ac000 [1474521.689712] [8027ce43b007] pgd=2027f003, pud= [1474521.689719] Internal error: Oops: 9605 [#1] SMP [1474521.689722] Modules linked in: binfmt_misc xt_MASQUERADE iptable_nat nf_nat xt_tcpudp xt_multiport xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter rpcsec_gss_krb5 nfsv4 nfs fscache bonding nls_iso8859_1 ipmi_ssif joydev input_leds hns_roce_hw_v2 ib_uverbs ipmi_si spi_dw_mmio ipmi_devintf ipmi_msghandler spi_dw hisi_dma cppc_cpufreq sch_fq_codel 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 xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure mlx5_ib(OE) hibmc_drm realtek drm_vram_helper ttm drm_kms_helper hid_generic crct10dif_ce syscopyarea sysfillrect ghash_ce mlx5_core(OE) sysimgblt hisi_sas_v3_hw sha2_ce hns3 hisi_sas_main sha256_arm64 fb_sys_fops mlx_compat(OE) sha1_ce hclge libsas usbhid tls drm hid hnae3 megaraid_sas ahci [1474521.689802] scsi_transport_sas mlxfw(OE) gpio_dwapb aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [1474521.689814] CPU: 14 PID: 5899 Comm: tcp_upload Kdump: loaded Tainted: G OE 5.4.0-47-generic #51~18.04.1-Ubuntu [1474521.689816] Hardware name: [About Privacy Deleted], BIOS 1.39 06/11/2020 [1474521.689819] pstate: 0049 (nzcv daif +PAN -UAO) [1474521.689831] pc : kmem_cache_alloc+0x4c/0x220 [1474521.689835] lr : kmem_cache_alloc+0x44/0x220 [1474521.689836] sp : 800010073b90 [1474521.689838] x29: 800010073b90 x28: 0001 [1474521.689841] x27: 0027b78270c0 x26: 2027cc2b [1474521.689844] x25: 05ea x24: 0040 [1474521.689847] x23: 2027d3896000 x22: 800010c11a8c [1474521.689850] x21: 0a20 x20: 0007 [1474521.689852] x19: 2027d3896000 x18: 0014 [1474521.689856] x17: ea74f425 x16: 5fe3fcbf [1474521.689859] x15: f26bfafa x14: 683f9e854da8ab18 [1474521.689862] x13: e3274a9b1fac7e1b x12: 298175ef2f49b6e3
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
** No longer affects: alsa-ucm-conf (Ubuntu) ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: New => Won't Fix ** Changed in: alsa-ucm-conf (Ubuntu Impish) Status: Confirmed => Won't Fix ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Focal: Confirmed Status in linux source package in Focal: New Status in linux-firmware source package in Focal: New Status in alsa-ucm-conf source package in Groovy: Won't Fix Status in linux source package in Groovy: Won't Fix Status in linux-firmware source package in Groovy: Won't Fix Status in alsa-ucm-conf source package in Hirsute: Won't Fix Status in linux source package in Hirsute: New Status in linux-firmware source package in Hirsute: New Status in alsa-ucm-conf source package in Impish: Won't Fix Status in linux source package in Impish: Confirmed Status in linux-firmware source package in Impish: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937220] Re: ubuntu_ltp.memcg_subgroup_charge fails on focal/linux on ppc64el Power9
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Krzysztof Kozlowski (krzk) ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: New => Won't Fix ** Changed in: linux (Ubuntu Bionic) Status: New => Won't Fix ** Changed in: linux (Ubuntu Focal) Status: Confirmed => Won't Fix ** Tags added: hinted -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937220 Title: ubuntu_ltp.memcg_subgroup_charge fails on focal/linux on ppc64el Power9 Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux source package in Bionic: Won't Fix Status in linux source package in Focal: Won't Fix Bug description: [Impact] memcg_subgroup_charge from ubuntu_ltp is failing on ppc64el (only with Power9) with focal/linux 5.4.0-81.91. 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 4325376 memcg_subgroup_charge 1 TINFO: Warming up pid: 530613 memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 530613 memcg_subgroup_charge 1 TFAIL: rss is 2949120, 4325376 expected memcg_subgroup_charge 1 TPASS: rss is 0 as expected memcg_subgroup_charge 2 TINFO: Running memcg_process --mmap-anon -s 4325376 memcg_subgroup_charge 2 TINFO: Warming up pid: 530633 memcg_subgroup_charge 2 TINFO: Process is still here after warm up: 530633 memcg_subgroup_charge 2 TFAIL: rss is 3997696, 4325376 expected memcg_subgroup_charge 2 TPASS: rss is 0 as expected memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 4325376 memcg_subgroup_charge 3 TINFO: Warming up pid: 530653 memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 530653 memcg_subgroup_charge 3 TFAIL: rss is 2883584, 4325376 expected memcg_subgroup_charge 3 TPASS: rss is 0 as expected memcg_subgroup_charge 4 TINFO: AppArmor enabled, this may affect test results memcg_subgroup_charge 4 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) memcg_subgroup_charge 4 TINFO: loaded AppArmor profiles: none Summary: passed 3 failed 3 broken 0 skipped 0 warnings 0 There has been some major changed on the testcase, so it's not clear if this is a test case issue or a kernel regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1937220/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930945] Re: [nouveau] ubuntu desktop - changing display configuration lost wallpaper (trap messages filled dmesg)
There isn't any supported stable graphics driver for "nvidia quadro nvs 290" after Ubuntu version 20.04. So if you can't replace the graphics card then I would recommend staying with Ubuntu 20.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930945 Title: [nouveau] ubuntu desktop - changing display configuration lost wallpaper (trap messages filled dmesg) Status in linux package in Ubuntu: New Bug description: Ubuntu Desktop Impish daily test on - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) Changing display positions in settings. I have two monitors, one above the other (so not the default). I made change and it looked okay so I said keep. I noticed I was wrong having TOP/BOTTOM displays the wrong way (detected via mouse movements between displays) so I made another change of the TOP/BOTTOM displays in "DISPLAYS" of GNOME settings clicked apply again & keep... ** Expected Results On changing display orientation I expect wallpaper to be redrawn, or remain on screen ** Actual Results I now have BLUE background on both displays. (this was soon changing.. but that didn't occur until I tried to change wallpapers...) /var/crash is empty... operation appears normal; I lost background. lots of TRAP messages though fill `dmesg` ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-desktop 1.469 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 5 03:01:52 2021 LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210604) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937072] Re: Incomplete screen redraws
Please try: * Installing the proprietary Nvidia driver via the 'Additional Drivers' app. The open source nouveau driver is frequently buggy so I would like to eliminate that from the equation ASAP. * Looking in your BIOS and see if you can disable the discrete Nvidia GPU temporarily. Does that fix it? ** 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/1937072 Title: Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. 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: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO 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/1937072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937072] Re: Screen tearing and display glitches
Thanks. It looks like you've tried both Xorg and Wayland sessions. Are the bugs the same in both? ** Tags added: hybrid i915 nouveau ** Package changed: ubuntu => mutter (Ubuntu) ** Summary changed: - Screen tearing and display glitches + Incomplete screen redraws ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: licelake ** Tags removed: licelake ** Tags added: icelake -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. 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: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO 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/1937072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919266] Re: kubuntu hirsute daily QA-test install & no background at first login
I used the dc7700 in a GNOME QA-test and got a response from vanvugt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930945/comments/5 "Yes this looks like a nouveau kernel driver bug. I recommend using the proprietary Nvidia driver instead, but it seems your GPU only supports driver version 340 and that's now too old to be supported in Ubuntu 21.10. So to continue using the "nvidia quadro nvs 290" you should probably install Ubuntu 20.04 instead where it is still supported. " I suspect they're related - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930945 ** Package changed: kubuntu-settings (Ubuntu) => linux (Ubuntu) ** Tags added: nouveau -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1919266 Title: kubuntu hirsute daily QA-test install & no background at first login Status in linux package in Ubuntu: New Bug description: This issue is minor. QA-test install on - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) (testcase: manual install, equivalent of install alongside) ** description & actual results On first login, there is NO WALLPAPER background. ** expected results I liked the wallpaper I saw behind `ubiquity` , and expected to see that on login (or another wallpaper). ** further notes I logged out, logged in again & this time I had wallpaper. (the wallpaper I saw & loved during install). Maybe this was a one-off fluke, but reporting... Minor issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: kubuntu-settings-desktop 1:21.04.4build1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Mar 16 12:50:44 2021 InstallationDate: Installed on 2021-03-16 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210315) PackageArchitecture: all SourcePackage: kubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937220] Re: ubuntu_ltp.memcg_subgroup_charge fails on focal/linux on ppc64el Power9
Fixed on focal/hwe-5.11 after applying:
f3344adf38bdb3107d40483dd9501215ad40edce
a3d4c05a447486b90298a8c964916c8f4fcb903f
a3747b53b1771a787fea71d86a2fc39aea337685
a18e6e6e150a98b9ce3e9acabeff407e7b6ba0c0
a7df69b81aac5bdeb5c5aef9addd680ce22feebf
dc26532aed0ab25c0801a34640d1f3b9b9098a48
2d146aa3aa842d7f5065802556b4f9a2c6e8ef12 ("mm: memcontrol: switch to rstat")
The last commit is actual fix but others are needed as dependencies and
to fix patch context.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1937220
Title:
ubuntu_ltp.memcg_subgroup_charge fails on focal/linux on ppc64el
Power9
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Focal:
Confirmed
Bug description:
[Impact]
memcg_subgroup_charge from ubuntu_ltp is failing on ppc64el (only with
Power9) with focal/linux 5.4.0-81.91.
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 4325376
memcg_subgroup_charge 1 TINFO: Warming up pid: 530613
memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 530613
memcg_subgroup_charge 1 TFAIL: rss is 2949120, 4325376 expected
memcg_subgroup_charge 1 TPASS: rss is 0 as expected
memcg_subgroup_charge 2 TINFO: Running memcg_process --mmap-anon -s 4325376
memcg_subgroup_charge 2 TINFO: Warming up pid: 530633
memcg_subgroup_charge 2 TINFO: Process is still here after warm up: 530633
memcg_subgroup_charge 2 TFAIL: rss is 3997696, 4325376 expected
memcg_subgroup_charge 2 TPASS: rss is 0 as expected
memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 4325376
memcg_subgroup_charge 3 TINFO: Warming up pid: 530653
memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 530653
memcg_subgroup_charge 3 TFAIL: rss is 2883584, 4325376 expected
memcg_subgroup_charge 3 TPASS: rss is 0 as expected
memcg_subgroup_charge 4 TINFO: AppArmor enabled, this may affect test results
memcg_subgroup_charge 4 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1
(requires super/root)
memcg_subgroup_charge 4 TINFO: loaded AppArmor profiles: none
Summary:
passed 3
failed 3
broken 0
skipped 0
warnings 0
There has been some major changed on the testcase, so it's not clear
if this is a test case issue or a kernel regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1937220/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930945] Re: [nouveau] ubuntu desktop - changing display configuration lost wallpaper (trap messages filled dmesg)
Likely related - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919266 (hirsute, kubuntu) wallpaper issues on same box (used only for QA-tests/support) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930945 Title: [nouveau] ubuntu desktop - changing display configuration lost wallpaper (trap messages filled dmesg) Status in linux package in Ubuntu: New Bug description: Ubuntu Desktop Impish daily test on - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) Changing display positions in settings. I have two monitors, one above the other (so not the default). I made change and it looked okay so I said keep. I noticed I was wrong having TOP/BOTTOM displays the wrong way (detected via mouse movements between displays) so I made another change of the TOP/BOTTOM displays in "DISPLAYS" of GNOME settings clicked apply again & keep... ** Expected Results On changing display orientation I expect wallpaper to be redrawn, or remain on screen ** Actual Results I now have BLUE background on both displays. (this was soon changing.. but that didn't occur until I tried to change wallpapers...) /var/crash is empty... operation appears normal; I lost background. lots of TRAP messages though fill `dmesg` ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-desktop 1.469 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 5 03:01:52 2021 LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210604) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919266] [NEW] kubuntu hirsute daily QA-test install & no background at first login
You have been subscribed to a public bug: This issue is minor. QA-test install on - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) (testcase: manual install, equivalent of install alongside) ** description & actual results On first login, there is NO WALLPAPER background. ** expected results I liked the wallpaper I saw behind `ubiquity` , and expected to see that on login (or another wallpaper). ** further notes I logged out, logged in again & this time I had wallpaper. (the wallpaper I saw & loved during install). Maybe this was a one-off fluke, but reporting... Minor issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: kubuntu-settings-desktop 1:21.04.4build1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Mar 16 12:50:44 2021 InstallationDate: Installed on 2021-03-16 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210315) PackageArchitecture: all SourcePackage: kubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute iso-testing -- kubuntu hirsute daily QA-test install & no background at first login https://bugs.launchpad.net/bugs/1919266 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 1934878] Re: Mute/mic LEDs no function on some HP platfroms
[Machines] 1) HP ProBook 630 G8 Notebook PC 2) HP ProBook 445 G8 Notebook PC 3) HP ProBook 450 G8 Notebook PC [Kernel version] 5.11.0.26.28 [Result] audio/mic mute LEDs works great ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1934878 Title: Mute/mic LEDs no function on some HP platfroms Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress 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: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress 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] The mic mute/audio mute LEDS are not work on 1) HP ProBook 630 G8 Notebook PC 2) HP ProBook 445 G8 Notebook PC 3) HP ProBook 450 G8 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
Just tested focal proposed kernel again using amplitude, there was only update for linux-base and like before fix has not been merged yet. So, I am not sure if I should update new label to done based on previous test of "linux-image-unsigned-5.13.0-1005-oem" where the fix has actually landed. If I can get some confirmation would be great. 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/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: New Bug description: Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923162] Re: riscv64 images fail to boot in qemu
Hey William! Any reason why the verification-failed-hirsute tag has been removed? Did you discuss with Dimitri and all is good already, or is the update still incorrect for hirsute? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: Fix Released Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Focal: Invalid Status in u-boot source package in Focal: Fix Committed Status in u-boot-menu source package in Focal: Fix Committed Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: Fix Committed Status in u-boot-menu source package in Hirsute: Fix Released Bug description: [Impact] * u-boot may crash when attempting to boot extlinux.conf which specifies fdtdir; the given u-boot config doesn't specify a dtb filename to load; autodetection tries to make one up using $soc & $board variables; and if one or both of them are not set (as it is the case for qemu) it would crash. Fix this crash by doing validation / checking when quering for $soc & $board variables in autodetectionn. [Test Plan] * Use qemu & uboot produced by the build that fixes this bug report properly and attempt to boot hirsute's riscv64+unmatched image. * It should boot correctly without a crash / qemu backtrace. [Where problems could occur] * This patch is bein upstreamed. If one is using external uboot (i.e. provided by some other vendor) it may still crash when trying to boot Ubuntu's riscv64 rootfs or cloud image. [Other Info] * Patch is being reviewed upstream https://lists.denx.de/pipermail/u-boot/2021-May/449176.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935583] Re: Kernel panic on Bionic 5.4.0-47-generic
[1516299.566982] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1516299.582325] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1516299.601741] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1516299.606825] Unable to handle kernel paging request at virtual address 800011691ab0 [1516299.609605] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1516299.612022] Unhandled fault at 0x8944d9d0 [1516299.612031] Mem abort info: [1516299.612034] ESR = 0x8630 [1516299.612037] EC = 0x21: IABT (current EL), IL = 32 bits [1516299.612042] SET = 0, FnV = 0 [1516299.612044] EA = 0, S1PTW = 0 [1516299.612047] swapper pgtable: 4k pages, 48-bit VAs, pgdp=014ac000 [1516299.612049] [8944d9d0] pgd=2027f003, pud=2027e003, pmd=0027d1ed3003, pte= [1516299.612055] Internal error: TLB conflict abort: 8630 [#1] SMP [1516299.612057] Modules linked in: binfmt_misc xt_MASQUERADE iptable_nat nf_nat xt_tcpudp xt_multiport xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding nls_iso8859_1 ipmi_ssif input_leds joydev hns_roce_hw_v2 hisi_dma spi_dw_mmio ipmi_si spi_dw ipmi_devintf ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser sunrpc rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure ib_uverbs ib_core realtek hibmc_drm drm_vram_helper ttm hid_generic drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce hisi_sas_v3_hw sha2_ce mlx5_core sysimgblt sha256_arm64 hns3 hisi_sas_main fb_sys_fops sha1_ce hclge libsas usbhid tls drm hid hnae3 megaraid_sas ahci scsi_transport_sas mlxfw gpio_dwapb [1516299.612109] aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [1516299.612116] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 5.4.0-47-generic #51~18.04.1-Ubuntu [1516299.612117] Hardware name: [About Privacy Deleted], BIOS 1.39 06/11/2020 [1516299.612118] pstate: 8049 (Nzcv daif +PAN -UAO) [1516299.612172] pc : mlx5e_features_check+0x0/0x490 [mlx5_core] [1516299.612178] lr : netif_skb_features+0xfc/0x248 [1516299.612179] sp : 80001001b140 [1516299.612180] x29: 80001001b140 x28: 001745f4 [1516299.612181] x27: 0027b157faac x26: [1516299.612183] x25: 0001 x24: 80001001b253 [1516299.612185] x23: 0027b4b8 x22: 0027b4b8 [1516299.612186] x21: 800011b78000 x20: 0027cea31c00 [1516299.612187] x19: 000850c21cd14ba9 x18: 800011254420 [1516299.612189] x17: x16: [1516299.612190] x15: 0001 x14: c178 [1516299.612192] x13: e238 x12: 088002c8 [1516299.612193] x11: 0027756dbe70 x10: 0070 [1516299.612195] x9 : 0001 x8 : 0001 [1516299.612196] x7 : f6576c61 x6 : 354623ec [1516299.612198] x5 : 0001 x4 : [1516299.612199] x3 : 8944d9d0 x2 : 000850c21cd14ba9 [1516299.612201] x1 : 0027b4b8 x0 : 0027cea31c00 [1516299.612202] Call trace: [1516299.612239] mlx5e_features_check+0x0/0x490 [mlx5_core] [1516299.612241] validate_xmit_skb+0x2c/0x2f8 [1516299.612242] validate_xmit_skb_list+0x50/0xb0 [1516299.612245] sch_direct_xmit+0xfc/0x528 [1516299.612246] __dev_queue_xmit+0x818/0x890 [1516299.612248] dev_queue_xmit+0x24/0x30 [1516299.612257] bond_dev_queue_xmit+0x44/0x98 [bonding] [1516299.612264] bond_do_alb_xmit+0xcc/0x1b0 [bonding] [1516299.612270] bond_alb_xmit+0xd0/0x660 [bonding] [1516299.612275] bond_start_xmit+0x154/0x4f8 [bonding] [1516299.612277] dev_hard_start_xmit+0xb4/0x268 [1516299.612278] __dev_queue_xmit+0x740/0x890 [1516299.612280] dev_queue_xmit+0x24/0x30 [1516299.612282] ip_finish_output2+0x31c/0x570 [1516299.612284] __ip_finish_output+0x128/0x200 [1516299.612285] ip_finish_output+0x38/0xd0 [1516299.612287] ip_output+0xb0/0x130 [1516299.612288] ip_local_out+0x58/0x68 [1516299.612290] __ip_queue_xmit+0x12c/0x368 [1516299.612294] ip_queue_xmit+0x10/0x18 [1516299.612295] __tcp_transmit_skb+0x4cc/0xa58 [1516299.612297] __tcp_send_ack.part.47+0xb0/0x128 [1516299.612299] tcp_send_ack+0x34/0x40 [1516299.612300] __tcp_ack_snd_check+0x50/0x1b8 [1516299.612302] tcp_rcv_established+0x338/0x6a0 [1516299.612304] tcp_v4_do_rcv+0x94/0x208 [1516299.612306] tcp_v4_rcv+0xa50/0xba8 [1516299.612307] ip_protocol_deliver_rcu+0x44/0x200 [1516299.612308] ip_local_deliver_finish+0x64/0x78 [1516299.612310] ip_local_deliver+0x90/0x108 [1516299.612311] ip_sublist_rcv_finish+0x5c/0x88 [1516299.612312] ip_sublist_rcv+0x1d0/0x260 [1516299.612314] ip_list_rcv+0x110/0x1b8 [1516299.612315]
[Kernel-packages] [Bug 1937169] Re: [SRU][OEM-5.13/U] Add support of Foxconn bluetooth 0xe0cd on MT7921
** This bug is no longer a duplicate of bug 1937004 Add additional Mediatek MT7921 WiFi/BT device IDs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937169 Title: [SRU][OEM-5.13/U] Add support of Foxconn bluetooth 0xe0cd on MT7921 Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Bug description: SRU justification: [Impact] Another Foxconn bluetooth device on MT7921 doesn't load driver. [Fix] MT7921 bluetooth needs both driver and firmware, firmware is SRUed. Add ID in btusb. Due to the project schedule, this patch is not applied by upstream, SRU it for oem-5.13 kernel and Unstable as SAUCE. [Test] Verified on hardware, bluetooth works fine with headset and phone. [Where problems could occur] The MT7921 BT may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937169] Re: [SRU][OEM-5.13/U] Add support of Foxconn bluetooth 0xe0cd on MT7921
*** This bug is a duplicate of bug 1937004 *** https://bugs.launchpad.net/bugs/1937004 ** This bug has been marked a duplicate of bug 1937004 Add additional Mediatek MT7921 WiFi/BT device IDs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937169 Title: [SRU][OEM-5.13/U] Add support of Foxconn bluetooth 0xe0cd on MT7921 Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Bug description: SRU justification: [Impact] Another Foxconn bluetooth device on MT7921 doesn't load driver. [Fix] MT7921 bluetooth needs both driver and firmware, firmware is SRUed. Add ID in btusb. Due to the project schedule, this patch is not applied by upstream, SRU it for oem-5.13 kernel and Unstable as SAUCE. [Test] Verified on hardware, bluetooth works fine with headset and phone. [Where problems could occur] The MT7921 BT may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937004] Re: Add additional Mediatek MT7921 WiFi/BT device IDs
SRU: * https://lists.ubuntu.com/archives/kernel-team/2021-July/122611.html (oem-5.13, h) * https://lists.ubuntu.com/archives/kernel-team/2021-July/122618.html (u) ** Description changed: + [SRU Justification] + + [Impact] + + Some Mediatek MT7921 Bluetooth doesn't work out of box. + + [Fix] + + One ID for Lite-On was included in upstream, but we need two additional + more from different vendors. + + [Test Case] + + With firmware from bug 1936452, this will bring up MT7921 Bluetooth. + Check BD address from output of `hciconfig`. + + [Where problems could occur] + + This brings up new devices that wasn't working. After being up and + running, we may face some other runtime issue, e.g. power consumption. + + == original bug description == + Mediatek MT7921 has been added to mainline kernel & firmware. Firmware part is being handled by bug 1936452, and WiFi fw loading failure in bug 1936790. This issue will focus on backport/add device IDs for MT7921: * Bus 001 Device 004: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device * Bus 002 Device 003: ID 13d3:3567 IMC Networks linux$ git log --graph --oneline korg/master -- \ drivers/bluetooth/ \ drivers/net/wireless/mediatek/mt76/mt7921/ linux-firmware$ git log --graph --oneline korg/master -- \ mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin \ mediatek/WIFI_RAM_CODE_MT7961_1.bin \ mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin * a7882719 linux-firmware: update frimware for mediatek bluetooth chip (MT7921) * 2fd5139f linux-firmware: update firmware for MT7921 WiFi device to 20210612122753 * 42a66e5b linux-firmware: update firmware for MT7921 WiFi device * 58fb90a0 linux-firmware: add frimware for mediatek bluetooth chip (MT7921) * 391fd50d linux-firmware: add firmware for MT7921 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1278 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X135 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-05 (16 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 192f:0616 Avago Technologies, Pte. ADNS-5700 Optical Mouse Controller (5-button) Bus 001 Device 002: ID 03f0:344a HP, Inc HP USB Slim Keyboard Bus 001 Device 004: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3910 Package: linux-firmware 1.187.15+staging.9 [origin: LP-PPA-vicamo-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9009-oem root=UUID=6ae05750-3063-48a4-92af-626f62ff75fc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9009.10+staging.2-oem 5.13.0 RelatedPackageVersions: linux-restricted-modules-5.13.0-9009-oem N/A linux-backports-modules-5.13.0-9009-oem N/A linux-firmware 1.187.15+staging.9 Tags: third-party-packages focal Uname: Linux 5.13.0-9009-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/12/2021 dmi.bios.release: 0.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.8.22 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.8.22:bd07/12/2021:br0.8:svnDellInc.:pnInspiron3910:pvr:sku0AD3:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: Inspiron 3910 dmi.product.sku: 0AD3 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/1937004 Title: Add additional Mediatek MT7921 WiFi/BT device IDs Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] Some Mediatek MT7921 Bluetooth doesn't work out of box. [Fix] One ID for Lite-On was included in upstream,
[Kernel-packages] [Bug 1937220] Re: ubuntu_ltp.memcg_subgroup_charge fails on focal/linux on ppc64el Power9
v5.4.0-81.91 and 5.4.0-77 reproduced only on Power9. Power8 machines with these behave good. Reproduced on Power9 also with: - focal/hwe-5.11 5.11.0-25-generic - mainline 5.11 - mainline 5.12 - mainline 5.12.19 Seems to be fixed on: - mainline 5.13-rc2 - mainline 5.13-rc4 - mainline 5.13 ** Tags added: 5.11 5.4 focal ppc64el ubuntu-ltp ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Krzysztof Kozlowski (krzk) ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Krzysztof Kozlowski (krzk) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Krzysztof Kozlowski (krzk) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937220 Title: ubuntu_ltp.memcg_subgroup_charge fails on focal/linux on ppc64el Power9 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Focal: Confirmed Bug description: [Impact] memcg_subgroup_charge from ubuntu_ltp is failing on ppc64el (only with Power9) with focal/linux 5.4.0-81.91. 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 4325376 memcg_subgroup_charge 1 TINFO: Warming up pid: 530613 memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 530613 memcg_subgroup_charge 1 TFAIL: rss is 2949120, 4325376 expected memcg_subgroup_charge 1 TPASS: rss is 0 as expected memcg_subgroup_charge 2 TINFO: Running memcg_process --mmap-anon -s 4325376 memcg_subgroup_charge 2 TINFO: Warming up pid: 530633 memcg_subgroup_charge 2 TINFO: Process is still here after warm up: 530633 memcg_subgroup_charge 2 TFAIL: rss is 3997696, 4325376 expected memcg_subgroup_charge 2 TPASS: rss is 0 as expected memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 4325376 memcg_subgroup_charge 3 TINFO: Warming up pid: 530653 memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 530653 memcg_subgroup_charge 3 TFAIL: rss is 2883584, 4325376 expected memcg_subgroup_charge 3 TPASS: rss is 0 as expected memcg_subgroup_charge 4 TINFO: AppArmor enabled, this may affect test results memcg_subgroup_charge 4 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) memcg_subgroup_charge 4 TINFO: loaded AppArmor profiles: none Summary: passed 3 failed 3 broken 0 skipped 0 warnings 0 There has been some major changed on the testcase, so it's not clear if this is a test case issue or a kernel regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1937220/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935853] Re: Fix second monitor hotplug on Intel TGP PCH
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Confirmed => Fix Committed -- 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/1935853 Title: Fix second monitor hotplug on Intel TGP PCH Status in HWE Next: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Bug description: [Impact] Intel TGP dekstop cannot detect second monitor. [Fix] Remove an IRQ setup routine and re-order some other IRQ setups. [Test] 1. Boot up the system with single monitor connected. 2. Hotplug second monitor. With the fix applied, the system can detect the 2nd monitor correctly. [Where problems could occur] This fix removed some special handling for early gen Core, so HPD on those old Core systems might be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1935853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936998] Re: e1000e blocks the boot process when it tried to write checksum to its NVM
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1936998 Title: e1000e blocks the boot process when it tried to write checksum to its NVM Status in HWE Next: New Status in linux package in Ubuntu: In Progress 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: In Progress Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress 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] While probing e1000e, it checks its NVM checksum, and write correct checksum back if the checksum is not correct. But for recent GBE update for security, its NVM could be written once for MAC address during production, so write checksum during driver probing is not allowed and would block the boot process. [Fix] Intel provides a fix for it. https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20210718041031.3619696-1-sasha.nef...@intel.com/ [Test] Verified on a Dell machine which has wrong NVM checksum. [Where problems could occur] From what Intel told us, the checksum isn't correct is not a big deal, we could ignore it and it won't lead to any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937010] Re: Focal update: v5.10.47 upstream stable release
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Fix Committed -- 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/1937010 Title: Focal update: v5.10.47 upstream stable release Status in linux-oem-5.10 package in Ubuntu: Confirmed Status in linux-oem-5.10 source package in Focal: 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.10.47 upstream stable release from git://git.kernel.org/ Linux 5.10.47 integrity: Load mokx variables into the blacklist keyring certs: Add ability to preload revocation certs certs: Move load_system_certificate_list to a common function certs: Add EFI_CERT_X509_GUID support for dbx entries Revert "drm: add a locked version of drm_is_current_master" netfs: fix test for whether we can skip read when writing beyond EOF swiotlb: manipulate orig_addr when tlb_addr has offset KVM: SVM: Call SEV Guest Decommission if ASID binding fails mm, futex: fix shared futex pgoff on shmem huge page mm/thp: another PVMW_SYNC fix in page_vma_mapped_walk() mm/thp: fix page_vma_mapped_walk() if THP mapped by ptes mm: page_vma_mapped_walk(): get vma_address_end() earlier mm: page_vma_mapped_walk(): use goto instead of while (1) mm: page_vma_mapped_walk(): add a level of indentation mm: page_vma_mapped_walk(): crossing page table boundary mm: page_vma_mapped_walk(): prettify PVMW_MIGRATION block mm: page_vma_mapped_walk(): use pmde for *pvmw->pmd mm: page_vma_mapped_walk(): settle PageHuge on entry mm: page_vma_mapped_walk(): use page for pvmw->page mm: thp: replace DEBUG_VM BUG with VM_WARN when unmap fails for split mm/thp: unmap_mapping_page() to fix THP truncate_cleanup_page() mm/thp: fix page_address_in_vma() on file THP tails mm/thp: fix vma_address() if virtual address below file offset mm/thp: try_to_unmap() use TTU_SYNC for safe splitting mm/thp: make is_huge_zero_pmd() safe and quicker mm/thp: fix __split_huge_pmd_locked() on shmem migration entry mm, thp: use head page in __migration_entry_wait() mm/rmap: use page_not_mapped in try_to_unmap() mm/rmap: remove unneeded semicolon in page_not_mapped() mm: add VM_WARN_ON_ONCE_PAGE() macro x86/fpu: Make init_fpstate correct with optimized XSAVE x86/fpu: Preserve supervisor states in sanitize_restored_user_xstate() kthread: prevent deadlock when kthread_mod_delayed_work() races with kthread_cancel_delayed_work_sync() kthread_worker: split code for canceling the delayed work timer ceph: must hold snap_rwsem when filling inode for async create i2c: robotfuzz-osif: fix control-request directions KVM: do not allow mapping valid but non-reference-counted pages s390/stack: fix possible register corruption with stack switch helper nilfs2: fix memory leak in nilfs_sysfs_delete_device_group scsi: sd: Call sd_revalidate_disk() for ioctl(BLKRRPART) gpiolib: cdev: zero padding during conversion to gpioline_info_changed i2c: i801: Ensure that SMBHSTSTS_INUSE_STS is cleared when leaving i801_access pinctrl: stm32: fix the reported number of GPIO lines per bank perf/x86: Track pmu in per-CPU cpu_hw_events net: ll_temac: Avoid ndo_start_xmit returning NETDEV_TX_BUSY net: ll_temac: Add memory-barriers for TX BD access PCI: Add AMD RS690 quirk to enable 64-bit DMA recordmcount: Correct st_shndx handling mac80211: handle various extensible elements correctly mac80211: reset profile_periodicity/ema_ap net: qed: Fix memcpy() overflow of qed_dcbx_params() KVM: selftests: Fix kvm_check_cap() assertion r8169: Avoid memcpy() over-reading of ETH_SS_STATS sh_eth: Avoid memcpy() over-reading of ETH_SS_STATS r8152: Avoid memcpy() over-reading of ETH_SS_STATS net/packet: annotate accesses to po->ifindex net/packet: annotate accesses to po->bind net: caif: fix memory leak in ldisc_open riscv32: Use medany C model for modules net: phy: dp83867: perform soft reset and retain established link net/packet: annotate data race in packet_sendmsg() inet: annotate date races around sk->sk_txhash net: annotate data race in sock_error() ping: Check return value of function 'ping_queue_rcv_skb' inet: annotate data race in inet_send_prepare() and inet_dgram_connect() net: ethtool: clear heap allocations for ethtool function mac80211: drop multicast fragments net: ipv4: Remove unneed BUG() function dmaengine: mediatek: use GFP_NOWAIT
[Kernel-packages] [Bug 1937144] Re: The front mic can't be detected on a lenovo thinkstation machine
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-oem-5.10 (Ubuntu) Status: In Progress => Invalid ** Changed in: linux-oem-5.10 (Ubuntu) Assignee: Hui Wang (hui.wang) => (unassigned) -- 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/1937144 Title: The front mic can't be detected on a lenovo thinkstation machine Status in HWE Next: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Bug description: The patch is sent to oem-5.10 first, and other ubuntu kernels will merge this patch with stable update since this patch was already CCed to stable. [Impact] Users plug a headset or microphone to the front mic jack, but the system can't detect the plug and will not set the mic to be the active input device. [Fix] Backport a upstream patch, this will change the front mic jack's name from Front Mic to Mic, then the pulseaudio could handle the plug/unplug. [Test] Plug a headset to the front mic jack, open the gnome-sound-setting, the front mic is the active input device, use this device to record sound, it could record the sound successfully. [Where problems could occur] It could make the other mic can't be detected, but this possibility is very low and I alreaed tested all audio jacks on that machine, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937144/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936682] Re: Fix kernel panic caused by legacy devices on AMD platforms
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Confirmed => Fix Committed -- 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/1936682 Title: Fix kernel panic caused by legacy devices on AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] When a legacy device is only 32bit DMA capable and it's in the same IOMMU group with iommu_v2 capable devices, the device in question will be forced to use identity mapping and triggers kernel panic on DMA operation because it can't do 64bit DMA. [Fix] Keep swiotlb enabled so legacy devices can do 64bit DMA. This is also how Intel and ARM64 platforms deal with legacy devices. [Test] Boot an affected system. Kernel panic in Realtek WiFi driver's probe routine. After the patch is applied, the system can work normally. [Where problems could occur] The default swiotlb uses 64MB memory, so if the system doesn't have any legacy device, there are 64MB ram less for the system to use. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936921] Re: While screen while vt switching with AMD W5700 or W5500
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1936921 Title: While screen while vt switching with AMD W5700 or W5500 Status in HWE Next: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Bug description: [Impact] Ubuntu-oem-5.10-5.10.0-1027.28 includes some amdgpu patches to support s2idle feature, but it leads to the white screen while vt switching during booting up. [Fix] After bisect the kernel, we need below commit to fix this issue. 0b08c54bb7a37 drm/amd/display: Fix the display corruption issue on Navi10 [Test] Verified on Dell machine with AMD W5700 graphics card. [Where problems could occur] Hard to evaluate, but there is no further code modification on this part since 10/20/2020, and no "Fixes:" on this commit, so it should be stable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937220] [NEW] ubuntu_ltp.memcg_subgroup_charge fails on focal/linux on ppc64el Power9
Public bug reported: [Impact] memcg_subgroup_charge from ubuntu_ltp is failing on ppc64el (only with Power9) with focal/linux 5.4.0-81.91. 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 4325376 memcg_subgroup_charge 1 TINFO: Warming up pid: 530613 memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 530613 memcg_subgroup_charge 1 TFAIL: rss is 2949120, 4325376 expected memcg_subgroup_charge 1 TPASS: rss is 0 as expected memcg_subgroup_charge 2 TINFO: Running memcg_process --mmap-anon -s 4325376 memcg_subgroup_charge 2 TINFO: Warming up pid: 530633 memcg_subgroup_charge 2 TINFO: Process is still here after warm up: 530633 memcg_subgroup_charge 2 TFAIL: rss is 3997696, 4325376 expected memcg_subgroup_charge 2 TPASS: rss is 0 as expected memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 4325376 memcg_subgroup_charge 3 TINFO: Warming up pid: 530653 memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 530653 memcg_subgroup_charge 3 TFAIL: rss is 2883584, 4325376 expected memcg_subgroup_charge 3 TPASS: rss is 0 as expected memcg_subgroup_charge 4 TINFO: AppArmor enabled, this may affect test results memcg_subgroup_charge 4 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) memcg_subgroup_charge 4 TINFO: loaded AppArmor profiles: none Summary: passed 3 failed 3 broken 0 skipped 0 warnings 0 There has been some major changed on the testcase, so it's not clear if this is a test case issue or a kernel regression. ** Affects: ubuntu-kernel-tests Importance: Undecided Assignee: Krzysztof Kozlowski (krzk) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Krzysztof Kozlowski (krzk) Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Krzysztof Kozlowski (krzk) Status: Confirmed ** Tags: 5.11 5.4 focal ppc64el ubuntu-ltp ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) 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/1937220 Title: ubuntu_ltp.memcg_subgroup_charge fails on focal/linux on ppc64el Power9 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Focal: Confirmed Bug description: [Impact] memcg_subgroup_charge from ubuntu_ltp is failing on ppc64el (only with Power9) with focal/linux 5.4.0-81.91. 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 4325376 memcg_subgroup_charge 1 TINFO: Warming up pid: 530613 memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 530613 memcg_subgroup_charge 1 TFAIL: rss is 2949120, 4325376 expected memcg_subgroup_charge 1 TPASS: rss is 0 as expected memcg_subgroup_charge 2 TINFO: Running memcg_process --mmap-anon -s 4325376 memcg_subgroup_charge 2 TINFO: Warming up pid: 530633 memcg_subgroup_charge 2 TINFO: Process is still here after warm up: 530633 memcg_subgroup_charge 2 TFAIL: rss is 3997696, 4325376 expected memcg_subgroup_charge 2 TPASS: rss is 0 as expected memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 4325376 memcg_subgroup_charge 3 TINFO: Warming up pid: 530653 memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 530653 memcg_subgroup_charge 3 TFAIL: rss is 2883584, 4325376 expected memcg_subgroup_charge 3 TPASS: rss is 0 as expected memcg_subgroup_charge 4 TINFO: AppArmor enabled, this may affect test results memcg_subgroup_charge 4 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) memcg_subgroup_charge 4 TINFO: loaded AppArmor profiles: none Summary: passed 3 failed 3 broken 0 skipped 0 warnings 0 There has been some major changed on the testcase, so it's not clear if this is a test case issue or a kernel regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1937220/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936296] Re: Fix display output on HP hybrid GFX laptops
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Confirmed => Fix Committed -- 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/1936296 Title: Fix display output on HP hybrid GFX laptops Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] Video output MUX switched from Intel GPU to Nvidia GPU after S3, so display settings are lost. [Fix] Always use Nvidia GPU to do the video output. This matches the behavior on the other OS. [Test] Connect and external monitor, and change the scaling factor or resolution, suspend the laptop. After wakeup, the custom monitor setting is kept. [Where problems could occur] If nvidia.ko or nouveau.ko is blacklisted, the video output may stop working, as it's now routed away from i915 device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937169] Re: [SRU][OEM-5.13/U] Add support of Foxconn bluetooth 0xe0cd on MT7921
** Summary changed: - [SRU][OEM-5.13/U] Add support of Foxconn bluetooth on MT7921 + [SRU][OEM-5.13/U] Add support of Foxconn bluetooth 0xe0cd on MT7921 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937169 Title: [SRU][OEM-5.13/U] Add support of Foxconn bluetooth 0xe0cd on MT7921 Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Bug description: SRU justification: [Impact] Another Foxconn bluetooth device on MT7921 doesn't load driver. [Fix] MT7921 bluetooth needs both driver and firmware, firmware is SRUed. Add ID in btusb. Due to the project schedule, this patch is not applied by upstream, SRU it for oem-5.13 kernel and Unstable as SAUCE. [Test] Verified on hardware, bluetooth works fine with headset and phone. [Where problems could occur] The MT7921 BT may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937004] Re: Add additional Mediatek MT7921 WiFi/BT device IDs
Upstream 0489:e0c8 and 13d3:3567 to bluetooth-next: http://lists.infradead.org/pipermail/linux- mediatek/2021-July/027176.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/1937004 Title: Add additional Mediatek MT7921 WiFi/BT device IDs Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: Mediatek MT7921 has been added to mainline kernel & firmware. Firmware part is being handled by bug 1936452, and WiFi fw loading failure in bug 1936790. This issue will focus on backport/add device IDs for MT7921: * Bus 001 Device 004: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device * Bus 002 Device 003: ID 13d3:3567 IMC Networks linux$ git log --graph --oneline korg/master -- \ drivers/bluetooth/ \ drivers/net/wireless/mediatek/mt76/mt7921/ linux-firmware$ git log --graph --oneline korg/master -- \ mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin \ mediatek/WIFI_RAM_CODE_MT7961_1.bin \ mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin * a7882719 linux-firmware: update frimware for mediatek bluetooth chip (MT7921) * 2fd5139f linux-firmware: update firmware for MT7921 WiFi device to 20210612122753 * 42a66e5b linux-firmware: update firmware for MT7921 WiFi device * 58fb90a0 linux-firmware: add frimware for mediatek bluetooth chip (MT7921) * 391fd50d linux-firmware: add firmware for MT7921 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1278 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X135 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-05 (16 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 192f:0616 Avago Technologies, Pte. ADNS-5700 Optical Mouse Controller (5-button) Bus 001 Device 002: ID 03f0:344a HP, Inc HP USB Slim Keyboard Bus 001 Device 004: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3910 Package: linux-firmware 1.187.15+staging.9 [origin: LP-PPA-vicamo-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9009-oem root=UUID=6ae05750-3063-48a4-92af-626f62ff75fc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9009.10+staging.2-oem 5.13.0 RelatedPackageVersions: linux-restricted-modules-5.13.0-9009-oem N/A linux-backports-modules-5.13.0-9009-oem N/A linux-firmware 1.187.15+staging.9 Tags: third-party-packages focal Uname: Linux 5.13.0-9009-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/12/2021 dmi.bios.release: 0.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.8.22 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.8.22:bd07/12/2021:br0.8:svnDellInc.:pnInspiron3910:pvr:sku0AD3:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: Inspiron 3910 dmi.product.sku: 0AD3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932165] Re: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Description changed: + [Impact] + + lttng-modules-dkms is reporting many build errors with linux-hwe-5.11, + because of many kernel ABI changes. + + [Fix] + + Backporting the individual patches to fix all the build errors would be + a lot of work and the risk to introduce regressions would be pretty + high, therefore it seems safer to update to the version that is also + used in impish, that works with 5.11 and it's backward compatible (so it + works also with 5.4). + + [Test] + + ubuntu_lttng_smoke_test from (git://kernel.ubuntu.com/ubuntu/autotest- + client-tests) + + [Where problems could occur] + + This is a major version update, so it does not contain trivial changes + as backporting individual patches/fixes, so there's a risk to see + regressions with lttng (however potential regressions are *only* limited + to lttng). + + However, this way is definitely safer than backporting all the + individual changes to fix the all the kernel ABI changes introduced in + 5.11. + + [Original bug report] + This is a scripted bug report about ADT failures while running lttng- modules tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lttng-modules/20210611_205859_b8295@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lttng-modules/20210612_123048_fc99b@/log.gz - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lttng-modules/20210611_210510_27086@/log.gz - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lttng-modules/20210611_210134_272f4@/log.gz + amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lttng-modules/20210611_205859_b8295@/log.gz + arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lttng-modules/20210612_123048_fc99b@/log.gz + ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lttng-modules/20210611_210510_27086@/log.gz + s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lttng-modules/20210611_210134_272f4@/log.gz -- 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/1932165 Title: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in lttng-modules package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in lttng-modules source package in Focal: Confirmed Bug description: [Impact] lttng-modules-dkms is reporting many build errors with linux-hwe-5.11, because of many kernel ABI changes. [Fix] Backporting the individual patches to fix all the build errors would be a lot of work and the risk to introduce regressions would be pretty high, therefore it seems safer to update to the version that is also used in impish, that works with 5.11 and it's backward compatible (so it works also with 5.4). [Test] ubuntu_lttng_smoke_test from (git://kernel.ubuntu.com/ubuntu/autotest- client-tests) [Where problems could occur] This is a major version update, so it does not contain trivial changes as backporting individual patches/fixes, so there's a risk to see regressions with lttng (however potential regressions are *only* limited to lttng). However, this way is definitely safer than backporting all the individual changes to fix the all the kernel ABI changes introduced in 5.11. [Original bug report] This is a scripted bug report about ADT failures while running lttng- modules tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lttng-modules/20210611_205859_b8295@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lttng-modules/20210612_123048_fc99b@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lttng-modules/20210611_210510_27086@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lttng-modules/20210611_210134_272f4@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937216] Re: nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2: nvidia kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1937216 Title: nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-450 package in Ubuntu: New Bug description: new DELL computer (pre-configured by DELL) with ubuntu 20.04 istalled by DELL. started working with this machine since 4 days ONLY ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46 Uname: Linux 5.10.0-1038-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.10.0-1038-oem Date: Wed Jul 21 10:49:29 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DuplicateSignature: dkms:nvidia-dkms-450:450.80.02-0ubuntu0.20.04.2:/var/lib/dkms/nvidia/450.80.02/build/nvidia/nv-dma.c:600:37: error: implicit declaration of function ‘get_dma_ops’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2021-06-27 (25 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 PackageVersion: 450.80.02-0ubuntu0.20.04.2 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.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2: nvidia kernel module failed to build 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-450/+bug/1937216/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937216] [NEW] nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2: nvidia kernel module failed to build
Public bug reported: new DELL computer (pre-configured by DELL) with ubuntu 20.04 istalled by DELL. started working with this machine since 4 days ONLY ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46 Uname: Linux 5.10.0-1038-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.10.0-1038-oem Date: Wed Jul 21 10:49:29 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DuplicateSignature: dkms:nvidia-dkms-450:450.80.02-0ubuntu0.20.04.2:/var/lib/dkms/nvidia/450.80.02/build/nvidia/nv-dma.c:600:37: error: implicit declaration of function ‘get_dma_ops’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2021-06-27 (25 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 PackageVersion: 450.80.02-0ubuntu0.20.04.2 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.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-450 (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 nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1937216 Title: nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-450 package in Ubuntu: New Bug description: new DELL computer (pre-configured by DELL) with ubuntu 20.04 istalled by DELL. started working with this machine since 4 days ONLY ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46 Uname: Linux 5.10.0-1038-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.10.0-1038-oem Date: Wed Jul 21 10:49:29 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DuplicateSignature: dkms:nvidia-dkms-450:450.80.02-0ubuntu0.20.04.2:/var/lib/dkms/nvidia/450.80.02/build/nvidia/nv-dma.c:600:37: error: implicit declaration of function ‘get_dma_ops’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2021-06-27 (25 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 PackageVersion: 450.80.02-0ubuntu0.20.04.2 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.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2: nvidia kernel module failed to build 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-450/+bug/1937216/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937004] Re: Add additional Mediatek MT7921 WiFi/BT device IDs
** Description changed: Mediatek MT7921 has been added to mainline kernel & firmware. Firmware part is being handled by bug 1936452, and WiFi fw loading failure in bug 1936790. This issue will focus on backport/add device IDs for MT7921: - * Bus 001 Device 004: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device - * + * Bus 001 Device 004: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device + * Bus 002 Device 003: ID 13d3:3567 IMC Networks linux$ git log --graph --oneline korg/master -- \ drivers/bluetooth/ \ drivers/net/wireless/mediatek/mt76/mt7921/ linux-firmware$ git log --graph --oneline korg/master -- \ mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin \ mediatek/WIFI_RAM_CODE_MT7961_1.bin \ mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin * a7882719 linux-firmware: update frimware for mediatek bluetooth chip (MT7921) * 2fd5139f linux-firmware: update firmware for MT7921 WiFi device to 20210612122753 * 42a66e5b linux-firmware: update firmware for MT7921 WiFi device * 58fb90a0 linux-firmware: add frimware for mediatek bluetooth chip (MT7921) * 391fd50d linux-firmware: add firmware for MT7921 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1278 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X135 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-05 (16 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 192f:0616 Avago Technologies, Pte. ADNS-5700 Optical Mouse Controller (5-button) Bus 001 Device 002: ID 03f0:344a HP, Inc HP USB Slim Keyboard Bus 001 Device 004: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3910 Package: linux-firmware 1.187.15+staging.9 [origin: LP-PPA-vicamo-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9009-oem root=UUID=6ae05750-3063-48a4-92af-626f62ff75fc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9009.10+staging.2-oem 5.13.0 RelatedPackageVersions: linux-restricted-modules-5.13.0-9009-oem N/A linux-backports-modules-5.13.0-9009-oem N/A linux-firmware 1.187.15+staging.9 Tags: third-party-packages focal Uname: Linux 5.13.0-9009-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/12/2021 dmi.bios.release: 0.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.8.22 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.8.22:bd07/12/2021:br0.8:svnDellInc.:pnInspiron3910:pvr:sku0AD3:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: Inspiron 3910 dmi.product.sku: 0AD3 dmi.sys.vendor: Dell Inc. ** Attachment added: "lsusb.13d3:3567" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937004/+attachment/5512811/+files/lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937004 Title: Add additional Mediatek MT7921 WiFi/BT device IDs Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: Mediatek MT7921 has been added to mainline kernel & firmware. Firmware part is being handled by bug 1936452, and WiFi fw loading failure in bug 1936790. This issue will focus on backport/add device IDs for MT7921: * Bus 001 Device 004: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device * Bus 002 Device 003: ID 13d3:3567 IMC Networks linux$ git log --graph --oneline korg/master -- \ drivers/bluetooth/ \ drivers/net/wireless/mediatek/mt76/mt7921/ linux-firmware$ git log --graph --oneline korg/master -- \ mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin \ mediatek/WIFI_RAM_CODE_MT7961_1.bin \ mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin
[Kernel-packages] [Bug 1934548] Re: RISC-V: Illegal instruction
This appears to be resolved in 5.11.0-1015-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1934548 Title: RISC-V: Illegal instruction Status in Ubuntu: New Status in linux-riscv package in Ubuntu: New Bug description: When booting the Ubuntu Server image on the SiFive HiFive Unmatched I am getting the following error. The last known working version was 1012. The issue is being tracked on the SiFive forums at https://forums.sifive.com/t/u-boot-says-unhandled-exception-illegal-instruction/4898 ``` Starting kernel ... [0.00] Linux version 5.11.0-1014-generic (buildd@riscv64-qemu-lcy01-084) (gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #14-Ubuntu SMP Wed Jun 30 17:56:50 UTC 2021 (Ubuntu 5.11.0-1014.14-generic 5.11.22) [0.00] OF: fdt: Ignoring memory range 0x8000 - 0x8020 [0.00] earlycon: sifive0 at MMIO 0x1001 (options '') [0.00] printk: bootconsole [sifive0] enabled [0.00] efi: UEFI not found. [0.00] Initial ramdisk at: 0x(ptrval) (183422976 bytes) [0.00] cma: Reserved 32 MiB at 0xfe00 [0.00] Zone ranges: [0.00] DMA32[mem 0x8020-0x] [0.00] Normal [mem 0x0001-0x00047fff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x8020-0x00047fff] [0.00] Initmem setup node 0 [mem 0x8020-0x00047fff] [0.00] DMA32 zone: 512 pages in unavailable ranges [0.00] SBI specification v0.2 detected [0.00] SBI implementation ID=0x1 Version=0x9 [0.00] SBI v0.2 TIME extension detected [0.00] SBI v0.2 IPI extension detected [0.00] SBI v0.2 RFENCE extension detected [0.00] software IO TLB: mapped [mem 0xfa00-0xfe00] (64MB) [0.00] SBI v0.2 HSM extension detected [0.00] CPU with hartid=0 is not available [0.00] CPU with hartid=0 is not available [0.00] riscv: ISA extensions acdfim [0.00] riscv: ELF capabilities acdfim [0.00] percpu: Embedded 26 pages/cpu s69272 r8192 d29032 u106496 [0.00] Built 1 zonelists, mobility grouping on. Total pages: 4128264 [0.00] Kernel command line: root=/dev/nvme0n1p1 ro earlycon [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [0.00] Sorting __ex_table... [0.00] mem auto-init: stack:off, heap alloc:on, heap free:off [0.00] Memory: 16165452K/16775168K available (9854K kernel code, 5763K rwdata, 8192K rodata, 2519K init, 997K bss, 576948K reserved, 32768K cma-reserved) [0.00] random: get_random_u64 called from kmem_cache_open+0x36/0x338 with crng_init=0 [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] ftrace: allocating 38893 entries in 152 pages [0.00] Oops - illegal instruction [#1] [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 5.11.0-1014-generic #14-Ubuntu [0.00] epc: ffe0920e ra : ffe09384 sp : ffe001803d30 [0.00] gp : ffe001a14240 tp : ffe00180f440 t0 : ffe07fe38000 [0.00] t1 : ffe0019cd338 t2 : s0 : ffe001803d70 [0.00] s1 : a0 : ffe095aa a1 : 0001 [0.00] a2 : 0002 a3 : a4 : [0.00] a5 : a6 : 0004 a7 : 52464e43 [0.00] s2 : 0002 s3 : 0001 s4 : [0.00] s5 : s6 : s7 : [0.00] s8 : ffe001a170c0 s9 : 0001 s10: 0001 [0.00] s11: fffcc5d0 t3 : 0068 t4 : 000b [0.00] t5 : ffe0019cd3e0 t6 : ffe001803cd8 [0.00] status: 00020100 badaddr: 0513f187 cause: 0002 [0.00] ---[ end trace f67eb9af4d8d492b ]--- [0.00] Kernel panic - not syncing: Attempted to kill the idle task! [0.00] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]--- ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1934548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1932163] Re: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
This bug was fixed in the package evdi - 1.9.1-1ubuntu4 --- evdi (1.9.1-1ubuntu4) impish; urgency=medium * Support USB-less systems (e.g. s390x). (LP: #1932163) -- Andrea Righi Tue, 20 Jul 2021 14:32:12 + ** Changed in: evdi (Ubuntu) Status: Confirmed => Fix Released -- 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/1932163 Title: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in evdi package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Confirmed Status in evdi source package in Focal: Confirmed Status in linux-hwe-5.11 source package in Focal: Confirmed Status in evdi source package in Hirsute: Confirmed Status in linux-hwe-5.11 source package in Hirsute: Confirmed Bug description: [Impact] focal users running latest hwe kernel, version 5.11, won't be able to use evdi-dkms. [Test case] Built evdi dkms and loaded the evdi module on 5.4, 5.8 and 5.11 kernels. [Potential regression] DisplayLink devices will stop working. -- This is a scripted bug report about ADT failures while running evdi tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/e/evdi/20210611_210228_7f0da@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/e/evdi/20210612_122245_bd52e@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/e/evdi/20210611_210028_038f3@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/e/evdi/20210611_205902_3dc65@/log.gz [Other] NB! dkms ftbfs fixes must be built in security, such that after SRU process in -proposed & -updates it can be copied into -security pocket too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937169] Re: [SRU][OEM-5.13/U] Add support of Foxconn bluetooth on MT7921
** Summary changed: - [SRU][OEM-5.13/U] Add support of Foxconn bluetooch on MT7921 + [SRU][OEM-5.13/U] Add support of Foxconn bluetooth on MT7921 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937169 Title: [SRU][OEM-5.13/U] Add support of Foxconn bluetooth on MT7921 Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Bug description: SRU justification: [Impact] Another Foxconn bluetooth device on MT7921 doesn't load driver. [Fix] MT7921 bluetooth needs both driver and firmware, firmware is SRUed. Add ID in btusb. Due to the project schedule, this patch is not applied by upstream, SRU it for oem-5.13 kernel and Unstable as SAUCE. [Test] Verified on hardware, bluetooth works fine with headset and phone. [Where problems could occur] The MT7921 BT may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937169] [NEW] [SRU][OEM-5.13/U] Add support of Foxconn bluetooch on MT7921
Public bug reported: SRU justification: [Impact] Another Foxconn bluetooth device on MT7921 doesn't load driver. [Fix] MT7921 bluetooth needs both driver and firmware, firmware is SRUed. Add ID in btusb. Due to the project schedule, this patch is not applied by upstream, SRU it for oem-5.13 kernel and Unstable as SAUCE. [Test] Verified on hardware, bluetooth works fine with headset and phone. [Where problems could occur] The MT7921 BT may not work. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux-oem-5.13 (Ubuntu 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/1937169 Title: [SRU][OEM-5.13/U] Add support of Foxconn bluetooch on MT7921 Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Bug description: SRU justification: [Impact] Another Foxconn bluetooth device on MT7921 doesn't load driver. [Fix] MT7921 bluetooth needs both driver and firmware, firmware is SRUed. Add ID in btusb. Due to the project schedule, this patch is not applied by upstream, SRU it for oem-5.13 kernel and Unstable as SAUCE. [Test] Verified on hardware, bluetooth works fine with headset and phone. [Where problems could occur] The MT7921 BT may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934239] Re: mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1934239 Title: mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC Status in OEM Priority Project: Triaged 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: New Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook 830 G8 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
