[Kernel-packages] [Bug 1952385] Re: Fix missing external headset after resume problem for Cirrus CS8409 sound driver
** Tags added: oem-priority originate-from-1951215 somerville -- 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/1952385 Title: Fix missing external headset after resume problem for Cirrus CS8409 sound driver Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: Incomplete Status in linux-oem-5.13 source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: New Bug description: [SRU Justification] [Impact] On some platforms with Cirrus CS8409 audio codec, the external headset will fail to be detected after system resume. [Fix] Cirrus released a fix and send it upstream for approval. It's trying to schedule a harmless delayed work to do jack detection to reflect the real power state after resume. [Test] Plug-in an external headset in front headset port, suspend/resume the system then check whether the headset function works as expected. [Where problem could occur] Low. It only affect the platforms with Cirrus codec CS8409 which used to have problem. == Original Bug Description == [Summary] System can't detect external headset after suspend [Steps to reproduce] 1. install manifest and boot into OS 2. plug-in an external headset in front headset port 3. un-plug external headset 4. suspend system 5. resume system from suspend 6. plug-in an external headset [Expected result] System could detect external headset after suspend [Actual result] System can't detect external headset after suspend [Failure rate] 3/3 [Additional information] CID: 202110-29567 SKU: DLPV-SFF-DVT-C1 Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X152 system-manufacturer: Dell Inc. system-product-name: Vostro 3710 bios-version: 0.13.73 CPU: 12th Gen Intel(R) Core(TM) i7-12700 (20x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4680] (rev 0c) kernel-version: 5.13.0-1019-oem [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952385] 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 1952385 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 ** Changed in: linux (Ubuntu Focal) 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/1952385 Title: Fix missing external headset after resume problem for Cirrus CS8409 sound driver Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: Incomplete Status in linux-oem-5.13 source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: New Bug description: [SRU Justification] [Impact] On some platforms with Cirrus CS8409 audio codec, the external headset will fail to be detected after system resume. [Fix] Cirrus released a fix and send it upstream for approval. It's trying to schedule a harmless delayed work to do jack detection to reflect the real power state after resume. [Test] Plug-in an external headset in front headset port, suspend/resume the system then check whether the headset function works as expected. [Where problem could occur] Low. It only affect the platforms with Cirrus codec CS8409 which used to have problem. == Original Bug Description == [Summary] System can't detect external headset after suspend [Steps to reproduce] 1. install manifest and boot into OS 2. plug-in an external headset in front headset port 3. un-plug external headset 4. suspend system 5. resume system from suspend 6. plug-in an external headset [Expected result] System could detect external headset after suspend [Actual result] System can't detect external headset after suspend [Failure rate] 3/3 [Additional information] CID: 202110-29567 SKU: DLPV-SFF-DVT-C1 Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X152 system-manufacturer: Dell Inc. system-product-name: Vostro 3710 bios-version: 0.13.73 CPU: 12th Gen Intel(R) Core(TM) i7-12700 (20x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4680] (rev 0c) kernel-version: 5.13.0-1019-oem [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952385] [NEW] Fix missing external headset after resume problem for Cirrus CS8409 sound driver
Public bug reported: [SRU Justification] [Impact] On some platforms with Cirrus CS8409 audio codec, the external headset will fail to be detected after system resume. [Fix] Cirrus released a fix and send it upstream for approval. It's trying to schedule a harmless delayed work to do jack detection to reflect the real power state after resume. [Test] Plug-in an external headset in front headset port, suspend/resume the system then check whether the headset function works as expected. [Where problem could occur] Low. It only affect the platforms with Cirrus codec CS8409 which used to have problem. == Original Bug Description == [Summary] System can't detect external headset after suspend [Steps to reproduce] 1. install manifest and boot into OS 2. plug-in an external headset in front headset port 3. un-plug external headset 4. suspend system 5. resume system from suspend 6. plug-in an external headset [Expected result] System could detect external headset after suspend [Actual result] System can't detect external headset after suspend [Failure rate] 3/3 [Additional information] CID: 202110-29567 SKU: DLPV-SFF-DVT-C1 Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X152 system-manufacturer: Dell Inc. system-product-name: Vostro 3710 bios-version: 0.13.73 CPU: 12th Gen Intel(R) Core(TM) i7-12700 (20x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4680] (rev 0c) kernel-version: 5.13.0-1019-oem [Stage] Issue reported and logs collected right after it happened ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.13 (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/1952385 Title: Fix missing external headset after resume problem for Cirrus CS8409 sound driver Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: New Status in linux-oem-5.13 source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: New Bug description: [SRU Justification] [Impact] On some platforms with Cirrus CS8409 audio codec, the external headset will fail to be detected after system resume. [Fix] Cirrus released a fix and send it upstream for approval. It's trying to schedule a harmless delayed work to do jack detection to reflect the real power state after resume. [Test] Plug-in an external headset in front headset port, suspend/resume the system then check whether the headset function works as expected. [Where problem could occur] Low. It only affect the platforms with Cirrus codec CS8409 which used to have problem. == Original Bug Description == [Summary] System can't detect external headset after suspend [Steps to reproduce] 1. install manifest and boot into OS 2. plug-in an external headset in front headset port 3. un-plug external headset 4. suspend system 5. resume system from suspend 6. plug-in an external headset [Expected
[Kernel-packages] [Bug 1952375] Re: Blutooth headset not taking
Please tell us: 1. The exact model of headset. 2. Whether the Bluetooth pairing is stable and just audio not working, or the whole pairing is lost. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1952375 Title: Blutooth headset not taking Status in bluez package in Ubuntu: Incomplete Bug description: Blutooth Headset problem ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 26 01:09:24 2021 InstallationDate: Installed on 2020-07-22 (491 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 003: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-54 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=c9b8ebcf-747e-454e-8dfb-68b609629c3a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to impish on 2021-10-15 (41 days ago) dmi.bios.date: 08/01/2019 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Doc_WC dmi.board.vendor: CML dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd08/01/2019:br1.11:efr1.6:svnAcer:pnAspireA515-54:pvrV1.11:rvnCML:rnDoc_WC:rvrV1.11:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 84:FD:D1:EA:D2:2D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:151467 acl:66 sco:0 events:20824 errors:0 TX bytes:13788724 acl:20413 sco:0 commands:299 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952375/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952217] Re: bluetoothd coredumps from double free on connection of headset
Please also check for crash reports so we can identify *which* double- free this is: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1952217 Title: bluetoothd coredumps from double free on connection of headset Status in bluez package in Ubuntu: Incomplete Bug description: Problem: Since the security updates on 2021-11-23 connecting my headset causes bluetoothd to crash, which drops all the other connections. Expected: Headset connects and works as it has done previously. ❯ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ❯ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.4 Candidate: 5.53-0ubuntu3.4 Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for the LDAC codecs for this headset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952217] Re: bluetoothd coredumps from double free on connection of headset
Thanks for the bug report. It appears there have been a few double-free fixes in BlueZ over the years. Please try the latest version by live booting Ubuntu 22.04 from USB: http://cdimage.ubuntu.com/daily- live/current/ ** Tags added: focal ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1952217 Title: bluetoothd coredumps from double free on connection of headset Status in bluez package in Ubuntu: Incomplete Bug description: Problem: Since the security updates on 2021-11-23 connecting my headset causes bluetoothd to crash, which drops all the other connections. Expected: Headset connects and works as it has done previously. ❯ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ❯ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.4 Candidate: 5.53-0ubuntu3.4 Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for the LDAC codecs for this headset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 989646] Re: package linux-image-3.2.0-24-generic 3.2.0-24.37 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2
3.2 EOL ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/989646 Title: package linux-image-3.2.0-24-generic 3.2.0-24.37 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Won't Fix Bug description: As an experiment, I loaded version 11.10 Desktop onto to a 8GB USB key using pendrivelinux.com's Universal USB Installer (for WinXP) with the 'Persistent' file size set to 4GB (leaving 4GB for the operating system/image). I then upgraded Ubuntu to version 12.04 LTS using the 'Updates Available' from the system drop-down menu. I wasn't sure this would work...but AFAICT, it works! BTW: all this was done on a Panasonic CF-29 MK3 w/touchscreen. The only thing that doesn't quite work right is the touchscreen, which needs calibration, but I can't find a way to do it - it's not important. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-24-generic 3.2.0-24.37 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4481 F pulseaudio Card0.Amixer.info: Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with STAC9750,51 at irq 9' Mixer name : 'SigmaTel STAC9750,51' Components : 'AC97a:83847650' Controls : 33 Simple ctrls : 22 CasperVersion: 1.315 CurrentDmesg: [ 82.768042] eth0: no IPv6 routers present [ 95.472059] eth1: no IPv6 routers present Date: Fri Apr 27 08:08:04 2012 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 2 LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MachineType: Matsushita Electric Industrial Co.,Ltd. CF-29HTM50BM PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/hostname.seed boot=casper persistent initrd=/casper/initrd.lz splash -- BOOT_IMAGE=/casper/vmlinuz PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 1.99-21ubuntu3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-3.2.0-24-generic 3.2.0-24.37 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to precise on 2012-04-27 (0 days ago) dmi.bios.date: 12/08/2004 dmi.bios.vendor: Phoenix Technologies K.K. dmi.bios.version: V3.00L11 dmi.board.name: CF29-3 dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd. dmi.board.version: 001 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd. dmi.chassis.version: 001 dmi.modalias: dmi:bvnPhoenixTechnologiesK.K.:bvrV3.00L11:bd12/08/2004:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-29HTM50BM:pvr001:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF29-3:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001: dmi.product.name: CF-29HTM50BM dmi.product.version: 001 dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/989646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951784] Re: Can't read/write SD card after running CPU offline test in 5.11.0 and 5.13.0
https://lkml.org/lkml/2021/11/25/964 ** Changed in: linux (Ubuntu) Status: In Progress => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1951784 Title: Can't read/write SD card after running CPU offline test in 5.11.0 and 5.13.0 Status in linux package in Ubuntu: Triaged Status in linux-signed-hwe-5.11 package in Ubuntu: New Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: [Summary] I'm reviewing SRU testing on Dell XPS 13 7390(201906-27131) and mediacard test always fails. I found that after CPU offline test, I can't read/write SD card. After checking dmesg, I got those error msgs. [ 232.577510] __common_interrupt: 7.34 No irq handler for vector [ 234.354327] mmc0: error -110 doing runtime resume I found the same issue on Dell Precision 3551(202002-27718) and Dell Precision 5530(201807-26342) in 5.13.0-21 and 5.11.0-36 Before I didn't think it's a bug since I re-run mediacard test then it's pass. But this cycle there are more systems failed to the test, I just started digging into that. [Step to reproduce] 1. install ubuntu-20.04.2/ubuntu-21.10/ubuntu-21.04 2. sudo apt update; sudo apt dist-upgrade -y 3. run cpu offline test via checkbox-cli or execute following command for ((i=1;i<=$(nproc --all) -1;i++));do sudo chcpu -d $i;sudo chcpu -e $i; done; cd $mount_point_of_sd_card sudo dd if=/dev/urandom of=test bs=1M count=10 [Expected result] Can read/write SD card. [Actual result] Can't read/write SD card. [Failure rate] 5/5 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 22 01:28:59 2021 InstallationDate: Installed on 2020-08-03 (475 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952375] [NEW] Blutooth headset not taking
Public bug reported: Blutooth Headset problem ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 26 01:09:24 2021 InstallationDate: Installed on 2020-07-22 (491 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 003: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-54 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=c9b8ebcf-747e-454e-8dfb-68b609629c3a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to impish on 2021-10-15 (41 days ago) dmi.bios.date: 08/01/2019 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Doc_WC dmi.board.vendor: CML dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd08/01/2019:br1.11:efr1.6:svnAcer:pnAspireA515-54:pvrV1.11:rvnCML:rnDoc_WC:rvrV1.11:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer hciconfig: hci0: Type: Primary Bus: USB BD Address: 84:FD:D1:EA:D2:2D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:151467 acl:66 sco:0 events:20824 errors:0 TX bytes:13788724 acl:20413 sco:0 commands:299 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1952375 Title: Blutooth headset not taking Status in bluez package in Ubuntu: New Bug description: Blutooth Headset problem ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 26 01:09:24 2021 InstallationDate: Installed on 2020-07-22 (491 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 003: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-54 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=c9b8ebcf-747e-454e-8dfb-68b609629c3a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to impish on 2021-10-15 (41 days ago) dmi.bios.date: 08/01/2019 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Doc_WC dmi.board.vendor: CML dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd08/01/2019:br1.11:efr1.6:svnAcer:pnAspireA515-54:pvrV1.11:rvnCML:rnDoc_WC:rvrV1.11:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 84:FD:D1:EA:D2:2D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:151467 acl:66 sco:0 events:20824 errors:0 TX bytes:13788724 acl:20413 sco:0 commands:299 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952375/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1951772] Re: post upgrade, no video after suspend
I don't think the computer is coming up at all after suspend? Commands typed blindly into an xterm window don't run and "systemctl suspend ; sleep 10 ; cp /var/log/dmesg FILE" in csh doesn't make a file after waking. -- 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/1951772 Title: post upgrade, no video after suspend Status in linux package in Ubuntu: Confirmed Bug description: Suspend on desktop worked fine before upgrade to impish. Post upgrade, coming up after suspend leaves monitors with no signal from nvidia graphics card. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: XFCE Date: Sun Nov 21 20:47:15 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/tcsh SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to impish on 2021-11-21 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-gkeop-5.4/5.4.0.1027.28~18.04.28)
All autopkgtests for the newly accepted linux-meta-gkeop-5.4 (5.4.0.1027.28~18.04.28) for bionic have finished running. The following regressions have been reported in tests triggered by the package: kpatch/0.5.0-0ubuntu1.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (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/bionic/update_excuses.html#linux-meta-gkeop-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949516] Re: require CAP_NET_ADMIN to attach N_HCI ldisc
ldattach HCI /dev/tty That command works on 4.15.0-162, and fails with EPERM on 4.15.0-163. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1949516 Title: require CAP_NET_ADMIN to attach N_HCI ldisc Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.10 source package in Jammy: Invalid Bug description: [Impact] Any unprivileged user can attach N_HCI ldisc and send packets coming from a virtual controller by using PTYs. This exposes attack surface on systems where bluetooth is not needed or even allow local attacks that would otherwise require physical proximity. [Test case] Try attaching N_HCI ldisc to a tty. ldattach HCI /dev/tty [Potential regression] Users who rely on programs using N_HCI line discipline in order to emulate or proxy a bluetooth controller will require privilege they may not have. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788578] Re: Some test in ubuntu_bpf test_verifier failed on i386 Bionic kernel
5 tests failed with 4.15.0-162. ALL pass with 4.15.0-163. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788578 Title: Some test in ubuntu_bpf test_verifier failed on i386 Bionic kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Narrow loads for bpf_perf_event_data is not possible on 32-bit arches. [Test case] Run the bpf test_verifier. [Potential regression] Loading sample_period of bpf_perf_event_data may fail. Unaligned access may lead to processor exceptions on some architectures. == This issue was only spotted on i386 Bionic kernel. #146/p unpriv: spill/fill of different pointers ldx FAIL Unexpected error message! 0: (bf) r6 = r10 1: (07) r6 += -8 2: (15) if r1 == 0x0 goto pc+3 R1=ctx(id=0,off=0,imm=0) R6=fp-8 R10=fp0 3: (bf) r2 = r10 4: (07) r2 += -76 5: (7b) *(u64 *)(r6 +0) = r2 6: (55) if r1 != 0x0 goto pc+1 R1=ctx(id=0,off=0,imm=0) R2=fp-76 R6=fp-8 R10=fp0 fp-8=fp 7: (7b) *(u64 *)(r6 +0) = r1 8: (79) r1 = *(u64 *)(r6 +0) 9: (79) r1 = *(u64 *)(r1 +68) #352/p check bpf_perf_event_data->sample_period byte load permitted FAIL Failed to load prog 'Permission denied'! 0: (b7) r0 = 0 1: (71) r0 = *(u8 *)(r1 +68) invalid bpf_context access off=68 size=1 #353/p check bpf_perf_event_data->sample_period half load permitted FAIL Failed to load prog 'Permission denied'! 0: (b7) r0 = 0 1: (69) r0 = *(u16 *)(r1 +68) invalid bpf_context access off=68 size=2 #354/p check bpf_perf_event_data->sample_period word load permitted FAIL Failed to load prog 'Permission denied'! 0: (b7) r0 = 0 1: (61) r0 = *(u32 *)(r1 +68) invalid bpf_context access off=68 size=4 #355/p check bpf_perf_event_data->sample_period dword load permitted FAIL Failed to load prog 'Permission denied'! 0: (b7) r0 = 0 1: (79) r0 = *(u64 *)(r1 +68) invalid bpf_context access off=68 size=8 Summary: 708 PASSED, 5 FAILED ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: User Name 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 23 08:23 seq crw-rw 1 root audio 116, 33 Aug 23 08:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Thu Aug 23 08:41:26 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1788578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952356] [NEW] [EHL][TGL][ADL] PMU support
Public bug reported: [Impact] The patches enable PMU support [Fix] Intel provides a list of patches to provide Linux perf supports [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel ElkhartLake/TigerLake/AdlerLake. Further testing will be required. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Alex Hung (alexhung) Status: Triaged ** Tags: intel oem-priority originate-from-1943541 ** Tags added: intel oem-priority originate-from-1943541 ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Alex Hung (alexhung) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952356 Title: [EHL][TGL][ADL] PMU support Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] The patches enable PMU support [Fix] Intel provides a list of patches to provide Linux perf supports [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel ElkhartLake/TigerLake/AdlerLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952356/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950443] Re: Missing nvidia-driver-460 Transitional package for nvidia-driver-470
** Also affects: nvidia-drivers-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/1950443 Title: Missing nvidia-driver-460 Transitional package for nvidia-driver-470 Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I cannot correctly upgrade from nvidia-driver-460 to nvidia-driver-470 because of missed nvidia-driver-460 Transitional package for nvidia-driver-470. The problem exists on Ubuntu 18.04 and 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1950443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952246] Re: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests
Since it seems to depend on the host it likely is the chip, so here some info about that. This is the bad system. ** Attachment added: "cpuinfo-badsystem.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952246/+attachment/5543370/+files/cpuinfo-badsystem.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/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
[Kernel-packages] [Bug 1952246] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543353/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1952246] Re: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests
Now I have completed attaching (apport-collect) data of both: - Host (hostname: node-horse) - first level guest (hostname: f) -- 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/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP
[Kernel-packages] [Bug 1952246] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543349/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1952246] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543352/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1952246] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543347/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP
[Kernel-packages] [Bug 1952246] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543355/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType:
[Kernel-packages] [Bug 1952246] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543351/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory:
[Kernel-packages] [Bug 1952246] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543368/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1952246] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543364/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1952246] Re: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests
Now that all data is in place I set it to confirmed to silence the bots. @Kernel people - is this known, if so where? If it is not known what else would you need here? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or
[Kernel-packages] [Bug 1952246] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543363/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory:
[Kernel-packages] [Bug 1952246] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543369/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1952246] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543358/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1952246] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543356/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1952246] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543366/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1952246] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543365/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1952246] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543359/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP
[Kernel-packages] [Bug 1952246] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543350/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1952246] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543367/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType:
[Kernel-packages] [Bug 1952246] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543348/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1952246] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543361/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1952246] Re: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests
Since it seems to depend on the host it likely is the chip, so here some info about that. This is the good system. ** Attachment added: "cpuinfo-goodsystem.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952246/+attachment/5543371/+files/cpuinfo-goodsystem.txt ** 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/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser',
[Kernel-packages] [Bug 1952246] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543360/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1952246] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543357/+files/acpidump.txt ** Description changed: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=c941b173-e6b5-485a-a02b-8d966b8d3c73 ro --- console=ttyS1,115200
[Kernel-packages] [Bug 1952246] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543354/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1952246] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543362/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1952246] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543344/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1952246] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543345/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP
[Kernel-packages] [Bug 1952246] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543346/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1952246] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1952246/+attachment/5543343/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952246 Title: 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests Status in linux package in Ubuntu: Confirmed Bug description: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP
[Kernel-packages] [Bug 1952246] [NEW] 5.13 (I/J/F-HWE) Hosts crash 5.4 (F) 1st+2nd level KVM guests
Public bug reported: Issue - on start the second level Guest enters paused state due to a KVM fail: $ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log ... KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=04 66 41 eb f1 66 83 c9 ff 66 89 c8 66 5b 66 5e 66 5f 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Warning, this message is rather generic you will find many very different issues in the *net - I think the kernel Team has to check commints between the versions I identified or recreate it (instructions below). ubuntu@focal-kvm:~$ virsh start focal-2nd-lvm-test Domain focal-2nd-lvm-test started ubuntu@focal-kvm:~$ virsh list Id Name State --- 2focal-2nd-lvm-test paused OS: - Jammy Host / Focal 1st level Guest / Focal 2nd level Guest - Bionic 1st level guest worked fine - Jammy 1st level Guest worked fine Guests: - First level Guest Focal with cpu host-passthrough - Second level Focal with basic cpu model qemu64 - Otherwise as uvtool-libvirt default provides it The real CPU is an older: Model name:Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz CPU family: 6 Model: 63 Trying different kernel versions H 5.13.0-19 G1 generic5.4.0-90 => Fail H 5.13.0-19 G1 hwe-20.04-edge 5.13.0.22.22~20.04.9 => Work H 5.13.0-19 G1 hwe-20.04 5.11.0-41 => Work H 5.13.0-19 G1 Proposed 5.4.0-91 => Fail H 5.13.0-19 G1 Release5.4.0.26.32 => Fail I redeployed Focal on the Host and checked this as well as a 5.13 hwe-20.04-edge kernel. Focal Host (qemu/libvirt and such are now much different) now: (The redeploy also clears any unexpected old config that might cause this) H 5.4.0-90 G1 generic5.4.0-90 => works H 5.4.0-90 G1 generic5.13.0-21.21 => works H 5.13.0-21.21 G1 generic5.4.0-90 => fails H 5.13.0-21.21 G1 generic5.13.0-21.21 => works So it is the same pattern everywhere, "BareMetal 5.13, first level 5.4 can not start second level guest anymore" Repro steps: 1. Take a Impish/Jammy Host with 5.13 or Focal with HWE 5.13 kernel 2. create first level Focal (5.4) uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --memory 8192 --cpu 4 --host-passthrough --password=ubuntu f1 release=focal arch=amd64 label=daily 3. In there create a second level focal guest uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=focal ssh-keygen uvt-kvm create --password=ubuntu f2 release=focal arch=amd64 label=daily That guest will crash on start then as reported above. We have cross checked this on a laptop with Jammy, there it worked fine. Biggest releated difference would be in the used Hardware, therefore I'll attach details about the chips. The crashing system is internal, logins/VPNs can be granted if not reproducible elsehwere. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 25 14:53 seq crw-rw 1 root audio 116, 33 Nov 25 14:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=c941b173-e6b5-485a-a02b-8d966b8d3c73 ro --- console=ttyS1,115200 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-21-generic x86_64
[Kernel-packages] [Bug 1926439] Re: Dependencies conflicts breaks upgrade process
** Also affects: nvidia-drivers-ubuntu Importance: Undecided Status: New ** Also affects: unattended-upgrades Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1926439 Title: Dependencies conflicts breaks upgrade process Status in NVIDIA Drivers Ubuntu: New Status in unattended-upgrades: New Status in linux-restricted-modules package in Ubuntu: Confirmed Bug description: Latest updates of linux-restricted-modules breaks upgrade process, updates cannot be installed without removing nvidia modules for previous kernel version, unattended-upgrade cannot do that, as result we have broken system without nvidia driver ~# apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: linux-modules-nvidia-460-5.4.0-71-generic The following NEW packages will be installed: linux-modules-nvidia-460-5.4.0-72-generic linux-objects-nvidia-460-5.4.0-72-generic linux-signatures-nvidia-5.4.0-72-generic The following packages will be upgraded: libnvidia-cfg1-460 libnvidia-compute-460 libnvidia-compute-460:i386 libnvidia-decode-460 libnvidia-decode-460:i386 libnvidia-encode-460 libnvidia-encode-460:i386 libnvidia-extra-460 libnvidia-fbc1-460 libnvidia-fbc1-460:i386 libnvidia-gl-460 libnvidia-gl-460:i386 libnvidia-ifr1-460 libnvidia-ifr1-460:i386 linux-modules-nvidia-460-generic nvidia-compute-utils-460 nvidia-driver-460 nvidia-kernel-common-460 nvidia-kernel-source-460 nvidia-utils-460 xserver-xorg-video-nvidia-460 21 upgraded, 3 newly installed, 1 to remove and 0 not upgraded. Need to get 199 MB of archives. After this operation, 45.6 MB of additional disk space will be used. Do you want to continue? [Y/n] ~# apt show linux-modules-nvidia-460-5.4.0-71-generic Package: linux-modules-nvidia-460-5.4.0-71-generic Version: 5.4.0-71.79+1 Priority: optional Section: restricted/kernel Source: linux-restricted-modules Origin: Ubuntu Maintainer: Canonical Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 32.8 kB Depends: debconf (>= 0.5) | debconf-2.0, linux-image-5.4.0-71-generic | linux-image-unsigned-5.4.0-71-generic, linux-signatures-nvidia-5.4.0-71-generic (= 5.4.0-71.79+1), linux-objects-nvidia-460-5.4.0-71-generic (= 5.4.0-71.79+1), nvidia-kernel-common-460 (<= 460.56-1), nvidia-kernel-common-460 (>= 460.56) Download-Size: 7136 B APT-Manual-Installed: no APT-Sources: http://archive.pls.pbank.com.ua/ubuntu-current focal-updates/restricted amd64 Packages Description: Linux kernel nvidia modules for version 5.4.0-71 This dependencies should be removed to fix this problem: nvidia-kernel-common-460 (<= 460.56-1), nvidia-kernel-common-460 (>= 460.56) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1926439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950665] Re: Update the 470 NVIDIA driver to 470.86
** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-hirsute verification-needed-impish ** Tags added: block-proposed-bionic block-proposed-focal block-proposed-hirsute block-proposed-impish verification-done verification-done-bionic verification-done-focal verification-done-hirsute verification-done-impish -- 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/1950665 Title: Update the 470 NVIDIA driver to 470.86 Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Bug description: Update the 470 NVIDIA series in Bionic, Focal, Hirsute, and Impish. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470 == * New upstream release (LP: #1950665): - Fixed a regression which prevented DisplayPort and HDMI 2.1 variable refresh rate (VRR) G-SYNC Compatible monitors from functioning correctly in variable refresh rate mode, resulting in issues such as flickering. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1950665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948025] Re: Update the NVIDIA drivers October 2021
This bug was fixed in the package libnvidia-nscq-460 -
460.106.00-0ubuntu0.21.04.1
---
libnvidia-nscq-460 (460.106.00-0ubuntu0.21.04.1) hirsute; urgency=medium
* New upstream release (LP: #1948025).
* debian/rules{.defs}:
- Switch to new tarball format.
- Change path to extract soname.
* debian/templates/libnvidia-nscq-BRANCH.install.in:
- Change source paths.
-- Alberto Milone Fri, 22 Oct 2021
17:55:11 +0200
** Changed in: libnvidia-nscq-460 (Ubuntu Hirsute)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1948025
Title:
Update the NVIDIA drivers October 2021
Status in fabric-manager-450 package in Ubuntu:
Fix Released
Status in fabric-manager-460 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-460 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-470 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-495 package in Ubuntu:
Fix Released
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in libnvidia-nscq-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-495 source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in libnvidia-nscq-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-495 source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-470 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-495 source package in Hirsute:
Fix Released
Status in fabric-manager-450 source package in Impish:
Fix Released
Status in fabric-manager-460 source package in Impish:
Fix Released
Status in libnvidia-nscq-450 source package in Impish:
Fix Released
Status in libnvidia-nscq-460 source package in Impish:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Impish:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Impish:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Impish:
Fix Released
Status in nvidia-graphics-drivers-470 source package in Impish:
Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
Fix Released
Bug description:
Update the NVIDIA series and introduce the new 495 series in Bionic,
Focal, Hirsute, and Impish.
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was followed:
[Kernel-packages] [Bug 1952234] [NEW] linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver
Public bug reported:
[SRU Justification]
[Impact]
Starting with the AH2020 Azure host build, Hyper-V is virtualizing some
registers that provide information about the CPU frequency. The
registers are read-only in a guest VM, so the guest can see the
frequency, but cannot make any modifications.
This feature also requires that the VM Configuration Version be 9.2 or
later, which means it needs to be a new VM type, such as the just
introduced Dv5/Ev5 series, and the new M832v2 VMs.
Within the Linux VM, the presence of the feature is indicated by the
“aperfmperf” flag in the “lscpu” flags output (or in the flags field in
/proc/cpuinfo).
It turns out there is a Linux kernel limitation when running on the new
Intel IceLake processors used for the Dv5/Ev5 series. Upstream commit
fbdc21e9b038 was added to provide IceLake support in the 5.14 kernel.
Microsoft has asked to backport fbdc21e9b038 commit to all supported
kernels.
[Test Plan]
Run Intel IceLake based VM and check the "aperfmperf" flag in the
"lscpu" flags output.
Without the patch the intel_pstate directory is missing from
/sys/devices/system/cpu/ and /sys/devices/system/cpu/cpufreq/ is empty.
[Where problems could occur]
* intel_pstate driver is always used on Intel IceLake based VMs without
checking for presence of "aperfmperf" CPU flag.
* In earlier (5.4 and 4.15) linux-azure kernels when intel_pstate driver
is used it is in "active" mode instead of "passive" one (as reported by
"cat /sys/devices/system/cpu/intel_pstate/status", also "cat
/sys/devices/system/cpu/cpufreq/policy0/scaling_driver" returns
"intel_pstate" instead of "intel_cpufreq" which is the expected behavior
when in "active" mode).
If a consistent behavior across all kernel versions is desired commit
33aa46f252c7 ("cpufreq: intel_pstate: Use passive mode by default
without HWP") from the upstream should probably also be backported.
* /sys/devices/system/cpu/cpufreq/policy*/scaling_{min,max}_freq files
can be modified and the values reported by kernel will no longer match
the values used by hardware.
[Other Info]
None.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1952234
Title:
linux-azure: add Icelake servers support in no-HWP mode to
cpufreq/intel_pstate driver
Status in linux-azure package in Ubuntu:
New
Bug description:
[SRU Justification]
[Impact]
Starting with the AH2020 Azure host build, Hyper-V is virtualizing
some registers that provide information about the CPU frequency. The
registers are read-only in a guest VM, so the guest can see the
frequency, but cannot make any modifications.
This feature also requires that the VM Configuration Version be 9.2 or
later, which means it needs to be a new VM type, such as the just
introduced Dv5/Ev5 series, and the new M832v2 VMs.
Within the Linux VM, the presence of the feature is indicated by the
“aperfmperf” flag in the “lscpu” flags output (or in the flags field
in /proc/cpuinfo).
It turns out there is a Linux kernel limitation when running on the
new Intel IceLake processors used for the Dv5/Ev5 series. Upstream
commit fbdc21e9b038 was added to provide IceLake support in the 5.14
kernel.
Microsoft has asked to backport fbdc21e9b038 commit to all supported
kernels.
[Test Plan]
Run Intel IceLake based VM and check the "aperfmperf" flag in the
"lscpu" flags output.
Without the patch the intel_pstate directory is missing from
/sys/devices/system/cpu/ and /sys/devices/system/cpu/cpufreq/ is
empty.
[Where problems could occur]
* intel_pstate driver is always used on Intel IceLake based VMs
without checking for presence of "aperfmperf" CPU flag.
* In earlier (5.4 and 4.15) linux-azure kernels when intel_pstate
driver is used it is in "active" mode instead of "passive" one (as
reported by "cat /sys/devices/system/cpu/intel_pstate/status", also
"cat /sys/devices/system/cpu/cpufreq/policy0/scaling_driver" returns
"intel_pstate" instead of "intel_cpufreq" which is the expected
behavior when in "active" mode).
If a consistent behavior across all kernel versions is desired commit
33aa46f252c7 ("cpufreq: intel_pstate: Use passive mode by default
without HWP") from the upstream should probably also be backported.
* /sys/devices/system/cpu/cpufreq/policy*/scaling_{min,max}_freq files
can be modified and the values reported by kernel will no longer match
the values used by hardware.
[Other Info]
None.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1952234/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help :
[Kernel-packages] [Bug 1950165] Re: Focal update: v5.14.17 upstream stable release
** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950165 Title: Focal update: v5.14.17 upstream stable release Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.14.17 upstream stable release from git://git.kernel.org/ Linux 5.14.17 ALSA: usb-audio: Add Audient iD14 to mixer map quirk table ALSA: usb-audio: Add Schiit Hel device to mixer map quirk table Revert "drm/i915/gt: Propagate change in error status to children on unhold" drm/amd/display: Revert "Directly retrain link from debugfs" drm/amdgpu: revert "Add autodump debugfs node for gpu reset v8" Revert "wcn36xx: Disable bmps when encryption is disabled" ARM: 9120/1: Revert "amba: make use of -1 IRQs warn" Revert "soc: imx: gpcv2: move reset assert after requesting domain power up" drm/i915: Remove memory frequency calculation drm/amdkfd: fix boot failure when iommu is disabled in Picasso. Revert "usb: core: hcd: Add support for deferring roothub registration" Revert "xhci: Set HCD flag to defer primary roothub registration" media: firewire: firedtv-avc: fix a buffer overflow in avc_ca_pmt() vrf: Revert "Reset skb conntrack connection..." sfc: Fix reading non-legacy supported link modes scsi: core: Put LLD module refcnt after SCSI device is released To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1950165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950164] Re: Focal update: v5.14.16 upstream stable release
** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950164 Title: Focal update: v5.14.16 upstream stable release Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.14.16 upstream stable release from git://git.kernel.org/ Linux 5.14.16 KVM: x86: Take srcu lock in post_kvm_run_save() KVM: SEV-ES: fix another issue with string I/O VMGEXITs KVM: x86: switch pvclock_gtod_sync_lock to a raw spinlock KVM: x86/xen: Fix kvm_xen_has_interrupt() sleeping in kvm_vcpu_block() perf script: Check session->header.env.arch before using it riscv: Fix asan-stack clang build riscv: Do not re-populate shadow memory with kasan_populate_early_shadow riscv: fix misalgned trap vector base address scsi: ibmvfc: Fix up duplicate response detection perf script: Fix PERF_SAMPLE_WEIGHT_STRUCT support scsi: ufs: ufs-exynos: Correct timeout value setting registers KVM: s390: preserve deliverable_mask in __airqs_kick_single_vcpu KVM: s390: clear kicked_mask before sleeping again octeontx2-af: Check whether ipolicers exists virtio-ring: fix DMA metadata flags net: hns3: expand buffer len for some debugfs command net: hns3: add more string spaces for dumping packets number of queue info in debugfs bpf: Move BPF_MAP_TYPE for INODE_STORAGE and TASK_STORAGE outside of CONFIG_NET watchdog: sbsa: only use 32-bit accessors bpf: Use kvmalloc for map values in syscall sctp: add vtag check in sctp_sf_ootb sctp: add vtag check in sctp_sf_do_8_5_1_E_sa sctp: add vtag check in sctp_sf_violation sctp: fix the processing for COOKIE_ECHO chunk sctp: fix the processing for INIT_ACK chunk sctp: fix the processing for INIT chunk sctp: use init_tag from inithdr for ABORT chunk RDMA/irdma: Do not hold qos mutex twice on QP resume RDMA/irdma: Set VLAN in UD work completion correctly RDMA/irdma: Process extended CQ entries correctly phy: phy_ethtool_ksettings_set: Lock the PHY while changing settings phy: phy_start_aneg: Add an unlocked version phy: phy_ethtool_ksettings_set: Move after phy_start_aneg phy: phy_ethtool_ksettings_get: Lock the phy for consistency net/tls: Fix flipped sign in async_wait.err assignment net: ethernet: microchip: lan743x: Fix skb allocation failure net: hns3: fix data endian problem of some functions of debugfs net: hns3: fix pause config problem after autoneg disabled net: nxp: lpc_eth.c: avoid hang when bringing interface down net: ethernet: microchip: lan743x: Fix dma allocation failure by using dma_set_mask_and_coherent net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume fails mlxsw: pci: Recycle received packet upon allocation failure nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST gpio: xgs-iproc: fix parsing of ngpios property RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string RDMA/mlx5: Initialize the ODP xarray when creating an ODP MR net: Prevent infinite while loop in skb_tx_hash() cfg80211: correct bridge/4addr mode check net-sysfs: initialize uid and gid before calling net_ns_get_ownership net: batman-adv: fix error handling regmap: Fix possible double-free in regcache_rbtree_exit() reset: brcmstb-rescal: fix incorrect polarity of status bit arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node ice: check whether PTP is initialized in ice_ptp_release() RDMA/mlx5: Set user priority for DCT ice: Respond to a NETDEV_UNREGISTER event for LAG octeontx2-af: Fix possible null pointer dereference. octeontx2-af: Display all enabled PF VF rsrc_alloc entries. nvme-tcp: fix possible req->offset corruption nvme-tcp: fix data digest pointer calculation nvmet-tcp: fix data digest pointer calculation IB/hfi1: Fix abba locking issue with sc_disable() IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields bpf: Fix error usage of map_fd and fdget() in generic_map_update_batch() bpf: Fix potential race in tail call compatibility check tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function riscv, bpf: Fix potential NULL dereference cgroup: Fix memory leak caused by missing cgroup_bpf_offline Revert "watchdog: iTCO_wdt: Account for rebooting on second timeout"
[Kernel-packages] [Bug 1950160] Re: Focal update: v5.14.15 upstream stable release
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1950160
Title:
Focal update: v5.14.15 upstream stable release
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.14.15 upstream stable release
from git://git.kernel.org/
Linux 5.14.15
pinctrl: stm32: use valid pin identifier in stm32_pinctrl_resume()
ARM: 9122/1: select HAVE_FUTEX_CMPXCHG
e1000e: Separate TGP board type from SPT
net: mdiobus: Fix memory leak in __mdiobus_register
bpf, test, cgroup: Use sk_{alloc,free} for test cases
s390/pci: fix zpci_zdev_put() on reserve
s390/pci: cleanup resources only if necessary
scsi: core: Fix shost->cmd_per_lun calculation in scsi_add_host_with_dma()
autofs: fix wait name hash calculation in autofs_wait()
drm/kmb: Limit supported mode to 1080p
drm/kmb: Enable alpha blended second plane
net/mlx5: Lag, change multipath and bonding to be mutually exclusive
net/mlx5: Lag, move lag destruction to a workqueue
net: hns3: fix for miscalculation of rx unused desc
sched/scs: Reset the shadow stack when idle_task_exit
mm/thp: decrease nr_thps in file's mapping on THP split
scsi: qla2xxx: Fix a memory leak in an error path of qla2x00_process_els()
scsi: mpi3mr: Fix duplicate device entries when scanning through sysfs
scsi: storvsc: Fix validation for unsolicited incoming packets
scsi: iscsi: Fix set_param() handling
ASoC: codec: wcd938x: Add irq config support
Input: snvs_pwrkey - add clk handling
perf/x86/msr: Add Sapphire Rapids CPU support
libperf tests: Fix test_stat_cpu
libperf test evsel: Fix build error on !x86 architectures
spi-mux: Fix false-positive lockdep splats
spi: Fix deadlock when adding SPI controllers on SPI buses
ALSA: hda: avoid write to STATESTS if controller is in reset
platform/x86: intel_scu_ipc: Update timeout value in comment
platform/x86: intel_scu_ipc: Increase virtual timeout to 10s
isdn: mISDN: Fix sleeping function called from invalid context
ARM: dts: spear3xx: Fix gmac node
net: stmmac: add support for dwmac 3.40a
btrfs: deal with errors when checking if a dir entry exists during log replay
ALSA: hda: intel: Allow repeatedly probing on codec configuration errors
objtool: Update section header before relocations
objtool: Check for gelf_update_rel[a] failures
bitfield: build kunit tests without structleak plugin
thunderbolt: build kunit tests without structleak plugin
device property: build kunit tests without structleak plugin
iio/test-format: build kunit tests without structleak plugin
gcc-plugins/structleak: add makefile var for disabling structleak
drm/msm/a6xx: Serialize GMU communication
kunit: fix reference count leak in kfree_at_end
KVM: MMU: Reset mmu->pkru_mask to avoid stale data
net: hns3: fix the max tx size according to user manual
drm: mxsfb: Fix NULL pointer dereference crash on unload
KVM: SEV-ES: Set guest_state_protected after VMSA update
net: bridge: mcast: use multicast_membership_interval for IGMPv3
selftests: netfilter: remove stray bash debug line
netfilter: Kconfig: use 'default y' instead of 'm' for bool config option
isdn: cpai: check ctr->cnr to avoid array index out of bound
nfc: nci: fix the UAF of rf_conn_info object
KVM: x86: remove unnecessary arguments from complete_emulator_pio_in
KVM: x86: split the two parts of emulator_pio_in
KVM: x86: check for interrupts before deciding whether to exit the fast path
KVM: x86: leave vcpu->arch.pio.count alone in emulator_pio_in_out
KVM: SEV-ES: reduce ghcb_sa_len to 32 bits
KVM: SEV-ES: go over the sev_pio_data buffer in multiple passes if needed
KVM: SEV-ES: fix length of string I/O
KVM: SEV-ES: keep INS functions together
KVM: SEV-ES: clean up kvm_sev_es_ins/outs
KVM: SEV-ES: rename guest_ins_data to sev_pio_data
KVM: SEV: Flush cache on non-coherent systems before RECEIVE_UPDATE_DATA
KVM: nVMX: promptly process interrupts delivered while in guest mode
mm, slub: fix incorrect memcg slab count for bulk free
mm, slub: fix potential use-after-free in slab_debugfs_fops
mm, slub: fix potential memoryleak in kmem_cache_open()
mm, slub: fix mismatch between reconstructed freelist depth and cnt
powerpc/idle: Don't corrupt back chain when going idle
[Kernel-packages] [Bug 1952231] 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/1952231 Title: Touchpad not recognised Status in linux package in Ubuntu: Confirmed Bug description: My touchpad is not recognised by Ubuntu (and thus doesn't work). I am using Ubuntu 20.04.3 LTS. This has been so since the beginning (when I installed Ubuntu). My laptop is a HP-ZBook-Studio-15-6-Inch-G8-Mobile- Workstation-PC. It has a Synaptics touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-90-generic 5.4.0-90.101 ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: charlotte 1479 F pulseaudio /dev/snd/controlC1: charlotte 1479 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 25 14:40:31 2021 InstallationDate: Installed on 2021-10-18 (37 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) MachineType: HP HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-90-generic root=UUID=c3e92346-d135-4ebb-bc9f-8e4ba83aa843 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-90-generic N/A linux-backports-modules-5.4.0-90-generic N/A linux-firmware1.187.20 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-10-28 (28 days ago) dmi.bios.date: 07/07/2021 dmi.bios.vendor: HP dmi.bios.version: T92 Ver. 01.01.08 dmi.board.name: 8873 dmi.board.vendor: HP dmi.board.version: KBC Version 53.18.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrT92Ver.01.01.08:bd07/07/2021:svnHP:pnHPZBookStudio15.6InchG8MobileWorkstationPC:pvr:rvnHP:rn8873:rvrKBCVersion53.18.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC dmi.product.sku: 314F7EA#ABH dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952231] Re: Touchpad not recognised
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952231/+attachment/5543337/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952231 Title: Touchpad not recognised Status in linux package in Ubuntu: Confirmed Bug description: My touchpad is not recognised by Ubuntu (and thus doesn't work). I am using Ubuntu 20.04.3 LTS. This has been so since the beginning (when I installed Ubuntu). My laptop is a HP-ZBook-Studio-15-6-Inch-G8-Mobile- Workstation-PC. It has a Synaptics touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-90-generic 5.4.0-90.101 ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: charlotte 1479 F pulseaudio /dev/snd/controlC1: charlotte 1479 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 25 14:40:31 2021 InstallationDate: Installed on 2021-10-18 (37 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) MachineType: HP HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-90-generic root=UUID=c3e92346-d135-4ebb-bc9f-8e4ba83aa843 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-90-generic N/A linux-backports-modules-5.4.0-90-generic N/A linux-firmware1.187.20 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-10-28 (28 days ago) dmi.bios.date: 07/07/2021 dmi.bios.vendor: HP dmi.bios.version: T92 Ver. 01.01.08 dmi.board.name: 8873 dmi.board.vendor: HP dmi.board.version: KBC Version 53.18.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrT92Ver.01.01.08:bd07/07/2021:svnHP:pnHPZBookStudio15.6InchG8MobileWorkstationPC:pvr:rvnHP:rn8873:rvrKBCVersion53.18.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC dmi.product.sku: 314F7EA#ABH dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952231] Re: Touchpad not recognised
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952231/+attachment/5543338/+files/version.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/1952231 Title: Touchpad not recognised Status in linux package in Ubuntu: Confirmed Bug description: My touchpad is not recognised by Ubuntu (and thus doesn't work). I am using Ubuntu 20.04.3 LTS. This has been so since the beginning (when I installed Ubuntu). My laptop is a HP-ZBook-Studio-15-6-Inch-G8-Mobile- Workstation-PC. It has a Synaptics touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-90-generic 5.4.0-90.101 ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: charlotte 1479 F pulseaudio /dev/snd/controlC1: charlotte 1479 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 25 14:40:31 2021 InstallationDate: Installed on 2021-10-18 (37 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) MachineType: HP HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-90-generic root=UUID=c3e92346-d135-4ebb-bc9f-8e4ba83aa843 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-90-generic N/A linux-backports-modules-5.4.0-90-generic N/A linux-firmware1.187.20 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-10-28 (28 days ago) dmi.bios.date: 07/07/2021 dmi.bios.vendor: HP dmi.bios.version: T92 Ver. 01.01.08 dmi.board.name: 8873 dmi.board.vendor: HP dmi.board.version: KBC Version 53.18.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrT92Ver.01.01.08:bd07/07/2021:svnHP:pnHPZBookStudio15.6InchG8MobileWorkstationPC:pvr:rvnHP:rn8873:rvrKBCVersion53.18.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC dmi.product.sku: 314F7EA#ABH dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952231] [NEW] Touchpad not recognised
Public bug reported: My touchpad is not recognised by Ubuntu (and thus doesn't work). I am using Ubuntu 20.04.3 LTS. This has been so since the beginning (when I installed Ubuntu). My laptop is a HP-ZBook-Studio-15-6-Inch-G8-Mobile- Workstation-PC. It has a Synaptics touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-90-generic 5.4.0-90.101 ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: charlotte 1479 F pulseaudio /dev/snd/controlC1: charlotte 1479 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 25 14:40:31 2021 InstallationDate: Installed on 2021-10-18 (37 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) MachineType: HP HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-90-generic root=UUID=c3e92346-d135-4ebb-bc9f-8e4ba83aa843 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-90-generic N/A linux-backports-modules-5.4.0-90-generic N/A linux-firmware1.187.20 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-10-28 (28 days ago) dmi.bios.date: 07/07/2021 dmi.bios.vendor: HP dmi.bios.version: T92 Ver. 01.01.08 dmi.board.name: 8873 dmi.board.vendor: HP dmi.board.version: KBC Version 53.18.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrT92Ver.01.01.08:bd07/07/2021:svnHP:pnHPZBookStudio15.6InchG8MobileWorkstationPC:pvr:rvnHP:rn8873:rvrKBCVersion53.18.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC dmi.product.sku: 314F7EA#ABH dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1952231/+attachment/5543316/+files/devices -- 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/1952231 Title: Touchpad not recognised Status in linux package in Ubuntu: Confirmed Bug description: My touchpad is not recognised by Ubuntu (and thus doesn't work). I am using Ubuntu 20.04.3 LTS. This has been so since the beginning (when I installed Ubuntu). My laptop is a HP-ZBook-Studio-15-6-Inch-G8-Mobile- Workstation-PC. It has a Synaptics touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-90-generic 5.4.0-90.101 ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: charlotte 1479 F pulseaudio /dev/snd/controlC1: charlotte 1479 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 25 14:40:31 2021 InstallationDate: Installed on 2021-10-18 (37 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) MachineType: HP HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-90-generic root=UUID=c3e92346-d135-4ebb-bc9f-8e4ba83aa843 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-90-generic N/A linux-backports-modules-5.4.0-90-generic N/A linux-firmware1.187.20 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-10-28 (28 days ago) dmi.bios.date: 07/07/2021 dmi.bios.vendor: HP dmi.bios.version: T92 Ver. 01.01.08 dmi.board.name: 8873 dmi.board.vendor: HP dmi.board.version: KBC Version 53.18.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrT92Ver.01.01.08:bd07/07/2021:svnHP:pnHPZBookStudio15.6InchG8MobileWorkstationPC:pvr:rvnHP:rn8873:rvrKBCVersion53.18.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC dmi.product.sku: 314F7EA#ABH dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945764] Re: crda: Fail to build against OpenSSL 3.0
Refresh of the debdiff against the latest version ** Patch added: "crda.debdiff" https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1945764/+attachment/5543314/+files/crda.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1945764 Title: crda: Fail to build against OpenSSL 3.0 Status in crda package in Ubuntu: New Bug description: Hello, As part of a rebuild against OpenSSL3, this package failed to build on one or several architectures. You can find the details of the rebuild at https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html or for the amd64 failed build, directly at https://launchpadlibrarian.net/559464520/buildlog_ubuntu-impish- amd64.crda_4.14+git20191112.9856751-1.0~ssl3ppa1.1_BUILDING.txt.gz We're planning to transition to OpenSSL 3.0 for the 22.04 release, and consider this issue as blocking for this transition. For your tests, you can build against libssl-dev as found in the PPA schopin/openssl-3.0.0 I haven't found any mention of the issue upstream. However, a quick glance at the logs tells me the errors seem due to the use of deprecated APIs combined with -Werror. Thus, a quick fix might be to simply add -Wno-error=deprecated-declarations to the CFLAGS ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1945764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930086] Re: [22.04 FEAT] gcc tunings for power9
** Changed in: gcc-defaults (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-power-systems 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/1930086 Title: [22.04 FEAT] gcc tunings for power9 Status in The Ubuntu-power-systems project: In Progress Status in gcc-defaults package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Bug description: This is an Ubuntu-power-systems 22.04 LTS feature bug to track changing the gcc configure options from --with-cpu=power8 to --with- cpu=power9. Prerequisites for this bug include power9 builder hardware in Canonical datacenter. I'm still learning my way around Debian/Ubuntu source so go easy on me if this isn't the correct branch: https://salsa.debian.org/toolchain- team/gcc/-/blob/gcc-10-debian/debian/rules2#L394 But we'll want to add some logic around line 394 to add --with- cpu=power9 for 22.04 and possibly --with-tune=? but I'll reverse mirror this bug and verify with our IBM Power toolchain architect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1930086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] [NEW] io_uring regression - lost write request
Public bug reported: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b >From reading the thread and looking at the history in >linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. ** Affects: linux-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Package changed: samba (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/195 Title: io_uring regression - lost write request Status in linux-hwe-5.13 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] [NEW] io_uring regression - lost write request
You have been subscribed to a public bug: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b >From reading the thread and looking at the history in >linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. ** Affects: linux-hwe-5.13 (Ubuntu) Importance: Undecided Status: New -- io_uring regression - lost write request https://bugs.launchpad.net/bugs/195 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 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 1945542] 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 1945542 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/1945542 Title: mouse starts going up and has a laggy response Status in linux package in Ubuntu: Incomplete Bug description: Writing lsb_release -rd I got this: Description: Ubuntu 20.04.3 LTS Release: 20.04 I don't know exactly what package has the issue but I think is most probably the kernel itself. I can use my touchpad normally most of the time. But randomly and suddenly, it stops working properly. When I don't move the cursor, it starts going up and for re-using it I have to pass my finger three times (aprox.) and then it starts to respond. But when I leave it, the bug comes again. The problem got solved when I restart my laptop. I've tried a lot of troubleshooting I've found on internet but nothing works without restarting. Also, when I write xinput -list in the terminal, it does not detect my touchpad. Moreover, today I got two like-windows blue screen but instead of having a blue screen I got something like a TV receiving noise in color. Nothing works -neither the power button- I've lost few of my college work (not anything serious by luck). Thank you for making Ubuntu and best Regards. Josue Laszeski, Argentina. PD: I'm not an English native speaker, please ignore my redaction faults. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Sep 29 21:46:41 2021 InstallationDate: Installed on 2021-07-26 (65 days ago) InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945542] Re: mouse starts going up and has a laggy response
** 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/1945542 Title: mouse starts going up and has a laggy response Status in linux package in Ubuntu: New Bug description: Writing lsb_release -rd I got this: Description: Ubuntu 20.04.3 LTS Release: 20.04 I don't know exactly what package has the issue but I think is most probably the kernel itself. I can use my touchpad normally most of the time. But randomly and suddenly, it stops working properly. When I don't move the cursor, it starts going up and for re-using it I have to pass my finger three times (aprox.) and then it starts to respond. But when I leave it, the bug comes again. The problem got solved when I restart my laptop. I've tried a lot of troubleshooting I've found on internet but nothing works without restarting. Also, when I write xinput -list in the terminal, it does not detect my touchpad. Moreover, today I got two like-windows blue screen but instead of having a blue screen I got something like a TV receiving noise in color. Nothing works -neither the power button- I've lost few of my college work (not anything serious by luck). Thank you for making Ubuntu and best Regards. Josue Laszeski, Argentina. PD: I'm not an English native speaker, please ignore my redaction faults. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Sep 29 21:46:41 2021 InstallationDate: Installed on 2021-07-26 (65 days ago) InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951767] Re: [SRU][I/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks
** Changed in: linux (Ubuntu Impish) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1951767 Title: [SRU][I/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Incomplete Bug description: [Impact] MAC pass through is not working on new TBT and USB-C docks. [Fix] Enable MAC pass through based on Lenovo USB hub. [Test] Tested on Lenovo TBT4 and TBT3 dock, MAC pass through works well. [Where problems could occur] The Realtek USB ethernet in Lenovo USB hub will mess the MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951861] Re: Fix non-working e1000e device after resume
** Changed in: linux (Ubuntu Impish) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1951861 Title: Fix non-working e1000e device after resume Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: Fix Committed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] e1000e devices stop working after s2idle resume. [Fix] Revert the offending patch series, which is to bring some minor power saving. [Test] Vendor did extensive tests and didn't find any regression, and the power consumption remains the same. [Where problems could occur] Maybe on some system the series can save some energy, so reverting will cause some power consumption increase. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945632] Re: Re-enable DEBUG_INFO_BTF where it was disabled
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945632 Title: Re-enable DEBUG_INFO_BTF where it was disabled Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-hwe-5.11 source package in Focal: Fix Released Status in linux-hwe-5.13 source package in Focal: Fix Released Bug description: [Impact] * pahole used to segfault on 32-bit platforms, which has now been fixed * pahole used to be too old in focal, which is now being SRUed * renable DEBUG_INFO_BTF in all the kernels/arches that had it disabled, as otherwise one cannot compile/use advanced BTF features on newer kernels. [Test Plan] * Check the built kernel's config that it has CONFIG_DEBUG_INFO_BTF=y * Check build log that it contains ``` BTF .btf.vmlinux.bin.o ``` [Where problems could occur] * In the future, kernel may require even newer version of pahole from dwarves, making the builds fail to build again, as building BTF debug information will now be required. Until either BTF is disabled again or pahole is upgraded again. [Other Info] * Latest pahole is available from focal-proposed, hirsute-proposed, impish release, builders-extra PPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945632/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951935] Re: artifacts after a long sleep
I'm unable to download your screenshot. Maybe you could re-upload using a filename that doesn't include Cyrillic characters? You've given us no information about your hardware or the version of Ubuntu you are using. https://wiki.ubuntu.com/Bugs/FindRightPackage#Suspend_and_Hibernate tells me that initially your problem should have been reported against the 'linux' package. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1951935 and then change the status of the bug report to 'Confirmed'. This will then bring your issue to the attention of an Ubuntu developer. When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: ubuntu => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951935 Title: artifacts after a long sleep Status in linux package in Ubuntu: Incomplete Bug description: I've have artifacts after a long sleep (about 8 hours) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952217] Re: bluetoothd coredumps from double free on connection of headset
bluetoothd 5.62 (installed from source @ `applied/ubuntu/devel` ) working well. ** Attachment added: "syslog.5.62.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+attachment/5543298/+files/syslog.5.62.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1952217 Title: bluetoothd coredumps from double free on connection of headset Status in bluez package in Ubuntu: New Bug description: Problem: Since the security updates on 2021-11-23 connecting my headset causes bluetoothd to crash, which drops all the other connections. Expected: Headset connects and works as it has done previously. ❯ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ❯ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.4 Candidate: 5.53-0ubuntu3.4 Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for the LDAC codecs for this headset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945542] [NEW] mouse starts going up and has a laggy response
You have been subscribed to a public bug: Writing lsb_release -rd I got this: Description:Ubuntu 20.04.3 LTS Release:20.04 I don't know exactly what package has the issue but I think is most probably the kernel itself. I can use my touchpad normally most of the time. But randomly and suddenly, it stops working properly. When I don't move the cursor, it starts going up and for re-using it I have to pass my finger three times (aprox.) and then it starts to respond. But when I leave it, the bug comes again. The problem got solved when I restart my laptop. I've tried a lot of troubleshooting I've found on internet but nothing works without restarting. Also, when I write xinput -list in the terminal, it does not detect my touchpad. Moreover, today I got two like-windows blue screen but instead of having a blue screen I got something like a TV receiving noise in color. Nothing works -neither the power button- I've lost few of my college work (not anything serious by luck). Thank you for making Ubuntu and best Regards. Josue Laszeski, Argentina. PD: I'm not an English native speaker, please ignore my redaction faults. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Sep 29 21:46:41 2021 InstallationDate: Installed on 2021-07-26 (65 days ago) InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- mouse starts going up and has a laggy response https://bugs.launchpad.net/bugs/1945542 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 1950462] Re: Focal linux-azure: Vm crash on Dv5/Ev5
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1950462 Title: Focal linux-azure: Vm crash on Dv5/Ev5 Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] We are seeing a below crash for Nested VM scenario in Dv5/Ev5. [ 284.769421] [ cut here ] [ 284.769422] KVM: accessing unsupported EVMCS field 2032 [ 284.769443] WARNING: CPU: 30 PID: 8426 at /build/linux-azure-5.4-YivnXz/linux-azure-5.4-5.4.0/arch/x86/kvm/vmx/evmcs.h:85 evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769443] Modules linked in: vhost_net vhost tap ipt_REJECT nf_reject_ipv4 xt_tcpudp iptable_filter xt_MASQUERADE iptable_nat nf_nat bridge stp llc xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_security bpfilter udf crc_itu_t nls_iso8859_1 kvm_intel kvm serio_raw hv_balloon joydev sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic crct10dif_pclmul hid_hyperv crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd hyperv_fb cfbfillrect glue_helper cfbimgblt hid hv_netvsc hv_utils hyperv_keyboard cfbcopyarea [ 284.769463] CPU: 30 PID: 8426 Comm: qemu-system-x86 Not tainted 5.4.0-1062-azure #65~18.04.1-Ubuntu [ 284.769464] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 07/22/2021 [ 284.769467] RIP: 0010:evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769469] Code: c2 f7 d0 21 81 38 03 00 00 5d c3 80 3d 1c 32 03 00 00 75 f5 48 89 fe 48 c7 c7 f8 63 57 c0 c6 05 09 32 03 00 01 e8 eb d1 53 cd <0f> 0b 5d c3 0f 1f 80 00 00 00 00 0f 1f 44 00 00 48 8b 07 80 b8 ea [ 284.769469] RSP: 0018:b75a03f0fb68 EFLAGS: 00010282 [ 284.769471] RAX: RBX: 8e126a9e8000 RCX: 0006 [ 284.769471] RDX: 0007 RSI: 0082 RDI: 8e12dfb96580 [ 284.769472] RBP: b75a03f0fb68 R08: 022b R09: 0004 [ 284.769472] R10: b75a03f0fcf8 R11: 0001 R12: 001e [ 284.769473] R13: fe5fd000 R14: R15: [ 284.769474] FS: 7f4bc4c09700() GS:8e12dfb8() knlGS: [ 284.769476] CS: 0010 DS: ES: CR0: 80050033 [ 284.769477] CR2: 7f3fddb8eba0 CR3: 003f69dbe002 CR4: 00372ee0 [ 284.769478] DR0: DR1: DR2: [ 284.769478] DR3: DR6: fffe0ff0 DR7: 0400 [ 284.769479] Call Trace: [ 284.769485] vmx_vcpu_load_vmcs+0x2f9/0x440 [kvm_intel] [ 284.769488] vmx_vcpu_load+0x47/0x200 [kvm_intel] [ 284.769493] ? __memcg_kmem_charge+0x87/0x150 [ 284.769495] ? __alloc_pages_nodemask+0x246/0x320 [ 284.769499] vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769500] ? __get_free_pages+0x11/0x40 [ 284.769504] ? alloc_loaded_vmcs+0xa2/0x120 [kvm_intel] [ 284.769507] ? vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769528] kvm_arch_vcpu_create+0x4f/0x70 [kvm] [ 284.769538] kvm_vm_ioctl+0x2e2/0x980 [kvm] [ 284.769542] do_vfs_ioctl+0xa9/0x640 [ 284.769545] ? __switch_to_asm+0x40/0x70 [ 284.769546] ? __switch_to_asm+0x34/0x70 [ 284.769547] ? __switch_to_asm+0x40/0x70 [ 284.769548] ? __switch_to_asm+0x34/0x70 [ 284.769550] ? __switch_to_asm+0x40/0x70 [ 284.769551] ? __switch_to_asm+0x34/0x70 [ 284.769552] ? __switch_to_asm+0x40/0x70 [ 284.769553] ? __switch_to_asm+0x34/0x70 [ 284.769554] ? __switch_to_asm+0x40/0x70 [ 284.769555] ksys_ioctl+0x75/0x80 [ 284.769556] ? __switch_to_asm+0x34/0x70 [ 284.769557] __x64_sys_ioctl+0x1a/0x20 [ 284.769559] do_syscall_64+0x5e/0x200 [ 284.769561] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 284.769562] RIP: 0033:0x7f4bcf01d317 [ 284.769563] Code: b3 66 90 48 8b 05 71 4b 2d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 41 4b 2d 00 f7 d8 64 89 01 48 [ 284.769564] RSP: 002b:7f4bc4c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 284.769565] RAX: ffda RBX: ae41 RCX: 7f4bcf01d317 [ 284.769566] RDX: RSI: ae41 RDI: 000b [ 284.769566] RBP: R08: 5596f71e0ec0 R09: 5596f896c170 [ 284.769567] R10: 5596f77fb8e0 R11: 0246 R12:
[Kernel-packages] [Bug 1951935] [NEW] artifacts after a long sleep
You have been subscribed to a public bug: I've have artifacts after a long sleep (about 8 hours) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-comment -- artifacts after a long sleep https://bugs.launchpad.net/bugs/1951935 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 1952217] Re: bluetoothd coredumps from double free on connection of headset
Syslog from affected system. - First action is to select the affected headset from the Bluetooth applet The first thing that happens is the coredum. Then the service restarts ; this seems to be fast enough that the connection is still in progress, you can see the audio endpoints being registered, ? because the state is lost this does not complete and the device reports disconnection. * - Second action is activation of a Bluetooth keyboard This connects and functions correctly - Third action is selecting the affected headset again Same response. The keyboard is also disconnected but reconnects automatically. * this is not true : these endpoints are re-registered merely on restarting the bluetooth service. ** Attachment added: "syslog.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+attachment/5543295/+files/syslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1952217 Title: bluetoothd coredumps from double free on connection of headset Status in bluez package in Ubuntu: New Bug description: Problem: Since the security updates on 2021-11-23 connecting my headset causes bluetoothd to crash, which drops all the other connections. Expected: Headset connects and works as it has done previously. ❯ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ❯ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.4 Candidate: 5.53-0ubuntu3.4 Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for the LDAC codecs for this headset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952217] [NEW] bluetoothd coredumps from double free on connection of headset
Public bug reported: Problem: Since the security updates on 2021-11-23 connecting my headset causes bluetoothd to crash, which drops all the other connections. Expected: Headset connects and works as it has done previously. ❯ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 ❯ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.4 Candidate: 5.53-0ubuntu3.4 Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for the LDAC codecs for this headset. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1952217 Title: bluetoothd coredumps from double free on connection of headset Status in bluez package in Ubuntu: New Bug description: Problem: Since the security updates on 2021-11-23 connecting my headset causes bluetoothd to crash, which drops all the other connections. Expected: Headset connects and works as it has done previously. ❯ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ❯ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.4 Candidate: 5.53-0ubuntu3.4 Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for the LDAC codecs for this headset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952136] Re: Hirsute update: upstream stable patchset 2021-11-24
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952136 Title: Hirsute update: upstream stable patchset 2021-11-24 Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-11-24 Ported from the following upstream stable releases: v5.10.74, v5.14.13 v5.10.75, v5.14.14 v5.10.76, v5.14.15 from git://git.kernel.org/ ext4: check and update i_disksize properly ext4: correct the error path of ext4_write_inline_data_end() ASoC: Intel: sof_sdw: tag SoundWire BEs as non-atomic HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS netfilter: ip6_tables: zero-initialize fragment offset HID: wacom: Add new Intuos BT (CTL-4100WL/CTL-6100WL) device IDs ASoC: SOF: loader: release_firmware() on load failure to avoid batching netfilter: nf_nat_masquerade: make async masq_inet6_event handling generic netfilter: nf_nat_masquerade: defer conntrack walk to work queue mac80211: Drop frames from invalid MAC address in ad-hoc mode m68k: Handle arrivals of multiple signals correctly hwmon: (ltc2947) Properly handle errors when looking for the external clock net: prevent user from passing illegal stab size mac80211: check return value of rhashtable_init vboxfs: fix broken legacy mount signature checking net: sun: SUNVNET_COMMON should depend on INET drm/amdgpu: fix gart.bo pin_count leak scsi: ses: Fix unsigned comparison with less than zero scsi: virtio_scsi: Fix spelling mistake "Unsupport" -> "Unsupported" perf/core: fix userpage->time_enabled of inactive events sched: Always inline is_percpu_thread() hwmon: (pmbus/ibm-cffps) max_power_out swap changes ALSA: usb-audio: Unify mixer resume and reset_resume procedure pinctrl: qcom: sc7280: Add PM suspend callbacks io_uring: kill fasync UBUNTU: upstream stable to v5.10.74, v5.14.13 ALSA: usb-audio: Add quirk for VF0770 ALSA: pcm: Workaround for a wrong offset in SYNC_PTR compat ioctl ALSA: seq: Fix a potential UAF by wrong private_free call order ALSA: hda/realtek: Enable 4-speaker output for Dell Precision 5560 laptop ALSA: hda - Enable headphone mic on Dell Latitude laptops with ALC3254 ALSA: hda/realtek: Complete partial device name to avoid ambiguity ALSA: hda/realtek: Add quirk for Clevo X170KM-G ALSA: hda/realtek - ALC236 headset MIC recording issue ALSA: hda/realtek: Add quirk for TongFang PHxTxX1 ALSA: hda/realtek: Fix the mic type detection issue for ASUS G551JW nds32/ftrace: Fix Error: invalid operands (*UND* and *UND* sections) for `^' s390: fix strrchr() implementation clk: socfpga: agilex: fix duplicate s2f_user0_clk csky: don't let sigreturn play with priveleged bits of status register csky: Fixup regs.sr broken in ptrace arm64/hugetlb: fix CMA gigantic page order for non-4K PAGE_SIZE drm/msm: Avoid potential overflow in timeout_to_jiffies() btrfs: unlock newly allocated extent buffer after error btrfs: deal with errors when replaying dir entry during log replay btrfs: deal with errors when adding inode reference during log replay btrfs: check for error when looking up inode during dir entry replay btrfs: update refs for any root except tree log roots btrfs: fix abort logic in btrfs_replace_file_extents x86/resctrl: Free the ctrlval arrays when domain_setup_mon_state() fails mei: me: add Ice Lake-N device id. USB: xhci: dbc: fix tty registration race xhci: guard accesses to ep_state in xhci_endpoint_reset() xhci: Fix command ring pointer corruption while aborting a command xhci: Enable trust tx length quirk for Fresco FL11 USB controller cb710: avoid NULL pointer subtraction efi/cper: use stack buffer for error record decoding efi: Change down_interruptible() in virt_efi_reset_system() to down_trylock() usb: musb: dsps: Fix the probe error path Input: xpad - add support for another USB ID of Nacon GC-100 USB: serial: qcserial: add EM9191 QDL support USB: serial: option: add Quectel EC200S-CN module support USB: serial: option: add Telit LE910Cx composition 0x1204 USB: serial: option: add prod. id for Quectel EG91 misc: fastrpc: Add missing lock before accessing
[Kernel-packages] [Bug 1951873] Re: Enable arm64 nitro enclaves
** Changed in: linux-aws (Ubuntu Impish) Importance: Undecided => Low ** Changed in: linux-aws (Ubuntu Impish) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: linux-aws (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Focal) Importance: Undecided => Low ** Changed in: linux-aws (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1951873 Title: Enable arm64 nitro enclaves Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Focal: In Progress Status in linux-aws source package in Hirsute: In Progress Status in linux-aws source package in Impish: In Progress Bug description: SRU Justification [Impact] Enable arm64 support for Nitro Enclaves [Test Plan] Boot an AWS arm64 instance. Test for the existence of enclaves. [Where things could go wrong] Its possible this could affect amd64 enclave support. [Other Info] SF: #00323459 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1951873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950968] Re: v5.15 RT kernel fails to boot on some arm64 instances
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950968 Title: v5.15 RT kernel fails to boot on some arm64 instances Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: d2021.10.26/jammy/linux-realtime/5.15.0-1002.2 failed to boot on helo- kernel.arm64 without any logs. - Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-1002-realtime Found initrd image: /boot/initrd.img-5.15.0-1002-realtime Found linux image: /boot/vmlinuz-5.13.0-21-generic Found initrd image: /boot/initrd.img-5.13.0-21-generic done . Rebooting for installed Kernel meta package Traceback (most recent call last): File "/home/maas/ckct/sut-prep", line 187, in exit(app.main(args)) File "/home/maas/ckct/sut-prep", line 74, in main if instance.provision(): File "/home/maas/ckct/lib/target.py", line 1301, in provision s.reboot(progress=reboot) File "/home/maas/ckct/lib/target.py", line 621, in reboot s.wait_for_target() File "/home/maas/ckct/lib/target.py", line 173, in wait_for_target raise WaitForTarget(message) lib.target.WaitForTarget: The specified timeout (30 minutes) was reached while waiting for the target system (10.229.83.183) to come back up. WARNING - [2021-11-15 10:42:43.270713] ssh command (return): uname -vr (0) 5.13.0-21-generic #21-Ubuntu SMP Tue Oct 19 09:01:50 UTC 2021 - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952155] Re: 5.13.0-21 startup failed , show white noise screen (lenovo r9000x 4800h nvidia 2060)
attachment is screen appearance ** Attachment added: "Screenshot_2021-11-25-17-23-26-026_com.miui.gallery.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952155/+attachment/5543277/+files/Screenshot_2021-11-25-17-23-26-026_com.miui.gallery.jpg -- 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/1952155 Title: 5.13.0-21 startup failed , show white noise screen (lenovo r9000x 4800h nvidia 2060) Status in linux package in Ubuntu: Confirmed Bug description: After upgrading kernel 5.13.0-21 startup failed. screen stays at white noise. laptop is lenovo r9000x , os: Linux Mint 20.2 Cinnamon cpu : amd 4800h gpu : nvidia 2060 max [code] System:Kernel: 5.11.0-40-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.0.7 wm: muffin dm: LightDM Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal Machine: Type: Laptop System: LENOVO product: 82HN v: Lenovo Legion R9000X 2021 serial: Chassis: type: 10 v: Lenovo Legion R9000X 2021 serial: Mobo: LENOVO model: LNVNB161216 v: SDK0L77769WIN serial: UEFI: LENOVO v: G1CN17WW date: 11/18/2020 Battery: ID-1: BAT0 charge: 62.3 Wh condition: 64.0/71.0 Wh (90%) volts: 15.4/N/A model: Celxpert L19C4PC3 serial: status: Unknown CPU: Topology: 8-Core model: AMD Ryzen 7 4800H with Radeon Graphics bits: 64 type: MT MCP arch: Zen rev: 1 L2 cache: 4096 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 92630 Speed: 1327 MHz min/max: 1400/2900 MHz Core speeds (MHz): 1: 1289 2: 1231 3: 1397 4: 1397 5: 1386 6: 1397 7: 1397 8: 1338 9: 2253 10: 2611 11: 1408 12: 1633 13: 1484 14: 1397 15: 1392 16: 1397 Graphics: Device-1: NVIDIA TU106 [GeForce RTX 2060] vendor: Lenovo driver: nvidia v: 460.106.00 bus ID: 01:00.0 chip ID: 10de:1f12 Device-2: AMD Renoir vendor: Lenovo driver: amdgpu v: kernel bus ID: 06:00.0 chip ID: 1002:1636 Display: x11 server: X.Org 1.20.11 driver: amdgpu,ati,nvidia unloaded: fbdev,modesetting,nouveau,vesa resolution: 1920x1080~60Hz, 1920x1080~144Hz OpenGL: renderer: GeForce RTX 2060 with Max-Q Design/PCIe/SSE2 v: 4.6.0 NVIDIA 460.106.00 direct render: Yes Audio: Device-1: NVIDIA TU106 High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:10f9 Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor vendor: Lenovo driver: N/A bus ID: 06:00.5 chip ID: 1022:15e2 Device-3: AMD Family 17h HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 06:00.6 chip ID: 1022:15e3 Sound Server: ALSA v: k5.11.0-40-generic Network: Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: 2000 bus ID: 03:00.0 chip ID: 8086:2723 IF: wlp3s0 state: up mac: Device-2: Realtek RTL8152 Fast Ethernet Adapter type: USB driver: r8152 bus ID: 5-1.4:6 chip ID: 0bda:8152 IF: enx00e04c36059b state: up speed: 100 Mbps duplex: full mac: IF-ID-1: br-db36e140ddeb state: up speed: 1 Mbps duplex: unknown mac: IF-ID-2: docker0 state: up speed: 1 Mbps duplex: unknown mac: IF-ID-3: veth0 state: up speed: N/A duplex: N/A mac: IF-ID-4: veth071d8bc state: up speed: 1 Mbps duplex: full mac: IF-ID-5: veth260b138 state: up speed: 1 Mbps duplex: full mac: IF-ID-6: veth405e95b state: up speed: 1 Mbps duplex: full mac: IF-ID-7: veth4412542 state: up speed: 1 Mbps duplex: full mac: IF-ID-8: veth56cd37a state: up speed: 1 Mbps duplex: full mac: IF-ID-9: veth9c83b77 state: up speed: 1 Mbps duplex: full mac: IF-ID-10: veth9dea6f7 state: up speed: 1 Mbps duplex: full mac: IF-ID-11: vethae53fe1 state: up speed: 1 Mbps duplex: full mac: IF-ID-12: vethdc074a2 state: up speed: 1 Mbps duplex: full mac: IF-ID-13: vethf040e52 state: up speed: 1 Mbps duplex: full mac: Drives:Local Storage: total: 1.82 TiB used: 758.93 GiB (40.7%) ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HBJQ-000L2 size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: ID-2: /dev/nvme1n1 vendor: Seagate model: FireCuda 510 SSD ZP2000GM30001 size: 1.82 TiB speed: 31.6 Gb/s lanes: 4 serial: Partition: ID-1: / size: 1.02 TiB used: 758.90 GiB (72.6%) fs: ext4 dev: /dev/nvme1n1p5 USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 chip ID:
[Kernel-packages] [Bug 1952155] Re: 5.13.0-21 startup failed , show white noise screen (lenovo r9000x 4800h nvidia 2060)
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1952155 Title: 5.13.0-21 startup failed , show white noise screen (lenovo r9000x 4800h nvidia 2060) Status in linux package in Ubuntu: Confirmed Bug description: After upgrading kernel 5.13.0-21 startup failed. screen stays at white noise. laptop is lenovo r9000x , os: Linux Mint 20.2 Cinnamon cpu : amd 4800h gpu : nvidia 2060 max [code] System:Kernel: 5.11.0-40-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.0.7 wm: muffin dm: LightDM Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal Machine: Type: Laptop System: LENOVO product: 82HN v: Lenovo Legion R9000X 2021 serial: Chassis: type: 10 v: Lenovo Legion R9000X 2021 serial: Mobo: LENOVO model: LNVNB161216 v: SDK0L77769WIN serial: UEFI: LENOVO v: G1CN17WW date: 11/18/2020 Battery: ID-1: BAT0 charge: 62.3 Wh condition: 64.0/71.0 Wh (90%) volts: 15.4/N/A model: Celxpert L19C4PC3 serial: status: Unknown CPU: Topology: 8-Core model: AMD Ryzen 7 4800H with Radeon Graphics bits: 64 type: MT MCP arch: Zen rev: 1 L2 cache: 4096 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 92630 Speed: 1327 MHz min/max: 1400/2900 MHz Core speeds (MHz): 1: 1289 2: 1231 3: 1397 4: 1397 5: 1386 6: 1397 7: 1397 8: 1338 9: 2253 10: 2611 11: 1408 12: 1633 13: 1484 14: 1397 15: 1392 16: 1397 Graphics: Device-1: NVIDIA TU106 [GeForce RTX 2060] vendor: Lenovo driver: nvidia v: 460.106.00 bus ID: 01:00.0 chip ID: 10de:1f12 Device-2: AMD Renoir vendor: Lenovo driver: amdgpu v: kernel bus ID: 06:00.0 chip ID: 1002:1636 Display: x11 server: X.Org 1.20.11 driver: amdgpu,ati,nvidia unloaded: fbdev,modesetting,nouveau,vesa resolution: 1920x1080~60Hz, 1920x1080~144Hz OpenGL: renderer: GeForce RTX 2060 with Max-Q Design/PCIe/SSE2 v: 4.6.0 NVIDIA 460.106.00 direct render: Yes Audio: Device-1: NVIDIA TU106 High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:10f9 Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor vendor: Lenovo driver: N/A bus ID: 06:00.5 chip ID: 1022:15e2 Device-3: AMD Family 17h HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 06:00.6 chip ID: 1022:15e3 Sound Server: ALSA v: k5.11.0-40-generic Network: Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: 2000 bus ID: 03:00.0 chip ID: 8086:2723 IF: wlp3s0 state: up mac: Device-2: Realtek RTL8152 Fast Ethernet Adapter type: USB driver: r8152 bus ID: 5-1.4:6 chip ID: 0bda:8152 IF: enx00e04c36059b state: up speed: 100 Mbps duplex: full mac: IF-ID-1: br-db36e140ddeb state: up speed: 1 Mbps duplex: unknown mac: IF-ID-2: docker0 state: up speed: 1 Mbps duplex: unknown mac: IF-ID-3: veth0 state: up speed: N/A duplex: N/A mac: IF-ID-4: veth071d8bc state: up speed: 1 Mbps duplex: full mac: IF-ID-5: veth260b138 state: up speed: 1 Mbps duplex: full mac: IF-ID-6: veth405e95b state: up speed: 1 Mbps duplex: full mac: IF-ID-7: veth4412542 state: up speed: 1 Mbps duplex: full mac: IF-ID-8: veth56cd37a state: up speed: 1 Mbps duplex: full mac: IF-ID-9: veth9c83b77 state: up speed: 1 Mbps duplex: full mac: IF-ID-10: veth9dea6f7 state: up speed: 1 Mbps duplex: full mac: IF-ID-11: vethae53fe1 state: up speed: 1 Mbps duplex: full mac: IF-ID-12: vethdc074a2 state: up speed: 1 Mbps duplex: full mac: IF-ID-13: vethf040e52 state: up speed: 1 Mbps duplex: full mac: Drives:Local Storage: total: 1.82 TiB used: 758.93 GiB (40.7%) ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HBJQ-000L2 size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: ID-2: /dev/nvme1n1 vendor: Seagate model: FireCuda 510 SSD ZP2000GM30001 size: 1.82 TiB speed: 31.6 Gb/s lanes: 4 serial: Partition: ID-1: / size: 1.02 TiB used: 758.90 GiB (72.6%) fs: ext4 dev: /dev/nvme1n1p5 USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 chip ID: 1d6b:0002 Hub: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 chip ID: 1d6b:0003 Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID:
