[Kernel-packages] [Bug 1915071] Re: [MIR] kdump-tools
kdump-tools (1:1.6.8.2) unstable; urgency=medium * debian/control: Add Vcs-* tags. * Support compressing the core file at dump time (Closes: #856960). Thanks to Benjamin Drung! * kdump-config: Allow running in an initrd, thanks to Benjamin Drung. -- dann frazier Mon, 01 Feb 2021 13:35:59 -0700 ** Changed in: kdump-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kdump-tools in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/1915071 Title: [MIR] kdump-tools Status in kdump-tools package in Ubuntu: Fix Released Bug description: kdump-tools was split out of makedumpfile into its own source package in Debian. Since this is source that was already in main, I'd like to request that kdump-tools also be included in main. I'm submitting this "lightweight" MIR per https://wiki.ubuntu.com/MainInclusionProcess: "If a new source package contains only code which is already in main (e.g., the result of a source package split or rename, or source packages with a version in the name), it may not need a full review. Submitting a bug with an explanation is sufficient." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1915071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
** Tags added: oem-priority -- 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/1962349 Title: Bolt doesn't work with native USB4 hosts Status in bolt package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-oem-5.14 package in Ubuntu: Invalid Status in bolt source package in Focal: In Progress Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Triaged Status in bolt source package in Impish: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released Status in linux source package in Jammy: Triaged Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. * There haven't been any significant bugs reported upstream or in Ubuntu since 0.9.1 release. [Other Info] * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. * It is fixed in bolt 0.9.1 or later release. * To solve the SRU, will backport 0.9.1 release from Impish. * I did look into backporting just the commit(s) for fixing this, but it's not a trivial backport. Quoting the changelog (https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): "Additionally the unique_id of said host controller changes with every boot, which breaks one of the fundamental assumptions in boltd". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1962349/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964560] Re: file transfers have trouble finishing
Flash drives are usually very slow devices. Next time a transfer has trouble finishing please open a Terminal window and run: sync If the command returns immediately then this is a Nautilus bug. If the command does not return until the file transfer finishes then this is either a kernel bug or just the slowness of the flash drive. ** Package changed: wayland (Ubuntu) => nautilus (Ubuntu) ** Tags added: impish ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: nautilus (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/1964560 Title: file transfers have trouble finishing Status in linux package in Ubuntu: Incomplete Status in nautilus package in Ubuntu: Incomplete Bug description: Ubuntu 21.10 with wayland windowing system sits on completed file transfers on and off usb and takes its time realising its finished and closing the little transfer progress logo. running an HP elitedesk 800 G1 SFF with 16gb ram, i5 4690 cpu and an HD 4600 onboard graphics card. It's either the linux system or old flash drives causing it. Don't think its the circuit boards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
Hi Vicamo, Please let us know if you are able to pick the V5 driver patches already on top of Backported V4 changeset. Please let us know if any additional help is needed. Thanks and Best Regards, Murali -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 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.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964414] 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 1964414 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/1964414 Title: wifi disconnecting when i use bluetooth Status in linux package in Ubuntu: Incomplete Bug description: My network interface is the Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter and the driver is the ath9k. I've had this problem years before and I solved it by updating the kernel, but this time the problem came with the update. What happens: when I use my bluetooth headphones, the wifi connection is extremely slow, unusable. I turn off bluetooth and it works again quickly. When it started: Earlier today when I updated the system and the package was replaced. I send the update history below. 2022-03-08 18:08:32 upgrade linux-generic-hwe-20.04:amd64 5.13.0.30.33~20.04.17 5.13.0.35.40~20.04.20 2022-03-08 18:08:32 upgrade linux-image-generic-hwe-20.04:amd64 5.13.0.30.33~20.04.17 5.13.0.35.40~20.04.20 2022-03-08 18:08:36 upgrade linux-headers-generic-hwe-20.04:amd64 5.13.0.30.33~20.04.17 5.13.0.35.40~20.04.20 2022-03-08 18:08:36 upgrade linux-libc-dev:amd64 5.4.0-100.113 5.4.0-104.118 I didn't want to manually install another kernel version. Is it possible to go back to the previous version? It was working really well. What can I do? Well, thank you very much in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964542] Re: [nvidia] One monitor fails to wake after resuming from sleep
Thanks for the bug report. Next time the problem happens please immediately run: journalctl -b0 > journal.txt and attach the resulting text file here. ** Summary changed: - monitor not recognized displayport + [nvidia] One monitor fails to wake after resuming from sleep ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-470 (Ubuntu) ** Tags added: multimonitor nvidia ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1964542 Title: [nvidia] One monitor fails to wake after resuming from sleep Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: when the pc starts up or comes out of sleep mode the primary screen remains black. To reactivate it I have to go through screen clone apply and redo join the screens and apply. Thanks Ps: have done several research and attempt, without success, on the internet including in your forums. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 18:45:17 2022 DistUpgraded: 2022-02-23 17:47:37,810 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu DkmsStatus: nvidia, 470.103.01, 5.13.0-32-generic, x86_64: installed nvidia, 470.103.01, 5.13.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM206 [GeForce GTX 960] [3842:2966] InstallationDate: Installed on 2022-02-15 (23 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS All Series ProcEnviron: LANGUAGE=fr_CA:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=c8e08c76-0308-495c-8c5a-83f9aa24b1a0 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2022-02-23 (15 days ago) dmi.bios.date: 07/10/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4101:bd07/10/2019:br5.11:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/nvidia-graphics-drivers-470/+bug/1964542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-azure/5.13.0.1018.18)
All autopkgtests for the newly accepted linux-meta-azure (5.13.0.1018.18) for impish have finished running. The following regressions have been reported in tests triggered by the package: systemd/248.3-1ubuntu8.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/impish/update_excuses.html#linux-meta-azure [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 1964542] [NEW] [nvidia] One monitor fails to wake after resuming from sleep
You have been subscribed to a public bug: when the pc starts up or comes out of sleep mode the primary screen remains black. To reactivate it I have to go through screen clone apply and redo join the screens and apply. Thanks Ps: have done several research and attempt, without success, on the internet including in your forums. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 18:45:17 2022 DistUpgraded: 2022-02-23 17:47:37,810 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu DkmsStatus: nvidia, 470.103.01, 5.13.0-32-generic, x86_64: installed nvidia, 470.103.01, 5.13.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM206 [GeForce GTX 960] [3842:2966] InstallationDate: Installed on 2022-02-15 (23 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS All Series ProcEnviron: LANGUAGE=fr_CA:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=c8e08c76-0308-495c-8c5a-83f9aa24b1a0 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2022-02-23 (15 days ago) dmi.bios.date: 07/10/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4101:bd07/10/2019:br5.11:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages ubuntu -- [nvidia] One monitor fails to wake after resuming from sleep https://bugs.launchpad.net/bugs/1964542 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964414] Re: wifi disconnecting when i use bluetooth
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964414 Title: wifi disconnecting when i use bluetooth Status in linux package in Ubuntu: New Bug description: My network interface is the Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter and the driver is the ath9k. I've had this problem years before and I solved it by updating the kernel, but this time the problem came with the update. What happens: when I use my bluetooth headphones, the wifi connection is extremely slow, unusable. I turn off bluetooth and it works again quickly. When it started: Earlier today when I updated the system and the package was replaced. I send the update history below. 2022-03-08 18:08:32 upgrade linux-generic-hwe-20.04:amd64 5.13.0.30.33~20.04.17 5.13.0.35.40~20.04.20 2022-03-08 18:08:32 upgrade linux-image-generic-hwe-20.04:amd64 5.13.0.30.33~20.04.17 5.13.0.35.40~20.04.20 2022-03-08 18:08:36 upgrade linux-headers-generic-hwe-20.04:amd64 5.13.0.30.33~20.04.17 5.13.0.35.40~20.04.20 2022-03-08 18:08:36 upgrade linux-libc-dev:amd64 5.4.0-100.113 5.4.0-104.118 I didn't want to manually install another kernel version. Is it possible to go back to the previous version? It was working really well. What can I do? Well, thank you very much in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964414] [NEW] wifi disconnecting when i use bluetooth
You have been subscribed to a public bug: My network interface is the Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter and the driver is the ath9k. I've had this problem years before and I solved it by updating the kernel, but this time the problem came with the update. What happens: when I use my bluetooth headphones, the wifi connection is extremely slow, unusable. I turn off bluetooth and it works again quickly. When it started: Earlier today when I updated the system and the package was replaced. I send the update history below. 2022-03-08 18:08:32 upgrade linux-generic-hwe-20.04:amd64 5.13.0.30.33~20.04.17 5.13.0.35.40~20.04.20 2022-03-08 18:08:32 upgrade linux-image-generic-hwe-20.04:amd64 5.13.0.30.33~20.04.17 5.13.0.35.40~20.04.20 2022-03-08 18:08:36 upgrade linux-headers-generic-hwe-20.04:amd64 5.13.0.30.33~20.04.17 5.13.0.35.40~20.04.20 2022-03-08 18:08:36 upgrade linux-libc-dev:amd64 5.4.0-100.113 5.4.0-104.118 I didn't want to manually install another kernel version. Is it possible to go back to the previous version? It was working really well. What can I do? Well, thank you very much in advance. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- wifi disconnecting when i use bluetooth https://bugs.launchpad.net/bugs/1964414 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964537] 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 1964537 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/1964537 Title: Synaptics touchpad not detected on HP Laptop Model 17-cn0078cl Status in linux package in Ubuntu: Incomplete Bug description: 1. Laptop: HP Laptop Model 17-cn0078cl 2. Touchpad: Synaptics 3. When first appeared: 3/9/22 at initial load of Linux Mint 20.3 4. lsb_release -rd Description: Linux Mint 20.3 Release: 20.3 5. Expected: touchpad to work 6. What actually happened: nothing, no response from the touchpad (usb mouse works ok though) 7. cat version.log Ubuntu 5.4.0-104.118-generic 5.4.166 8. cat devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:01/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input5 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=2 20 0 0 1500f0210 3803078f900d401 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=046d Product=4091 Version=0111 N: Name="Logitech Wireless Mouse" P: Phys=usb-:00:14.0-1/input1:2 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C534.0002/0003:046D:4091.0003/input/input16 U: Uniq=4091-00-00-00-00 H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY= 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="HP Wireless hotkeys" P: Phys=hpq6001/input0 S: Sysfs=/devices/virtual/input/input17 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="HP WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input18 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=33 B: KEY=40 0 10007 2102400 0 0 B: MSC=10 B: SW=20 I: Bus=0003 Vendor=04f2 Product=b710 Version=2747 N: Name="HP TrueVision HD Camera: HP Tru" P: Phys=usb-:00:14.0-5/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input19 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="sof-hda-dsp Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input20 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="sof-hda-dsp Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input21 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964537/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964537] Re: Synaptics touchpad not detected on HP Laptop Model 17-cn0078cl
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964537 Title: Synaptics touchpad not detected on HP Laptop Model 17-cn0078cl Status in linux package in Ubuntu: New Bug description: 1. Laptop: HP Laptop Model 17-cn0078cl 2. Touchpad: Synaptics 3. When first appeared: 3/9/22 at initial load of Linux Mint 20.3 4. lsb_release -rd Description: Linux Mint 20.3 Release: 20.3 5. Expected: touchpad to work 6. What actually happened: nothing, no response from the touchpad (usb mouse works ok though) 7. cat version.log Ubuntu 5.4.0-104.118-generic 5.4.166 8. cat devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:01/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input5 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=2 20 0 0 1500f0210 3803078f900d401 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=046d Product=4091 Version=0111 N: Name="Logitech Wireless Mouse" P: Phys=usb-:00:14.0-1/input1:2 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C534.0002/0003:046D:4091.0003/input/input16 U: Uniq=4091-00-00-00-00 H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY= 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="HP Wireless hotkeys" P: Phys=hpq6001/input0 S: Sysfs=/devices/virtual/input/input17 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="HP WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input18 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=33 B: KEY=40 0 10007 2102400 0 0 B: MSC=10 B: SW=20 I: Bus=0003 Vendor=04f2 Product=b710 Version=2747 N: Name="HP TrueVision HD Camera: HP Tru" P: Phys=usb-:00:14.0-5/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input19 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="sof-hda-dsp Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input20 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="sof-hda-dsp Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input21 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964537/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964537] [NEW] Synaptics touchpad not detected on HP Laptop Model 17-cn0078cl
You have been subscribed to a public bug: 1. Laptop: HP Laptop Model 17-cn0078cl 2. Touchpad: Synaptics 3. When first appeared: 3/9/22 at initial load of Linux Mint 20.3 4. lsb_release -rd Description: Linux Mint 20.3 Release: 20.3 5. Expected: touchpad to work 6. What actually happened: nothing, no response from the touchpad (usb mouse works ok though) 7. cat version.log Ubuntu 5.4.0-104.118-generic 5.4.166 8. cat devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:01/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input5 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=2 20 0 0 1500f0210 3803078f900d401 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=046d Product=4091 Version=0111 N: Name="Logitech Wireless Mouse" P: Phys=usb-:00:14.0-1/input1:2 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C534.0002/0003:046D:4091.0003/input/input16 U: Uniq=4091-00-00-00-00 H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY= 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="HP Wireless hotkeys" P: Phys=hpq6001/input0 S: Sysfs=/devices/virtual/input/input17 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="HP WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input18 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=33 B: KEY=40 0 10007 2102400 0 0 B: MSC=10 B: SW=20 I: Bus=0003 Vendor=04f2 Product=b710 Version=2747 N: Name="HP TrueVision HD Camera: HP Tru" P: Phys=usb-:00:14.0-5/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input19 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="sof-hda-dsp Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input20 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="sof-hda-dsp Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input21 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=4 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Synaptics touchpad not detected on HP Laptop Model 17-cn0078cl https://bugs.launchpad.net/bugs/1964537 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964440] Re: 5.15.0-22: No console displayed on EFI systems
See also bug 1964305 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems Status in linux package in Ubuntu: Confirmed Bug description: DISCLAIMER: This is my second-ever bug report. Apologies in advance for any missing or inaccurate info. I am willing to troubleshoot and supply more/better info as needed. PROBLEM DESCRIPTION: After upgrading the kernel on my Ubuntu 22.04 Server test system from 5.15.0-18 to 5.15.0-22, I see absolutely no console output on my display past the grub menu. I can give the system a few seconds to finish booting, log in blindly and watch the activity LEDs on e.g. the network interface as i run a ping or similar. I can also log in remotely via SSH, and/or use a serial console. So the system definitely does boot. But my actual display/screen shows no console output. ENVIRONMENT: (Output gathered via SSH while display was showing no output) testuser@testserver:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy testuser@testserver:~$ uname -a Linux testserver 5.15.0-22-generic #22-Ubuntu SMP Tue Feb 8 10:16:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This was initially discovered on an Ubuntu Server VM running in EFI mode on VirtualBox 6.1.32. System was installed with the daily 'jammy-live-server-amd64.iso' image from 2022-03-07, fully upgraded as of 2022-03-10. Switching Graphics Controller in Virtualbox does not help, nor does 'nomodeset' or 'noacpi'. I am able to reproduce the issue on real hardware and with different physical graphics cards. Similar symptoms can also be observed in Ubuntu Desktop (still using EFI) by attempting to switch to tty with CTRL + ALT + F[3-6], or by taking note of the missing plymouth screen during boot. Systems installed/booted in legacy BIOS mode (both Server and Desktop) do not appear to be affected. I have tried reinstalling on both virtual and hardware platforms, with same result before and after upgrading the kernel. HOW TO REPRODUCE - Ubuntu Server: - Boot existing Ubuntu Server EFI installation with 5.15.0-18 and observe console output - Set GRUB_TIMEOUT_STYLE=menu and GRUB_TIMEOUT=10 in /etc/default/grub (to enable rollback) - Run update-grub - Run sudo apt full-upgrade and watch linux version 5.15.0-22 get installed - Reboot and observe your display (no console output will be shown after grub) HOW TO REPRODUCE - Ubuntu Desktop: - Download Ubuntu 22.04 Desktop daily ISO - Write ISO to USB - Boot from USB in EFI mode - Install system - Run sudo apt full-upgrade and upgrade linux* to kernel 5.15.0-22 - Reboot and observe missing plymouth screen during boot - Wait for graphical login screen to appear - Press CTRL + ALT + F[3-6] (screen will go black and/or freeze) - Press CTRL + ALT + F1 (screen will unfreeze and/or return to gdm greeter) WORKAROUNDS: If you still have 5.15.0-18 or earlier installed, select it in Grub. and/or install mainline kernel 5.16.11+ (for testing only - will not work if you have Secure Boot enabled). Alternatively, re-install/convert/boot your system to boot in legacy BIOS mode. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220307) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=8fe50fbe-79d7-47a9-ad2f-ff36ddc1fe54 ro ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 RelatedPackageVersions:
[Kernel-packages] [Bug 1963614] Re: mt7921e device disappear after warm boot stress
Test 1.187.29 on WVB4-DVT2-A2, BIOS 1.2.0, can pass 50 times reboot stress. 1. enable proposed 2. $ sudo apt install linux-firmware 3. $ sudo add-apt-repository ppa:checkbox-dev/ppa 4. $ sudo apt install checkbox-ng plainbox-provider-checkbox 5. $ sudo /usr/lib/plainbox-provider-checkbox/bin/pm_test.py -r 50 reboot Wi-Fi works normally after 50 times reboot. ** Tags removed: verification-failed-focal ** Tags added: verification-done-focal -- 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/1963614 Title: mt7921e device disappear after warm boot stress Status in HWE Next: New Status in OEM Priority Project: New 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 Jammy: Fix Released Bug description: [SRU Justification] [Impact] mt7921e may not appear in the bus enumeration during warm boot stress tests. [Fix] This can only be fixed in the firmware. [Test Case] Run checkbox reboot stress tests to try trigger this issue: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] While this backports proprietary fw blob, it may bring driver compatibility issues we cannot know in the first place. Jammy has these already, so only Focal (for oem-5.14) is nominated. We don't have mt7921e hardware v2.1 support in Impish 5.13 kernel. == original bug report == [Summary] mt7921 wlan device disappear after warm reset, can be recovered by cold boot. [Reproduce Steps] 1. do warm boot stress 100 times 2. check wifi function after stress finished 3. wifi has no function and mt7921e device disappeared [Results] Expected: wifi works normally Actual: wifi broken To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1963614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961300] Re: linux-azure: Fix NUMA node assignment when kernel boots with custom NUMA topology
This bug is awaiting verification that the linux-azure/5.13.0-1018.20
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-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1961300
Title:
linux-azure: Fix NUMA node assignment when kernel boots with custom
NUMA topology
Status in linux-azure package in Ubuntu:
Fix Committed
Status in linux-hwe-5.11 package in Ubuntu:
Invalid
Status in linux-azure source package in Focal:
Fix Committed
Status in linux-hwe-5.11 source package in Focal:
In Progress
Status in linux-azure source package in Impish:
Fix Committed
Status in linux-hwe-5.11 source package in Impish:
Invalid
Status in linux-azure source package in Jammy:
Fix Committed
Status in linux-hwe-5.11 source package in Jammy:
Invalid
Bug description:
SRU Justification
[Impact]
When kernel boots with a NUMA topology with some NUMA nodes offline, the PCI
driver should only set an online NUMA node on the device. This can happen
during KDUMP where some NUMA nodes are not made online by the KDUMP kernel.
This patch also fixes the case where kernel is booting with "numa=off".
Fixes: 999dd956d838 ("PCI: hv: Add support for protocol 1.3 and
support PCI_BUS_RELATIONS2")
[Test Case]
Microsoft tested.
[Where things could go wrong]
NUMA node assignments could be wrong.
[Other Info]
SF: #00323281
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1961300/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922523] Re: package nvidia-dkms-390 390.141-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exi
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1922523 Title: package nvidia-dkms-390 390.141-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Upon startup after a routine software update, my desktop was limited to 640×480 resolution, making the desktop UI unusable. Switching graphics drivers didn't help. Downgrading the kernel from linux-image-5.11.0-7612-generic to linux- image-5.8.0-7642-generic via Grub after restart solved the problem, at least temporarily. After the "fix" (reversion to old kernel): $ uname -a Linux flying-gazelle 5.8.0-7642-generic #47~1614007149~20.10~82fb226~dev-Ubuntu SMP Wed Feb 24 15:29:29 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 $ apt-cache policy nvidia-dkms-390 nvidia-dkms-390: Installed: 390.141-0ubuntu0.20.10.1 Candidate: 390.141-0ubuntu0.20.10.1 Version table: *** 390.141-0ubuntu0.20.10.1 500 500 http://us.archive.ubuntu.com/ubuntu groovy-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu groovy-security/restricted amd64 Packages 100 /var/lib/dpkg/status 390.138-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu groovy/restricted amd64 Packages ProblemType: Package DistroRelease: Ubuntu 20.10 Package: nvidia-dkms-390 390.141-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.11.0-7612.13~1617215757~20.10~97a8d1a~dev-generic 5.11.7 Uname: Linux 5.11.0-7612-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Apr 4 08:52:31 2021 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2016-09-24 (1652 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.2 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.141-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1922523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964531] 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/1964531 Title: Touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: My touchpad on this hp laptop is not working or being detected while executing the command "cat /proc/bus/input/devices" Description: Ubuntu 20.04.4 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-104-generic 5.4.0-104.118 ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166 Uname: Linux 5.4.0-104-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: klas 1401 F pulseaudio CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 21:54:53 2022 InstallationDate: Installed on 2022-03-09 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223.1) MachineType: HP HP ProBook 640 G8 Notebook PC ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-104-generic root=UUID=8e56aa93-1741-4ffb-b3d2-0a2a2142afc6 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-104-generic N/A linux-backports-modules-5.4.0-104-generic N/A linux-firmware 1.187.27 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2021 dmi.bios.vendor: HP dmi.bios.version: T74 Ver. 01.07.02 dmi.board.name: 87ED dmi.board.vendor: HP dmi.board.version: KBC Version 33.14.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrT74Ver.01.07.02:bd11/25/2021:svnHP:pnHPProBook640G8NotebookPC:pvr:rvnHP:rn87ED:rvrKBCVersion33.14.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 640 G8 Notebook PC dmi.product.sku: 3S8S9EA#UUW dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964531] [NEW] Touchpad not detected
Public bug reported: My touchpad on this hp laptop is not working or being detected while executing the command "cat /proc/bus/input/devices" Description:Ubuntu 20.04.4 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-104-generic 5.4.0-104.118 ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166 Uname: Linux 5.4.0-104-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: klas 1401 F pulseaudio CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 21:54:53 2022 InstallationDate: Installed on 2022-03-09 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223.1) MachineType: HP HP ProBook 640 G8 Notebook PC ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-104-generic root=UUID=8e56aa93-1741-4ffb-b3d2-0a2a2142afc6 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-104-generic N/A linux-backports-modules-5.4.0-104-generic N/A linux-firmware 1.187.27 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2021 dmi.bios.vendor: HP dmi.bios.version: T74 Ver. 01.07.02 dmi.board.name: 87ED dmi.board.vendor: HP dmi.board.version: KBC Version 33.14.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrT74Ver.01.07.02:bd11/25/2021:svnHP:pnHPProBook640G8NotebookPC:pvr:rvnHP:rn87ED:rvrKBCVersion33.14.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 640 G8 Notebook PC dmi.product.sku: 3S8S9EA#UUW dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964531 Title: Touchpad not detected Status in linux package in Ubuntu: New Bug description: My touchpad on this hp laptop is not working or being detected while executing the command "cat /proc/bus/input/devices" Description: Ubuntu 20.04.4 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-104-generic 5.4.0-104.118 ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166 Uname: Linux 5.4.0-104-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: klas 1401 F pulseaudio CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 21:54:53 2022 InstallationDate: Installed on 2022-03-09 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223.1) MachineType: HP HP ProBook 640 G8 Notebook PC ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-104-generic root=UUID=8e56aa93-1741-4ffb-b3d2-0a2a2142afc6 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-104-generic N/A linux-backports-modules-5.4.0-104-generic N/A linux-firmware 1.187.27 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2021 dmi.bios.vendor: HP dmi.bios.version: T74 Ver. 01.07.02 dmi.board.name: 87ED dmi.board.vendor: HP dmi.board.version: KBC Version 33.14.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrT74Ver.01.07.02:bd11/25/2021:svnHP:pnHPProBook640G8NotebookPC:pvr:rvnHP:rn87ED:rvrKBCVersion33.14.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 640 G8 Notebook PC dmi.product.sku: 3S8S9EA#UUW dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32
Not a bug in the test. ** Changed in: linux (Ubuntu Hirsute) Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: kunpeng920 Status: New => In Progress ** Also affects: kunpeng920/ubuntu-18.04-hwe Importance: Undecided Status: New ** Also affects: kunpeng920/ubuntu-18.04 Importance: Undecided Status: New ** Also affects: kunpeng920/upstream-kernel Importance: Undecided Status: New ** Also affects: kunpeng920/ubuntu-20.04 Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Status: New => Invalid ** Changed in: kunpeng920/upstream-kernel Milestone: None => linux-v5.12 ** Changed in: kunpeng920/ubuntu-18.04 Status: New => In Progress ** Changed in: kunpeng920/ubuntu-18.04 Assignee: (unassigned) => dann frazier (dannf) ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: New => In Progress ** Changed in: kunpeng920/ubuntu-18.04-hwe Assignee: (unassigned) => dann frazier (dannf) ** Changed in: kunpeng920/ubuntu-20.04 Status: New => In Progress ** Changed in: kunpeng920/ubuntu-20.04 Assignee: (unassigned) => dann frazier (dannf) ** Changed in: kunpeng920/upstream-kernel Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951289 Title: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25 report incorrect sched domain for cpu#32 Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Released Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Won't Fix Bug description: On scobee-kernel(arm64) with hirsute:linux(5.11.0-41.45) for sru-20211108 there are several reports about the sched domain not covering the full range. The same does not happen on kuzzle. But 32 is a bit of a suspicious number. Running tests... cpuset_sched_domains 1 TINFO: CPUs are numbered continuously starting at 0 (0-127) cpuset_sched_domains 1 TINFO: Nodes are numbered continuously starting at 0 (0-3) cpuset_sched_domains 1 TINFO: root group load balance test cpuset_sched_domains 1 TINFO: sched load balance: 0 cpuset_sched_domains 1 TINFO: CPU hotplug: cpuset_check_domains1 TPASS : check_sched_domains passed cpuset_sched_domains 1 TPASS: partition sched domains succeeded. cpuset_sched_domains 3 TINFO: root group load balance test cpuset_sched_domains 3 TINFO: sched load balance: 1 cpuset_sched_domains 3 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). cpuset_sched_domains 3 TFAIL: partition sched domains failed. cpuset_sched_domains 5 TINFO: root group load balance test cpuset_sched_domains 5 TINFO: sched load balance: 0 cpuset_sched_domains 5 TINFO: CPU hotplug: cpuset_check_domains1 TPASS : check_sched_domains passed cpuset_sched_domains 5 TPASS: partition sched domains succeeded. cpuset_sched_domains 7 TINFO: root group load balance test cpuset_sched_domains 7 TINFO: sched load balance: 0 cpuset_sched_domains 7 TINFO: CPU hotplug: cpuset_check_domains1 TPASS : check_sched_domains passed cpuset_sched_domains 7 TPASS: partition sched domains succeeded. cpuset_sched_domains 9 TINFO: root group load balance test cpuset_sched_domains 9 TINFO: sched load balance: 1 cpuset_sched_domains 9 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). cpuset_sched_domains 9 TFAIL: partition sched domains failed. cpuset_sched_domains 11 TINFO: root group load balance test cpuset_sched_domains 11 TINFO: sched load balance: 1 cpuset_sched_domains 11 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). cpuset_sched_domains 11 TFAIL: partition sched domains failed.
[Kernel-packages] [Bug 1964527] [NEW] Enable CONFIG_UNICODE for linux-gcp
Public bug reported: See https://lists.ubuntu.com/archives/kernel-team/2022-March/128565.html NOTE: This config is enabled in other gcp kernels and in non-gcp kernels. ** Affects: linux-gcp (Ubuntu) Importance: Undecided Assignee: Khaled El Mously (kmously) Status: New ** Affects: linux-gcp (Ubuntu Focal) Importance: Undecided Assignee: Khaled El Mously (kmously) Status: New ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: klibc (Ubuntu) ** Also affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Focal) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1964527 Title: Enable CONFIG_UNICODE for linux-gcp Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: New Bug description: See https://lists.ubuntu.com/archives/kernel- team/2022-March/128565.html NOTE: This config is enabled in other gcp kernels and in non-gcp kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1964527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-hwe-5.13/5.13.0.36.41~20.04.21)
All autopkgtests for the newly accepted linux-meta-hwe-5.13 (5.13.0.36.41~20.04.21) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.15 (ppc64el, amd64, s390x) nvidia-graphics-drivers-340/340.108-0ubuntu5.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-hwe-5.13 [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 1964512] Re: Low RX performance for 40G Solarflare NICs
** Changed in: linux (Ubuntu Impish) Importance: Undecided => High ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Focal) 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/1964512 Title: Low RX performance for 40G Solarflare NICs Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] * Some 40G Solarflare NICs have low RX performance in some cases, due low RX recycle ring size * RX recycle ring size is either 4096 for IOMMU, 16 for NOIOMMU * The low fixed sizes can cause a high number of calls to alloc_pages, tanking performance for higher link speeds [Test Plan] * Users report that iperf3 is sufficient to showcase the bad RX performance * For some setups, RX performance was around 15Gbps while TX stayed consistently above 30Gbps [Fix] * This patch sets the RX recycle ring size according to an adapter's maximum link speed * Fix was introduced by commit: 000fe940e51f "sfc: The size of the RX recycle ring should be more flexible" * --!-- Commit is from net-next --!-- [Regression Potential] * Regressions would show primarily as performance issues, as we're effectively changing ring sizes for all RX traffic * It's possible to see increased calls to alloc_pages if ring sizes aren't being set correctly * We should look out for excessive memory usage in the sfc driver due to the increased ring sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964512/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964305] Re: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works)
Another possibly related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1964305 Title: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Steps to reproduce: 1. Boot Ubuntu. 2. Press Ctrl+Alt+F4. Expected: VT to be displayed Observed: Monitor turns off. Notes: * This failure only happens in 5.15.0-22-generic. Kernel version 5.15.0-18-generic works fine. * I am currently using the nvidia-470 driver in case that's relevant. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-22-generic 5.15.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Mar 9 14:33:12 2022 InstallationDate: Installed on 2021-11-05 (123 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964512] [NEW] Low RX performance for 40G Solarflare NICs
Public bug reported: [Impact] * Some 40G Solarflare NICs have low RX performance in some cases, due low RX recycle ring size * RX recycle ring size is either 4096 for IOMMU, 16 for NOIOMMU * The low fixed sizes can cause a high number of calls to alloc_pages, tanking performance for higher link speeds [Test Plan] * Users report that iperf3 is sufficient to showcase the bad RX performance * For some setups, RX performance was around 15Gbps while TX stayed consistently above 30Gbps [Fix] * This patch sets the RX recycle ring size according to an adapter's maximum link speed * Fix was introduced by commit: 000fe940e51f "sfc: The size of the RX recycle ring should be more flexible" * --!-- Commit is from net-next --!-- [Regression Potential] * Regressions would show primarily as performance issues, as we're effectively changing ring sizes for all RX traffic * It's possible to see increased calls to alloc_pages if ring sizes aren't being set correctly * We should look out for excessive memory usage in the sfc driver due to the increased ring sizes ** Affects: linux (Ubuntu) Importance: High Assignee: Heitor Alves de Siqueira (halves) Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: High Assignee: Heitor Alves de Siqueira (halves) Status: Confirmed ** Tags: sts ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: High Assignee: Heitor Alves de Siqueira (halves) Status: Confirmed ** Also affects: linux (Ubuntu Impish) 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/1964512 Title: Low RX performance for 40G Solarflare NICs Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: New Status in linux source package in Impish: New Status in linux source package in Jammy: Confirmed Bug description: [Impact] * Some 40G Solarflare NICs have low RX performance in some cases, due low RX recycle ring size * RX recycle ring size is either 4096 for IOMMU, 16 for NOIOMMU * The low fixed sizes can cause a high number of calls to alloc_pages, tanking performance for higher link speeds [Test Plan] * Users report that iperf3 is sufficient to showcase the bad RX performance * For some setups, RX performance was around 15Gbps while TX stayed consistently above 30Gbps [Fix] * This patch sets the RX recycle ring size according to an adapter's maximum link speed * Fix was introduced by commit: 000fe940e51f "sfc: The size of the RX recycle ring should be more flexible" * --!-- Commit is from net-next --!-- [Regression Potential] * Regressions would show primarily as performance issues, as we're effectively changing ring sizes for all RX traffic * It's possible to see increased calls to alloc_pages if ring sizes aren't being set correctly * We should look out for excessive memory usage in the sfc driver due to the increased ring sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964512/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956982] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04
test kernels can be found for now here: https://people.canonical.com/~jlane/kernels/1956982/ I've built those this morning as the patches have landed in the Jammy kernel tree but have yet to be built into the next binary due to delays in the kernel release. So for now, that should be sufficient to test, it's a straight build of the 5.15 tree as of this morning. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956982 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04 Status in linux package in Ubuntu: Fix Committed Bug description: Please integrate this customer critical/reported fix that was submitted as a stand along patch: Accepted 11/29/21: Applied to 5.16/scsi-fixes, thanks! [1/1] lpfc: Fix nonrecovery of remote ports following an unsolicited LOGO https://git.kernel.org/mkp/scsi/c/0956ba63bd94 As well as this latest set of bug fix patches accepted upstream 12/6/2021: scsi: lpfc: Fix leaked lpfc_dmabuf mbox allocations with NPIV commitf0d3919697492950f57a26a1093aee53880d669d scsi: lpfc: Change return code on I/Os received during link bounce commit2e81b1a374da5d6024208c16c4a5224a70cafa64 scsi: lpfc: Fix lpfc_force_rscn ndlp kref imbalance commit7576d48c64f36f6fea9df2882f710a474fa35f40 scsi: lpfc: Fix NPIV port deletion crash commit8ed190a91950564775cbaae9e8e8083a69a8da23 scsi: lpfc: Trigger SLI4 firmware dump before doing driver cleanup commit7dd2e2a923173d637c272e483966be8e96a72b64 scsi: lpfc: Adjust CMF total bytes and rxmonitor commita6269f837045acb02904f31f05acde847ec8f8a7 scsi: lpfc: Cap CMF read bytes to MBPI commit05116ef9c4b444f7fdbb56f9e13c2ec941726639 scsi: lpfc: Add additional debugfs support for CMF commit6014a2468f0e49194f612b1f09f99eacee0a409a scsi: lpfc: Update lpfc version to 14.0.0.4 commit4437503bfbec2f02b41b2492520fe627715889a7 Extended log info: -cover-letter.patch 0001-lpfc-Fix-leaked-lpfc_dmabuf-mbox-allocations-with-np.patch commitf0d3919697492950f57a26a1093aee53880d669d lpfc: Fix memory leaked lpfc_dmabuf mbox allocations Fix leaked lpfc_dmabuf allocations in an mbox. svn: r82112 bz: 249968 250131 0002-lpfc-Change-return-code-on-ios-received-during-link-.patch commit2e81b1a374da5d6024208c16c4a5224a70cafa64 lpfc: Group RPI_SUSPENDED error action with DID_REQUEUE Fix Medusa IO errors on Scope and Scale LIP test svn: r82348 bz: 247164 250466 Fix Medusa IO errors on Scope and Scale LIP test - build svn: r82377 bz: 247164 250466 0003-lpfc-Fix-lpfc_force_rscn-ndlp-kref-imbalance.patch commit7576d48c64f36f6fea9df2882f710a474fa35f40 lpfc: Fix lpfc_force_rscn ndlp kref imbalance Fix ndlp kref crash during lpfc_force_rscn svn: r82526 bz: 250692 250695 0004-lpfc-Fix-NPIV-port-deletion-crash.patch commit8ed190a91950564775cbaae9e8e8083a69a8da23 lpfc: Fix NPIV port deletion crash Fix crash when deleting a large number of vports. svn: r82120 bz: 240671 250158 Fix a log message formatting error introduced in svn r82120. svn: r82743 bz: 249968 250131 0005-lpfc-Trigger-SLI4-firmware-dump-before-doing-driver-.patch commit7dd2e2a923173d637c272e483966be8e96a72b64 lpfc: Trigger SLI4 firmware dump immediately without delays Trigger SLI4 firmware dump immediately without delays svn: r82770 bz: 250111 251061 0006-lpfc-Adjust-CMF-total-bytes-and-rxmonitor.patch commita6269f837045acb02904f31f05acde847ec8f8a7 lpfc: Adjust CMF total bytes and rxmonitor Adjust CMF total bytes and add to rxmonitor svn: r82429 bz: 250581 250587 0007-lpfc-Cap-CMF-read-bytes-to-MBPI.patch commit05116ef9c4b444f7fdbb56f9e13c2ec941726639 lpfc: Cap CMF read bytes to MBPI Cap CMF read bytes to MBPI only for shortened timer intervals svn: r82483 bz: 250605 251274 0008-lpfc-Add-additional-debugfs-support-for-CMF.patch commit6014a2468f0e49194f612b1f09f99eacee0a409a lpfc: Add additional debugfs support for CMF Add debugfs support for CMF parameters svn: r82144 bz: 250206 250237 Coverity: CID 19805 Fix memory illegal access svn: r82349 bz: 250454 250465 0009-lpfc-Update-lpfc-version-to-14.0.0.4.patch commit4437503bfbec2f02b41b2492520fe627715889a7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956982] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04
Jeff - thank you for the update but what is the ETA for a kernel with these patches integrated? Laurie -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956982 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04 Status in linux package in Ubuntu: Fix Committed Bug description: Please integrate this customer critical/reported fix that was submitted as a stand along patch: Accepted 11/29/21: Applied to 5.16/scsi-fixes, thanks! [1/1] lpfc: Fix nonrecovery of remote ports following an unsolicited LOGO https://git.kernel.org/mkp/scsi/c/0956ba63bd94 As well as this latest set of bug fix patches accepted upstream 12/6/2021: scsi: lpfc: Fix leaked lpfc_dmabuf mbox allocations with NPIV commitf0d3919697492950f57a26a1093aee53880d669d scsi: lpfc: Change return code on I/Os received during link bounce commit2e81b1a374da5d6024208c16c4a5224a70cafa64 scsi: lpfc: Fix lpfc_force_rscn ndlp kref imbalance commit7576d48c64f36f6fea9df2882f710a474fa35f40 scsi: lpfc: Fix NPIV port deletion crash commit8ed190a91950564775cbaae9e8e8083a69a8da23 scsi: lpfc: Trigger SLI4 firmware dump before doing driver cleanup commit7dd2e2a923173d637c272e483966be8e96a72b64 scsi: lpfc: Adjust CMF total bytes and rxmonitor commita6269f837045acb02904f31f05acde847ec8f8a7 scsi: lpfc: Cap CMF read bytes to MBPI commit05116ef9c4b444f7fdbb56f9e13c2ec941726639 scsi: lpfc: Add additional debugfs support for CMF commit6014a2468f0e49194f612b1f09f99eacee0a409a scsi: lpfc: Update lpfc version to 14.0.0.4 commit4437503bfbec2f02b41b2492520fe627715889a7 Extended log info: -cover-letter.patch 0001-lpfc-Fix-leaked-lpfc_dmabuf-mbox-allocations-with-np.patch commitf0d3919697492950f57a26a1093aee53880d669d lpfc: Fix memory leaked lpfc_dmabuf mbox allocations Fix leaked lpfc_dmabuf allocations in an mbox. svn: r82112 bz: 249968 250131 0002-lpfc-Change-return-code-on-ios-received-during-link-.patch commit2e81b1a374da5d6024208c16c4a5224a70cafa64 lpfc: Group RPI_SUSPENDED error action with DID_REQUEUE Fix Medusa IO errors on Scope and Scale LIP test svn: r82348 bz: 247164 250466 Fix Medusa IO errors on Scope and Scale LIP test - build svn: r82377 bz: 247164 250466 0003-lpfc-Fix-lpfc_force_rscn-ndlp-kref-imbalance.patch commit7576d48c64f36f6fea9df2882f710a474fa35f40 lpfc: Fix lpfc_force_rscn ndlp kref imbalance Fix ndlp kref crash during lpfc_force_rscn svn: r82526 bz: 250692 250695 0004-lpfc-Fix-NPIV-port-deletion-crash.patch commit8ed190a91950564775cbaae9e8e8083a69a8da23 lpfc: Fix NPIV port deletion crash Fix crash when deleting a large number of vports. svn: r82120 bz: 240671 250158 Fix a log message formatting error introduced in svn r82120. svn: r82743 bz: 249968 250131 0005-lpfc-Trigger-SLI4-firmware-dump-before-doing-driver-.patch commit7dd2e2a923173d637c272e483966be8e96a72b64 lpfc: Trigger SLI4 firmware dump immediately without delays Trigger SLI4 firmware dump immediately without delays svn: r82770 bz: 250111 251061 0006-lpfc-Adjust-CMF-total-bytes-and-rxmonitor.patch commita6269f837045acb02904f31f05acde847ec8f8a7 lpfc: Adjust CMF total bytes and rxmonitor Adjust CMF total bytes and add to rxmonitor svn: r82429 bz: 250581 250587 0007-lpfc-Cap-CMF-read-bytes-to-MBPI.patch commit05116ef9c4b444f7fdbb56f9e13c2ec941726639 lpfc: Cap CMF read bytes to MBPI Cap CMF read bytes to MBPI only for shortened timer intervals svn: r82483 bz: 250605 251274 0008-lpfc-Add-additional-debugfs-support-for-CMF.patch commit6014a2468f0e49194f612b1f09f99eacee0a409a lpfc: Add additional debugfs support for CMF Add debugfs support for CMF parameters svn: r82144 bz: 250206 250237 Coverity: CID 19805 Fix memory illegal access svn: r82349 bz: 250454 250465 0009-lpfc-Update-lpfc-version-to-14.0.0.4.patch commit4437503bfbec2f02b41b2492520fe627715889a7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956855] Re: [SRU] alsa-ucm-conf: Add Realtek 4050 USB Codec profile for a Dell machine
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu0.12 --- alsa-ucm-conf (1.2.2-1ubuntu0.12) focal; urgency=medium * d/p/0034-ucm2-Add-UCM-support-for-Dell-Desktop.patch Add Realtek 4050 USB Codec front and rear profiles for a Dell machine. (LP: #1956855) -- Hui Wang Sun, 09 Jan 2022 16:10:43 +0800 ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1956855 Title: [SRU] alsa-ucm-conf: Add Realtek 4050 USB Codec profile for a Dell machine Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Released Bug description: [Impact] This Dell machine has dual Realtek 4050 USB Codecs as front and rear codec, the front codec has speaker and headset, the rear codec has line-out audio jack. Without UCM, the pulseaudio can't detect this two usb audio codec and the audio can't work at all. [Fix] Backport a upstream patch, the patch adds the front and rear profiles in the ucm, then pulseaudio will enable all audio devices in this machine. [Test] booting with patched ucm, open the gnome-sound-setting, we could see usb speaker, usb headset and usb lineout, play sound to speaker, headset and lineout, all worked well, record sound via headset, it could record the sound correctly. [Where problems could occur] This SRU adds the new ucm files to a folder, in theory it will not introduce regressions, but It adds a file USB-Audio.conf, it could make other ucm conf files in the USB-Audio folder fail to parse, and make the P620 and WD15/19's audio fail to work, but this possibility is very low, we already tested it and no regression found so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630837] Re: mpt2sas aborts ATA pass through security erase command
There was a timeout bug in hdparm which was fixed upstream in 9.31 and
further fixed in 9.44
There was a SEPARATE timeout bug in mpt2sas drivers which was fixed
after xenial but has been reintroduced in 21.10 and 22.04 kernels
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-xenial in Ubuntu.
https://bugs.launchpad.net/bugs/1630837
Title:
mpt2sas aborts ATA pass through security erase command
Status in linux-lts-xenial package in Ubuntu:
Confirmed
Bug description:
Hello,
I think I have encountered an issue in the mpt3sas Linux driver. I am using
Lubuntu 16.04, kernel version 4.4. I have a SATA drive connected to a LSI
9211-8i controller, and I am trying to issue a security erase command to the
drive using the hdparm utility v9.48 and it fails.
It seems that the driver thinks that the command got stuck and tries to abort
it before it completes. The security erase ATA command needs a large timeout
that can be as much as several hours.
Below is the trace from hdparm:
user@user-MS-7887:~$ sudo hdparm --security-set-pass xxx /dev/sdb
security_password: "xxx"
/dev/sdb:
Issuing SECURITY_SET_PASS command, password="xxx", user=user, mode=high
user@user-MS-7887:~$ sudo hdparm --verbose --security-erase xxx /dev/sdb
security_password: "xxx"
/dev/sdb:
Issuing SECURITY_ERASE command, password="xxx", user=user
outgoing cdb: 85 08 0e 00 00 00 01 00 00 00 00 00 00 40 ec 00
SG_IO: ATA_16 status=0x0, host_status=0x0, driver_status=0x0
SG_IO: sb[]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00
incoming_data: 7a 42 ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00 00 00 00 00
20 20 20 20 57 20 2d 44 43 57 33 43 33 46 54 4b 54 50 31 33 00 00 00 00 00 00
31 30 30 2e 41 31 31 30 44 57 20 43 44 57 30 31 5a 45 58 45 30 2d 42 30 35 4e
30 41 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 10 80 00 40
00 2f 01 40 00 00 00 00 07 00 ff 3f 10 00 3f 00 10 fc fb 00 00 01 ff ff ff 0f
00 00 07 00 03 00 78 00 78 00 78 00 78 00 00 00 00 00 00 00 00 00 00 00 00 00
1f 00 0e 97 06 00 44 00 44 00 fe 03 1f 00 6b 74 61 7d 23 41 6b 74 41 bc 23 41
7f 40 3f 00 3f 00 00 00 fe ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0 6d
70 74 00 00 00 00 00 00 00 00 03 60 00 00 01 50 e2 4e 7a b6 f8 7e 00 00 00 00
00 00 00 00 00 00 00 00 00 00 18 40 18 40 00 00 00 00 00 00 00 00 00 00 00 00
00 00 23 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 35 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 1c
00 00 00 00 00 00 00 00 7e 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 01 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a5 ef
SG_IO: desc[]: 00 00
ATA_16 stat=00 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=00
outgoing cdb: 85 06 20 00 00 00 00 00 00 00 00 00 00 40 f3 00
SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
SG_IO: sb[]: 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00 00 00 00 00 40
50 00 00 00 00 00 00 00 00 00 00
SG_IO: desc[]: 09 0c 00 00 00 00 00 00 00 00 00 00 40 50
ATA_16 stat=50 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=40
oflags.bits.lob_all=0x8a, flags={ feat nsect command }
oflags.bits.hob_all=0x00, flags={ }
outgoing cdb: 85 0a 06 00 00 00 01 00 00 00 00 00 00 40 f4 00
outgoing_data: 00 00 4d 43 49 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00
[Kernel-packages] [Bug 1630837] Re: mpt2sas aborts ATA pass through security erase command
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-xenial in Ubuntu.
https://bugs.launchpad.net/bugs/1630837
Title:
mpt2sas aborts ATA pass through security erase command
Status in linux-lts-xenial package in Ubuntu:
Confirmed
Bug description:
Hello,
I think I have encountered an issue in the mpt3sas Linux driver. I am using
Lubuntu 16.04, kernel version 4.4. I have a SATA drive connected to a LSI
9211-8i controller, and I am trying to issue a security erase command to the
drive using the hdparm utility v9.48 and it fails.
It seems that the driver thinks that the command got stuck and tries to abort
it before it completes. The security erase ATA command needs a large timeout
that can be as much as several hours.
Below is the trace from hdparm:
user@user-MS-7887:~$ sudo hdparm --security-set-pass xxx /dev/sdb
security_password: "xxx"
/dev/sdb:
Issuing SECURITY_SET_PASS command, password="xxx", user=user, mode=high
user@user-MS-7887:~$ sudo hdparm --verbose --security-erase xxx /dev/sdb
security_password: "xxx"
/dev/sdb:
Issuing SECURITY_ERASE command, password="xxx", user=user
outgoing cdb: 85 08 0e 00 00 00 01 00 00 00 00 00 00 40 ec 00
SG_IO: ATA_16 status=0x0, host_status=0x0, driver_status=0x0
SG_IO: sb[]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00
incoming_data: 7a 42 ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00 00 00 00 00
20 20 20 20 57 20 2d 44 43 57 33 43 33 46 54 4b 54 50 31 33 00 00 00 00 00 00
31 30 30 2e 41 31 31 30 44 57 20 43 44 57 30 31 5a 45 58 45 30 2d 42 30 35 4e
30 41 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 10 80 00 40
00 2f 01 40 00 00 00 00 07 00 ff 3f 10 00 3f 00 10 fc fb 00 00 01 ff ff ff 0f
00 00 07 00 03 00 78 00 78 00 78 00 78 00 00 00 00 00 00 00 00 00 00 00 00 00
1f 00 0e 97 06 00 44 00 44 00 fe 03 1f 00 6b 74 61 7d 23 41 6b 74 41 bc 23 41
7f 40 3f 00 3f 00 00 00 fe ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0 6d
70 74 00 00 00 00 00 00 00 00 03 60 00 00 01 50 e2 4e 7a b6 f8 7e 00 00 00 00
00 00 00 00 00 00 00 00 00 00 18 40 18 40 00 00 00 00 00 00 00 00 00 00 00 00
00 00 23 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 35 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 1c
00 00 00 00 00 00 00 00 7e 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 01 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a5 ef
SG_IO: desc[]: 00 00
ATA_16 stat=00 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=00
outgoing cdb: 85 06 20 00 00 00 00 00 00 00 00 00 00 40 f3 00
SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
SG_IO: sb[]: 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00 00 00 00 00 40
50 00 00 00 00 00 00 00 00 00 00
SG_IO: desc[]: 09 0c 00 00 00 00 00 00 00 00 00 00 40 50
ATA_16 stat=50 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=40
oflags.bits.lob_all=0x8a, flags={ feat nsect command }
oflags.bits.hob_all=0x00, flags={ }
outgoing cdb: 85 0a 06 00 00 00 01 00 00 00 00 00 00 40 f4 00
outgoing_data: 00 00 4d 43 49 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
[Kernel-packages] [Bug 1956982] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956982 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04 Status in linux package in Ubuntu: Fix Committed Bug description: Please integrate this customer critical/reported fix that was submitted as a stand along patch: Accepted 11/29/21: Applied to 5.16/scsi-fixes, thanks! [1/1] lpfc: Fix nonrecovery of remote ports following an unsolicited LOGO https://git.kernel.org/mkp/scsi/c/0956ba63bd94 As well as this latest set of bug fix patches accepted upstream 12/6/2021: scsi: lpfc: Fix leaked lpfc_dmabuf mbox allocations with NPIV commitf0d3919697492950f57a26a1093aee53880d669d scsi: lpfc: Change return code on I/Os received during link bounce commit2e81b1a374da5d6024208c16c4a5224a70cafa64 scsi: lpfc: Fix lpfc_force_rscn ndlp kref imbalance commit7576d48c64f36f6fea9df2882f710a474fa35f40 scsi: lpfc: Fix NPIV port deletion crash commit8ed190a91950564775cbaae9e8e8083a69a8da23 scsi: lpfc: Trigger SLI4 firmware dump before doing driver cleanup commit7dd2e2a923173d637c272e483966be8e96a72b64 scsi: lpfc: Adjust CMF total bytes and rxmonitor commita6269f837045acb02904f31f05acde847ec8f8a7 scsi: lpfc: Cap CMF read bytes to MBPI commit05116ef9c4b444f7fdbb56f9e13c2ec941726639 scsi: lpfc: Add additional debugfs support for CMF commit6014a2468f0e49194f612b1f09f99eacee0a409a scsi: lpfc: Update lpfc version to 14.0.0.4 commit4437503bfbec2f02b41b2492520fe627715889a7 Extended log info: -cover-letter.patch 0001-lpfc-Fix-leaked-lpfc_dmabuf-mbox-allocations-with-np.patch commitf0d3919697492950f57a26a1093aee53880d669d lpfc: Fix memory leaked lpfc_dmabuf mbox allocations Fix leaked lpfc_dmabuf allocations in an mbox. svn: r82112 bz: 249968 250131 0002-lpfc-Change-return-code-on-ios-received-during-link-.patch commit2e81b1a374da5d6024208c16c4a5224a70cafa64 lpfc: Group RPI_SUSPENDED error action with DID_REQUEUE Fix Medusa IO errors on Scope and Scale LIP test svn: r82348 bz: 247164 250466 Fix Medusa IO errors on Scope and Scale LIP test - build svn: r82377 bz: 247164 250466 0003-lpfc-Fix-lpfc_force_rscn-ndlp-kref-imbalance.patch commit7576d48c64f36f6fea9df2882f710a474fa35f40 lpfc: Fix lpfc_force_rscn ndlp kref imbalance Fix ndlp kref crash during lpfc_force_rscn svn: r82526 bz: 250692 250695 0004-lpfc-Fix-NPIV-port-deletion-crash.patch commit8ed190a91950564775cbaae9e8e8083a69a8da23 lpfc: Fix NPIV port deletion crash Fix crash when deleting a large number of vports. svn: r82120 bz: 240671 250158 Fix a log message formatting error introduced in svn r82120. svn: r82743 bz: 249968 250131 0005-lpfc-Trigger-SLI4-firmware-dump-before-doing-driver-.patch commit7dd2e2a923173d637c272e483966be8e96a72b64 lpfc: Trigger SLI4 firmware dump immediately without delays Trigger SLI4 firmware dump immediately without delays svn: r82770 bz: 250111 251061 0006-lpfc-Adjust-CMF-total-bytes-and-rxmonitor.patch commita6269f837045acb02904f31f05acde847ec8f8a7 lpfc: Adjust CMF total bytes and rxmonitor Adjust CMF total bytes and add to rxmonitor svn: r82429 bz: 250581 250587 0007-lpfc-Cap-CMF-read-bytes-to-MBPI.patch commit05116ef9c4b444f7fdbb56f9e13c2ec941726639 lpfc: Cap CMF read bytes to MBPI Cap CMF read bytes to MBPI only for shortened timer intervals svn: r82483 bz: 250605 251274 0008-lpfc-Add-additional-debugfs-support-for-CMF.patch commit6014a2468f0e49194f612b1f09f99eacee0a409a lpfc: Add additional debugfs support for CMF Add debugfs support for CMF parameters svn: r82144 bz: 250206 250237 Coverity: CID 19805 Fix memory illegal access svn: r82349 bz: 250454 250465 0009-lpfc-Update-lpfc-version-to-14.0.0.4.patch commit4437503bfbec2f02b41b2492520fe627715889a7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948636] 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 1948636 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/1948636 Title: Ubuntu 22.04 Feature Request-NVMe: Include libnvme package Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Upstream (Keith Busch) has started to revive libnvme with the hope of having nvme-cli use libnvme in future. New features like CDC client will be developed on libnvme. Upstream plans are to make libnvme a standalone package that other projects would depend on. We request that Ubuntu 22.04 carry the new libnvme package. https://github.com/linux-nvme/libnvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948636] Re: Ubuntu 22.04 Feature Request-NVMe: Include libnvme package
** Changed in: linux (Ubuntu Jammy) Status: Incomplete => New ** Tags added: soa -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948636 Title: Ubuntu 22.04 Feature Request-NVMe: Include libnvme package Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Bug description: Upstream (Keith Busch) has started to revive libnvme with the hope of having nvme-cli use libnvme in future. New features like CDC client will be developed on libnvme. Upstream plans are to make libnvme a standalone package that other projects would depend on. We request that Ubuntu 22.04 carry the new libnvme package. https://github.com/linux-nvme/libnvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964471] Re: 5.13.0-36 fails to boot on Parallels on Mac M1 eg aarch64
And this is the kernel side trigger for the issue: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/impish/commit/?id=7936f2a576f1d7c3e1a80f8a07a217cdfa2b7338 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964471 Title: 5.13.0-36 fails to boot on Parallels on Mac M1 eg aarch64 Status in linux package in Ubuntu: Confirmed Bug description: After allowing an Ubuntu Impish system running under Parallels Desktop on M1 Mac (aarch64) to update, and rebooting for a new kernel it gets stuck after loading kernel and ramdisk, no further output on 5.13.0-36 Reverting to 5.13.0-20 by selecting it at the grub screen allows the system to boot as normal. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moon1272538 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 11:42:47 2022 InstallationDate: Installed on 2021-02-18 (385 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release arm64 (20210218) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci-vt: -[:00]-+-01.0 Intel Corporation 82801I (ICH9 Family) HD Audio Controller +-02.0 Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller +-03.0 NEC Corporation uPD720200 USB 3.0 Host Controller +-09.0 Parallels, Inc. Virtual Machine Communication Interface \-0a.0 Red Hat, Inc. Virtio GPU MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-19 (142 days ago) acpidump: dmi.bios.date: Wed, 24 Nov 2021 19:24:24 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 17.1.1 (51537) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr17.1.1(51537):bdWed,24Nov2021192424:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:skuParallels_ARM_VM:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964471] Re: 5.13.0-36 fails to boot on Parallels on Mac M1 eg aarch64
For reference, this is what fixes it on QEMU: https://github.com/qemu/qemu/compare/48006e0...7f6c295 I doubt this is a reason to do anything to the Ubuntu kernel, then. Filing a bug with Parallels referencing that may be good. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964471 Title: 5.13.0-36 fails to boot on Parallels on Mac M1 eg aarch64 Status in linux package in Ubuntu: Confirmed Bug description: After allowing an Ubuntu Impish system running under Parallels Desktop on M1 Mac (aarch64) to update, and rebooting for a new kernel it gets stuck after loading kernel and ramdisk, no further output on 5.13.0-36 Reverting to 5.13.0-20 by selecting it at the grub screen allows the system to boot as normal. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moon1272538 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 11:42:47 2022 InstallationDate: Installed on 2021-02-18 (385 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release arm64 (20210218) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci-vt: -[:00]-+-01.0 Intel Corporation 82801I (ICH9 Family) HD Audio Controller +-02.0 Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller +-03.0 NEC Corporation uPD720200 USB 3.0 Host Controller +-09.0 Parallels, Inc. Virtual Machine Communication Interface \-0a.0 Red Hat, Inc. Virtio GPU MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-19 (142 days ago) acpidump: dmi.bios.date: Wed, 24 Nov 2021 19:24:24 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 17.1.1 (51537) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr17.1.1(51537):bdWed,24Nov2021192424:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:skuParallels_ARM_VM:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961955] Re: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream
Thanks, the HBA and BOSS ones are part of the update https://launchpad.net/ubuntu/+source/hwdata/0.357-1 now but the ROR one doesn't seem to be upstream https://github.com/vcrhonek/hwdata/blob/master/pci.ids ? could you submit a merge proposal on github, that doesn't seem something we should carry as a distribution specific delta ** Changed in: hwdata (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1961955 Title: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream Status in hwdata package in Ubuntu: Incomplete Status in hwdata source package in Focal: New Status in hwdata source package in Jammy: Incomplete Bug description: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET 1b4b: 2241: 1028: 2196 ROR-N100 Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1961955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960117] Re: [22.04 FEAT] Add new CPU-MF Counters for new IBM Z Hardware
*** This bug is a duplicate of bug 1960182 *** https://bugs.launchpad.net/bugs/1960182 These patches were already addressed by: https://lists.ubuntu.com/archives/kernel-team/2022-February/128125.html (LP#1960182) (see comment: https://lists.ubuntu.com/archives/kernel-team/2022-March/128513.html) Hence marking this as duplicate of LP#1960182. ** This bug has been marked a duplicate of bug 1960182 [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960117 Title: [22.04 FEAT] Add new CPU-MF Counters for new IBM Z Hardware Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: Add new CPU-MF Counters for new IBM Z Hardware - kernel part Description: Add new CPU-MF Counters for new IBM Z Hardware. Has a kernel, s390utils/s390-tools and libpfm part. Category: kernel Request Type: Kernel - Enhancement from IBM Upstream Acceptance: In Progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964471] Re: 5.13.0-36 fails to boot on Parallels on Mac M1 eg aarch64
We can confirm the same through Multipass on QEMU rather than Parallels. We found that using a different version of QEMU does help, we're trying to narrow it down to a QEMU commit now. There are a number of changes that can be seen in the recent kernel pertaining to aarch64: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/impish/log/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964471 Title: 5.13.0-36 fails to boot on Parallels on Mac M1 eg aarch64 Status in linux package in Ubuntu: Confirmed Bug description: After allowing an Ubuntu Impish system running under Parallels Desktop on M1 Mac (aarch64) to update, and rebooting for a new kernel it gets stuck after loading kernel and ramdisk, no further output on 5.13.0-36 Reverting to 5.13.0-20 by selecting it at the grub screen allows the system to boot as normal. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moon1272538 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 11:42:47 2022 InstallationDate: Installed on 2021-02-18 (385 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release arm64 (20210218) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci-vt: -[:00]-+-01.0 Intel Corporation 82801I (ICH9 Family) HD Audio Controller +-02.0 Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller +-03.0 NEC Corporation uPD720200 USB 3.0 Host Controller +-09.0 Parallels, Inc. Virtual Machine Communication Interface \-0a.0 Red Hat, Inc. Virtio GPU MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-19 (142 days ago) acpidump: dmi.bios.date: Wed, 24 Nov 2021 19:24:24 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 17.1.1 (51537) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr17.1.1(51537):bdWed,24Nov2021192424:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:skuParallels_ARM_VM:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964471] Re: 5.13.0-36 fails to boot on Parallels on Mac M1 eg aarch64
** Description changed: - After allowing an Ubuntu Impish system to update, and rebooting for a - new kernel it gets stuck after loading kernel and ramdisk, no further - output on 5.13.0-36 + After allowing an Ubuntu Impish system running under Parallels Desktop + on M1 Mac (aarch64) to update, and rebooting for a new kernel it gets + stuck after loading kernel and ramdisk, no further output on 5.13.0-36 Reverting to 5.13.0-20 by selecting it at the grub screen allows the system to boot as normal. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: moon1272538 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: moon1272538 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 11:42:47 2022 InstallationDate: Installed on 2021-02-18 (385 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release arm64 (20210218) IwConfig: - lono wireless extensions. - - eth0 no wireless extensions. + lono wireless extensions. + + eth0 no wireless extensions. Lspci-vt: - -[:00]-+-01.0 Intel Corporation 82801I (ICH9 Family) HD Audio Controller - +-02.0 Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller - +-03.0 NEC Corporation uPD720200 USB 3.0 Host Controller - +-09.0 Parallels, Inc. Virtual Machine Communication Interface - \-0a.0 Red Hat, Inc. Virtio GPU + -[:00]-+-01.0 Intel Corporation 82801I (ICH9 Family) HD Audio Controller + +-02.0 Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller + +-03.0 NEC Corporation uPD720200 USB 3.0 Host Controller + +-09.0 Parallels, Inc. Virtual Machine Communication Interface + \-0a.0 Red Hat, Inc. Virtio GPU MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: - linux-restricted-modules-5.13.0-20-generic N/A - linux-backports-modules-5.13.0-20-generic N/A - linux-firmware 1.201.5 + linux-restricted-modules-5.13.0-20-generic N/A + linux-backports-modules-5.13.0-20-generic N/A + linux-firmware 1.201.5 RfKill: - + SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-19 (142 days ago) acpidump: - + dmi.bios.date: Wed, 24 Nov 2021 19:24:24 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 17.1.1 (51537) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr17.1.1(51537):bdWed,24Nov2021192424:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:skuParallels_ARM_VM:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964471 Title: 5.13.0-36 fails to boot on Parallels on Mac M1 eg aarch64 Status in linux package in Ubuntu: Confirmed Bug description: After allowing an Ubuntu Impish system running under Parallels Desktop on M1 Mac (aarch64) to update, and rebooting for a new kernel it gets stuck after loading kernel and ramdisk, no further output on 5.13.0-36 Reverting to 5.13.0-20 by selecting it at the grub screen allows the system to boot as normal. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moon1272538 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 11:42:47 2022 InstallationDate: Installed on 2021-02-18 (385 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release arm64
[Kernel-packages] [Bug 1964471] 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/1964471 Title: 5.13.0-36 fails to boot on Parallels on Mac M1 eg aarch64 Status in linux package in Ubuntu: Confirmed Bug description: After allowing an Ubuntu Impish system to update, and rebooting for a new kernel it gets stuck after loading kernel and ramdisk, no further output on 5.13.0-36 Reverting to 5.13.0-20 by selecting it at the grub screen allows the system to boot as normal. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moon1272538 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 11:42:47 2022 InstallationDate: Installed on 2021-02-18 (385 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release arm64 (20210218) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci-vt: -[:00]-+-01.0 Intel Corporation 82801I (ICH9 Family) HD Audio Controller +-02.0 Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller +-03.0 NEC Corporation uPD720200 USB 3.0 Host Controller +-09.0 Parallels, Inc. Virtual Machine Communication Interface \-0a.0 Red Hat, Inc. Virtio GPU MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-19 (142 days ago) acpidump: dmi.bios.date: Wed, 24 Nov 2021 19:24:24 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 17.1.1 (51537) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr17.1.1(51537):bdWed,24Nov2021192424:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:skuParallels_ARM_VM:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964471] [NEW] 5.13.0-36 fails to boot on Parallels on Mac M1 eg aarch64
Public bug reported: After allowing an Ubuntu Impish system to update, and rebooting for a new kernel it gets stuck after loading kernel and ramdisk, no further output on 5.13.0-36 Reverting to 5.13.0-20 by selecting it at the grub screen allows the system to boot as normal. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moon1272538 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 11:42:47 2022 InstallationDate: Installed on 2021-02-18 (385 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release arm64 (20210218) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci-vt: -[:00]-+-01.0 Intel Corporation 82801I (ICH9 Family) HD Audio Controller +-02.0 Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller +-03.0 NEC Corporation uPD720200 USB 3.0 Host Controller +-09.0 Parallels, Inc. Virtual Machine Communication Interface \-0a.0 Red Hat, Inc. Virtio GPU MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-19 (142 days ago) acpidump: dmi.bios.date: Wed, 24 Nov 2021 19:24:24 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 17.1.1 (51537) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr17.1.1(51537):bdWed,24Nov2021192424:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:skuParallels_ARM_VM:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 impish wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964471 Title: 5.13.0-36 fails to boot on Parallels on Mac M1 eg aarch64 Status in linux package in Ubuntu: New Bug description: After allowing an Ubuntu Impish system to update, and rebooting for a new kernel it gets stuck after loading kernel and ramdisk, no further output on 5.13.0-36 Reverting to 5.13.0-20 by selecting it at the grub screen allows the system to boot as normal. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moon1272538 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 11:42:47 2022 InstallationDate: Installed on 2021-02-18 (385 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release arm64 (20210218) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci-vt: -[:00]-+-01.0 Intel Corporation 82801I (ICH9 Family) HD Audio Controller +-02.0 Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller +-03.0 NEC Corporation uPD720200 USB 3.0 Host Controller +-09.0 Parallels, Inc. Virtual Machine Communication Interface \-0a.0 Red Hat, Inc. Virtio GPU MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-19 (142 days ago)
[Kernel-packages] [Bug 1964278] Re: package firmware-sof-signed 1.7-1 failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.201
This should be released in 1.9-1ubuntu1 and later releases ** Changed in: firmware-sof (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/1964278 Title: package firmware-sof-signed 1.7-1 failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.201.4 Status in firmware-sof package in Ubuntu: Fix Released Bug description: running script "apl-sof-setup-audio" to setup SOF audio on laptop. During the script, received an error "dpkg-deb: error: paste subprocess was killed by signal." and the bug report dialog appeared immediately after. ProblemType: Package DistroRelease: Ubuntu 21.10 Package: firmware-sof-signed 1.7-1 Uname: Linux 5.10.102-g142ef9297957-dirty x86_64 ApportVersion: 2.20.11-0ubuntu71 AptOrdering: firmware-sof-signed:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 8 17:44:45 2022 Dependencies: DpkgTerminalLog: Preparing to unpack .../firmware-sof-signed_1.7-1_all.deb ... Unpacking firmware-sof-signed (1.7-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.7-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.201.4 DuplicateSignature: package:firmware-sof-signed:1.7-1 Unpacking firmware-sof-signed (1.7-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.7-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.201.4 ErrorMessage: trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.201.4 PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: firmware-sof Title: package firmware-sof-signed 1.7-1 failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.201.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1964278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964467] [NEW] edge variants are not obvious
Public bug reported: The package description and sections for edge and non-edge variants is the same. In the kernel meta packages we should be able to do something better. For example include a trailer explanation in the description that whenever a variant is "-edge" it is preview kernel, for the upcoming change of the non-edge variant, and that it is a non production kernel, meant to be used for early testing for the upcoming changes that are about to happen to the non-edge variant. Also potentially point out that it receives non-timely security support without SLAs. We also can make use of split publishing of binaries. src:linux-meta* can produce most binaries into main, but it can publish "-edge" binaries to universe. We could for example mark out 'Sections' in the control file with "universe/kernel". ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- 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/1964467 Title: edge variants are not obvious Status in linux-meta package in Ubuntu: New Bug description: The package description and sections for edge and non-edge variants is the same. In the kernel meta packages we should be able to do something better. For example include a trailer explanation in the description that whenever a variant is "-edge" it is preview kernel, for the upcoming change of the non-edge variant, and that it is a non production kernel, meant to be used for early testing for the upcoming changes that are about to happen to the non-edge variant. Also potentially point out that it receives non-timely security support without SLAs. We also can make use of split publishing of binaries. src:linux-meta* can produce most binaries into main, but it can publish "-edge" binaries to universe. We could for example mark out 'Sections' in the control file with "universe/kernel". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1964467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898434] Re: HWE - opt-in edge kernel for LTS without PPA
We do that, once we validate that the edge kernels built correctly and boot. The ppa you point out is where we start preparing next hwe kernel, initially as hwe-edge kernel, which does get published to the main archive, and eventually becomes hwe variant. However hwe-edge kernels are not meant for production use, as they do not receive security support, until after they become hwe variant. The date of your bug report suggests that at the time 20.10 release was still in development, and so was the hwe-edge kernel which is based on 20.10 release. At that time you had wait until after 20.10 release, kernel be ready, and get rolled out in focal. ** Changed in: linux-meta (Ubuntu) Status: New => Opinion -- 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/1898434 Title: HWE - opt-in edge kernel for LTS without PPA Status in linux-meta package in Ubuntu: Opinion Bug description: Add linux-generic-hwe-20.04-edge from ppa:canonical-kernel-team/ppa to the LTS repository and stick with it for upcoming LTS releases as well. The problem is newer hardware is not functioning properly with Ubuntu, which is a showstopper bug of highest importance, adding a PPA shouldn't be required, and for a user to manually install linux- generic-hwe-20.04-edge package is already something that one opts-in accepting the risk. There might be an interface added for managing this or some message about the risk involved but this option is needed for lots of laptops and other devices to work with Ubuntu. Might be added to the installer, the additional drivers app, or 'About' page in Settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1898434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963901] Re: [22.04 FEAT] [VS2103] KVM: Enable storage key checking for intercepted instruction - Set Capability 211
** 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/1963901
Title:
[22.04 FEAT] [VS2103] KVM: Enable storage key checking for intercepted
instruction - Set Capability 211
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Bug description:
Title:
KVM: Enable storage key checking for intercepted instruction - Set Capability
211
Description:
This patch is required on top of "Bug 193314 - LP#1933179 : [22.04 FEAT]
[VS2103] KVM: Enable storage key checking for intercepted instruction" in order
to set the to set the Capability number to 211
See this merge:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git/commit/?h=next=4dfc4ec2b7f5a3a27d166ac42cf8a583fa2d3284
diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
index dbc550bbd9fa3..a02bbf8fd0f67 100644
--- a/include/uapi/linux/kvm.h
+++ b/include/uapi/linux/kvm.h
@@ -1140,7 +1140,8 @@ struct kvm_ppc_resize_hpt {
#define KVM_CAP_VM_GPA_BITS 207
#define KVM_CAP_XSAVE2 208
#define KVM_CAP_SYS_ATTRIBUTES 209
-#define KVM_CAP_S390_MEM_OP_EXTENSION 210
+#define KVM_CAP_PPC_AIL_MODE_3 210
+#define KVM_CAP_S390_MEM_OP_EXTENSION 211
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1963901/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960323] Re: jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-02-08)
This bug was fixed in the package linux-raspi - 5.15.0-1003.3
---
linux-raspi (5.15.0-1003.3) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1003.3 -proposed tracker (LP: #1960318)
* jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-02-08)
(LP: #1960323)
- media: i2c: imx219: Correct the minimum vblanking value
- drm/vc4_hdmi: Add Broadcast RGB property to allow override of RGB range
- configs: Add CONFIG_MAX30102=m
- overlays: Add MAX30102 HR to i2c-sensor overlay
- misc: bcm2835_smi: Use proper enum types for dma_{,un}map_single()
- ASoC: ma120x0p: Remove unnecessary const specifier
- ASoC: bcm: allo-piano-dac-plus: Remove unnecessary const specifiers
- media: bcm2835-unicam: Set ret on error path in unicam_async_complete()
- media: i2c: ov9281: Initialize id_msb to zero in ov9281_check_sensor_id()
- i2c: bcm2835: Make clock-stretch timeout configurable
- Patching lan78xx for SOF_TIMESTAMPING_TX_SOFTWARE support
- drm/vc4: Add DRM 210101010 RGB formats for hvs5.
- overlays: Add spi0-0cs overlay
- dtoverlays: Rework vc4-kms-dpi overlays to remove duplication
- media: uapi: Document format MEDIA_BUS_FMT_RGB565_1X24_CPADHI
- media: uapi: add MEDIA_BUS_FMT_RGB565_1X24_CPADHI
- drm/vc4: dpi: Support DPI interface in mode3 for RGB565
- dt-bindings: vendor-prefixes: Add Geekworm
- dt-bindings: display: simple: add Geekworm MZP280 Panel
- drm/panel: simple: add Geekworm MZP280 Panel
- overlays: README: Deprecate vc4-kms-kippah-7inch
- drm/panel: Add and initialise an orientation field to drm_panel
- SAUCE: drm/panel: Fix compilation error
- drm/panel: simple: Remove custom handling of orientation
- overlays: Add rotate property to vc4-kms-dpi-panel
- overlays: Add Geekworm mzp280 to vc4-kms-dpi-panel
- drm/panel: Add panel driver for Ilitek ILI9806E panel
- drm/panel: Add panel driver for TDO Y17B based panels
- drm/panel/panel-sitronix-st7701: Support SPI config and RGB data
- defconfig: Enable Pimoroni HyperPixel drivers in Pi defconfigs
- bindings: Add sck-idle-input to spi-gpio
- spi: gpio: Add sck-idle-input property
- dtoverlays: Add overlays for Pimoroni Hyperpixel displays
- dtoverlay: Reduce size of PCIE IB window in pcie-32-dma overlay
- ARM: dts: Permanently disable hdmi1 and ddc1 on CM4S
- net: phy: lan87xx: Decrease phy polling rate
- drm: panel: Fix compilation warnings
- media: bcm2835-unicam: Handle a repeated frame start with no end
- Revert "drm/vc4: Add DRM 210101010 RGB formats for hvs5."
- Revert "drm/vc4: Add alpha_blend_mode property to each plane."
- Revert "vc4/kms: vc4_plane: Support 2020 colourspace for yuv planes"
- Revert "vc4/drm: Fix source offsets with DRM_FORMAT_P030"
- Revert "drm/vc4: Add support for YUV color encodings and ranges"
- Revert "drm/vc4: Add support for DRM_FORMAT_P030 to vc4 planes"
- drm/vc4: plane: Add support for DRM_FORMAT_P030
- drm/vc4: plane: Add support for YUV color encodings and ranges
- drm/vc4: Add alpha_blend_mode property to each plane.
- drm/vc4: Add DRM 210101010 RGB formats for hvs5.
- Fix "drm/vc4: hdmi: Make sure the device is powered with CEC"
[ Ubuntu: 5.15.0-22.22 ]
* jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)
[ Ubuntu: 5.15.0-21.21 ]
* jammy/linux: 5.15.0-21.21 -proposed tracker (LP: #1960211)
* Miscellaneous Ubuntu changes
- [packaging] unhook lowlatency flavours from the build
[ Ubuntu: 5.15.0-20.20 ]
* jammy/linux: 5.15.0-20.20 -proposed tracker (LP: #1959881)
* Jammy update: v5.15.19 upstream stable release (LP: #1959879)
- can: m_can: m_can_fifo_{read,write}: don't read or write from/to FIFO if
length is 0
- net: sfp: ignore disabled SFP node
- net: stmmac: configure PTP clock source prior to PTP initialization
- net: stmmac: skip only stmmac_ptp_register when resume from suspend
- ARM: 9179/1: uaccess: avoid alignment faults in
copy_[from|to]_kernel_nofault
- ARM: 9180/1: Thumb2: align ALT_UP() sections in modules sufficiently
- KVM: arm64: Use shadow SPSR_EL1 when injecting exceptions on !VHE
- s390/hypfs: include z/VM guests with access control group set
- s390/nmi: handle guarded storage validity failures for KVM guests
- s390/nmi: handle vector validity failures for KVM guests
- bpf: Guard against accessing NULL pt_regs in bpf_get_task_stack()
- powerpc32/bpf: Fix codegen for bpf-to-bpf calls
- powerpc/bpf: Update ldimm64 instructions during extra pass
- scsi: zfcp: Fix failed recovery on gone remote port with non-NPIV FCP
devices
- udf: Restore i_lenAlloc when inode expansion fails
- udf: Fix NULL ptr deref when converting from inline format
- efi: runtime: avoid EFIv2 runtime services on Apple x86 machines
- PM: wakeup: simplify the output logic of
[Kernel-packages] [Bug 1964286] Re: Intel AX201 [8086:a0f0] subsys [8086:4070] iwlwifi microcode crash after updating to 5.14.0-1027-oem
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed -- 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/1964286 Title: Intel AX201 [8086:a0f0] subsys [8086:4070] iwlwifi microcode crash after updating to 5.14.0-1027-oem Status in OEM Priority Project: Triaged Status in linux-oem-5.14 package in Ubuntu: Confirmed Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: Mar 09 10:33:40 MDAT-DVT2-D8 kernel: FAT-fs (sda1): unable to read boot sector to mark fs as dirty Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Start IWL Error Log Dump: Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Transport status: 0x004B, valid: 6 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Loaded firmware version: 63.c04f3485.0 QuZ-a0-hr-b0-63.ucode Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x0FAD | ADVANCED_SYSASSERT Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0xA210 | trm_hw_status0 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x | trm_hw_status1 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004CAD42 | branchlink2 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004C17C6 | interruptlink1 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004C17C6 | interruptlink2 ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1027-oem 5.14.0-1027.30 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 9 11:13:53 2022 InstallationDate: Installed on 2021-10-19 (140 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964286] Re: Intel AX201 [8086:a0f0] subsys [8086:4070] iwlwifi microcode crash after updating to 5.14.0-1027-oem
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Confirmed -- 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/1964286 Title: Intel AX201 [8086:a0f0] subsys [8086:4070] iwlwifi microcode crash after updating to 5.14.0-1027-oem Status in OEM Priority Project: Triaged Status in linux-oem-5.14 package in Ubuntu: Confirmed Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: Mar 09 10:33:40 MDAT-DVT2-D8 kernel: FAT-fs (sda1): unable to read boot sector to mark fs as dirty Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Start IWL Error Log Dump: Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Transport status: 0x004B, valid: 6 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Loaded firmware version: 63.c04f3485.0 QuZ-a0-hr-b0-63.ucode Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x0FAD | ADVANCED_SYSASSERT Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0xA210 | trm_hw_status0 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x | trm_hw_status1 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004CAD42 | branchlink2 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004C17C6 | interruptlink1 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004C17C6 | interruptlink2 ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1027-oem 5.14.0-1027.30 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 9 11:13:53 2022 InstallationDate: Installed on 2021-10-19 (140 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961955] Re: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream
** Description changed: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET + 1b4b: 2241: 1028: 2196 ROR-N100 Thanks. ** Description changed: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however - new form factors are being launched by Dell which are having new - subsystem-ids. + new form factors are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET - 1b4b: 2241: 1028: 2196 ROR-N100 + 1b4b: 2241: 1028: 2196 ROR-N100 Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1961955 Title: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream Status in hwdata package in Ubuntu: New Status in hwdata source package in Focal: New Status in hwdata source package in Jammy: New Bug description: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET 1b4b: 2241: 1028: 2196 ROR-N100 Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1961955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962299] Please test proposed package
Hello Juerg, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.29 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1962299 Title: Add missing firmware for HWE 5.15 kernel Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] Firmware files required by the HWE kernel 5.15 which are present in Jammy but missing in Focal: amd/amd_sev_fam17h_model3xh.sbin amd/amd_sev_fam19h_model0xh.sbin amdgpu/aldebaran_mec.bin amdgpu/aldebaran_mec2.bin amdgpu/aldebaran_rlc.bin amdgpu/aldebaran_sdma.bin amdgpu/aldebaran_smc.bin amdgpu/aldebaran_sos.bin amdgpu/aldebaran_ta.bin amdgpu/aldebaran_vcn.bin amdgpu/arcturus_asd.bin amdgpu/arcturus_gpu_info.bin amdgpu/arcturus_mec.bin amdgpu/arcturus_rlc.bin amdgpu/arcturus_sdma.bin amdgpu/arcturus_smc.bin amdgpu/arcturus_sos.bin amdgpu/arcturus_ta.bin amdgpu/arcturus_vcn.bin amdgpu/cyan_skillfish2_ce.bin amdgpu/cyan_skillfish2_me.bin amdgpu/cyan_skillfish2_mec.bin amdgpu/cyan_skillfish2_mec2.bin amdgpu/cyan_skillfish2_pfp.bin amdgpu/cyan_skillfish2_rlc.bin amdgpu/cyan_skillfish2_sdma.bin amdgpu/cyan_skillfish2_sdma1.bin amdgpu/navy_flounder_ce.bin amdgpu/navy_flounder_dmcub.bin amdgpu/navy_flounder_me.bin amdgpu/navy_flounder_mec.bin amdgpu/navy_flounder_mec2.bin amdgpu/navy_flounder_pfp.bin amdgpu/navy_flounder_rlc.bin amdgpu/navy_flounder_sdma.bin amdgpu/navy_flounder_smc.bin amdgpu/navy_flounder_sos.bin amdgpu/navy_flounder_ta.bin amdgpu/navy_flounder_vcn.bin amdgpu/vangogh_asd.bin amdgpu/vangogh_ce.bin amdgpu/vangogh_dmcub.bin amdgpu/vangogh_me.bin amdgpu/vangogh_mec.bin amdgpu/vangogh_mec2.bin amdgpu/vangogh_pfp.bin amdgpu/vangogh_rlc.bin amdgpu/vangogh_sdma.bin amdgpu/vangogh_toc.bin amdgpu/vangogh_vcn.bin atmel/wilc1000_wifi_firmware-1.bin brcm/brcmfmac43340-sdio.predia-basic.txt brcm/brcmfmac43430-sdio.friendlyarm,nanopi-r1.txt brcm/brcmfmac43430-sdio.raspberrypi,model-zero-w.txt brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-plus.txt brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-ultra.txt brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-zero.txt brcm/brcmfmac43430-sdio.sinovoip,bpi-m3.txt brcm/brcmfmac43430a0-sdio.ilife-S806.txt brcm/brcmfmac43455-sdio.Raspberry Pi Foundation-Raspberry Pi 4 Model B.txt brcm/brcmfmac43455-sdio.Raspberry Pi Foundation-Raspberry Pi Compute Module 4.txt brcm/brcmfmac43455-sdio.acepc-t8.txt brcm/brcmfmac43455-sdio.raspberrypi,3-model-a-plus.txt brcm/brcmfmac4356-sdio.khadas,vim2.txt brcm/brcmfmac4356-sdio.vamrs,rock960.txt brcm/brcmfmac43012-sdio.bin brcm/brcmfmac43012-sdio.clm_blob brcm/brcmfmac43430-sdio.clm_blob brcm/brcmfmac43455-sdio.clm_blob brcm/brcmfmac4354-sdio.clm_blob brcm/brcmfmac4356-pcie.clm_blob brcm/brcmfmac4356-sdio.clm_blob brcm/brcmfmac43570-pcie.clm_blob brcm/brcmfmac4373-sdio.clm_blob i915/adlp_guc_62.0.3.bin i915/bxt_guc_62.0.0.bin i915/cml_guc_62.0.0.bin i915/ehl_guc_62.0.0.bin i915/glk_guc_62.0.0.bin i915/icl_guc_62.0.0.bin i915/kbl_guc_62.0.0.bin i915/rkl_dmc_ver2_03.bin i915/skl_guc_62.0.0.bin i915/tgl_dmc_ver2_12.bin i915/tgl_guc_62.0.0.bin i915/tgl_huc_7.9.3.bin iwlwifi-Qu-b0-hr-b0-66.ucode iwlwifi-Qu-b0-jf-b0-66.ucode iwlwifi-Qu-c0-hr-b0-66.ucode iwlwifi-QuZ-a0-hr-b0-66.ucode iwlwifi-QuZ-a0-jf-b0-66.ucode iwlwifi-cc-a0-66.ucode iwlwifi-ty-a0-gf-a0-66.ucode mellanox/mlxsw_spectrum-13.2008.2406.mfa2 mellanox/mlxsw_spectrum2-29.2008.2406.mfa2 mellanox/mlxsw_spectrum3-30.2008.2406.mfa2 nvidia/tegra194/vic.bin rtl_bt/rtl8821a_config.bin
[Kernel-packages] [Bug 1962515] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.29 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1962515 Title: Intermittent AX211 iwlwifi RT ucode init failed -110 at boot Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Won't Fix Status in linux source package in Impish: New Status in linux-firmware source package in Impish: New Status in linux-oem-5.14 source package in Impish: New Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] AX211 might fail to load -64 firmware on some platforms. iwlwifi :00:14.3: Failed to start RT ucode: -110 [Fix] This can only be fixed in the firmware, and currently v5.14 kernel has FW API 64, v5.15 has 66 and only v5.16 or above has 67. [Test Case] Run checkbox reboot stress tests to try trigger this issue: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] The source commit originally contains 67 fw for several models, and yet AX211, which taks iwlwifi-so-a0-gf-a0-*.ucode and its corresponding pnvm file, is the only known problematic model affected. This pull request imports only the needed files to eliminate the possibility of regression as possible. == original bug report == [ 5.675835] iwlwifi :00:14.3: enabling device ( -> 0002) [ 5.693214] iwlwifi :00:14.3: api flags index 2 larger than supported by driver [ 5.693277] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.25 [ 5.698065] iwlwifi :00:14.3: loaded firmware version 64.97bbee0a.0 so-a0-gf-a0-64.ucode op_mode iwlmvm [ 5.933114] iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6E AX211 160MHz, REV=0x370 [ 6.101350] iwlwifi :00:14.3: loaded PNVM version 0x4b50f925 [ 6.113388] iwlwifi :00:14.3: Detected RF GF, rfid=0x2010d000 [ 6.181309] iwlwifi :00:14.3: base HW address: 7c:50:79:c9:29:67 [ 6.201398] iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0 [ 7.396811] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x71f7, CPU2 Status: 0xb03 [ 7.396859] iwlwifi :00:14.3: UMAC PC: 0xc0081906 [ 7.396912] iwlwifi :00:14.3: LMAC PC: 0x1541c [ 7.396914] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 7.399116] iwlwifi :00:14.3: Loaded firmware version: 64.97bbee0a.0 so-a0-gf-a0-64.ucode [ 7.399119] iwlwifi :00:14.3: 0x | ADVANCED_SYSASSERT [ 7.399121] iwlwifi :00:14.3: 0x | trm_hw_status0 [ 7.399123] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 7.399124] iwlwifi :00:14.3: 0x | branchlink2 [ 7.399125] iwlwifi :00:14.3: 0x | interruptlink1 [ 7.399127] iwlwifi :00:14.3: 0x | interruptlink2 [ 7.399128] iwlwifi :00:14.3: 0x | data1 [ 7.399129] iwlwifi :00:14.3: 0x | data2 [ 7.399130] iwlwifi :00:14.3: 0x | data3 [ 7.399132] iwlwifi :00:14.3: 0x | beacon time [ 7.399133] iwlwifi :00:14.3: 0x | tsf low [ 7.399134] iwlwifi :00:14.3: 0x | tsf hi [ 7.399135] iwlwifi :00:14.3: 0x | time gp1 [ 7.399136] iwlwifi :00:14.3: 0x | time gp2
[Kernel-packages] [Bug 1963614] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.29 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1963614 Title: mt7921e device disappear after warm boot stress Status in HWE Next: New Status in OEM Priority Project: New 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 Jammy: Fix Released Bug description: [SRU Justification] [Impact] mt7921e may not appear in the bus enumeration during warm boot stress tests. [Fix] This can only be fixed in the firmware. [Test Case] Run checkbox reboot stress tests to try trigger this issue: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] While this backports proprietary fw blob, it may bring driver compatibility issues we cannot know in the first place. Jammy has these already, so only Focal (for oem-5.14) is nominated. We don't have mt7921e hardware v2.1 support in Impish 5.13 kernel. == original bug report == [Summary] mt7921 wlan device disappear after warm reset, can be recovered by cold boot. [Reproduce Steps] 1. do warm boot stress 100 times 2. check wifi function after stress finished 3. wifi has no function and mt7921e device disappeared [Results] Expected: wifi works normally Actual: wifi broken To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1963614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.29 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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 1964305] Re: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works)
Confirmed in Nvidia 510.54 too, and booting kernel 5.15.0-18-generic avoids the issue. ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1964305 Title: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Steps to reproduce: 1. Boot Ubuntu. 2. Press Ctrl+Alt+F4. Expected: VT to be displayed Observed: Monitor turns off. Notes: * This failure only happens in 5.15.0-22-generic. Kernel version 5.15.0-18-generic works fine. * I am currently using the nvidia-470 driver in case that's relevant. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-22-generic 5.15.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Mar 9 14:33:12 2022 InstallationDate: Installed on 2021-11-05 (123 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964305] Re: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works)
The problem is reproducible with Nvidia driver 510.54, too. ** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1964305 Title: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Steps to reproduce: 1. Boot Ubuntu. 2. Press Ctrl+Alt+F4. Expected: VT to be displayed Observed: Monitor turns off. Notes: * This failure only happens in 5.15.0-22-generic. Kernel version 5.15.0-18-generic works fine. * I am currently using the nvidia-470 driver in case that's relevant. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-22-generic 5.15.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Mar 9 14:33:12 2022 InstallationDate: Installed on 2021-11-05 (123 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964305] Re: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works)
I will test with Nvidia-510 soon... Maybe also relevant: I am using a GT 1030 which is closely related to your GTX 1060. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1964305 Title: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Steps to reproduce: 1. Boot Ubuntu. 2. Press Ctrl+Alt+F4. Expected: VT to be displayed Observed: Monitor turns off. Notes: * This failure only happens in 5.15.0-22-generic. Kernel version 5.15.0-18-generic works fine. * I am currently using the nvidia-470 driver in case that's relevant. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-22-generic 5.15.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Mar 9 14:33:12 2022 InstallationDate: Installed on 2021-11-05 (123 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964440] Re: 5.15.0-22: No console displayed on EFI systems
** Description changed: DISCLAIMER: This is my second-ever bug report. Apologies in advance for any missing or inaccurate info. I am willing to troubleshoot and supply more/better info as needed. PROBLEM DESCRIPTION: After upgrading the kernel on my Ubuntu 22.04 Server test system from 5.15.0-18 to 5.15.0-22, I see absolutely no console output on my display past the grub menu. I can give the system a few seconds to finish booting, log in blindly and watch the activity LEDs on e.g. the network interface as i run a ping or similar. - I can also log in remotely via SSH. So the system definitely does boot. But my display shows no output. + I can also log in remotely via SSH, and/or use a serial console. So the system definitely does boot. But my actual display/screen shows no console output. ENVIRONMENT: (Output gathered via SSH while display was showing no output) testuser@testserver:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy testuser@testserver:~$ uname -a Linux testserver 5.15.0-22-generic #22-Ubuntu SMP Tue Feb 8 10:16:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This was initially discovered on an Ubuntu Server VM running in EFI mode on VirtualBox 6.1.32. System was installed with the daily 'jammy-live-server-amd64.iso' image from 2022-03-07, fully upgraded as of 2022-03-10. Switching Graphics Controller in Virtualbox does not help, nor does 'nomodeset' or 'noacpi'. I am able to reproduce the issue on real hardware and with different physical graphics cards. Similar symptoms can also be observed in Ubuntu Desktop (still using EFI) by attempting to switch to tty with CTRL + ALT + F[3-6], or by taking note of the missing plymouth screen during boot. Systems installed/booted in legacy BIOS mode (both Server and Desktop) do not appear to be affected. I have tried reinstalling on both virtual and hardware platforms, with same result before and after upgrading the kernel. HOW TO REPRODUCE - Ubuntu Server: - Boot existing Ubuntu Server EFI installation with 5.15.0-18 and observe console output - Set GRUB_TIMEOUT_STYLE=menu and GRUB_TIMEOUT=10 in /etc/default/grub (to enable rollback) - Run update-grub - Run sudo apt full-upgrade and watch linux version 5.15.0-22 get installed - Reboot and observe your display (no console output will be shown after grub) HOW TO REPRODUCE - Ubuntu Desktop: - Download Ubuntu 22.04 Desktop daily ISO - Write ISO to USB - Boot from USB in EFI mode - Install system - Run sudo apt full-upgrade and upgrade linux* to kernel 5.15.0-22 - Reboot and observe missing plymouth screen during boot - Wait for graphical login screen to appear - Press CTRL + ALT + F[3-6] (screen will go black and/or freeze) - Press CTRL + ALT + F1 (screen will unfreeze and/or return to gdm greeter) WORKAROUNDS: If you still have 5.15.0-18 or earlier installed, select it in Grub. and/or install mainline kernel 5.16.11+ (for testing only - will not work if you have Secure Boot enabled). Alternatively, re-install/convert/boot your system to boot in legacy BIOS mode. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220307) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=8fe50fbe-79d7-47a9-ad2f-ff36ddc1fe54 ro ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill:
[Kernel-packages] [Bug 1964305] Re: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1964305 Title: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Steps to reproduce: 1. Boot Ubuntu. 2. Press Ctrl+Alt+F4. Expected: VT to be displayed Observed: Monitor turns off. Notes: * This failure only happens in 5.15.0-22-generic. Kernel version 5.15.0-18-generic works fine. * I am currently using the nvidia-470 driver in case that's relevant. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-22-generic 5.15.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Mar 9 14:33:12 2022 InstallationDate: Installed on 2021-11-05 (123 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964384] Re: linux-image-5.15.0-22-generic does not boot
This seems to be a related bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964305 [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964305] Re: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works)
Is this related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384, no kernel log displayed while booting, no possibility to enter decryption password? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1964305 Title: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Steps to reproduce: 1. Boot Ubuntu. 2. Press Ctrl+Alt+F4. Expected: VT to be displayed Observed: Monitor turns off. Notes: * This failure only happens in 5.15.0-22-generic. Kernel version 5.15.0-18-generic works fine. * I am currently using the nvidia-470 driver in case that's relevant. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-22-generic 5.15.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Mar 9 14:33:12 2022 InstallationDate: Installed on 2021-11-05 (123 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964384] Re: linux-image-5.15.0-22-generic does not boot
** Attachment added: "dmesg for 5.15.0-22-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+attachment/5567644/+files/dmesg.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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964455] [NEW] Broadcom wifi does not connect with kernel 5.13
Public bug reported: It seems a DKMS patch is need for Ubuntu 20.04.4 and kernel 5.13 Tested 6.30.223.271+bdcom-0ubuntu7~20.04.3 on Imac 7.1 ( bcm4321): - Shows the Wifi networks - fail to get a DHCP answer even on open networks Works fine with 5.4. ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1964455 Title: Broadcom wifi does not connect with kernel 5.13 Status in bcmwl package in Ubuntu: New Bug description: It seems a DKMS patch is need for Ubuntu 20.04.4 and kernel 5.13 Tested 6.30.223.271+bdcom-0ubuntu7~20.04.3 on Imac 7.1 ( bcm4321): - Shows the Wifi networks - fail to get a DHCP answer even on open networks Works fine with 5.4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1964455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964286] Re: Intel AX201 [8086:a0f0] subsys [8086:4070] iwlwifi microcode crash after updating to 5.14.0-1027-oem
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Triaged -- 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/1964286 Title: Intel AX201 [8086:a0f0] subsys [8086:4070] iwlwifi microcode crash after updating to 5.14.0-1027-oem Status in OEM Priority Project: Triaged Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Bug description: Mar 09 10:33:40 MDAT-DVT2-D8 kernel: FAT-fs (sda1): unable to read boot sector to mark fs as dirty Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Start IWL Error Log Dump: Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Transport status: 0x004B, valid: 6 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Loaded firmware version: 63.c04f3485.0 QuZ-a0-hr-b0-63.ucode Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x0FAD | ADVANCED_SYSASSERT Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0xA210 | trm_hw_status0 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x | trm_hw_status1 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004CAD42 | branchlink2 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004C17C6 | interruptlink1 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004C17C6 | interruptlink2 ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1027-oem 5.14.0-1027.30 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 9 11:13:53 2022 InstallationDate: Installed on 2021-10-19 (140 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964286] Re: Intel AX201 [8086:a0f0] subsys [8086:4070] iwlwifi microcode crash after updating to 5.14.0-1027-oem
** Tags added: oem-priority -- 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/1964286 Title: Intel AX201 [8086:a0f0] subsys [8086:4070] iwlwifi microcode crash after updating to 5.14.0-1027-oem Status in OEM Priority Project: Triaged Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Bug description: Mar 09 10:33:40 MDAT-DVT2-D8 kernel: FAT-fs (sda1): unable to read boot sector to mark fs as dirty Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Start IWL Error Log Dump: Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Transport status: 0x004B, valid: 6 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Loaded firmware version: 63.c04f3485.0 QuZ-a0-hr-b0-63.ucode Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x0FAD | ADVANCED_SYSASSERT Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0xA210 | trm_hw_status0 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x | trm_hw_status1 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004CAD42 | branchlink2 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004C17C6 | interruptlink1 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004C17C6 | interruptlink2 ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1027-oem 5.14.0-1027.30 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 9 11:13:53 2022 InstallationDate: Installed on 2021-10-19 (140 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964384] Re: linux-image-5.15.0-22-generic does not boot
While nothing is shown on the display Linux seems still be waiting for keyboard input of the description key. If I type it in the system boots and sddm is the first thing displayed. The question remains why the KDE input mask for the encryption mask is not displayed and pressing the ESC key does not show the terminal style input. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964440] Re: 5.15.0-22: No console displayed on EFI systems
** Description changed: DISCLAIMER: This is my second-ever bug report. Apologies in advance for any missing or inaccurate info. I am willing to troubleshoot and supply more/better info as needed. PROBLEM DESCRIPTION: After upgrading the kernel on my Ubuntu 22.04 Server test system from 5.15.0-18 to 5.15.0-22, I see absolutely no console output on my display past the grub menu. I can give the system a few seconds to finish booting, log in blindly and watch the activity LEDs on e.g. the network interface as i run a ping or similar. I can also log in remotely via SSH. So the system definitely does boot. But my display shows no output. ENVIRONMENT: (Output gathered via SSH while display was showing no output) testuser@testserver:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy testuser@testserver:~$ uname -a Linux testserver 5.15.0-22-generic #22-Ubuntu SMP Tue Feb 8 10:16:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This was initially discovered on an Ubuntu Server VM running in EFI mode on VirtualBox 6.1.32. System was installed with the daily 'jammy-live-server-amd64.iso' image from 2022-03-07, fully upgraded as of 2022-03-10. Switching Graphics Controller in Virtualbox does not help, nor does 'nomodeset' or 'noacpi'. I am able to reproduce the issue on real hardware and with different physical graphics cards. Similar symptoms can also be observed in Ubuntu Desktop (still using EFI) by attempting to switch to tty with CTRL + ALT + F[3-6], or by taking note of the missing plymouth screen during boot. Systems installed/booted in legacy BIOS mode (both Server and Desktop) do not appear to be affected. I have tried reinstalling on both virtual and hardware platforms, with same result before and after upgrading the kernel. HOW TO REPRODUCE - Ubuntu Server: - Boot existing Ubuntu Server EFI installation with 5.15.0-18 and observe console output - Set GRUB_TIMEOUT_STYLE=menu and GRUB_TIMEOUT=10 in /etc/default/grub (to enable rollback) - Run update-grub - Run sudo apt full-upgrade and watch linux version 5.15.0-22 get installed - Reboot and observe your display (no console output will be shown after grub) HOW TO REPRODUCE - Ubuntu Desktop: - Download Ubuntu 22.04 Desktop daily ISO - Write ISO to USB - Boot from USB in EFI mode - Install system - Run sudo apt full-upgrade and upgrade linux* to kernel 5.15.0-22 - Reboot and observe missing plymouth screen during boot - Wait for graphical login screen to appear - Press CTRL + ALT + F[3-6] (screen will go black and/or freeze) - Press CTRL + ALT + F1 (screen will unfreeze and/or return to gdm greeter) WORKAROUNDS: If you still have 5.15.0-18 or earlier installed, select it in Grub. - OR install mainline kernel 5.16.11+ (for testing/recovery only). - OR boot/convert your system to boot in legacy BIOS mode. + and/or install mainline kernel 5.16.11+ (for testing only - will not work if you have Secure Boot enabled). + Alternatively, re-install/convert/boot your system to boot in legacy BIOS mode. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220307) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=8fe50fbe-79d7-47a9-ad2f-ff36ddc1fe54 ro ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Error: [Errno 2] No such file or
