[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
Confirm fix resolves issue in Quantal. Tested 3.5.0-47-generic
#71~precise1-Ubuntu SMP Wed Feb 19 22:02:52 UTC 2014 x86_64 x86_64
x86_64
Many thanks !
** Tags removed: verification-needed-quantal
** Tags added: verification-done-quantal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1269053
Title:
IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel
3.5.0-45.68
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux-armadaxp” package in Ubuntu:
Invalid
Status in “linux-ec2” package in Ubuntu:
Invalid
Status in “linux-lts-quantal” package in Ubuntu:
Invalid
Status in “linux-lts-raring” package in Ubuntu:
Invalid
Status in “linux-lts-saucy” package in Ubuntu:
Invalid
Status in “linux-ti-omap4” package in Ubuntu:
Invalid
Status in “linux” source package in Lucid:
Invalid
Status in “linux-armadaxp” source package in Lucid:
Invalid
Status in “linux-ec2” source package in Lucid:
Invalid
Status in “linux-lts-quantal” source package in Lucid:
Invalid
Status in “linux-lts-raring” source package in Lucid:
Invalid
Status in “linux-lts-saucy” source package in Lucid:
Invalid
Status in “linux-ti-omap4” source package in Lucid:
Invalid
Status in “linux” source package in Precise:
Fix Released
Status in “linux-armadaxp” source package in Precise:
Fix Released
Status in “linux-ec2” source package in Precise:
Invalid
Status in “linux-lts-quantal” source package in Precise:
Fix Committed
Status in “linux-lts-raring” source package in Precise:
Fix Committed
Status in “linux-lts-saucy” source package in Precise:
Fix Released
Status in “linux-ti-omap4” source package in Precise:
Fix Released
Status in “linux” source package in Quantal:
Fix Committed
Status in “linux-armadaxp” source package in Quantal:
Fix Committed
Status in “linux-ec2” source package in Quantal:
Invalid
Status in “linux-lts-quantal” source package in Quantal:
Invalid
Status in “linux-lts-raring” source package in Quantal:
Invalid
Status in “linux-lts-saucy” source package in Quantal:
Invalid
Status in “linux-ti-omap4” source package in Quantal:
Fix Committed
Status in “linux” source package in Saucy:
Fix Released
Status in “linux-armadaxp” source package in Saucy:
Invalid
Status in “linux-ec2” source package in Saucy:
Invalid
Status in “linux-lts-quantal” source package in Saucy:
Invalid
Status in “linux-lts-raring” source package in Saucy:
Invalid
Status in “linux-lts-saucy” source package in Saucy:
Invalid
Status in “linux-ti-omap4” source package in Saucy:
Fix Committed
Status in “linux” source package in Trusty:
Fix Released
Status in “linux-armadaxp” source package in Trusty:
Invalid
Status in “linux-ec2” source package in Trusty:
Invalid
Status in “linux-lts-quantal” source package in Trusty:
Invalid
Status in “linux-lts-raring” source package in Trusty:
Invalid
Status in “linux-lts-saucy” source package in Trusty:
Invalid
Status in “linux-ti-omap4” source package in Trusty:
Invalid
Bug description:
Something has changed in Ubuntu's Kernel 3.5.0-45 32 & 64-bit Intel,
has prevented IBM Domino's
"/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root
(setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3,
and HTTP processes. The IBM Domino Application Server's parent process
"/opt/ibm/domino/notes/latest/linux/server" runs as a Service Account
or a normal non-admin user, that launches "bindsock"and others like
"http", "ldap"
In the Live Domino Console we're seeing the Application Server report:
"Listener failure: 'bindsock' is missing, not executable, not owned by
root, not setuid root or user needs net_privaddr privilege."
Another thing in the Live Domino Console, which is unusual is:
"Error_CmdToDo_INVAL"... might be an IBM thang.
A number of us have to hold back the kernel now and there's lots of
scratching going on.
http://www-10.lotus.com/ldd/ndseforum.nsf/xpTopicThread.xsp?documentId=485F5F092833BCBE85257C33006AC7A3
It does seem to be limited to IBM Domino's "bindsock" binary and other
things are just fine, such as Nginx.
I have attached some files within the zip "ibm-domino-bindsock_strace.zip"
>>bindsock_binary_strace.txt
This is just running strace against the binary that isn't running in any
process.
>> domino-server-pid1052_strace-f.txt
The IBM Domino Application Server
("/opt/ibm/domino/notes/latest/linux/server") is running as PID 1052 so this is
what I applied "strace -f" to and towards the end, I told "server" to start the
"http" process ("l http") which would then try launch "bindsock" (I hope).
Hopeully this first attempt at strace provides some good info for you
kind folks :-)
Many thanks
MR
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-45-generic 3.5.0-45.68~precis
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
IBM Domino is able to bind to ports lower than 1024. This is fixed in
"saucy-proposed"
Enabled "saucy-proposed"
Installed linux-image-server/saucy-proposed linux-headers-server/saucy-
proposed linux-headers-generic/saucy-proposed linux-image-generic/saucy-
proposed
Rebooted with new kernel: Linux mru64dom64-1 3.11.0-17-generic
#31-Ubuntu SMP Mon Feb 3 21:52:43 UTC 2014 x86_64 x86_64 x86_64
GNU/Linux
Thanks folks !!!
MR
** Tags removed: verification-needed-saucy
** Tags added: verification-done-saucy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1269053
Title:
IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel
3.5.0-45.68
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux-armadaxp” package in Ubuntu:
Invalid
Status in “linux-ec2” package in Ubuntu:
Invalid
Status in “linux-lts-quantal” package in Ubuntu:
Invalid
Status in “linux-lts-raring” package in Ubuntu:
Invalid
Status in “linux-lts-saucy” package in Ubuntu:
Invalid
Status in “linux-ti-omap4” package in Ubuntu:
Invalid
Status in “linux” source package in Lucid:
Invalid
Status in “linux-armadaxp” source package in Lucid:
Invalid
Status in “linux-ec2” source package in Lucid:
Invalid
Status in “linux-lts-quantal” source package in Lucid:
Invalid
Status in “linux-lts-raring” source package in Lucid:
Invalid
Status in “linux-lts-saucy” source package in Lucid:
Invalid
Status in “linux-ti-omap4” source package in Lucid:
Invalid
Status in “linux” source package in Precise:
Fix Committed
Status in “linux-armadaxp” source package in Precise:
Fix Committed
Status in “linux-ec2” source package in Precise:
Invalid
Status in “linux-lts-quantal” source package in Precise:
Confirmed
Status in “linux-lts-raring” source package in Precise:
Fix Committed
Status in “linux-lts-saucy” source package in Precise:
Fix Committed
Status in “linux-ti-omap4” source package in Precise:
Fix Committed
Status in “linux” source package in Quantal:
Fix Committed
Status in “linux-armadaxp” source package in Quantal:
Confirmed
Status in “linux-ec2” source package in Quantal:
Invalid
Status in “linux-lts-quantal” source package in Quantal:
Invalid
Status in “linux-lts-raring” source package in Quantal:
Invalid
Status in “linux-lts-saucy” source package in Quantal:
Invalid
Status in “linux-ti-omap4” source package in Quantal:
Confirmed
Status in “linux” source package in Saucy:
Fix Committed
Status in “linux-armadaxp” source package in Saucy:
Invalid
Status in “linux-ec2” source package in Saucy:
Invalid
Status in “linux-lts-quantal” source package in Saucy:
Invalid
Status in “linux-lts-raring” source package in Saucy:
Invalid
Status in “linux-lts-saucy” source package in Saucy:
Invalid
Status in “linux-ti-omap4” source package in Saucy:
Confirmed
Status in “linux” source package in Trusty:
Fix Released
Status in “linux-armadaxp” source package in Trusty:
Invalid
Status in “linux-ec2” source package in Trusty:
Invalid
Status in “linux-lts-quantal” source package in Trusty:
Invalid
Status in “linux-lts-raring” source package in Trusty:
Invalid
Status in “linux-lts-saucy” source package in Trusty:
Invalid
Status in “linux-ti-omap4” source package in Trusty:
Invalid
Bug description:
Something has changed in Ubuntu's Kernel 3.5.0-45 32 & 64-bit Intel,
has prevented IBM Domino's
"/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root
(setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3,
and HTTP processes. The IBM Domino Application Server's parent process
"/opt/ibm/domino/notes/latest/linux/server" runs as a Service Account
or a normal non-admin user, that launches "bindsock"and others like
"http", "ldap"
In the Live Domino Console we're seeing the Application Server report:
"Listener failure: 'bindsock' is missing, not executable, not owned by
root, not setuid root or user needs net_privaddr privilege."
Another thing in the Live Domino Console, which is unusual is:
"Error_CmdToDo_INVAL"... might be an IBM thang.
A number of us have to hold back the kernel now and there's lots of
scratching going on.
http://www-10.lotus.com/ldd/ndseforum.nsf/xpTopicThread.xsp?documentId=485F5F092833BCBE85257C33006AC7A3
It does seem to be limited to IBM Domino's "bindsock" binary and other
things are just fine, such as Nginx.
I have attached some files within the zip "ibm-domino-bindsock_strace.zip"
>>bindsock_binary_strace.txt
This is just running strace against the binary that isn't running in any
process.
>> domino-server-pid1052_strace-f.txt
The IBM Domino Application Server
("/opt/ibm/domino/notes/latest/linux/server") is running as PID 1052 so this is
what I applied "strace -f" to and towards the end, I told "server" to start the
"http" process ("l http") which wo
[Kernel-packages] [Bug 2009522] Re: Upgrade Kernel 5.19.0-35-generic [Sound Blaster Recon3D / Z-Series] not detected anymore
*** This bug is a duplicate of bug 2009243 *** https://bugs.launchpad.net/bugs/2009243 Hi. I also am affected by this. I wondered why it worked on the install USB (5.15.xxx) but not on the actual computer it got installed on. This is on a fresh install of Ubuntu Desktop 64-bit 22.04, with an immediate `apt dist-upgrade -y` Thanks all! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009522 Title: Upgrade Kernel 5.19.0-35-generic [Sound Blaster Recon3D / Z-Series] not detected anymore Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: Upgrade Kernel 5.19.0-35-generic [Sound Blaster Recon3D / Z-Series] not detected anymore Operating System: Kubuntu 22.10 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: X11 Processors: 16 × Intel® Core™ i9-9900KF CPU @ 3.60GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z390 UD See also https://askubuntu.com/questions/1457574/upgrade- kernel-5-19-0-35-generic-sound-blaster-recon3d-z-series-not-detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009243] Re: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card
Hi, same for me and my new Ubuntu Desktop 22.04 64-bit installation and new "Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series] (rev 01)" (Sound Blaster Audigy Fx V2 + DBPro daughterboard). Wondered why it was working when playing around on the USB installation media (kernel 5.15) but not in the actually on the fresh install + dist- upgrade computer. Thanks folks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009243 Title: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: 2023-03-03 Attempted install of kernel 5.19.0-35 using the Linux Mint package installer LM 21.1 Vera, release 21.1). Clobbered my Sound Blaster AE-7. Could not even locate the device using Sound manager utility on Linux Mint Panel (the enumerated device showed up as the embedded sound chip on the mobo which I had previously disabled in the UEFI setup). Uninstalled kernel and reverted back to 5.19.0-32 using Timeshift restore feature which worked fine before the update to 5.19.0-35. Tried again to install 5.19.0-35 the same way, just to be sure. The SB AE-7 got clobbered again. So restored back to 5.19.0-32 generic one more time, using Timeshift. SB AE-7 works fine now with this lower version kernel. Current hardware config: Asus Prime Z790-P wifi mobo. Intel Core i3-13100 processor (with Intel UHD 730 graphics). Corsair Vengeance DDR5 32gb (2x16) ram, 5200Mhz. 3 x Nvme SSD. Boot drive is Western Digital Black SN770 500gb. Asus Nvidia RTX-3050 PCIe graphics card. Creative Labs Sound Blaster AE-7 audio card (PCIe). On-board audio chip (Realtek 7.1 Surround Sound High Definition Audio) is disabled in UEFI. UEFI is AMI/BIOS, revision 0812. Linux Mint 21.1 is running on barebones hardware, no VM involved. No other O/S's are installed on the machine. - Running sudo lspci -vnvn > lspci-vnvn.log gave the following error message... pcilib: sysfs_read_vpd: read failed: No such device --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mikey 4106 F wireplumber /dev/snd/controlC0: mikey 4106 F wireplumber /dev/snd/seq:mikey 4105 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-31 (32 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=854c280c-7c5c-494d-a304-db66cf592baf ro quiet splash ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: vera Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2023 dmi.bios.release: 8.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0812 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z790-P WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0812:bd02/24/2023:br8.12:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015455] [NEW] Intel PET not available on recent kernel causing QEMU VM crashes
Public bug reported: Hi Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to 5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are crashing every day. The CPU has Intel PET feature, but I've had to disable tdp_mmu using modprobe so stabilise the VMs. The platform: - Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The CPU tech specs on Dell R620: https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html The work-around (success with modprobe): https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021 LXD Issue: -- https://github.com/lxc/lxd/issues/11520 The QEMU log: - someadmin@us2204-iph-lxd03:/home/someadmin# cat /var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument with fd: 48, prog_fd: -1 KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=0008 EBX=00040ee0 ECX=83ac EDX= ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790 EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES = 00809300 CS =8000 7ff8 00809300 SS = 00809300 DS = 00809300 FS = 00809300 GS = 00809300 LDT= TR =0040 ff2a 0067 8b00 GDT= ff2a1fb0 0057 IDT= CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed. The CPU via lscpu: -- Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 40 On-line CPU(s) list: 0-39 Vendor ID: GenuineIntel Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz CPU family: 6 Model: 62 Thread(s) per core: 2 Core(s) per socket: 10 Socket(s): 2 Stepping:4 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS:5599.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs ibpb stibp tpr_shad ow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 640 KiB (20 instances) L1i: 640 KiB (20 instances) L2:5 MiB (20 instances) L3:50 MiB (2 instances) NUMA: NUMA node(s): 2 NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39 Vulnerabilities: Itlb multihit: KVM: Mitigation: Split huge pages L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Mds: Mitigation; Clear CPU buffers; SMT vulnerable Meltdown: Mitigation; PTI Mmio stale data: Unknown: No mitigations Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling, PBRSB-eIBRS Not affected Srbds: Not affected Tsx async abort: Not affected QEMU version: I am not able to determine this as yet, but whatever is bundled with the latest/stable channel's 5.12-c63881f version of the LXD Snap. When I am able to find out I will update this report. Thanks Mark ** Affects: linux (Ubuntu) Importance: Undecided Status: N
[Kernel-packages] [Bug 2015455] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2015455/+attachment/5661665/+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/2015455 Title: Intel PET not available on recent kernel causing QEMU VM crashes Status in linux package in Ubuntu: Incomplete Bug description: Hi Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to 5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are crashing every day. The CPU has Intel PET feature, but I've had to disable tdp_mmu using modprobe so stabilise the VMs. The platform: - Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The CPU tech specs on Dell R620: https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html The work-around (success with modprobe): https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021 LXD Issue: -- https://github.com/lxc/lxd/issues/11520 The QEMU log: - someadmin@us2204-iph-lxd03:/home/someadmin# cat /var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument with fd: 48, prog_fd: -1 KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=0008 EBX=00040ee0 ECX=83ac EDX= ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790 EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES = 00809300 CS =8000 7ff8 00809300 SS = 00809300 DS = 00809300 FS = 00809300 GS = 00809300 LDT= TR =0040 ff2a 0067 8b00 GDT= ff2a1fb0 0057 IDT= CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed. The CPU via lscpu: -- Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 40 On-line CPU(s) list: 0-39 Vendor ID: GenuineIntel Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz CPU family: 6 Model: 62 Thread(s) per core: 2 Core(s) per socket: 10 Socket(s): 2 Stepping:4 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS:5599.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs ibpb stibp tpr_shad ow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 640 KiB (20 instances) L1i: 640 KiB (20 instances) L2:5 MiB (20 instances) L3:50 MiB (2 instances) NUMA: NUMA node(s): 2 NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39 Vulnerabilities: Itlb multihit: KVM: Mitigation: Split huge pages L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Mds: Mitigation; Clear CPU buffers; SMT vulnerable Meltdown: Mitigation; PTI Mmio stale data: Unknown: No mitigations Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Sp
[Kernel-packages] [Bug 2015455] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2015455/+attachment/5661666/+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/2015455 Title: Intel PET not available on recent kernel causing QEMU VM crashes Status in linux package in Ubuntu: Incomplete Bug description: Hi Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to 5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are crashing every day. The CPU has Intel PET feature, but I've had to disable tdp_mmu using modprobe so stabilise the VMs. The platform: - Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The CPU tech specs on Dell R620: https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html The work-around (success with modprobe): https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021 LXD Issue: -- https://github.com/lxc/lxd/issues/11520 The QEMU log: - someadmin@us2204-iph-lxd03:/home/someadmin# cat /var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument with fd: 48, prog_fd: -1 KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=0008 EBX=00040ee0 ECX=83ac EDX= ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790 EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES = 00809300 CS =8000 7ff8 00809300 SS = 00809300 DS = 00809300 FS = 00809300 GS = 00809300 LDT= TR =0040 ff2a 0067 8b00 GDT= ff2a1fb0 0057 IDT= CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed. The CPU via lscpu: -- Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 40 On-line CPU(s) list: 0-39 Vendor ID: GenuineIntel Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz CPU family: 6 Model: 62 Thread(s) per core: 2 Core(s) per socket: 10 Socket(s): 2 Stepping:4 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS:5599.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs ibpb stibp tpr_shad ow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 640 KiB (20 instances) L1i: 640 KiB (20 instances) L2:5 MiB (20 instances) L3:50 MiB (2 instances) NUMA: NUMA node(s): 2 NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39 Vulnerabilities: Itlb multihit: KVM: Mitigation: Split huge pages L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Mds: Mitigation; Clear CPU buffers; SMT vulnerable Meltdown: Mitigation; PTI Mmio stale data: Unknown: No mitigations Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
[Kernel-packages] [Bug 2015455] Re: Intel PET not available on recent kernel causing QEMU VM crashes
apport information ** Tags added: apport-collected jammy uec-images ** Description changed: Hi Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to 5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are crashing every day. The CPU has Intel PET feature, but I've had to disable tdp_mmu using modprobe so stabilise the VMs. The platform: - Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The CPU tech specs on Dell R620: https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html The work-around (success with modprobe): https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021 LXD Issue: -- https://github.com/lxc/lxd/issues/11520 The QEMU log: - someadmin@us2204-iph-lxd03:/home/someadmin# cat /var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument with fd: 48, prog_fd: -1 KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=0008 EBX=00040ee0 ECX=83ac EDX= ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790 EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES = 00809300 CS =8000 7ff8 00809300 SS = 00809300 DS = 00809300 FS = 00809300 GS = 00809300 LDT= TR =0040 ff2a 0067 8b00 GDT= ff2a1fb0 0057 IDT= CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed. The CPU via lscpu: -- Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 40 On-line CPU(s) list: 0-39 Vendor ID: GenuineIntel Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz CPU family: 6 Model: 62 Thread(s) per core: 2 Core(s) per socket: 10 Socket(s): 2 Stepping:4 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS:5599.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs ibpb stibp tpr_shad ow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 640 KiB (20 instances) L1i: 640 KiB (20 instances) L2:5 MiB (20 instances) L3:50 MiB (2 instances) NUMA: NUMA node(s): 2 NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39 Vulnerabilities: Itlb multihit: KVM: Mitigation: Split huge pages L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Mds: Mitigation; Clear CPU buffers; SMT vulnerable Meltdown: Mitigation; PTI Mmio stale data: Unknown: No mitigations Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling, PBRSB-eIBRS Not affected Srbds: Not affected Tsx async abort: Not affected QEMU version:
[Kernel-packages] [Bug 2015455] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2015455/+attachment/5661668/+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/2015455 Title: Intel PET not available on recent kernel causing QEMU VM crashes Status in linux package in Ubuntu: Incomplete Bug description: Hi Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to 5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are crashing every day. The CPU has Intel PET feature, but I've had to disable tdp_mmu using modprobe so stabilise the VMs. The platform: - Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The CPU tech specs on Dell R620: https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html The work-around (success with modprobe): https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021 LXD Issue: -- https://github.com/lxc/lxd/issues/11520 The QEMU log: - someadmin@us2204-iph-lxd03:/home/someadmin# cat /var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument with fd: 48, prog_fd: -1 KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=0008 EBX=00040ee0 ECX=83ac EDX= ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790 EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES = 00809300 CS =8000 7ff8 00809300 SS = 00809300 DS = 00809300 FS = 00809300 GS = 00809300 LDT= TR =0040 ff2a 0067 8b00 GDT= ff2a1fb0 0057 IDT= CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed. The CPU via lscpu: -- Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 40 On-line CPU(s) list: 0-39 Vendor ID: GenuineIntel Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz CPU family: 6 Model: 62 Thread(s) per core: 2 Core(s) per socket: 10 Socket(s): 2 Stepping:4 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS:5599.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs ibpb stibp tpr_shad ow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 640 KiB (20 instances) L1i: 640 KiB (20 instances) L2:5 MiB (20 instances) L3:50 MiB (2 instances) NUMA: NUMA node(s): 2 NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39 Vulnerabilities: Itlb multihit: KVM: Mitigation: Split huge pages L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Mds: Mitigation; Clear CPU buffers; SMT vulnerable Meltdown: Mitigation; PTI Mmio stale data: Unknown: No mitigations Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
[Kernel-packages] [Bug 2015455] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2015455/+attachment/5661667/+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/2015455 Title: Intel PET not available on recent kernel causing QEMU VM crashes Status in linux package in Ubuntu: Incomplete Bug description: Hi Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to 5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are crashing every day. The CPU has Intel PET feature, but I've had to disable tdp_mmu using modprobe so stabilise the VMs. The platform: - Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The CPU tech specs on Dell R620: https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html The work-around (success with modprobe): https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021 LXD Issue: -- https://github.com/lxc/lxd/issues/11520 The QEMU log: - someadmin@us2204-iph-lxd03:/home/someadmin# cat /var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument with fd: 48, prog_fd: -1 KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=0008 EBX=00040ee0 ECX=83ac EDX= ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790 EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES = 00809300 CS =8000 7ff8 00809300 SS = 00809300 DS = 00809300 FS = 00809300 GS = 00809300 LDT= TR =0040 ff2a 0067 8b00 GDT= ff2a1fb0 0057 IDT= CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed. The CPU via lscpu: -- Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 40 On-line CPU(s) list: 0-39 Vendor ID: GenuineIntel Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz CPU family: 6 Model: 62 Thread(s) per core: 2 Core(s) per socket: 10 Socket(s): 2 Stepping:4 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS:5599.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs ibpb stibp tpr_shad ow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 640 KiB (20 instances) L1i: 640 KiB (20 instances) L2:5 MiB (20 instances) L3:50 MiB (2 instances) NUMA: NUMA node(s): 2 NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39 Vulnerabilities: Itlb multihit: KVM: Mitigation: Split huge pages L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Mds: Mitigation; Clear CPU buffers; SMT vulnerable Meltdown: Mitigation; PTI Mmio stale data: Unknown: No mitigations Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Sp
[Kernel-packages] [Bug 2015455] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2015455/+attachment/5661669/+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/2015455 Title: Intel PET not available on recent kernel causing QEMU VM crashes Status in linux package in Ubuntu: Incomplete Bug description: Hi Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to 5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are crashing every day. The CPU has Intel PET feature, but I've had to disable tdp_mmu using modprobe so stabilise the VMs. The platform: - Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The CPU tech specs on Dell R620: https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html The work-around (success with modprobe): https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021 LXD Issue: -- https://github.com/lxc/lxd/issues/11520 The QEMU log: - someadmin@us2204-iph-lxd03:/home/someadmin# cat /var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument with fd: 48, prog_fd: -1 KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=0008 EBX=00040ee0 ECX=83ac EDX= ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790 EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES = 00809300 CS =8000 7ff8 00809300 SS = 00809300 DS = 00809300 FS = 00809300 GS = 00809300 LDT= TR =0040 ff2a 0067 8b00 GDT= ff2a1fb0 0057 IDT= CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed. The CPU via lscpu: -- Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 40 On-line CPU(s) list: 0-39 Vendor ID: GenuineIntel Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz CPU family: 6 Model: 62 Thread(s) per core: 2 Core(s) per socket: 10 Socket(s): 2 Stepping:4 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS:5599.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs ibpb stibp tpr_shad ow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 640 KiB (20 instances) L1i: 640 KiB (20 instances) L2:5 MiB (20 instances) L3:50 MiB (2 instances) NUMA: NUMA node(s): 2 NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39 Vulnerabilities: Itlb multihit: KVM: Mitigation: Split huge pages L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Mds: Mitigation; Clear CPU buffers; SMT vulnerable Meltdown: Mitigation; PTI Mmio stale data: Unknown: No mitigations Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
[Kernel-packages] [Bug 2015455] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2015455/+attachment/5661670/+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/2015455 Title: Intel PET not available on recent kernel causing QEMU VM crashes Status in linux package in Ubuntu: Incomplete Bug description: Hi Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to 5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are crashing every day. The CPU has Intel PET feature, but I've had to disable tdp_mmu using modprobe so stabilise the VMs. The platform: - Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The CPU tech specs on Dell R620: https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html The work-around (success with modprobe): https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021 LXD Issue: -- https://github.com/lxc/lxd/issues/11520 The QEMU log: - someadmin@us2204-iph-lxd03:/home/someadmin# cat /var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument with fd: 48, prog_fd: -1 KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=0008 EBX=00040ee0 ECX=83ac EDX= ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790 EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES = 00809300 CS =8000 7ff8 00809300 SS = 00809300 DS = 00809300 FS = 00809300 GS = 00809300 LDT= TR =0040 ff2a 0067 8b00 GDT= ff2a1fb0 0057 IDT= CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed. The CPU via lscpu: -- Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 40 On-line CPU(s) list: 0-39 Vendor ID: GenuineIntel Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz CPU family: 6 Model: 62 Thread(s) per core: 2 Core(s) per socket: 10 Socket(s): 2 Stepping:4 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS:5599.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs ibpb stibp tpr_shad ow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 640 KiB (20 instances) L1i: 640 KiB (20 instances) L2:5 MiB (20 instances) L3:50 MiB (2 instances) NUMA: NUMA node(s): 2 NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39 Vulnerabilities: Itlb multihit: KVM: Mitigation: Split huge pages L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Mds: Mitigation; Clear CPU buffers; SMT vulnerable Meltdown: Mitigation; PTI Mmio stale data: Unknown: No mitigations Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via
[Kernel-packages] [Bug 2015455] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2015455/+attachment/5661672/+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/2015455 Title: Intel PET not available on recent kernel causing QEMU VM crashes Status in linux package in Ubuntu: Incomplete Bug description: Hi Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to 5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are crashing every day. The CPU has Intel PET feature, but I've had to disable tdp_mmu using modprobe so stabilise the VMs. The platform: - Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The CPU tech specs on Dell R620: https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html The work-around (success with modprobe): https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021 LXD Issue: -- https://github.com/lxc/lxd/issues/11520 The QEMU log: - someadmin@us2204-iph-lxd03:/home/someadmin# cat /var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument with fd: 48, prog_fd: -1 KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=0008 EBX=00040ee0 ECX=83ac EDX= ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790 EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES = 00809300 CS =8000 7ff8 00809300 SS = 00809300 DS = 00809300 FS = 00809300 GS = 00809300 LDT= TR =0040 ff2a 0067 8b00 GDT= ff2a1fb0 0057 IDT= CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed. The CPU via lscpu: -- Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 40 On-line CPU(s) list: 0-39 Vendor ID: GenuineIntel Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz CPU family: 6 Model: 62 Thread(s) per core: 2 Core(s) per socket: 10 Socket(s): 2 Stepping:4 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS:5599.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs ibpb stibp tpr_shad ow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 640 KiB (20 instances) L1i: 640 KiB (20 instances) L2:5 MiB (20 instances) L3:50 MiB (2 instances) NUMA: NUMA node(s): 2 NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39 Vulnerabilities: Itlb multihit: KVM: Mitigation: Split huge pages L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Mds: Mitigation; Clear CPU buffers; SMT vulnerable Meltdown: Mitigation; PTI Mmio stale data: Unknown: No mitigations Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disable
[Kernel-packages] [Bug 2015455] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2015455/+attachment/5661671/+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/2015455 Title: Intel PET not available on recent kernel causing QEMU VM crashes Status in linux package in Ubuntu: Incomplete Bug description: Hi Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to 5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are crashing every day. The CPU has Intel PET feature, but I've had to disable tdp_mmu using modprobe so stabilise the VMs. The platform: - Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The CPU tech specs on Dell R620: https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html The work-around (success with modprobe): https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021 LXD Issue: -- https://github.com/lxc/lxd/issues/11520 The QEMU log: - someadmin@us2204-iph-lxd03:/home/someadmin# cat /var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument with fd: 48, prog_fd: -1 KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=0008 EBX=00040ee0 ECX=83ac EDX= ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790 EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES = 00809300 CS =8000 7ff8 00809300 SS = 00809300 DS = 00809300 FS = 00809300 GS = 00809300 LDT= TR =0040 ff2a 0067 8b00 GDT= ff2a1fb0 0057 IDT= CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed. The CPU via lscpu: -- Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 40 On-line CPU(s) list: 0-39 Vendor ID: GenuineIntel Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz CPU family: 6 Model: 62 Thread(s) per core: 2 Core(s) per socket: 10 Socket(s): 2 Stepping:4 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS:5599.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs ibpb stibp tpr_shad ow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 640 KiB (20 instances) L1i: 640 KiB (20 instances) L2:5 MiB (20 instances) L3:50 MiB (2 instances) NUMA: NUMA node(s): 2 NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39 Vulnerabilities: Itlb multihit: KVM: Mitigation: Split huge pages L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Mds: Mitigation; Clear CPU buffers; SMT vulnerable Meltdown: Mitigation; PTI Mmio stale data: Unknown: No mitigations Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass
[Kernel-packages] [Bug 2015455] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2015455/+attachment/5661674/+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/2015455 Title: Intel PET not available on recent kernel causing QEMU VM crashes Status in linux package in Ubuntu: Incomplete Bug description: Hi Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to 5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are crashing every day. The CPU has Intel PET feature, but I've had to disable tdp_mmu using modprobe so stabilise the VMs. The platform: - Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The CPU tech specs on Dell R620: https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html The work-around (success with modprobe): https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021 LXD Issue: -- https://github.com/lxc/lxd/issues/11520 The QEMU log: - someadmin@us2204-iph-lxd03:/home/someadmin# cat /var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument with fd: 48, prog_fd: -1 KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=0008 EBX=00040ee0 ECX=83ac EDX= ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790 EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES = 00809300 CS =8000 7ff8 00809300 SS = 00809300 DS = 00809300 FS = 00809300 GS = 00809300 LDT= TR =0040 ff2a 0067 8b00 GDT= ff2a1fb0 0057 IDT= CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed. The CPU via lscpu: -- Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 40 On-line CPU(s) list: 0-39 Vendor ID: GenuineIntel Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz CPU family: 6 Model: 62 Thread(s) per core: 2 Core(s) per socket: 10 Socket(s): 2 Stepping:4 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS:5599.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs ibpb stibp tpr_shad ow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 640 KiB (20 instances) L1i: 640 KiB (20 instances) L2:5 MiB (20 instances) L3:50 MiB (2 instances) NUMA: NUMA node(s): 2 NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39 Vulnerabilities: Itlb multihit: KVM: Mitigation: Split huge pages L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Mds: Mitigation; Clear CPU buffers; SMT vulnerable Meltdown: Mitigation; PTI Mmio stale data: Unknown: No mitigations Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
[Kernel-packages] [Bug 2015455] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2015455/+attachment/5661673/+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/2015455 Title: Intel PET not available on recent kernel causing QEMU VM crashes Status in linux package in Ubuntu: Incomplete Bug description: Hi Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to 5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are crashing every day. The CPU has Intel PET feature, but I've had to disable tdp_mmu using modprobe so stabilise the VMs. The platform: - Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The CPU tech specs on Dell R620: https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html The work-around (success with modprobe): https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021 LXD Issue: -- https://github.com/lxc/lxd/issues/11520 The QEMU log: - someadmin@us2204-iph-lxd03:/home/someadmin# cat /var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument with fd: 48, prog_fd: -1 KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=0008 EBX=00040ee0 ECX=83ac EDX= ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790 EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES = 00809300 CS =8000 7ff8 00809300 SS = 00809300 DS = 00809300 FS = 00809300 GS = 00809300 LDT= TR =0040 ff2a 0067 8b00 GDT= ff2a1fb0 0057 IDT= CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed. The CPU via lscpu: -- Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 40 On-line CPU(s) list: 0-39 Vendor ID: GenuineIntel Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz CPU family: 6 Model: 62 Thread(s) per core: 2 Core(s) per socket: 10 Socket(s): 2 Stepping:4 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS:5599.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs ibpb stibp tpr_shad ow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 640 KiB (20 instances) L1i: 640 KiB (20 instances) L2:5 MiB (20 instances) L3:50 MiB (2 instances) NUMA: NUMA node(s): 2 NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39 Vulnerabilities: Itlb multihit: KVM: Mitigation: Split huge pages L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Mds: Mitigation; Clear CPU buffers; SMT vulnerable Meltdown: Mitigation; PTI Mmio stale data: Unknown: No mitigations Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via
[Kernel-packages] [Bug 2015455] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2015455/+attachment/5661675/+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/2015455 Title: Intel PET not available on recent kernel causing QEMU VM crashes Status in linux package in Ubuntu: Incomplete Bug description: Hi Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to 5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are crashing every day. The CPU has Intel PET feature, but I've had to disable tdp_mmu using modprobe so stabilise the VMs. The platform: - Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The CPU tech specs on Dell R620: https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html The work-around (success with modprobe): https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021 LXD Issue: -- https://github.com/lxc/lxd/issues/11520 The QEMU log: - someadmin@us2204-iph-lxd03:/home/someadmin# cat /var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument with fd: 48, prog_fd: -1 KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=0008 EBX=00040ee0 ECX=83ac EDX= ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790 EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES = 00809300 CS =8000 7ff8 00809300 SS = 00809300 DS = 00809300 FS = 00809300 GS = 00809300 LDT= TR =0040 ff2a 0067 8b00 GDT= ff2a1fb0 0057 IDT= CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed. The CPU via lscpu: -- Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 40 On-line CPU(s) list: 0-39 Vendor ID: GenuineIntel Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz CPU family: 6 Model: 62 Thread(s) per core: 2 Core(s) per socket: 10 Socket(s): 2 Stepping:4 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS:5599.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs ibpb stibp tpr_shad ow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 640 KiB (20 instances) L1i: 640 KiB (20 instances) L2:5 MiB (20 instances) L3:50 MiB (2 instances) NUMA: NUMA node(s): 2 NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39 Vulnerabilities: Itlb multihit: KVM: Mitigation: Split huge pages L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Mds: Mitigation; Clear CPU buffers; SMT vulnerable Meltdown: Mitigation; PTI Mmio stale data: Unknown: No mitigations Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via p
[Kernel-packages] [Bug 2015455] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2015455/+attachment/5661676/+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/2015455 Title: Intel PET not available on recent kernel causing QEMU VM crashes Status in linux package in Ubuntu: Incomplete Bug description: Hi Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to 5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are crashing every day. The CPU has Intel PET feature, but I've had to disable tdp_mmu using modprobe so stabilise the VMs. The platform: - Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The CPU tech specs on Dell R620: https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html The work-around (success with modprobe): https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021 LXD Issue: -- https://github.com/lxc/lxd/issues/11520 The QEMU log: - someadmin@us2204-iph-lxd03:/home/someadmin# cat /var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument with fd: 48, prog_fd: -1 KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=0008 EBX=00040ee0 ECX=83ac EDX= ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790 EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES = 00809300 CS =8000 7ff8 00809300 SS = 00809300 DS = 00809300 FS = 00809300 GS = 00809300 LDT= TR =0040 ff2a 0067 8b00 GDT= ff2a1fb0 0057 IDT= CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed. The CPU via lscpu: -- Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 40 On-line CPU(s) list: 0-39 Vendor ID: GenuineIntel Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz CPU family: 6 Model: 62 Thread(s) per core: 2 Core(s) per socket: 10 Socket(s): 2 Stepping:4 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS:5599.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs ibpb stibp tpr_shad ow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 640 KiB (20 instances) L1i: 640 KiB (20 instances) L2:5 MiB (20 instances) L3:50 MiB (2 instances) NUMA: NUMA node(s): 2 NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39 Vulnerabilities: Itlb multihit: KVM: Mitigation: Split huge pages L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Mds: Mitigation; Clear CPU buffers; SMT vulnerable Meltdown: Mitigation; PTI Mmio stale data: Unknown: No mitigations Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
[Kernel-packages] [Bug 2015455] Re: Intel PET not available on recent kernel causing QEMU VM crashes
** Changed in: linux (Ubuntu) Status: Incomplete => New ** 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/2015455 Title: Intel PET not available on recent kernel causing QEMU VM crashes Status in linux package in Ubuntu: Confirmed Bug description: Hi Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to 5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are crashing every day. The CPU has Intel PET feature, but I've had to disable tdp_mmu using modprobe so stabilise the VMs. The platform: - Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The CPU tech specs on Dell R620: https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html The work-around (success with modprobe): https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021 LXD Issue: -- https://github.com/lxc/lxd/issues/11520 The QEMU log: - someadmin@us2204-iph-lxd03:/home/someadmin# cat /var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument with fd: 48, prog_fd: -1 KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=0008 EBX=00040ee0 ECX=83ac EDX= ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790 EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES = 00809300 CS =8000 7ff8 00809300 SS = 00809300 DS = 00809300 FS = 00809300 GS = 00809300 LDT= TR =0040 ff2a 0067 8b00 GDT= ff2a1fb0 0057 IDT= CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed. The CPU via lscpu: -- Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 40 On-line CPU(s) list: 0-39 Vendor ID: GenuineIntel Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz CPU family: 6 Model: 62 Thread(s) per core: 2 Core(s) per socket: 10 Socket(s): 2 Stepping:4 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS:5599.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs ibpb stibp tpr_shad ow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 640 KiB (20 instances) L1i: 640 KiB (20 instances) L2:5 MiB (20 instances) L3:50 MiB (2 instances) NUMA: NUMA node(s): 2 NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39 Vulnerabilities: Itlb multihit: KVM: Mitigation: Split huge pages L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Mds: Mitigation; Clear CPU buffers; SMT vulnerable Meltdown: Mitigation; PTI Mmio stale data: Unknown: No mitigations Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1
[Kernel-packages] [Bug 2009243] Re: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card
Fixed for me in 5.19.0-42 and with Nvidia graphics. Thanks !!! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009243 Title: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: 2023-03-03 Attempted install of kernel 5.19.0-35 using the Linux Mint package installer LM 21.1 Vera, release 21.1). Clobbered my Sound Blaster AE-7. Could not even locate the device using Sound manager utility on Linux Mint Panel (the enumerated device showed up as the embedded sound chip on the mobo which I had previously disabled in the UEFI setup). Uninstalled kernel and reverted back to 5.19.0-32 using Timeshift restore feature which worked fine before the update to 5.19.0-35. Tried again to install 5.19.0-35 the same way, just to be sure. The SB AE-7 got clobbered again. So restored back to 5.19.0-32 generic one more time, using Timeshift. SB AE-7 works fine now with this lower version kernel. Current hardware config: Asus Prime Z790-P wifi mobo. Intel Core i3-13100 processor (with Intel UHD 730 graphics). Corsair Vengeance DDR5 32gb (2x16) ram, 5200Mhz. 3 x Nvme SSD. Boot drive is Western Digital Black SN770 500gb. Asus Nvidia RTX-3050 PCIe graphics card. Creative Labs Sound Blaster AE-7 audio card (PCIe). On-board audio chip (Realtek 7.1 Surround Sound High Definition Audio) is disabled in UEFI. UEFI is AMI/BIOS, revision 0812. Linux Mint 21.1 is running on barebones hardware, no VM involved. No other O/S's are installed on the machine. - Running sudo lspci -vnvn > lspci-vnvn.log gave the following error message... pcilib: sysfs_read_vpd: read failed: No such device --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mikey 4106 F wireplumber /dev/snd/controlC0: mikey 4106 F wireplumber /dev/snd/seq:mikey 4105 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-31 (32 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=854c280c-7c5c-494d-a304-db66cf592baf ro quiet splash ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: vera Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2023 dmi.bios.release: 8.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0812 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z790-P WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0812:bd02/24/2023:br8.12:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
