[Kernel-packages] [Bug 1962197] Re: sudo apt --fix-broken install crashes
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 You have filed this bug about 20.04, but mention Linux Mint & Ubuntu 18.04? they are different OSes so how do they relate to this bug report on a 20.04 system? Please don't confuse details with other unrelated details. I've marked this bug as 'incomplete' as it appears you're in need of support, with no details provided of a crash; no crash dump etc being provided; only screen with what appears to issues that would benefit from support. If you believe I'm incorrect, you leave a message explaining why, and the status can be returned to "New". ** Changed in: linux-signed-hwe-5.13 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1962197 Title: sudo apt --fix-broken install crashes Status in linux-signed-hwe-5.13 package in Ubuntu: Incomplete Bug description: Ubuntu MATE so buggy I had to reinstall (UEFI mode). Now HP OfficeJet Pro 7740 will not print but scanner works fine (It is an all-in-one) printer. Cannon install tesseract-ocr. Tried booting Ubuntu MATE 18.04 on a different drive. Get flashing dots all night. Will not boot. Machine is ASUS A88XM-A with 32GB DRam. A WD 1TB SSD with Ubuntu Mate 20.04.3 (not working). A WD 4TB HD with Ubuntu Mate 18.04 (not working). Running Linux Mint with Cinamon has no problem printing. Just Ubuntu. Found linux image: /boot/vmlinuz-5.13.0-28-generic downloads 17% then crashes. repeatedly! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu Feb 24 10:51:07 2022 InstallationDate: Installed on 2022-01-31 (23 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) SourcePackage: linux-signed-hwe-5.13 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.13/+bug/1962197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962276] Re: Laptop monitor does not turn off/disconnect when the lid is closed
Please try some older and newer kernel versions from https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: Laptop monitor does not turn off/disconnect when the lid is closed Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: After today's updates I can no longer run my Laptop in clam shell mode. I don't use a dock. I connect the second monitor via HDMI cable and and external keyboard/mouse via a USB hub. Usually I can just plugin the monitor and close the lid and the primary display will switch to the external monitor. Now it will default to Monitor 2 as part of the joint display. I also tested booting the machine and closing the lid but this still defaulted to the external monitor as the 2nd display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 16:44:37 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2226] InstallationDate: Installed on 2022-02-23 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) MachineType: LENOVO 20CLS3JN0F ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2015 dmi.bios.release: 1.7 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS3JN0F dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250: dmi.product.family: ThinkPad X250 dmi.product.name: 20CLS3JN0F dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962276] Re: Laptop monitor does not turn off/disconnect when the lid is closed
Hi Daniel yes it is a recent install. I reinstalled Jammy yesterday and ran the updates. It was working fine yesterday and also this morning. before I installed the latest updates. I only noticed that things were not working right when I came home and reconnected the laptop to the external monitor. I have reinstalled Jammy a few time on this machine. I'll keep an eye on the new updates that come through and continue researching. My work around at the moment is to plugin the external monitor and and in the display setting switch it to primary for the session. It works well enough Thanks Rue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: Laptop monitor does not turn off/disconnect when the lid is closed Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: After today's updates I can no longer run my Laptop in clam shell mode. I don't use a dock. I connect the second monitor via HDMI cable and and external keyboard/mouse via a USB hub. Usually I can just plugin the monitor and close the lid and the primary display will switch to the external monitor. Now it will default to Monitor 2 as part of the joint display. I also tested booting the machine and closing the lid but this still defaulted to the external monitor as the 2nd display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 16:44:37 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2226] InstallationDate: Installed on 2022-02-23 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) MachineType: LENOVO 20CLS3JN0F ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2015 dmi.bios.release: 1.7 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS3JN0F dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250: dmi.product.family: ThinkPad X250 dmi.product.name: 20CLS3JN0F dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962276] Re: Laptop monitor does not turn off/disconnect when the lid is closed
I wonder if this new kernel is failing to detect or report the lid closing... It also seems you only installed Ubuntu 1-2 days ago. What version were you using when it last worked? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** 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/1962276 Title: Laptop monitor does not turn off/disconnect when the lid is closed Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: After today's updates I can no longer run my Laptop in clam shell mode. I don't use a dock. I connect the second monitor via HDMI cable and and external keyboard/mouse via a USB hub. Usually I can just plugin the monitor and close the lid and the primary display will switch to the external monitor. Now it will default to Monitor 2 as part of the joint display. I also tested booting the machine and closing the lid but this still defaulted to the external monitor as the 2nd display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 16:44:37 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2226] InstallationDate: Installed on 2022-02-23 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) MachineType: LENOVO 20CLS3JN0F ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2015 dmi.bios.release: 1.7 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS3JN0F dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250: dmi.product.family: ThinkPad X250 dmi.product.name: 20CLS3JN0F dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877506] Re: Overgreedy dependencies for linux kernel
What is proper process for proposing a fix for packaging such important package as linux kernel ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877506 Title: Overgreedy dependencies for linux kernel Status in linux package in Ubuntu: Confirmed Bug description: linux-modules-extra-5.3.0-51-generic requires either linux- image-5.3.0-51-generic or linux-image-unsigned-5.3.0-51-generic to be installed while I have linux-image-5.3.0-51-lowlatency installed forcing me two have two vmlinuz and initrd in my /boot folder for same kernel. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-modules-extra-5.3.0-51-generic 5.3.0-51.44 ProcVersionSignature: Ubuntu 5.3.0-51.44-lowlatency 5.3.18 Uname: Linux 5.3.0-51-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bartek 2047 F pulseaudio /dev/snd/controlC0: bartek 2047 F pulseaudio CurrentDesktop: MATE Date: Fri May 8 06:55:15 2020 InstallationDate: Installed on 2020-01-29 (99 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-51-lowlatency root=UUID=a69a7b67-473c-478b-9f5f-abe99208eff6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-lowlatency N/A linux-backports-modules-5.3.0-51-lowlatency N/A linux-firmware 1.183.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/04/2010 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2A-VM HDMI ACPI BIOS Revision 5001 dmi.board.name: M2A-VM HDMI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMHDMIACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VMHDMI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877506/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952006] Re: [TGL][ADL] ACRN hypervisor support
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952006 Title: [TGL][ADL] ACRN hypervisor support Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] The driver enables the host to run ACRN hypervisor which is a flexible, lightweight reference hypervisor, built with real-time and safety-criticality in mind, optimized to streamline embedded development through an open-source platform. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable ACRN hypervisor [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel TigerLake/AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952007] Re: [ADL] ITBM support for Hybrid platforms
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952007 Title: [ADL] ITBM support for Hybrid platforms Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] Need ITBM support for Hybrid platforms. Need to change the scheduling order from Core, HT, ATOM to Core, ATOM, HT. When using ITBM on systems that has a mixture of CPUs supporting Hyper-Threading and others not supporting it (even offlining HT siblings may cause the issue to be reproducible). Hybrid topologies meet the aforementioned condition. In such cases, threads will be consolidated on CPUs of high priority using got HT siblings, while CPUs of medium priority will remain idle. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable AlderLake [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952356] Re: [EHL][TGL][ADL] PMU support
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952356 Title: [EHL][TGL][ADL] PMU support Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] The patches enable PMU support [Fix] Intel provides a list of patches to provide Linux perf supports [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel ElkhartLake/TigerLake/AdlerLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952356/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960820] Re: linux-azure: Missing ext4 commits
Marking Impish invalid since those commits came in via stable updates. ** Changed in: linux-azure (Ubuntu Impish) Status: Fix Committed => Invalid ** Changed in: linux-azure (Ubuntu Impish) Assignee: Tim Gardner (timg-tpi) => (unassigned) ** Changed in: linux-azure (Ubuntu Impish) Importance: Medium => Undecided -- 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/1960820 Title: linux-azure: Missing ext4 commits Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Invalid Status in linux-azure source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Microsoft has a test that checks for missing file system commits; It has detected that these commits are not present in Azure tuned kernels: 0f2f87d51aebcf71a709b52f661d681594c7dffa ext4: prevent partial update of the extent blocks 9c6e071913792d80894cd0be98cc3c4b770e26d3 ext4: check for inconsistent extents between index and leaf block 8dd27fecede55e8a4e67eef2878040ecad0f0d33 ext4: check for out-of-order index extents in ext4_valid_extent_entries() [Test Case] Microsoft tested [Where things could go wrong] Ext4 file systems could have problems. [Other Info] SF: #00324445 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962223] [NEW] uvcvideo Failed to query (GET_DEF) UVC control 2 on unit 1: -32 (exp. 1)
Public bug reported: Connecting a magnifying webcam (cheap microscope) fills the journal with the message "Failed to query (GET_DEF) UVC control 2 on unit 1: -32 (exp. 1)". It also makes amdgpu driver to start to write Fence "fallback timer expired on ring gfx" and on ring sdma0/sdma1. This corruption or whatever happens produces microstuttering and video/audio framerate loss, like it is reading the same audio buffer two times and then catches up to the current stream position. Because the device was not connected at the time of filing this bug, I have attached an extra file with the output of "lsusb -d a16f:0304 -v". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic-hwe-20.04 5.13.0.30.33~20.04.17 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 24 22:09:07 2022 InstallationDate: Installed on 2014-06-05 (2820 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: linux-meta-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "lsusb-device-verbose.txt" https://bugs.launchpad.net/bugs/1962223/+attachment/5563558/+files/lsusb-device-verbose.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1962223 Title: uvcvideo Failed to query (GET_DEF) UVC control 2 on unit 1: -32 (exp. 1) Status in linux-meta-hwe-5.13 package in Ubuntu: New Bug description: Connecting a magnifying webcam (cheap microscope) fills the journal with the message "Failed to query (GET_DEF) UVC control 2 on unit 1: -32 (exp. 1)". It also makes amdgpu driver to start to write Fence "fallback timer expired on ring gfx" and on ring sdma0/sdma1. This corruption or whatever happens produces microstuttering and video/audio framerate loss, like it is reading the same audio buffer two times and then catches up to the current stream position. Because the device was not connected at the time of filing this bug, I have attached an extra file with the output of "lsusb -d a16f:0304 -v". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic-hwe-20.04 5.13.0.30.33~20.04.17 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 24 22:09:07 2022 InstallationDate: Installed on 2014-06-05 (2820 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: linux-meta-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.13/+bug/1962223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961119] Re: Lower the volume of expected s0i3 WARN_ON
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal ** Changed in: hwe-next 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.14 in Ubuntu. https://bugs.launchpad.net/bugs/1961119 Title: Lower the volume of expected s0i3 WARN_ON Status in HWE Next: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] AMD has a known BIOS bug right now that leads to the following WARN traceback during s0i3 resume (see below). This doesn't have (measurable) functional impact to the system or GPU, but it is an ugly message to have in place and makes it look like a potentially major problem. AMD is working on fixing this in BIOS, but it may not be ready by the time the first platforms launch. [Fix] Print a shorter message warning instead: "Watermarks table not configured properly by SMU". The fixed was cherry-picked from mainline kernel v5.17-rc4. [Test] This is requested by AMD, and tested and verified on the AMD CRB. [Where problems could occur] Low. This only changes the behavors of message printing There are no functional changes. --- WARN_ON messages --- [ cut here ] WARNING: CPU: 8 PID: 60399 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn31/dcn31_smu.c:123 dcn31_smu_send_msg_with_param+0xec/0x130 [amdgpu] Modules linked in: btrfs blake2b_generic xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cpuid michael_mic hid_logitech_hidpp snd_usb_audio snd_usbmidi_lib hid_logitech_dj usbhid cdc_ether usbnet r8152 mii qrtr_mhi joydev intel_rapl_msr intel_rapl_common bnep snd_soc_dmic snd_acp6x_pdm_dma snd_soc_acp6x_mach snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine edac_mce_amd amdgpu snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi nls_iso8859_1 kvm_amd kvm snd_hda_intel qrtr snd_intel_dspcfg ns snd_intel_sdw_acpi snd_hda_codec ath11k_pci crct10dif_pclmul input_leds snd_pci_acp6x ghash_clmulni_intel ath11k snd_hda_core snd_hwdep qmi_helpers aesni_intel snd_pcm uvcvideo crypto_simd videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 iommu_v2 cryptd platform_profile btusb snd_seq_midi gpu_sched rapl mac80211 serio_raw snd_seq_midi_event videobuf2_common sparse_keymap drm_ttm_helper btrtl snd_rawmidi btbcm videodev btintel ttm efi_pstore wmi_bmof hid_multitouch mc bluetooth snd_seq drm_kms_helper snd_seq_device ecdh_generic cfg80211 ecc snd_timer cec rc_core i2c_algo_bit snd fb_sys_fops syscopyarea sysfillrect mhi sysimgblt libarc4 soundcore snd_rn_pci_acp3x snd_pci_acp3x ccp ucsi_acpi typec_ucsi amd_pmc wireless_hotkey mac_hid typec acpi_tad sch_fq_codel msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul thunderbolt nvme i2c_piix4 xhci_pci xhci_pci_renesas nvme_core iosm wmi i2c_hid_acpi video i2c_hid hid Workqueue: events_unbound async_run_entry_fn RIP: 0010:dcn31_smu_send_msg_with_param+0xec/0x130 [amdgpu] Code: 00 e8 38 60 fc ff 48 8b 3b 4c 89 ea be 9b 62 01 00 e8 c8 60 fc ff 85 c0 75 40 bf c6 a7 00 00 e8 aa da 0c c6 41 83 ec 01 75 dc <0f> 0b 48 8b 3b b9 80 84 1e 00 44 89 fa 44 89 f6 e8 af 9c fc ff 48 RSP: 0018:b76d03167bc8 EFLAGS: 00010202 RAX: 00ff RBX: 9dc54f492800 RCX: 0008 RDX: RSI: 0001629b RDI: 9dc548bc RBP: b76d03167bf8 R08: 0009 R09: 0320 R10: 0191 R11: 04451a00 R12: 00030b48 R13: c1717d90 R14: 0011 R15: 0001 FS: () GS:9dcc7e80() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 55f79ba89f68 CR3: 00052681 CR4: 00750ee0 PKRU: 5554 Call Trace: dcn31_smu_transfer_wm_table_dram_2_smu+0x23/0x30 [amdgpu] dcn31_notify_wm_ranges+0x145/0x180 [amdgpu] dcn31_init_hw+0x465/0x8e0 [amdgpu] dc_set_power_state+0x113/0x160 [amdgpu] dm_resume+0x2b5/0x610 [amdgpu] amdgpu_device_ip_resume_phase2+0x58/0xc0 [amdgpu] amdgpu_device_resume+0xd9/0x210 [amdgpu] amdgpu_pmops_resume+0x1d/0x40 [amdgpu] pci_pm_resume+0x5b/0x90 ? pci_pm_thaw+0x80/0x80 dpm_run_callback+0x52/0x160 device_resume+0xdd/0x1e0 async_resume+0x1f/0x60 async_run_entry_fn+0x33/0x120 process_one_work+0x236/0x420 worker_thread+0x34/0x410 ? process_one_work+0x420/0x420 kthread+0x12f/0x150 ? set_kthread_struct+0x40/0x40 ret_from_fork+0x22/0x30 ---[ end trace 71d329758d0428b2 ]--- [ cut here ] WARNING: CPU: 8 PID: 60399 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn31/dcn31_smu.c:105 dcn31_smu_send_msg_with_param+0x56/0x130 [amdgpu]
[Kernel-packages] [Bug 1961121] Re: Not able to enter s2idle state on AMD platforms
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal ** Changed in: hwe-next Assignee: Alex Hung (alexhung) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1961121 Title: Not able to enter s2idle state on AMD platforms Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] AMD Systems don't enter PC6 at runtime and cause failures to enter s2idle. Currently the fix is from kernel driver rather than MP2 firmware, which disable interrupts from kernel driver to fix MP2 firmware blocking CPUOFF. [Fix] The fixes involve 1) cancelling delayed work when entering s0ix and re-scheduling it when resuming from s0ix, and 2) clearing interrupts during the driver initialization and sensor command operations. [Test] This is requested by AMD and was tested on AMD CRB. [Where problems could occur] Risk is low to medium. Some code flow changes are guarded by reasonable conditions, but the fixes introduced additional suspend and resume operations. Having said that, clearing interrupts before driver initialization and cancelling work before entering sleeping states are standard approaches are usually safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961121/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961119] Re: Lower the volume of expected s0i3 WARN_ON
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1025.27 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1961119 Title: Lower the volume of expected s0i3 WARN_ON Status in HWE Next: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] AMD has a known BIOS bug right now that leads to the following WARN traceback during s0i3 resume (see below). This doesn't have (measurable) functional impact to the system or GPU, but it is an ugly message to have in place and makes it look like a potentially major problem. AMD is working on fixing this in BIOS, but it may not be ready by the time the first platforms launch. [Fix] Print a shorter message warning instead: "Watermarks table not configured properly by SMU". The fixed was cherry-picked from mainline kernel v5.17-rc4. [Test] This is requested by AMD, and tested and verified on the AMD CRB. [Where problems could occur] Low. This only changes the behavors of message printing There are no functional changes. --- WARN_ON messages --- [ cut here ] WARNING: CPU: 8 PID: 60399 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn31/dcn31_smu.c:123 dcn31_smu_send_msg_with_param+0xec/0x130 [amdgpu] Modules linked in: btrfs blake2b_generic xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cpuid michael_mic hid_logitech_hidpp snd_usb_audio snd_usbmidi_lib hid_logitech_dj usbhid cdc_ether usbnet r8152 mii qrtr_mhi joydev intel_rapl_msr intel_rapl_common bnep snd_soc_dmic snd_acp6x_pdm_dma snd_soc_acp6x_mach snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine edac_mce_amd amdgpu snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi nls_iso8859_1 kvm_amd kvm snd_hda_intel qrtr snd_intel_dspcfg ns snd_intel_sdw_acpi snd_hda_codec ath11k_pci crct10dif_pclmul input_leds snd_pci_acp6x ghash_clmulni_intel ath11k snd_hda_core snd_hwdep qmi_helpers aesni_intel snd_pcm uvcvideo crypto_simd videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 iommu_v2 cryptd platform_profile btusb snd_seq_midi gpu_sched rapl mac80211 serio_raw snd_seq_midi_event videobuf2_common sparse_keymap drm_ttm_helper btrtl snd_rawmidi btbcm videodev btintel ttm efi_pstore wmi_bmof hid_multitouch mc bluetooth snd_seq drm_kms_helper snd_seq_device ecdh_generic cfg80211 ecc snd_timer cec rc_core i2c_algo_bit snd fb_sys_fops syscopyarea sysfillrect mhi sysimgblt libarc4 soundcore snd_rn_pci_acp3x snd_pci_acp3x ccp ucsi_acpi typec_ucsi amd_pmc wireless_hotkey mac_hid typec acpi_tad sch_fq_codel msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul thunderbolt nvme i2c_piix4 xhci_pci xhci_pci_renesas nvme_core iosm wmi i2c_hid_acpi video i2c_hid hid Workqueue: events_unbound async_run_entry_fn RIP: 0010:dcn31_smu_send_msg_with_param+0xec/0x130 [amdgpu] Code: 00 e8 38 60 fc ff 48 8b 3b 4c 89 ea be 9b 62 01 00 e8 c8 60 fc ff 85 c0 75 40 bf c6 a7 00 00 e8 aa da 0c c6 41 83 ec 01 75 dc <0f> 0b 48 8b 3b b9 80 84 1e 00 44 89 fa 44 89 f6 e8 af 9c fc ff 48 RSP: 0018:b76d03167bc8 EFLAGS: 00010202 RAX: 00ff RBX: 9dc54f492800 RCX: 0008 RDX: RSI: 0001629b RDI: 9dc548bc RBP: b76d03167bf8 R08: 0009 R09: 0320 R10: 0191 R11: 04451a00 R12: 00030b48 R13: c1717d90 R14: 0011 R15: 0001 FS: () GS:9dcc7e80() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 55f79ba89f68 CR3: 00052681 CR4: 00750ee0 PKRU: 5554 Call Trace: dcn31_smu_transfer_wm_table_dram_2_smu+0x23/0x30 [amdgpu] dcn31_notify_wm_ranges+0x145/0x180 [amdgpu] dcn31_init_hw+0x465/0x8e0 [amdgpu] dc_set_power_state+0x113/0x160 [amdgpu] dm_resume+0x2b5/0x610 [amdgpu] amdgpu_device_ip_resume_phase2+0x58/0xc0 [amdgpu] amdgpu_device_resume+0xd9/0x210 [amdgpu] amdgpu_pmops_resume+0x1d/0x40 [amdgpu] pci_pm_resume+0x5b/0x90 ? pci_pm_thaw+0x80/0x80
[Kernel-packages] [Bug 1951055] Re: Reinstate ACPI S5 for reboot
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1025.27 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1951055 Title: Reinstate ACPI S5 for reboot Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] On some systems, Intel WiFi device may stop working after reboot. [Fix] Use ACPI S5 for reboot. [Test] 2000 times of reboot stress, and Intel WiFi continues work on affected system. [Where problems could occur] There was a bug introduced by this patch, but the user didn't want to find the root cause. Since we have more control on Ubuntu kernel, we'll fix the root cause properly this time. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961121] Re: Not able to enter s2idle state on AMD platforms
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1025.27 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1961121 Title: Not able to enter s2idle state on AMD platforms Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] AMD Systems don't enter PC6 at runtime and cause failures to enter s2idle. Currently the fix is from kernel driver rather than MP2 firmware, which disable interrupts from kernel driver to fix MP2 firmware blocking CPUOFF. [Fix] The fixes involve 1) cancelling delayed work when entering s0ix and re-scheduling it when resuming from s0ix, and 2) clearing interrupts during the driver initialization and sensor command operations. [Test] This is requested by AMD and was tested on AMD CRB. [Where problems could occur] Risk is low to medium. Some code flow changes are guarded by reasonable conditions, but the fixes introduced additional suspend and resume operations. Having said that, clearing interrupts before driver initialization and cancelling work before entering sleeping states are standard approaches are usually safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961121/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961855] Re: Fix With 20.04d kernel and WX3200, unit freezes on resume
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1025.27 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1961855 Title: Fix With 20.04d kernel and WX3200, unit freezes on resume Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: New Bug description: [Impact] With WX3200 and 20.04d kernel the unit freezes on resume [Fix] commit 0064b0ce85bb ("drm/amd/pm: enable ASPM by default") enabled ASPM by default but a variety of hardware configurations it turns out that this caused a regression. * PPC64LE hardware does not support ASPM at a hardware level. CONFIG_PCIEASPM is often disabled on these architectures. * Some dGPUs on ALD platforms don't work with ASPM enabled and PCIe subsystem disables it Check with the PCIe subsystem to see that ASPM has been enabled or not. [Test Case] 1. plug wx3200 on the adl machine and make it as a output. 2. suspend machine 3. check if machine could resume successfully [Where problems could occur] Low, just disable AMDGPU ASPM if system doesn't enable it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961971] Re: Disable iwlwifi UHB (ultra high band) channels if we don't support wifi 6e currently
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1025.27 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1961971 Title: Disable iwlwifi UHB (ultra high band) channels if we don't support wifi 6e currently Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: In Progress Bug description: [Impact] Ubuntu currently doesn't support wifi 6e, but wifi 6e AP will be discovered while scanning. User can't get connected to those wifi 6e AP, so disable UHB(ultra high band) in the driver to avoid scanning those bands. [Fix] Marks all AX210 and AX211 cards to disable UHB. [Test] Verified the system with AX211 card and confirm it can't discover wifi 6e bands. [Where problems could occur] Disable non-supported bands won't introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961971/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962185] Re: Add ConnectX7 support and bug fixes to Jammy
kernel change submitted: https://lists.ubuntu.com/archives/kernel-team/2022-February/128309.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/1962185 Title: Add ConnectX7 support and bug fixes to Jammy Status in linux package in Ubuntu: In Progress Status in rdma-core package in Ubuntu: Fix Committed Bug description: [Impact] Add support for NDR (next data rate) in IB MAD. This speed is supported From ConnectX7 onwards. And in addition user space support for NDR was extended. [Test Case] TBD [Regression Potential] TBD [Other Info] Feature patchset: (kernel v5.17-rc1) fbdb0ba7051e IB/mlx5: Expose NDR speed through MAD userspace (upstream rdma-core v39): eb7a7fb3 ibdiags: Extend support of NDR rates f6c49e79 verbs: Extend support of NDR rates 49c2d6e7 pyverbs: Extend support of NDR rates This list might not be full as i haven't ported the patches to Jammy yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oem-5.14/5.14.0.1025.23)
All autopkgtests for the newly accepted linux-meta-oem-5.14 (5.14.0.1025.23) for focal have finished running. The following regressions have been reported in tests triggered by the package: virtualbox-hwe/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64) virtualbox/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-oem-5.14 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853152] Re: [22.04 FEAT] In-kernel crypto: SIMD implementation of chacha20
Patch request submitted: https://lists.ubuntu.com/archives/kernel-team/2022-February/thread.html#128313 Updating status to 'In Progress'. Assigning kernel entry to 'Canonical Kernel Team'. ** Changed in: ubuntu-z-systems Status: New => In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel Team (canonical-kernel-team) ** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853152 Title: [22.04 FEAT] In-kernel crypto: SIMD implementation of chacha20 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: Recent kernel releases provide support for the chacha20 cipher and among others use it to compute pseudo random numbers for /dev/urandom. Chacha20 is a type of algorithm that can be accelerated using SIMD instructions. The goal of this item is to use z System SIMD instruction to implement chacha20. Will be made available earliest for kernel >=5.6. Mean, request for integration if backport is possible for 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1853152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
** Patch added: "fix for jammy" https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+attachment/5563543/+files/kdump-tools_1.6.10ubuntu1.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in kdump-tools package in Ubuntu: Fix Committed Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in kdump-tools source package in Groovy: Invalid Status in makedumpfile source package in Groovy: Won't Fix Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
The build failed on jammy because of a new shellcheck warning, which was fixed in Debian already. See https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1002270. I have uploaded a merge to a PPA, where it built just fine. I am attaching the debdiff for that. Cascardo. ** Bug watch added: Debian Bug tracker #1002270 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002270 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in kdump-tools package in Ubuntu: Fix Committed Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in kdump-tools source package in Groovy: Invalid Status in makedumpfile source package in Groovy: Won't Fix Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Thanks https://targetbay.com/mailchimp-alternatives/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic 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/linux/+bug/1690085/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1959085] Re: Ubuntu 21.10 boot stuck in initramfs
This is fixed release in pending images; which are failing installation due to other bugs. Once those bugs are resolved, and a new image is promoted, it shouldn't experience this zfs issue. So we are blocked on getting Ubuntu Desktop ISO passing the daily automated testing and getting promoted. I will separately double check that the upgrade path works correctly. ** Also affects: ubuntu-cdimage Importance: Undecided Status: New ** Changed in: zfs-linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-cdimage Status: New => Confirmed ** Changed in: zfs-linux (Ubuntu) Status: Invalid => Incomplete ** Summary changed: - Ubuntu 21.10 boot stuck in initramfs + Ubuntu 22.04 boot stuck in initramfs, when installed with zfs encryption -- 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/1959085 Title: Ubuntu 22.04 boot stuck in initramfs, when installed with zfs encryption Status in Ubuntu CD Images: Confirmed Status in initramfs-tools package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Incomplete Bug description: Hi, I just installed the latest Ubuntu desktop from iso file ubuntu-21.10-desktop-amd64.iso inside of VMWare workstation. I chose ZFS and native ZFS encryption of the filesystem. The installation went fine. Everything worked as expected. Then I upgraded the packages to the latest version via the Software updater. After reboot I'm stuck in the initramfs prompt. The following command fails: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_gtw63h /root// Permission denied. And the system never asks me for the password to unlock the root fs. So, I'm guessing that there is something wrong with the new initramfs disk: initrd.img-5.13.0-27-generic When I reboot and select the previous version in grub: initrd.img-5.13.0-27-generic, the system asks for the password and boots without a problem. Thanks. To summarize: 1. Installed new VM using the Ubuntu iso image. Chose ZFS native encryption. Minimal install. 2. As soon as the system came up, I hit the update/upgrade prompt. Rebooted and failed to boot the new version. I didn't customize anything or installed anything extra. root@ubud01:/var# lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 root@ubud01:/var# dpkg -l | grep zfs ii libzfs4linux 2.0.6-1ubuntu2 amd64OpenZFS filesystem library for Linux ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs ii zfs-zed2.0.6-1ubuntu2 amd64OpenZFS Event Daemon ii zfsutils-linux 2.0.6-1ubuntu2 amd64command-line tools to manage OpenZFS filesystems root@ubud01:/var# dpkg -l | grep init ii busybox-initramfs 1:1.30.1-6ubuntu3.1 amd64Standalone shell setup for initramfs ii cryptsetup-initramfs 2:2.3.6-0ubuntu1 all disk encryption support - initramfs integration ii gnome-initial-setup40.4-1ubuntu1 amd64Initial GNOME system setup helper ii init 1.60build1 amd64metapackage ensuring an init system is installed ii init-system-helpers1.60build1 all helper tools for all init systems ii initramfs-tools0.140ubuntu6 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.140ubuntu6 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.140ubuntu6 all generic modular initramfs generator (core tools) ii libatopology2:amd641.2.4-1.1ubuntu3.1 amd64shared library for handling ALSA topology definitions ii libklibc:amd64 2.0.8-6.1ubuntu2 amd64minimal libc subset for use with initramfs ii lsb-base 11.1.0ubuntu3 all Linux Standard Base init script functionality ii ncurses-base 6.2+20201114-2build1 all basic terminal type definitions ii sysvinit-utils
[Kernel-packages] [Bug 1960933] Re: rtw89_pci constantly drops connection with old firmware
yeah sure, I've upgraded to the proposed "linux-firmware 1.201.5". So far it keeps the connection to the Modem well enough for daily use... nevertheless, I'll keep an eye out for future improvements. -- 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/1960933 Title: rtw89_pci constantly drops connection with old firmware Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Impish: Fix Committed Bug description: [Impact] This was on a new Lenovo P14s Gen2 AMD. I'm using Ubuntu 21.10 (impish) The current linux-firmware package (1.201.4+1.201.3) ships with realtek rtw89_pci firmware (/lib/firmware/rtw89/rtw8852a_fw.bin) version v0.13.8.0. My wifi chip wasn't able to keep a connection for more than a minute when connected to a Rodgers "Advanced Wi-Fi Modem". I searched around tried disabling the power_save and stuff. But that had little to no effect. I was about to open an issue on the upstream project and did a last ditch attempt to see if there were any firmware updates... I found linux-firmware.git and it had two newer versions! - v0.13.30.0 (was submitted in May 2021, but it took until october 2021 to show up) https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=ec17b637b7ab928ca7ebc0389e0e3921f1cc7d17 - v0.13.33.0 (was submitted in November 2021 and got merged in December 2021): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=4a7e1f5cabaebe5c044b94b91149f35471d1e983 I've downloaded and installed the latest "v0.13.33.0" on a whim and rebooted. And what a pleasant surprise: Instantly, my wifi connection lasted until the rest of the day. Could you please consider updating this realtek firmware in the next release? Thanks! [Test Case] See above. [Fix] Cherry pick two commit to match current Jammy: 4a7e1f5cabae ("rtw89: 8852a: update fw to v0.13.33.0") ec17b637b7ab ("rtw89: 8852a: update fw to v0.13.30.0") [Where Problems Could Occur] Limited to wifi using RTL8852A HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1960933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959216] Re: linux-azure: CONFIG_FB_EFI=y
This bug is awaiting verification that the linux- azure-4.15/4.15.0-1132.145 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1959216 Title: linux-azure: CONFIG_FB_EFI=y Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-azure-5.11 package in Ubuntu: Invalid Status in linux-azure-5.13 package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Committed Status in linux-azure-5.11 source package in Bionic: Invalid Status in linux-azure-5.13 source package in Bionic: Invalid Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-azure-5.11 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Released Status in linux-azure-4.15 source package in Impish: Invalid Status in linux-azure-5.11 source package in Impish: Invalid Status in linux-azure-5.13 source package in Impish: Invalid Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure-4.15 source package in Jammy: Invalid Status in linux-azure-5.11 source package in Jammy: Invalid Status in linux-azure-5.13 source package in Jammy: Invalid Bug description: SRU Justification [Impact] Secure boot instances of linux-azure require an EFI framebuffer in some cases in order for the VM to boot. The issue was noticed in Ubuntu 18.04 linux-azure kernel, but actually exists in the latest mainline kernel. The issue happens when the below conditions are met: hyperv_pci is built into the kernel and hyperv_fb is not, i.e., this means hyperv_pci loads before hyperv_fb loads. CONFIG_FB_EFI is not defined, i.e., the efifb driver is not used. Here is how the bug happens: Linux VM starts, and vmbus_reserve_fb() reserves the VRAM [base=0xf800, length=8MB]. hyper-pci loads, gets MMIO [base=0xf880, lengh=8KB] as the bridge config window, and may get some other 64-bit MMIO ranges, and some 32-bit MMIO ranges (if needed.) hyperv-fb loads, and gets MMIO [base=0xf800, lengh=8MB or a different length], and sets screen_info.lfb_base = 0. VM panics. The kdump kernel starts to run, and vmbus_reserve_fb() is not reserving [base=0xf800, length=8MB] due to the lfb_base==0. hyperv-pci loads and gets [base=0xf800, lengh=8KB] and the host PCI VSP driver rejects this address as the bridge config window. The crux of the problem is that Linux vmbus driver itself is unable to detect the VRAM base/length (it looks like a video BIOS call is needed to get this info and such a BIOS call is inappropriate or impossible in hv_vmbus) and has to rely on screen_info.lfb_base (which is set by grub or the kdump/kexec tool and can be reset to zero by hyperv_fb/drm). Solution: Enable CONFIG_FB_EFI=y [Test Case] Microsoft tested. This config is also enabled on the master branch. [Where things could go wrong] VMs on certain instance types could fail to boot. [Other Info] SF: #00327005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1959216/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962197] [NEW] sudo apt --fix-broken install crashes
Public bug reported: Ubuntu MATE so buggy I had to reinstall (UEFI mode). Now HP OfficeJet Pro 7740 will not print but scanner works fine (It is an all-in-one) printer. Cannon install tesseract-ocr. Tried booting Ubuntu MATE 18.04 on a different drive. Get flashing dots all night. Will not boot. Machine is ASUS A88XM-A with 32GB DRam. A WD 1TB SSD with Ubuntu Mate 20.04.3 (not working). A WD 4TB HD with Ubuntu Mate 18.04 (not working). Running Linux Mint with Cinamon has no problem printing. Just Ubuntu. Found linux image: /boot/vmlinuz-5.13.0-28-generic downloads 17% then crashes. repeatedly! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu Feb 24 10:51:07 2022 InstallationDate: Installed on 2022-01-31 (23 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "apt installer crashes" https://bugs.launchpad.net/bugs/1962197/+attachment/5563519/+files/Screenshot%20at%202022-02-24%2010-50-13.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1962197 Title: sudo apt --fix-broken install crashes Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Ubuntu MATE so buggy I had to reinstall (UEFI mode). Now HP OfficeJet Pro 7740 will not print but scanner works fine (It is an all-in-one) printer. Cannon install tesseract-ocr. Tried booting Ubuntu MATE 18.04 on a different drive. Get flashing dots all night. Will not boot. Machine is ASUS A88XM-A with 32GB DRam. A WD 1TB SSD with Ubuntu Mate 20.04.3 (not working). A WD 4TB HD with Ubuntu Mate 18.04 (not working). Running Linux Mint with Cinamon has no problem printing. Just Ubuntu. Found linux image: /boot/vmlinuz-5.13.0-28-generic downloads 17% then crashes. repeatedly! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu Feb 24 10:51:07 2022 InstallationDate: Installed on 2022-01-31 (23 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) SourcePackage: linux-signed-hwe-5.13 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.13/+bug/1962197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957986] Re: Recalled NFSv4 files delegations overwhelm server
This bug is awaiting verification that the linux/5.4.0-102.115 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957986 Title: Recalled NFSv4 files delegations overwhelm server Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Bug description: [Impact] An NFSv4 client that does a lot of opens/closes can overwhelm and NFSv4 server, causing a significant drop in performance. In my testing, I've seen performance drop from ~700MiB/s down to < 10MiB/s. The same workload using NFSv3 does not have this problem. [Test Case] This can be demonstrated using the elbencho benchmark from https://github.com/breuner/elbencho: $ elbencho -t 40 -r -n 10 -N 5000 -s 128k -b 128k /mnt/nfs/ubuntu You'll notice the nfsd threads (I stuck w/ the default of 4) start to consume 100% CPU, and the performance of the elbencho benchmark will begin to trickle. [Fix] The following fix solves the problem, but there are a number of patches dependencies required before it will apply to focal: commit 10717f45639f6c1bc27b56405252c3a027406d92 (refs/bisect/bad) Author: Trond Myklebust Date: Mon Jan 27 09:58:19 2020 -0500 NFSv4: Limit the total number of cached delegations Delegations can be expensive to return, and can cause scalability issues for the server. Let's therefore try to limit the number of inactive delegations we hold. Once the number of delegations is above a certain threshold, start to return them on close. Signed-off-by: Trond Myklebust Signed-off-by: Anna Schumaker [What could go wrong] The fixes are restricted to NFS code, so problems should be limited to NFS users. They could include performance issues, crashes, etc. Because these changes are mostly related to NFS delegations, I use the `nfstest_delegation` test suite from nfstest[*] to try and identify any regressions: ./nfstest_delegation --client 192.168.42.1 --server 192.168.42.2 -e /srv/nfstest --trcdelay 4 Both before and after applying the fixes, I see the same 146 tests pass and 23 failures. The 23 failures are expected because I was using a Linux-based NFSv4 server which does not support all of the delegation modes that the test checks for. [*] git://git.linux-nfs.org/projects/mora/nfstest.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959529] Re: Hipersocket page allocation failure on Ubuntu 20.04 based SSC environments
This bug is awaiting verification that the linux/5.4.0-102.115 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959529 Title: Hipersocket page allocation failure on Ubuntu 20.04 based SSC environments Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: == Comment: #0 - D. Gary Chapman - 2022-01-26 12:43:25 == ---Problem Description--- IBM IDAA customer exposes hipersocket page allocation failure on Ubuntu 20.04 based SSC Contact Information = Gary Chapman (ch...@us.ibm.com) ---uname output--- 5.4.0-73-generic #82-Ubuntu Machine Type = IBM Z in IDAA SSC-mode lpar ---Debugger--- A debugger is not configured -- IBM SSC LEVEL: 4.1.5 IBM IDAA LEVEL: 7.5.6 On a client system we are observing this: Jan 19 16:25:57 data5 kernel: kworker/u760:28: page allocation failure: order:0, mode:0xa20(GFP_ATOMIC), nodemask=(null),cpuset=/,mems_allowed=0 Jan 19 16:25:57 data5 kernel: CPU: 20 PID: 4137988 Comm: kworker/u760:28 Kdump: loaded Tainted: G OE 5.4.0-73-generic #82-Ubuntu Jan 19 16:25:57 data5 kernel: Hardware name: IBM 8561 T01 727 (LPAR) Jan 19 16:25:57 data5 kernel: Workqueue: kcryptd/253:11 kcryptd_crypt [dm_crypt] Jan 19 16:25:57 data5 kernel: Call Trace: Jan 19 16:25:57 data5 kernel: ([<006b6d63e092>] show_stack+0x7a/0xc0) Jan 19 16:25:57 data5 kernel: [<006b6d64588a>] dump_stack+0x8a/0xb8 Jan 19 16:25:57 data5 kernel: [<006b6cfd8262>] warn_alloc+0xe2/0x160 IBM LTC Networking team has identified the upstream commit 714c9108851743bb718fbc1bfb81290f12a53854 as the root cause. This patch shows up in the Ubuntu kernel source tree: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/commit/?id=714c9108851743bb718fbc1bfb81290f12a53854 but has not been ported to Ubuntu 20.04 / kernel 5.4 IDAA on SSC requests backport to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959529/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959762] Re: HID_ASUS should depend on USB_HID in stable v4.15 backports
This bug is awaiting verification that the linux/5.4.0-102.115 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959762 Title: HID_ASUS should depend on USB_HID in stable v4.15 backports Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] Backported to bionic/linux commit f83baa0cb6cf ("HID: add hid_is_usb() function to make it simpler for USB detection") brings to HID_ASUS usage of hid_is_usb() which is provided by USB_HID. If HID_ASUS is built as module but USB_HID is not, the kernel build will fail (like linux-azure) did: ERROR: "usb_hid_driver" [drivers/hid/hid-asus.ko] undefined! [Fix] Because of backport of commit commit f83baa0cb6cf ("HID: add hid_is_usb() function to make it simpler for USB detection"), the bionic/linux needs also backport of commit c4f0126d487f ("HID: asus: Add depends on USB_HID to HID_ASUS Kconfig option"). [Test Plan] Build HID_ASUS as module with or without USB_HID. [Where problems could occur] It's a new KConfig dependency, so configs using HID_ASUS without USB_HID will loose HID_ASUS. This is expected, so no problems should occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960182] Re: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7
This bug is awaiting verification that the linux/5.4.0-102.115 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960182 Title: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: Fix CPU-MF error on new IBM Z Hardware by adding support for CPU-MF counter second version 7 Error Symptom: Daemon cpacfstatsd fails on start up of the system with this error message cpacfstatsd: Event DEA_FUNCTIONS for pmu cpum_cf not found (2:No such file or directory) Problem: When the CPU Measurement facility device driver is initialized during kernel boot, it reads out the CPU Measurement facility counter hardware first and second version numbers. Depending on these numbers the device driver exports attributes in the sysfs directory /sys/devices/cpum_cf/events. When the CPM-MF second version number is not known, no attributes of the crypto counter set are exported. However the cpacfstatsd program scans the sysfs directory /sys/devices/cpum_cf/events for attribute files of the crypto counter set, for example attribute file DEA_FUNCTIONS and others. Solution: Add support for the new CPU-MF Measurement counter facility second version number 7. This number then exports the crypto counter set in directory directory /sys/devices/cpum_cf/events. Also add support for limited samples. These hardware samples contain all zeroes and are of no value when using the CPU Measurement Facility sampling hardware. Drop these samples when the limited sampled bit is set in the sample descriptor. Reproduction: Run command ls -l /sys/devices/cpum_cf/events | fgrep DEA DEA_BLOCKED_CYCLES DEA_BLOCKED_FUNCTIONS DEA_CYCLES DEA_FUNCTIONS When there is no output at all the attributes files for the crypto counter set have not been exported. If above output is visible, the described problem does not show up. Upstream-ID: a87b0fd4f9003f8521226e226cf92b18147b3519 745f5d20e7936931f924410f32d8b0e599b5990e Problem-ID:196017 Preventive:yes Reported: Christian Rund SupportTicket: - Reference: - Date: 2022-01-20 Author:Thomas Richter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961968] Re: Broken network on some AWS instances with focal/impish kernels
This bug is awaiting verification that the linux/5.4.0-102.115 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1961968 Title: Broken network on some AWS instances with focal/impish kernels Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] With the latest focal/linux (5.4.0-101.114) and impish/linux (5.13.0-31.34) kernels built for SRU cycle 2022.02.21 some AWS instances fail to boot. This impacts mostly the instance types: c4.large, c3.xlarge and x1e.xlarge. However, not all instances deployed on those types will fail. This is affecting mostly c4.large which fails about 80-90% of all deployments. This was traced to be caused by the network interface failing to come up. The following console log snippets from 5.4.0-101-generic on a c4.large show some hints of what's going on: [...] [3.990368] unchecked MSR access error: RDMSR from 0xc90 at rIP: 0x8ea733c8 (native_read_msr+0x8/0x40) [3.998463] Call Trace: [4.001164] ? set_rdt_options+0x91/0x91 [4.004864] resctrl_late_init+0x592/0x63c [4.008711] ? set_rdt_options+0x91/0x91 [4.012452] do_one_initcall+0x4a/0x200 [4.016115] kernel_init_freeable+0x1c0/0x263 [4.020402] ? rest_init+0xb0/0xb0 [4.024889] kernel_init+0xe/0x110 [4.029245] ret_from_fork+0x35/0x40 [...] [7.718268] ena: The ena device sent a completion but the driver didn't receive a MSI-X interrupt (cmd 8), autopolling mode is OFF [7.727036] ena: Failed to submit get_feature command 12 error: -62 [7.731691] ena :00:03.0: Cannot init indirect table [7.735636] ena :00:03.0: Cannot init RSS rc: -62 [7.740700] ena: probe of :00:03.0 failed with error -62 [...] [Fix] Reverting the following upstream stable commit fixes the issue: 83dbf898a2d4 PCI/MSI: Mask MSI-X vectors only on success [Test Case] Boot an affected AWS instance type with focal/linux (5.4.0-101.114) and impish/linux (5.13.0-31.34) kernels with the mentioned patch reverted. Then boot with the original kernels. It should boot successfully with the reverted patch but fail with the original kernels. [Regression Potential] The patch description mentions fixing a MSI-X issue with a Marvell NVME device, which doesn't seem to be following the PCI-E specification. Reverting this commit will keep the issue on systems with that particular NVME device unfixed. As of now there is no follow-up fix for this commit upstream, we might need to keep an eye on any change and re-apply it in case a fix is found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962155] Re: bnx2x: Add FW 7.13.21.0
** Changed in: linux-firmware (Ubuntu Focal) Status: Triaged => Fix Committed -- 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/1962155 Title: bnx2x: Add FW 7.13.21.0 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Impish: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Bug description: [Impact] * There is new version of bnx2x firmware * oem-5.14 and hwe-5.15 kernels use that one; and when not found fallback to previous version of firmware. [Test Plan] * sudo apt install initramfs-tools * echo bnx2x | sudo tee -a /etc/initramfs-tools/modules * sudo apt install linux-oem-20.04 linux-generic-hwe-20.04-edge With current linux-firmware the above results in: update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic W: Possible missing firmware /lib/firmware/bnx2x/bnx2x-e2-7.13.21.0.fw for module bnx2x W: Possible missing firmware /lib/firmware/bnx2x/bnx2x-e1h-7.13.21.0.fw for module bnx2x W: Possible missing firmware /lib/firmware/bnx2x/bnx2x-e1-7.13.21.0.fw for module bnx2x with updated linux-firmware no lines of "Possible missing firmware" should appear. [Where problems could occur] * v21 firmware version is backwards compatible with v15 firmware previously used, but includes bugfixes. It may result in different NIC behavior. [Other Info] * The v21 firmware is already present in Jammy * The kernels that use v21 firmware are not going to be shipped in Impish * The kernels that use v21 firmware will be available/used in Focal Upstream changelog for the blobs: New firmware v7.13.21.0 along with below fixes/enhancements (which were also part of 7.13.20.0) maintains backward compatibility as well, so that driver can be worked with both the new firmware and an older firmware. - Support direct invalidation of FP HSI Ver per function ID, required for invalidating FP HSI Ver prior to each VF start, as there is no VF start - BRB parity error detection support for the driver - Fix the FCOE underrun flow - Fix PSOD during FCoE BFS over the NIC ports after preboot driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1962155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
Hi @ktanska- Reminder that we're waiting for your feedback on the provided test kernel, before we can merge the iostat/md patch series into the Ubuntu 5.13 kernels. Please verify that it works as expected and report your results here. Thanks very much! -Kamal Mostafa -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux-hwe-5.13 source package in Impish: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13=author=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
This bug returned on my machine. Not sure why it disappeared & reappeared. Also now on 5.15.0-18-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed Bug description: The undefined behaviour sanitiser picks up an array-index-out-of- bounds in the aquantia atlantic driver. The NIC is (I think) built into my gigabyte motherboard (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME- rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to 22.04 (or at least dmesg didn't previously complain). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 13:02:10 2022 InstallationDate: Installed on 2019-08-07 (899 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS XTREME-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS XTREME dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.13.0.32.42)
All autopkgtests for the newly accepted linux-meta (5.13.0.32.42) for impish have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.34-0ubuntu3 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962185] Re: Add ConnectX7 support and bug fixes to Jammy
Marking the rdma-core task fix-committed because those patches are in v39, which is in jammy-proposed. ** Also affects: rdma-core (Ubuntu) Importance: Undecided Status: New ** Changed in: rdma-core (Ubuntu) Status: New => Fix Committed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962185 Title: Add ConnectX7 support and bug fixes to Jammy Status in linux package in Ubuntu: In Progress Status in rdma-core package in Ubuntu: Fix Committed Bug description: [Impact] Add support for NDR (next data rate) in IB MAD. This speed is supported From ConnectX7 onwards. And in addition user space support for NDR was extended. [Test Case] TBD [Regression Potential] TBD [Other Info] Feature patchset: (kernel v5.17-rc1) fbdb0ba7051e IB/mlx5: Expose NDR speed through MAD userspace (upstream rdma-core v39): eb7a7fb3 ibdiags: Extend support of NDR rates f6c49e79 verbs: Extend support of NDR rates 49c2d6e7 pyverbs: Extend support of NDR rates This list might not be full as i haven't ported the patches to Jammy yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958013] Re: System freeze during Shutdown, Restart, or Suspend
*** This bug is a duplicate of bug 1956467 *** https://bugs.launchpad.net/bugs/1956467 I'm not sure whether this report is a duplicate of #1956467. The symptoms described there seem to be slightly different, at least for suspend mode. Anyway, I hereby report that the problem seems to be solved in the kernel 5.13.0-30 for my system: AMD APU A8-7680, Ubuntu 20.04 LTS. I have not tested, however, any other kernels newer than 5.11.0-46. Thank you very much for your great work! Radek -- 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/1958013 Title: System freeze during Shutdown, Restart, or Suspend Status in linux-hwe-5.11 package in Ubuntu: Confirmed Bug description: Dear developers, My system freezes whenever I try to 1) shutdown, 2) restart, or 3) suspend it. System gets unresponsive (keyborad, mouse, network - ssh/ping from outside), screen turns black. However, non of the actions 1-3 gets finished, i.e. my system does not turn off, restart, or sleep. Hw reset needed after it. It is always reproducible and happens for kernels linux-image-5.11.0-41-generic and later. Does not happen for kernels linux-image-5.11.0-40-generic and earlier. Corresponding Journal sections (5.11.0-40 & 5.11.0-46) attached. Any other information or test you need, please let me know. Thank you! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: radek 1495 F pulseaudio /dev/snd/pcmC1D0p: radek 1495 F...m pulseaudio /dev/snd/controlC0: radek 1495 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap no_console_suspend quiet ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-46-generic N/A linux-backports-modules-5.11.0-46-generic N/A linux-firmware 1.187.25 RfKill: Tags: focal Uname: Linux 5.11.0-46-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 02/13/2019 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.20 dmi.board.name: FM2A68M-HD+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1958013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962185] Re: Add ConnectX7 support and bug fixes to Jammy
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1962185 Title: Add ConnectX7 support and bug fixes to Jammy Status in linux package in Ubuntu: New Bug description: [Impact] Add support for NDR (next data rate) in IB MAD. This speed is supported From ConnectX7 onwards. And in addition user space support for NDR was extended. [Test Case] TBD [Regression Potential] TBD [Other Info] Feature patchset: (kernel v5.17-rc1) fbdb0ba7051e IB/mlx5: Expose NDR speed through MAD userspace (upstream rdma-core v39): eb7a7fb3 ibdiags: Extend support of NDR rates f6c49e79 verbs: Extend support of NDR rates 49c2d6e7 pyverbs: Extend support of NDR rates This list might not be full as i haven't ported the patches to Jammy yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962185] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1962185 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962185 Title: Add ConnectX7 support and bug fixes to Jammy Status in linux package in Ubuntu: New Bug description: [Impact] Add support for NDR (next data rate) in IB MAD. This speed is supported From ConnectX7 onwards. And in addition user space support for NDR was extended. [Test Case] TBD [Regression Potential] TBD [Other Info] Feature patchset: (kernel v5.17-rc1) fbdb0ba7051e IB/mlx5: Expose NDR speed through MAD userspace (upstream rdma-core v39): eb7a7fb3 ibdiags: Extend support of NDR rates f6c49e79 verbs: Extend support of NDR rates 49c2d6e7 pyverbs: Extend support of NDR rates This list might not be full as i haven't ported the patches to Jammy yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962185] [NEW] Add ConnectX7 support and bug fixes to Jammy
Public bug reported: [Impact] Add support for NDR (next data rate) in IB MAD. This speed is supported From ConnectX7 onwards. And in addition user space support for NDR was extended. [Test Case] TBD [Regression Potential] TBD [Other Info] Feature patchset: (kernel v5.17-rc1) fbdb0ba7051e IB/mlx5: Expose NDR speed through MAD userspace (upstream rdma-core v39): eb7a7fb3 ibdiags: Extend support of NDR rates f6c49e79 verbs: Extend support of NDR rates 49c2d6e7 pyverbs: Extend support of NDR rates This list might not be full as i haven't ported the patches to Jammy yet. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962185 Title: Add ConnectX7 support and bug fixes to Jammy Status in linux package in Ubuntu: New Bug description: [Impact] Add support for NDR (next data rate) in IB MAD. This speed is supported From ConnectX7 onwards. And in addition user space support for NDR was extended. [Test Case] TBD [Regression Potential] TBD [Other Info] Feature patchset: (kernel v5.17-rc1) fbdb0ba7051e IB/mlx5: Expose NDR speed through MAD userspace (upstream rdma-core v39): eb7a7fb3 ibdiags: Extend support of NDR rates f6c49e79 verbs: Extend support of NDR rates 49c2d6e7 pyverbs: Extend support of NDR rates This list might not be full as i haven't ported the patches to Jammy yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962180] [NEW] Samba performance degraded after last update
Public bug reported: Hi, Updating my RPI4 this week SMB performances dropped from consistent >=100MB/s to 60-70MB/s. Not much were updated recently, it may comes from the kernel 5.13.0-1016-raspi (a guess). At this time I'm fully updated but the last kernel 1017 seems not active yet (flash-kernel not triggered) even if present on the /boot Does it ring a bell? #Version info .-/+oooo+/-. root@babylon `:+ss+:` -+ssyy+- OS: Ubuntu 21.10 aarch64 .ossdMMMNyo. Host: Raspberry Pi 4 Model B Rev 1.4 /ssshdmmNNmmyNhss/ Kernel: 5.13.0-1016-raspi +shmydMMMNy+ Uptime: 41 mins /hNMMMyhhhmNMMMNh/Packages: 1860 (dpkg), 10 (snap) .dMMMNhsshNMMMd. Shell: bash 5.1.8 +hhhyNMMNyyNMMMysss+ Resolution: 1920x1080 ossyNMMMNyMMhsshmmmhssso WM: Mutter ossyNMMMNyMMhsshmmmhssso WM Theme: Adwaita +hhhyNMMNyyNMMMysss+ Theme: Adwaita [GTK3] .dMMMNhsshNMMMd. Icons: Adwaita [GTK3] /hNMMMyhhhdNMMMNh/Terminal: gnome-terminal +sdmydy+ CPU: BCM2835 (4) @ 1.800GHz /ssshdmmyNhss/ Memory: 1504MiB / 7808MiB .ossdMMMNyo. -+syyy+- `:+ss+:` .-/+oooo+/-. #The /boot content /boot total 51679 drwxr-xr-x 5 root root 4096 Feb 22 08:18 ./ drwxr-xr-x 20 root root 4096 Jun 28 2021 ../ -rw-r--r-- 1 root root 241429 Jan 20 09:09 config-5.13.0-1016-raspi -rw-r--r-- 1 root root 241429 Feb 9 10:01 config-5.13.0-1017-raspi lrwxrwxrwx 1 root root 44 Feb 22 08:13 dtb -> dtbs/5.13.0-1017-raspi/./bcm2711-rpi-4-b.dtb* lrwxrwxrwx 1 root root 44 Feb 16 08:12 dtb-5.13.0-1016-raspi -> dtbs/5.13.0-1016-raspi/./bcm2711-rpi-4-b.dtb* lrwxrwxrwx 1 root root 44 Feb 22 08:13 dtb-5.13.0-1017-raspi -> dtbs/5.13.0-1017-raspi/./bcm2711-rpi-4-b.dtb* drwxr-xr-x 17 root root 4096 Feb 22 08:13 dtbs/ drwxr-xr-x 5 root root 7168 Jan 1 1970 firmware/ drwxr-xr-x 2 root root 4096 Jun 24 2021 grub/ lrwxrwxrwx 1 root root 28 Feb 22 08:12 initrd.img -> initrd.img-5.13.0-1017-raspi -rw-r--r-- 1 root root 11583918 Feb 16 08:11 initrd.img-5.13.0-1016-raspi -rw-r--r-- 1 root root 11593765 Feb 22 08:13 initrd.img-5.13.0-1017-raspi lrwxrwxrwx 1 root root 28 Feb 22 08:12 initrd.img.old -> initrd.img-5.13.0-1016-raspi -rw--- 1 root root 5114984 Jan 20 09:09 System.map-5.13.0-1016-raspi -rw--- 1 root root 5115142 Feb 9 10:01 System.map-5.13.0-1017-raspi lrwxrwxrwx 1 root root 25 Feb 22 08:12 vmlinuz -> vmlinuz-5.13.0-1017-raspi -rw--- 1 root root 9498568 Jan 20 09:09 vmlinuz-5.13.0-1016-raspi -rw--- 1 root root 9497818 Feb 9 10:01 vmlinuz-5.13.0-1017-raspi lrwxrwxrwx 1 root root 25 Feb 22 08:12 vmlinuz.old -> vmlinuz-5.13.0-1016-raspi #Recently installed grep "install " /var/log/dpkg.log 2022-02-02 08:02:32 install linux-raspi-headers-5.13.0-1016:arm64 5.13.0-1016.18 2022-02-02 08:02:48 install linux-headers-5.13.0-1016-raspi:arm64 5.13.0-1016.18 2022-02-02 08:02:53 install linux-modules-5.13.0-1016-raspi:arm64 5.13.0-1016.18 2022-02-02 08:02:59 install linux-image-5.13.0-1016-raspi:arm64 5.13.0-1016.18 2022-02-16 08:09:44 install libqt5sql5:arm64 5.15.2+dfsg-12ubuntu1.1 2022-02-16 08:09:44 install libqt5sql5-sqlite:arm64 5.15.2+dfsg-12ubuntu1.1 2022-02-22 08:11:28 install linux-raspi-headers-5.13.0-1017:arm64 5.13.0-1017.19 2022-02-22 08:11:43 install linux-headers-5.13.0-1017-raspi:arm64 5.13.0-1017.19 2022-02-22 08:11:48 install linux-modules-5.13.0-1017-raspi:arm64 5.13.0-1017.19 2022-02-22 08:11:54 install linux-image-5.13.0-1017-raspi:arm64 5.13.0-1017.19 ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1962180 Title: Samba performance degraded after last update Status in linux-raspi package in Ubuntu: New Bug description: Hi, Updating my RPI4 this week SMB performances dropped from consistent >=100MB/s to 60-70MB/s. Not much were updated recently, it may comes from the kernel 5.13.0-1016-raspi (a guess). At this time I'm fully updated but the last kernel 1017 seems not active yet (flash-kernel not triggered) even if present on the /boot Does it ring a bell? #Version info .-/+oooo+/-. root@babylon `:+ss+:` -+ssyy+-
[Kernel-packages] [Bug 1945289] Re: Failed to properly resume from S3 (suspend-to-ram) on kernel version 5.13.0-16 (installed while updating to impish), amdgpu driver.
I'm experiencing the same issue with kernels: 5.13.0-28-generic, 5.13.0-30-generic. GPU AMD ATI 03:00.0 Lucienne However, it doesn't occur with kernel 5.13.0-27-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1945289 Title: Failed to properly resume from S3 (suspend-to-ram) on kernel version 5.13.0-16 (installed while updating to impish), amdgpu driver. Status in linux-meta package in Ubuntu: Confirmed Bug description: On 5.11.0 everything is OK. The GPU is AMD Carrizo APU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1945289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933179] Comment bridged from LTC Bugzilla
--- Comment From janis.schoetterl-glau...@ibm.com 2022-02-24 07:29 EDT--- Am I looking at the wrong thing? https://git.launchpad.net/~fheimes/+git/lp1933179/commit/?h=master-next=1e2aeba3bda1e4ab7e91487ac1df29f1e3767adc Those lines are superfluous: +/x86_64/amx_test +/x86_64/cpuid_test Similarly the cap patch pulls in unrelated caps. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933179 Title: [22.04 FEAT] KVM: Enable storage key checking for intercepted instruction handled by userspace Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: KVM uses lazy storage key enablement as Linux does no longer make use of the storage keys. When the guest enters keyed mode, then KVM will save/restore the key during paging, provide change/reference tracking for guest and host and for all interpreted instructions will do key protection. If an instruction is intercepted and passed along to userspace (like QEMU) no storage key protection is checked, though. This is in violation of the architecture and it can result in misbehaving guests that rely on key protection for all instructions. This item will improve the MEMOP ioctl to also add key checking. In case of a key protection the right fault is injected in the guest. Value: Interoperability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962152] Re: failed to build Intel IPU6 camera driver against linux-unstable 5.17
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-unstable in Ubuntu. https://bugs.launchpad.net/bugs/1962152 Title: failed to build Intel IPU6 camera driver against linux-unstable 5.17 Status in linux-unstable package in Ubuntu: New Bug description: In commit 3c8c15391481 ("media: v4l: async: Rename async nf functions, clean up long lines"), functions *v4l2_async_notifier_* had been renamed to *v4l2_async_nf_*. In commit 16b0314aa746 ("dma-buf: move dma-buf symbols into the DMA_BUF module namespace") needs the proper MODULE_IMPORT_NS(DMA_BUF) line for those who use dma-buf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-unstable/+bug/1962152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962162] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962162 Title: Suspend/Resume/Reboot fails with 5.15 Kernel Status in linux package in Ubuntu: Confirmed Bug description: Suspend/Resume and don't seem to work with the shipped 5.15 Kernel. When rebooting or shutting down the system gets stuck at "Reached Target: System Poweroff" or "Reboot". Installing the mainline kernel 5.16.11 fixes this issue and the system is able to properly shutdown/reboot and suspend. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 24 12:53:52 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) MachineType: Micro-Star International Co., Ltd. MS-7D29 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_m9rbzq@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_m9rbzq ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220217.git6342082c-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.24 dmi.board.asset.tag: Default string dmi.board.name: MEG Z690I UNIFY (MS-7D29) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.24:bd01/21/2022:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D29:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGZ690IUNIFY(MS-7D29):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D29 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962162] [NEW] Suspend/Resume/Reboot fails with 5.15 Kernel
Public bug reported: Suspend/Resume and don't seem to work with the shipped 5.15 Kernel. When rebooting or shutting down the system gets stuck at "Reached Target: System Poweroff" or "Reboot". Installing the mainline kernel 5.16.11 fixes this issue and the system is able to properly shutdown/reboot and suspend. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 24 12:53:52 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) MachineType: Micro-Star International Co., Ltd. MS-7D29 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_m9rbzq@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_m9rbzq ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220217.git6342082c-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.24 dmi.board.asset.tag: Default string dmi.board.name: MEG Z690I UNIFY (MS-7D29) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.24:bd01/21/2022:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D29:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGZ690IUNIFY(MS-7D29):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D29 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962162 Title: Suspend/Resume/Reboot fails with 5.15 Kernel Status in linux package in Ubuntu: New Bug description: Suspend/Resume and don't seem to work with the shipped 5.15 Kernel. When rebooting or shutting down the system gets stuck at "Reached Target: System Poweroff" or "Reboot". Installing the mainline kernel 5.16.11 fixes this issue and the system is able to properly shutdown/reboot and suspend. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 24 12:53:52 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) MachineType: Micro-Star International Co., Ltd. MS-7D29 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_m9rbzq@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_m9rbzq ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220217.git6342082c-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.24 dmi.board.asset.tag: Default string dmi.board.name: MEG Z690I UNIFY (MS-7D29) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias:
[Kernel-packages] [Bug 1933179] Re: [22.04 FEAT] KVM: Enable storage key checking for intercepted instruction handled by userspace
Yes, that's already incl. in the pull request that I've mentioned in the comment above ... and with that also incl. in the test kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933179 Title: [22.04 FEAT] KVM: Enable storage key checking for intercepted instruction handled by userspace Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: KVM uses lazy storage key enablement as Linux does no longer make use of the storage keys. When the guest enters keyed mode, then KVM will save/restore the key during paging, provide change/reference tracking for guest and host and for all interpreted instructions will do key protection. If an instruction is intercepted and passed along to userspace (like QEMU) no storage key protection is checked, though. This is in violation of the architecture and it can result in misbehaving guests that rely on key protection for all instructions. This item will improve the MEMOP ioctl to also add key checking. In case of a key protection the right fault is injected in the guest. Value: Interoperability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952006] Re: [TGL][ADL] ACRN hypervisor support
This bug is awaiting verification that the linux-intel- iotg-5.15/5.15.0-1002.4~20.04.2 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952006 Title: [TGL][ADL] ACRN hypervisor support Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] The driver enables the host to run ACRN hypervisor which is a flexible, lightweight reference hypervisor, built with real-time and safety-criticality in mind, optimized to streamline embedded development through an open-source platform. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable ACRN hypervisor [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel TigerLake/AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929895] Re: [EHL] Enable ISHTP
This bug is awaiting verification that the linux-intel- iotg-5.15/5.15.0-1002.4~20.04.2 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929895 Title: [EHL] Enable ISHTP Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description This driver enables the OS to talk to eclite firmware on a dedicated low power chip over ISH Transport Protocol (ISHTP) Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952007] Re: [ADL] ITBM support for Hybrid platforms
This bug is awaiting verification that the linux-intel- iotg-5.15/5.15.0-1002.4~20.04.2 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952007 Title: [ADL] ITBM support for Hybrid platforms Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] Need ITBM support for Hybrid platforms. Need to change the scheduling order from Core, HT, ATOM to Core, ATOM, HT. When using ITBM on systems that has a mixture of CPUs supporting Hyper-Threading and others not supporting it (even offlining HT siblings may cause the issue to be reproducible). Hybrid topologies meet the aforementioned condition. In such cases, threads will be consolidated on CPUs of high priority using got HT siblings, while CPUs of medium priority will remain idle. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable AlderLake [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952356] Re: [EHL][TGL][ADL] PMU support
This bug is awaiting verification that the linux-intel- iotg-5.15/5.15.0-1002.4~20.04.2 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952356 Title: [EHL][TGL][ADL] PMU support Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] The patches enable PMU support [Fix] Intel provides a list of patches to provide Linux perf supports [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel ElkhartLake/TigerLake/AdlerLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952356/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
This bug is awaiting verification that the linux/5.13.0-32.35 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-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. 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-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/1937295 Title: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU Status in subiquity: Invalid Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] A hardware partner discovered they were unable to install Ubuntu on some servers using VROC setups. They point to this issue involving DMAR that is blocking discovery of the VROC RAID devices: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2565e5b69c44b4e42469afea3cc5a97e74d1ed45 `git bisect` points to this offending commit ee81ee84f873 ("PCI: vmd: Disable MSI-X remapping when possible"), which disables VMD MSI remapping. The IOMMU hardware blocks the compatibility format interrupt request because Interrupt Remapping Enable Status (IRES) and Extended Interrupt Mode Enable (EIME) are enabled. Please refer to section "5.1.4 Interrupt-Remapping Hardware Operation" in Intel VT-d spec. To fix the issue, VMD driver still enables the interrupt remapping irrespective of VMD_FEAT_CAN_BYPASS_MSI_REMAP if the IOMMU subsystem enables the interrupt remapping. [Fix] 2565e5b69c44 PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU [Test Plan] 1. Boot into VRoC controller in uEFI Setup and create a raid10 disk. 2. Install affected Ubuntu release on the RAID10. 3. The system hangs at "Partitions formatting 33%". [Where problems could occur] The fix itself is a very small change to drivers/pci/controller/vmd.c and problems should not occur. The root cause was discovered by the hardware partner's engineers, who tested and submitted it upstream where it was accepted and landed in 5.16. That said, I doubt this will fix 18.04.6 as it would require a respin to get the patched kernel onto the ISO. 20.04 should pick it up in ISO in 20.04.5, so there could still be the initial issue since those ISOs would be lacking the patched kernel. [Other Info] As noted, this would need to not only land in the kernel but land in the kernel in the ISO to resolve the issue in the installation process. I'll bring this back as far as Focal with the expectation that while 20.04.4 is too late, it will be present using the GA kernel in 20.04.5 later on. * Original Bug Summary: A hardware partner has been testing 18.04 subiquity images on their servers with VROC enabled and configured in a RAID 10 setup. In their own words: Steps to reproduce: 1. Boot into VRoC controller in uEFI Setup and create a raid10 disk. 2. Install Ubuntu 18.04.5 on the RAID10. 3. The system hangs at "Partitions formatting 33%". After looking at the launchpad (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/), the fix was included in the updated kernel. [Quotes from the launchpad] The released kernels are: Hirsute: 5.11.0-22-generic Groovy: 5.8.0-59-generic Focal: 5.4.0-77-generic Bionic: 4.15.0-147-generic I've asked them to also confirm this on 20.04.2, and check that 20.04.3 dailies fix the issue. It is at least a very reasonable hypothesis that this will also break on all current ISO installs as none of them are respun once released to include updated SRUs in the installation media. This currently affects 20.04.2 but that will be resolved shortly when 20.04.3 releases as the GA and HWE kernels in that image should have the SRU that fixes this issue. However, 18.04 has no further releases, and even the 18.04.5 daily-live and daily images on cdimages.ubuntu.com are not built after 18.04.5 was released. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937295/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1954676] Re: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x
This bug is awaiting verification that the linux/5.13.0-32.35 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-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. 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-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/1954676 Title: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x Status in Ubuntu on IBM z Systems: Fix Committed Status in gcc-11 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in gcc-11 source package in Impish: New Status in linux source package in Impish: Fix Committed Status in gcc-11 source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. This seems to happen only when zfs is compile with gcc >= 11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show the problem and zfs is working just fine. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Temporary workaround is to build zfs with gcc-10 on s390x. [Regression potential] Building a kernel module with a different compiler is never 100% safe, we may experience potential crashes / panics if the ABI is not compatible. Moreover, if we build zfs with gcc-10 we are going to lose some of the performance benefits provided by gcc-11. However these regressions are limited to zfs on s390x and without this change zfs is broken anyway on this architecture. [Further analysis] @IBM Issue report to zfs upstream at https://github.com/openzfs/zfs/issues/12942 Reverting https://gcc.gnu.org/git/?p=gcc.git;a=patch;h=2335aa8771acd06b082d3e15d9f21ae0a802afd7 appears to make everything work, the compiled kernel and zfs.ko are loadable/unloadable once again. Please bring this issue to the attention of Ilya Leoshkevich Potentially this means we may have missbuilt userspace binaries in the archive for s390x. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1954676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960182] Re: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7
This bug is awaiting verification that the linux/5.13.0-32.35 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-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. 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-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/1960182 Title: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: Fix CPU-MF error on new IBM Z Hardware by adding support for CPU-MF counter second version 7 Error Symptom: Daemon cpacfstatsd fails on start up of the system with this error message cpacfstatsd: Event DEA_FUNCTIONS for pmu cpum_cf not found (2:No such file or directory) Problem: When the CPU Measurement facility device driver is initialized during kernel boot, it reads out the CPU Measurement facility counter hardware first and second version numbers. Depending on these numbers the device driver exports attributes in the sysfs directory /sys/devices/cpum_cf/events. When the CPM-MF second version number is not known, no attributes of the crypto counter set are exported. However the cpacfstatsd program scans the sysfs directory /sys/devices/cpum_cf/events for attribute files of the crypto counter set, for example attribute file DEA_FUNCTIONS and others. Solution: Add support for the new CPU-MF Measurement counter facility second version number 7. This number then exports the crypto counter set in directory directory /sys/devices/cpum_cf/events. Also add support for limited samples. These hardware samples contain all zeroes and are of no value when using the CPU Measurement Facility sampling hardware. Drop these samples when the limited sampled bit is set in the sample descriptor. Reproduction: Run command ls -l /sys/devices/cpum_cf/events | fgrep DEA DEA_BLOCKED_CYCLES DEA_BLOCKED_FUNCTIONS DEA_CYCLES DEA_FUNCTIONS When there is no output at all the attributes files for the crypto counter set have not been exported. If above output is visible, the described problem does not show up. Upstream-ID: a87b0fd4f9003f8521226e226cf92b18147b3519 745f5d20e7936931f924410f32d8b0e599b5990e Problem-ID:196017 Preventive:yes Reported: Christian Rund SupportTicket: - Reference: - Date: 2022-01-20 Author:Thomas Richter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960875] Re: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call
This bug is awaiting verification that the linux/5.13.0-32.35 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-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. 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-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/1960875 Title: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: Description: s390/cio: verify the driver availability for path_event call Symptom: If no driver is attached to a device or the driver does not provide the path_event function, an FCES path-event on this device could end up in a kernel-panic. Problem: There can be path-event generated for devices which are not bound to any drivers. And this is not verified before callback. Solution: Make sure the driver is available before the callback. Reproduction: - Upstream-ID: dd9cb842fa9d90653a9b48aba52f89c069f3bc50 Problem-ID:196414 Distros: Ubuntu 21.10 and higher Preventive:yes Reported: - SupportTicket: - Reference: - Date: 2022-02-14 Author:Vineeth Vijayan Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961968] Re: Broken network on some AWS instances with focal/impish kernels
This bug is awaiting verification that the linux/5.13.0-32.35 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-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. 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-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/1961968 Title: Broken network on some AWS instances with focal/impish kernels Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] With the latest focal/linux (5.4.0-101.114) and impish/linux (5.13.0-31.34) kernels built for SRU cycle 2022.02.21 some AWS instances fail to boot. This impacts mostly the instance types: c4.large, c3.xlarge and x1e.xlarge. However, not all instances deployed on those types will fail. This is affecting mostly c4.large which fails about 80-90% of all deployments. This was traced to be caused by the network interface failing to come up. The following console log snippets from 5.4.0-101-generic on a c4.large show some hints of what's going on: [...] [3.990368] unchecked MSR access error: RDMSR from 0xc90 at rIP: 0x8ea733c8 (native_read_msr+0x8/0x40) [3.998463] Call Trace: [4.001164] ? set_rdt_options+0x91/0x91 [4.004864] resctrl_late_init+0x592/0x63c [4.008711] ? set_rdt_options+0x91/0x91 [4.012452] do_one_initcall+0x4a/0x200 [4.016115] kernel_init_freeable+0x1c0/0x263 [4.020402] ? rest_init+0xb0/0xb0 [4.024889] kernel_init+0xe/0x110 [4.029245] ret_from_fork+0x35/0x40 [...] [7.718268] ena: The ena device sent a completion but the driver didn't receive a MSI-X interrupt (cmd 8), autopolling mode is OFF [7.727036] ena: Failed to submit get_feature command 12 error: -62 [7.731691] ena :00:03.0: Cannot init indirect table [7.735636] ena :00:03.0: Cannot init RSS rc: -62 [7.740700] ena: probe of :00:03.0 failed with error -62 [...] [Fix] Reverting the following upstream stable commit fixes the issue: 83dbf898a2d4 PCI/MSI: Mask MSI-X vectors only on success [Test Case] Boot an affected AWS instance type with focal/linux (5.4.0-101.114) and impish/linux (5.13.0-31.34) kernels with the mentioned patch reverted. Then boot with the original kernels. It should boot successfully with the reverted patch but fail with the original kernels. [Regression Potential] The patch description mentions fixing a MSI-X issue with a Marvell NVME device, which doesn't seem to be following the PCI-E specification. Reverting this commit will keep the issue on systems with that particular NVME device unfixed. As of now there is no follow-up fix for this commit upstream, we might need to keep an eye on any change and re-apply it in case a fix is found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962152] Re: failed to build Intel IPU6 camera driver against linux-unstable 5.17
** Patch added: "0002-UBUNTU-SAUCE-IPU6-import-dma-buf-symbols.patch" https://bugs.launchpad.net/ubuntu/+source/linux-unstable/+bug/1962152/+attachment/5563422/+files/0002-UBUNTU-SAUCE-IPU6-import-dma-buf-symbols.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-unstable in Ubuntu. https://bugs.launchpad.net/bugs/1962152 Title: failed to build Intel IPU6 camera driver against linux-unstable 5.17 Status in linux-unstable package in Ubuntu: New Bug description: In commit 3c8c15391481 ("media: v4l: async: Rename async nf functions, clean up long lines"), functions *v4l2_async_notifier_* had been renamed to *v4l2_async_nf_*. In commit 16b0314aa746 ("dma-buf: move dma-buf symbols into the DMA_BUF module namespace") needs the proper MODULE_IMPORT_NS(DMA_BUF) line for those who use dma-buf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-unstable/+bug/1962152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962152] Re: failed to build Intel IPU6 camera driver against linux-unstable 5.17
** Description changed: In commit 3c8c15391481 ("media: v4l: async: Rename async nf functions, clean up long lines"), functions *v4l2_async_notifier_* had been renamed to *v4l2_async_nf_*. + + In commit 16b0314aa746 ("dma-buf: move dma-buf symbols into the DMA_BUF + module namespace") needs the proper MODULE_IMPORT_NS(DMA_BUF) line for + those who use dma-buf. ** Patch added: "0001-UBUNTU-SAUCE-IPU6-fix-build-against-v5.16.patch" https://bugs.launchpad.net/ubuntu/+source/linux-unstable/+bug/1962152/+attachment/5563421/+files/0001-UBUNTU-SAUCE-IPU6-fix-build-against-v5.16.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-unstable in Ubuntu. https://bugs.launchpad.net/bugs/1962152 Title: failed to build Intel IPU6 camera driver against linux-unstable 5.17 Status in linux-unstable package in Ubuntu: New Bug description: In commit 3c8c15391481 ("media: v4l: async: Rename async nf functions, clean up long lines"), functions *v4l2_async_notifier_* had been renamed to *v4l2_async_nf_*. In commit 16b0314aa746 ("dma-buf: move dma-buf symbols into the DMA_BUF module namespace") needs the proper MODULE_IMPORT_NS(DMA_BUF) line for those who use dma-buf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-unstable/+bug/1962152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959345] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1959345/+attachment/5563419/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959345 Title: vulkaninfo reports error Status in linux package in Ubuntu: Incomplete Bug description: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gary 12435 F pulseaudio /dev/snd/controlC2: gary 12435 F pulseaudio /dev/snd/controlC0: gary 12435 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c InstallationDate: Installed on 2020-02-14 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE 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 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 RelatedPackageVersions: linux-restricted-modules-5.4.0-99-generic N/A linux-backports-modules-5.4.0-99-generic N/A linux-firmware1.173.20 RfKill: Tags: bionic Uname: Linux 5.4.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F63d dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B450 MB dmi.product.name: B450 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959345] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1959345/+attachment/5563418/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959345 Title: vulkaninfo reports error Status in linux package in Ubuntu: Incomplete Bug description: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gary 12435 F pulseaudio /dev/snd/controlC2: gary 12435 F pulseaudio /dev/snd/controlC0: gary 12435 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c InstallationDate: Installed on 2020-02-14 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE 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 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 RelatedPackageVersions: linux-restricted-modules-5.4.0-99-generic N/A linux-backports-modules-5.4.0-99-generic N/A linux-firmware1.173.20 RfKill: Tags: bionic Uname: Linux 5.4.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F63d dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B450 MB dmi.product.name: B450 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959345] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1959345/+attachment/5563415/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959345 Title: vulkaninfo reports error Status in linux package in Ubuntu: Incomplete Bug description: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gary 12435 F pulseaudio /dev/snd/controlC2: gary 12435 F pulseaudio /dev/snd/controlC0: gary 12435 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c InstallationDate: Installed on 2020-02-14 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE 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 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 RelatedPackageVersions: linux-restricted-modules-5.4.0-99-generic N/A linux-backports-modules-5.4.0-99-generic N/A linux-firmware1.173.20 RfKill: Tags: bionic Uname: Linux 5.4.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F63d dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B450 MB dmi.product.name: B450 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959345] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1959345/+attachment/5563417/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959345 Title: vulkaninfo reports error Status in linux package in Ubuntu: Incomplete Bug description: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gary 12435 F pulseaudio /dev/snd/controlC2: gary 12435 F pulseaudio /dev/snd/controlC0: gary 12435 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c InstallationDate: Installed on 2020-02-14 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE 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 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 RelatedPackageVersions: linux-restricted-modules-5.4.0-99-generic N/A linux-backports-modules-5.4.0-99-generic N/A linux-firmware1.173.20 RfKill: Tags: bionic Uname: Linux 5.4.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F63d dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B450 MB dmi.product.name: B450 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959345] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1959345/+attachment/5563412/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959345 Title: vulkaninfo reports error Status in linux package in Ubuntu: Incomplete Bug description: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gary 12435 F pulseaudio /dev/snd/controlC2: gary 12435 F pulseaudio /dev/snd/controlC0: gary 12435 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c InstallationDate: Installed on 2020-02-14 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE 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 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 RelatedPackageVersions: linux-restricted-modules-5.4.0-99-generic N/A linux-backports-modules-5.4.0-99-generic N/A linux-firmware1.173.20 RfKill: Tags: bionic Uname: Linux 5.4.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F63d dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B450 MB dmi.product.name: B450 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959345] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1959345/+attachment/5563414/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959345 Title: vulkaninfo reports error Status in linux package in Ubuntu: Incomplete Bug description: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gary 12435 F pulseaudio /dev/snd/controlC2: gary 12435 F pulseaudio /dev/snd/controlC0: gary 12435 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c InstallationDate: Installed on 2020-02-14 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE 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 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 RelatedPackageVersions: linux-restricted-modules-5.4.0-99-generic N/A linux-backports-modules-5.4.0-99-generic N/A linux-firmware1.173.20 RfKill: Tags: bionic Uname: Linux 5.4.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F63d dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B450 MB dmi.product.name: B450 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959345] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1959345/+attachment/5563413/+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/1959345 Title: vulkaninfo reports error Status in linux package in Ubuntu: Incomplete Bug description: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gary 12435 F pulseaudio /dev/snd/controlC2: gary 12435 F pulseaudio /dev/snd/controlC0: gary 12435 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c InstallationDate: Installed on 2020-02-14 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE 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 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 RelatedPackageVersions: linux-restricted-modules-5.4.0-99-generic N/A linux-backports-modules-5.4.0-99-generic N/A linux-firmware1.173.20 RfKill: Tags: bionic Uname: Linux 5.4.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F63d dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B450 MB dmi.product.name: B450 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959345] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1959345/+attachment/5563410/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959345 Title: vulkaninfo reports error Status in linux package in Ubuntu: Incomplete Bug description: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gary 12435 F pulseaudio /dev/snd/controlC2: gary 12435 F pulseaudio /dev/snd/controlC0: gary 12435 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c InstallationDate: Installed on 2020-02-14 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE 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 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 RelatedPackageVersions: linux-restricted-modules-5.4.0-99-generic N/A linux-backports-modules-5.4.0-99-generic N/A linux-firmware1.173.20 RfKill: Tags: bionic Uname: Linux 5.4.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F63d dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B450 MB dmi.product.name: B450 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933179] Comment bridged from LTC Bugzilla
--- Comment From janis.schoetterl-glau...@ibm.com 2022-02-24 04:54 EDT--- You only need the s390 specific lines for the two conflicts, i.e. +/s390x/tprot and +#define KVM_CAP_S390_MEM_OP_EXTENSION 210 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933179 Title: [22.04 FEAT] KVM: Enable storage key checking for intercepted instruction handled by userspace Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: KVM uses lazy storage key enablement as Linux does no longer make use of the storage keys. When the guest enters keyed mode, then KVM will save/restore the key during paging, provide change/reference tracking for guest and host and for all interpreted instructions will do key protection. If an instruction is intercepted and passed along to userspace (like QEMU) no storage key protection is checked, though. This is in violation of the architecture and it can result in misbehaving guests that rely on key protection for all instructions. This item will improve the MEMOP ioctl to also add key checking. In case of a key protection the right fault is injected in the guest. Value: Interoperability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959345] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1959345/+attachment/5563409/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959345 Title: vulkaninfo reports error Status in linux package in Ubuntu: Incomplete Bug description: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gary 12435 F pulseaudio /dev/snd/controlC2: gary 12435 F pulseaudio /dev/snd/controlC0: gary 12435 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c InstallationDate: Installed on 2020-02-14 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE 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 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 RelatedPackageVersions: linux-restricted-modules-5.4.0-99-generic N/A linux-backports-modules-5.4.0-99-generic N/A linux-firmware1.173.20 RfKill: Tags: bionic Uname: Linux 5.4.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F63d dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B450 MB dmi.product.name: B450 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959345] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1959345/+attachment/5563416/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959345 Title: vulkaninfo reports error Status in linux package in Ubuntu: Incomplete Bug description: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gary 12435 F pulseaudio /dev/snd/controlC2: gary 12435 F pulseaudio /dev/snd/controlC0: gary 12435 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c InstallationDate: Installed on 2020-02-14 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE 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 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 RelatedPackageVersions: linux-restricted-modules-5.4.0-99-generic N/A linux-backports-modules-5.4.0-99-generic N/A linux-firmware1.173.20 RfKill: Tags: bionic Uname: Linux 5.4.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F63d dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B450 MB dmi.product.name: B450 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959345] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1959345/+attachment/5563411/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959345 Title: vulkaninfo reports error Status in linux package in Ubuntu: Incomplete Bug description: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gary 12435 F pulseaudio /dev/snd/controlC2: gary 12435 F pulseaudio /dev/snd/controlC0: gary 12435 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c InstallationDate: Installed on 2020-02-14 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE 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 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 RelatedPackageVersions: linux-restricted-modules-5.4.0-99-generic N/A linux-backports-modules-5.4.0-99-generic N/A linux-firmware1.173.20 RfKill: Tags: bionic Uname: Linux 5.4.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F63d dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B450 MB dmi.product.name: B450 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959345] Re: vulkaninfo reports error
apport information ** Tags added: apport-collected bionic ** Description changed: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ - Either the error is a false positive or I should have amd_icd64.json - - and then maybe all the other problems with the GPU would go away! + Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.27 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: gary 12435 F pulseaudio + /dev/snd/controlC2: gary 12435 F pulseaudio + /dev/snd/controlC0: gary 12435 F pulseaudio + CurrentDesktop: GNOME + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c + InstallationDate: Installed on 2020-02-14 (740 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE + 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 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-99-generic N/A + linux-backports-modules-5.4.0-99-generic N/A + linux-firmware1.173.20 + RfKill: + + Tags: bionic + Uname: Linux 5.4.0-99-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/13/2021 + dmi.bios.vendor: American Megatrends International, LLC. + dmi.bios.version: F63d + dmi.board.asset.tag: Default string + dmi.board.name: B450 AORUS ELITE + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: Default string + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: + dmi.product.family: B450 MB + dmi.product.name: B450 AORUS ELITE + dmi.product.sku: Default string + dmi.product.version: Default string + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1959345/+attachment/5563408/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959345 Title: vulkaninfo reports error Status in linux package in Ubuntu: Incomplete Bug description: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gary 12435 F pulseaudio /dev/snd/controlC2: gary 12435 F pulseaudio /dev/snd/controlC0: gary 12435 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c InstallationDate: Installed on 2020-02-14 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE Package: linux (not installed) ProcEnviron: TERM=xterm-256color
[Kernel-packages] [Bug 1962155] Re: bnx2x: Add FW 7.13.21.0
** Description changed: [Impact] * There is new version of bnx2x firmware * oem-5.14 and hwe-5.15 kernels use that one; and when not found fallback to previous version of firmware. [Test Plan] * sudo apt install initramfs-tools * echo bnx2x | sudo tee -a /etc/initramfs-tools/modules * sudo apt install linux-oem-20.04 linux-generic-hwe-20.04-edge With current linux-firmware the above results in: update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic W: Possible missing firmware /lib/firmware/bnx2x/bnx2x-e2-7.13.21.0.fw for module bnx2x W: Possible missing firmware /lib/firmware/bnx2x/bnx2x-e1h-7.13.21.0.fw for module bnx2x W: Possible missing firmware /lib/firmware/bnx2x/bnx2x-e1-7.13.21.0.fw for module bnx2x with updated linux-firmware no lines of "Possible missing firmware" should appear. [Where problems could occur] * v21 firmware version is backwards compatible with v15 firmware previously used, but includes bugfixes. It may result in different NIC behavior. [Other Info] * The v21 firmware is already present in Jammy - * The kernels that use v21 firmware are not going to be shipped in Impish - * The kernels that use v21 firmware will be available/used in Focal + * The kernels that use v21 firmware are not going to be shipped in Impish + * The kernels that use v21 firmware will be available/used in Focal + + Upstream changelog for the blobs: + + New firmware v7.13.21.0 along with below fixes/enhancements (which + were also part of 7.13.20.0) maintains backward compatibility as well, + so that driver can be worked with both the new firmware and an older + firmware. + + - Support direct invalidation of FP HSI Ver per function ID, required for + invalidating FP HSI Ver prior to each VF start, as there is no VF start + - BRB parity error detection support for the driver + - Fix the FCOE underrun flow + - Fix PSOD during FCoE BFS over the NIC ports after preboot driver -- 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/1962155 Title: bnx2x: Add FW 7.13.21.0 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Triaged Status in linux-firmware source package in Impish: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Bug description: [Impact] * There is new version of bnx2x firmware * oem-5.14 and hwe-5.15 kernels use that one; and when not found fallback to previous version of firmware. [Test Plan] * sudo apt install initramfs-tools * echo bnx2x | sudo tee -a /etc/initramfs-tools/modules * sudo apt install linux-oem-20.04 linux-generic-hwe-20.04-edge With current linux-firmware the above results in: update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic W: Possible missing firmware /lib/firmware/bnx2x/bnx2x-e2-7.13.21.0.fw for module bnx2x W: Possible missing firmware /lib/firmware/bnx2x/bnx2x-e1h-7.13.21.0.fw for module bnx2x W: Possible missing firmware /lib/firmware/bnx2x/bnx2x-e1-7.13.21.0.fw for module bnx2x with updated linux-firmware no lines of "Possible missing firmware" should appear. [Where problems could occur] * v21 firmware version is backwards compatible with v15 firmware previously used, but includes bugfixes. It may result in different NIC behavior. [Other Info] * The v21 firmware is already present in Jammy * The kernels that use v21 firmware are not going to be shipped in Impish * The kernels that use v21 firmware will be available/used in Focal Upstream changelog for the blobs: New firmware v7.13.21.0 along with below fixes/enhancements (which were also part of 7.13.20.0) maintains backward compatibility as well, so that driver can be worked with both the new firmware and an older firmware. - Support direct invalidation of FP HSI Ver per function ID, required for invalidating FP HSI Ver prior to each VF start, as there is no VF start - BRB parity error detection support for the driver - Fix the FCOE underrun flow - Fix PSOD during FCoE BFS over the NIC ports after preboot driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1962155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962155] [NEW] bnx2x: Add FW 7.13.21.0
Public bug reported: [Impact] * There is new version of bnx2x firmware * oem-5.14 and hwe-5.15 kernels use that one; and when not found fallback to previous version of firmware. [Test Plan] * sudo apt install initramfs-tools * echo bnx2x | sudo tee -a /etc/initramfs-tools/modules * sudo apt install linux-oem-20.04 linux-generic-hwe-20.04-edge With current linux-firmware the above results in: update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic W: Possible missing firmware /lib/firmware/bnx2x/bnx2x-e2-7.13.21.0.fw for module bnx2x W: Possible missing firmware /lib/firmware/bnx2x/bnx2x-e1h-7.13.21.0.fw for module bnx2x W: Possible missing firmware /lib/firmware/bnx2x/bnx2x-e1-7.13.21.0.fw for module bnx2x with updated linux-firmware no lines of "Possible missing firmware" should appear. [Where problems could occur] * v21 firmware version is backwards compatible with v15 firmware previously used, but includes bugfixes. It may result in different NIC behavior. [Other Info] * The v21 firmware is already present in Jammy * The kernels that use v21 firmware are not going to be shipped in Impish * The kernels that use v21 firmware will be available/used in Focal ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: Triaged ** Affects: linux-firmware (Ubuntu Impish) Importance: Undecided Status: Won't Fix ** Affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: Fix Released ** Also affects: linux-firmware (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Description changed: [Impact] - * There is new version of bnx2x firmware + * There is new version of bnx2x firmware - * oem-5.14 and hwe-5.15 kernels use that one; and when not found + * oem-5.14 and hwe-5.15 kernels use that one; and when not found fallback to previous version of firmware. [Test Plan] - * sudo apt install initramfs-tools - * echo bnx2x | sudo tee -a /etc/initramfs-tools/modules - * sudo apt install linux-oem-20.04 linux-generic-hwe-20.04-edge + * sudo apt install initramfs-tools + * echo bnx2x | sudo tee -a /etc/initramfs-tools/modules + * sudo apt install linux-oem-20.04 linux-generic-hwe-20.04-edge With current linux-firmware the above results in: update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic W: Possible missing firmware /lib/firmware/bnx2x/bnx2x-e2-7.13.21.0.fw for module bnx2x W: Possible missing firmware /lib/firmware/bnx2x/bnx2x-e1h-7.13.21.0.fw for module bnx2x W: Possible missing firmware /lib/firmware/bnx2x/bnx2x-e1-7.13.21.0.fw for module bnx2x with updated linux-firmware no lines of "Possible missing firmware" should appear. [Where problems could occur] - * v21 firmware version is backwards compatible with v15 firmware + * v21 firmware version is backwards compatible with v15 firmware previously used, but includes bugfixes. It may result in different NIC behavior. [Other Info] - - * The v21 firmware is already present in Jammy + + * The v21 firmware is already present in Jammy + * The kernels that use v21 firmware are not going to be shipped in Impish + * The kernels that use v21 firmware will be available/used in Focal ** Changed in: linux-firmware (Ubuntu Impish) Status: New => Won't Fix ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-firmware (Ubuntu Focal) Status: New => Triaged -- 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/1962155 Title: bnx2x: Add FW 7.13.21.0 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Triaged Status in linux-firmware source package in Impish: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Bug description: [Impact] * There is new version of bnx2x firmware * oem-5.14 and hwe-5.15 kernels use that one; and when not found fallback to previous version of firmware. [Test Plan] * sudo apt install initramfs-tools * echo bnx2x | sudo tee -a /etc/initramfs-tools/modules * sudo apt install linux-oem-20.04 linux-generic-hwe-20.04-edge With current linux-firmware the above results in: update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic W: Possible missing firmware /lib/firmware/bnx2x/bnx2x-e2-7.13.21.0.fw for module bnx2x W: Possible missing firmware /lib/firmware/bnx2x/bnx2x-e1h-7.13.21.0.fw for module bnx2x W: Possible missing firmware /lib/firmware/bnx2x/bnx2x-e1-7.13.21.0.fw for module
[Kernel-packages] [Bug 1933179] Re: [22.04 FEAT] KVM: Enable storage key checking for intercepted instruction handled by userspace
Pull request submitted to kernel team's mailing list: https://lists.ubuntu.com/archives/kernel-team/2022-February/thread.html#128293 changing status to 'In Progress'. A test build was done here: https://launchpad.net/~fheimes/+archive/ubuntu/lp1933179/ ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: ubuntu-z-systems Status: Incomplete => In Progress ** Information type changed from Private to Public ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933179 Title: [22.04 FEAT] KVM: Enable storage key checking for intercepted instruction handled by userspace Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: KVM uses lazy storage key enablement as Linux does no longer make use of the storage keys. When the guest enters keyed mode, then KVM will save/restore the key during paging, provide change/reference tracking for guest and host and for all interpreted instructions will do key protection. If an instruction is intercepted and passed along to userspace (like QEMU) no storage key protection is checked, though. This is in violation of the architecture and it can result in misbehaving guests that rely on key protection for all instructions. This item will improve the MEMOP ioctl to also add key checking. In case of a key protection the right fault is injected in the guest. Value: Interoperability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962152] [NEW] failed to build Intel IPU6 camera driver against linux-unstable 5.17
Public bug reported: In commit 3c8c15391481 ("media: v4l: async: Rename async nf functions, clean up long lines"), functions *v4l2_async_notifier_* had been renamed to *v4l2_async_nf_*. ** Affects: linux-unstable (Ubuntu) Importance: Undecided Status: New ** Tags: hwe-media ihv-intel ** Attachment added: "build.log" https://bugs.launchpad.net/bugs/1962152/+attachment/5563404/+files/build.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-unstable in Ubuntu. https://bugs.launchpad.net/bugs/1962152 Title: failed to build Intel IPU6 camera driver against linux-unstable 5.17 Status in linux-unstable package in Ubuntu: New Bug description: In commit 3c8c15391481 ("media: v4l: async: Rename async nf functions, clean up long lines"), functions *v4l2_async_notifier_* had been renamed to *v4l2_async_nf_*. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-unstable/+bug/1962152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962143] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1962143 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962143 Title: [Ubuntu 22.04] "TSC calibration failed" is shown in dmesg Status in linux package in Ubuntu: Incomplete Bug description: When booting into RHEL9.0, the "TSC calibration failed" message is shown in dmesg. [0.00] kernel: tsc: Fast TSC calibration failed The issue was fixed by upstream series c7719e793478 and b50db7095fe0. I've tested the series, and the test passed. commit c7719e79347803b8e3b6b50da8c6db410a3012b5 Author: Feng Tang Date: Wed Nov 17 10:37:50 2021 +0800 x86/tsc: Add a timer to make sure TSC_adjust is always checked commit b50db7095fe002fa3e16605546cba66bf1b68a3e Author: Feng Tang Date: Wed Nov 17 10:37:51 2021 +0800 x86/tsc: Disable clocksource watchdog for TSC on qualified platorms Please consider to include the series in 22.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962143] [NEW] [Ubuntu 22.04] "TSC calibration failed" is shown in dmesg
Public bug reported: When booting into RHEL9.0, the "TSC calibration failed" message is shown in dmesg. [0.00] kernel: tsc: Fast TSC calibration failed The issue was fixed by upstream series c7719e793478 and b50db7095fe0. I've tested the series, and the test passed. commit c7719e79347803b8e3b6b50da8c6db410a3012b5 Author: Feng Tang Date: Wed Nov 17 10:37:50 2021 +0800 x86/tsc: Add a timer to make sure TSC_adjust is always checked commit b50db7095fe002fa3e16605546cba66bf1b68a3e Author: Feng Tang Date: Wed Nov 17 10:37:51 2021 +0800 x86/tsc: Disable clocksource watchdog for TSC on qualified platorms Please consider to include the series in 22.04. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/1962143/+attachment/5563344/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962143 Title: [Ubuntu 22.04] "TSC calibration failed" is shown in dmesg Status in linux package in Ubuntu: New Bug description: When booting into RHEL9.0, the "TSC calibration failed" message is shown in dmesg. [0.00] kernel: tsc: Fast TSC calibration failed The issue was fixed by upstream series c7719e793478 and b50db7095fe0. I've tested the series, and the test passed. commit c7719e79347803b8e3b6b50da8c6db410a3012b5 Author: Feng Tang Date: Wed Nov 17 10:37:50 2021 +0800 x86/tsc: Add a timer to make sure TSC_adjust is always checked commit b50db7095fe002fa3e16605546cba66bf1b68a3e Author: Feng Tang Date: Wed Nov 17 10:37:51 2021 +0800 x86/tsc: Disable clocksource watchdog for TSC on qualified platorms Please consider to include the series in 22.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp