[Kernel-packages] [Bug 1749961]
I also have the issue. Using Proxmox 7.2 (Debian Bullseye) with a Lenovo M910q core-i7-7700T, using two TPLink UE300 (RTL8153) USB to 1Gbe Ethernet adapters. Each one is stable in a lower USB slot. Swapping the adapters does not change the behavior and only impacts the USB device in the higher slot. Changes to different ports without change. Easily reproducible with the following commands. Basically I'm trying to plumb bond0 again, which works initially, I get the xhci_hcd warning, and the link is down again. System details are also below. root@higgins:~# dmesg -C ; ifup -a ; ip link | grep enx ; \ > dmesg -H ; dmesg -C ; sleep 70 ; \ > ip link | grep enx ; dmesg -H 3: enxd03745be5afc: mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT group default qlen 1000 16: enx54af9786ab11: mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT group default qlen 1000 [Sep 3 11:05] device enx54af9786ab11 entered promiscuous mode [ +0.001236] bond0: (slave enx54af9786ab11): Enslaving as a backup interface with a down link [ +0.006363] vmbr0: the hash_elasticity option has been deprecated and is always 16 [ +0.013972] r8152 2-4:1.0 enx54af9786ab11: Promiscuous mode enabled [ +0.001344] r8152 2-4:1.0 enx54af9786ab11: carrier on 3: enxd03745be5afc: mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT group default qlen 1000 17: enx54af9786ab11: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 [Sep 3 11:05] bond0: (slave enx54af9786ab11): link status definitely up, 1000 Mbps full duplex [Sep 3 11:06] usb 2-4: USB disconnect, device number 12 [ +0.001544] xhci_hcd :00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. [ +0.001435] bond0: (slave enx54af9786ab11): Releasing backup interface [ +0.029081] device enx54af9786ab11 left promiscuous mode [ +0.316190] usb 2-4: new SuperSpeed USB device number 13 using xhci_hcd [ +0.022053] usb 2-4: New USB device found, idVendor=2357, idProduct=0601, bcdDevice=30.00 [ +0.001297] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ +0.001337] usb 2-4: Product: USB 10/100/1000 LAN [ +0.001261] usb 2-4: Manufacturer: TP-Link [ +0.001208] usb 2-4: SerialNumber: 01 [ +0.137200] usb 2-4: reset SuperSpeed USB device number 13 using xhci_hcd [ +0.049197] r8152 2-4:1.0: load rtl8153a-4 v2 02/07/20 successfully [ +0.030905] r8152 2-4:1.0 eth0: v1.12.12 [ +0.007834] r8152 2-4:1.0 enx54af9786ab11: renamed from eth0 root@higgins:~# --- System Details --- root@higgins:~# uname -a Linux higgins 5.15.39-4-pve #1 SMP PVE 5.15.39-4 (Mon, 08 Aug 2022 15:11:15 +0200) x86_64 GNU/Linux root@higgins:~# lspci -k -nn | grep -B2 xhci 00:14.0 USB controller [0c03]: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller [8086:a2af] Subsystem: Lenovo 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller [17aa:310b] Kernel driver in use: xhci_hcd Kernel modules: xhci_pci root@higgins:~# lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M ID 2357:0601 TP-Link UE300 10/100/1000 LAN (ethernet mode) [Realtek RTL8153] |__ Port 4: Dev 13, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M ID 2357:0601 TP-Link UE300 10/100/1000 LAN (ethernet mode) [Realtek RTL8153] /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub root@higgins:~# modinfo r8152 filename: /lib/modules/5.15.39-4-pve/kernel/drivers/net/usb/r8152.ko version:v1.12.12 license:GPL description:Realtek RTL8152/RTL8153 Based USB Ethernet Adapters author: Realtek linux nic maintainers firmware: rtl_nic/rtl8156b-2.fw firmware: rtl_nic/rtl8156a-2.fw firmware: rtl_nic/rtl8153c-1.fw firmware: rtl_nic/rtl8153b-2.fw firmware: rtl_nic/rtl8153a-4.fw firmware: rtl_nic/rtl8153a-3.fw firmware: rtl_nic/rtl8153a-2.fw srcversion: 9144C27A9617457A5BEE55E alias: usb:v2357p0601d*dc*dsc*dp*ic02isc06ip00in* alias: usb:v2357p0601d*dc*dsc*dp*icFFisc*ip*in* alias: usb:v0955p09FFd*dc*dsc*dp*ic02isc06ip00in* alias: usb:v0955p09FFd*dc*dsc*dp*icFFisc*ip*in* alias: usb:v13B1p0041d*dc*dsc*dp*ic02isc06ip00in* alias: usb:v13B1p0041d*dc*dsc*dp*icFFisc*ip*in* alias: usb:v17EFpA387d*dc*dsc*dp*ic02isc06ip00in* alias: usb:v17EFpA387d*dc*dsc*dp*icFFisc*ip*in* alias: usb:v17EFp721Ed*dc*dsc*dp*ic02isc06ip00in* alias: usb:v17EFp721Ed*dc*dsc*dp*icFFisc*ip*in* alias: usb:v17EFp7214d*dc*dsc*dp*ic02isc06ip00in* alias: usb:v17EFp7214d*dc*dsc*dp*icFFisc*ip*in* alias: usb:v17EFp720Cd*dc*dsc*dp*ic02isc06ip00in* alias: usb:v17EFp720Cd*dc*dsc*dp*icFFisc*ip*in*
[Kernel-packages] [Bug 1667750]
I also have the issue. Using Proxmox 7.2 (Debian Bullseye) with a Lenovo M910q core-i7-7700T, using two TPLink UE300 (RTL8153) USB to 1Gbe Ethernet adapters. Each one is stable in a lower USB slot. Swapping the adapters does not change the behavior and only impacts the USB device in the higher slot. Changes to different ports without change. Easily reproducible with the following commands. Basically I'm trying to plumb bond0 again, which works initially, I get the xhci_hcd warning, and the link is down again. System details are also below. root@higgins:~# dmesg -C ; ifup -a ; ip link | grep enx ; \ > dmesg -H ; dmesg -C ; sleep 70 ; \ > ip link | grep enx ; dmesg -H 3: enxd03745be5afc: mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT group default qlen 1000 16: enx54af9786ab11: mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT group default qlen 1000 [Sep 3 11:05] device enx54af9786ab11 entered promiscuous mode [ +0.001236] bond0: (slave enx54af9786ab11): Enslaving as a backup interface with a down link [ +0.006363] vmbr0: the hash_elasticity option has been deprecated and is always 16 [ +0.013972] r8152 2-4:1.0 enx54af9786ab11: Promiscuous mode enabled [ +0.001344] r8152 2-4:1.0 enx54af9786ab11: carrier on 3: enxd03745be5afc: mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT group default qlen 1000 17: enx54af9786ab11: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 [Sep 3 11:05] bond0: (slave enx54af9786ab11): link status definitely up, 1000 Mbps full duplex [Sep 3 11:06] usb 2-4: USB disconnect, device number 12 [ +0.001544] xhci_hcd :00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. [ +0.001435] bond0: (slave enx54af9786ab11): Releasing backup interface [ +0.029081] device enx54af9786ab11 left promiscuous mode [ +0.316190] usb 2-4: new SuperSpeed USB device number 13 using xhci_hcd [ +0.022053] usb 2-4: New USB device found, idVendor=2357, idProduct=0601, bcdDevice=30.00 [ +0.001297] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ +0.001337] usb 2-4: Product: USB 10/100/1000 LAN [ +0.001261] usb 2-4: Manufacturer: TP-Link [ +0.001208] usb 2-4: SerialNumber: 01 [ +0.137200] usb 2-4: reset SuperSpeed USB device number 13 using xhci_hcd [ +0.049197] r8152 2-4:1.0: load rtl8153a-4 v2 02/07/20 successfully [ +0.030905] r8152 2-4:1.0 eth0: v1.12.12 [ +0.007834] r8152 2-4:1.0 enx54af9786ab11: renamed from eth0 root@higgins:~# --- System Details --- root@higgins:~# uname -a Linux higgins 5.15.39-4-pve #1 SMP PVE 5.15.39-4 (Mon, 08 Aug 2022 15:11:15 +0200) x86_64 GNU/Linux root@higgins:~# lspci -k -nn | grep -B2 xhci 00:14.0 USB controller [0c03]: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller [8086:a2af] Subsystem: Lenovo 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller [17aa:310b] Kernel driver in use: xhci_hcd Kernel modules: xhci_pci root@higgins:~# lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M ID 2357:0601 TP-Link UE300 10/100/1000 LAN (ethernet mode) [Realtek RTL8153] |__ Port 4: Dev 13, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M ID 2357:0601 TP-Link UE300 10/100/1000 LAN (ethernet mode) [Realtek RTL8153] /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub root@higgins:~# modinfo r8152 filename: /lib/modules/5.15.39-4-pve/kernel/drivers/net/usb/r8152.ko version:v1.12.12 license:GPL description:Realtek RTL8152/RTL8153 Based USB Ethernet Adapters author: Realtek linux nic maintainers firmware: rtl_nic/rtl8156b-2.fw firmware: rtl_nic/rtl8156a-2.fw firmware: rtl_nic/rtl8153c-1.fw firmware: rtl_nic/rtl8153b-2.fw firmware: rtl_nic/rtl8153a-4.fw firmware: rtl_nic/rtl8153a-3.fw firmware: rtl_nic/rtl8153a-2.fw srcversion: 9144C27A9617457A5BEE55E alias: usb:v2357p0601d*dc*dsc*dp*ic02isc06ip00in* alias: usb:v2357p0601d*dc*dsc*dp*icFFisc*ip*in* alias: usb:v0955p09FFd*dc*dsc*dp*ic02isc06ip00in* alias: usb:v0955p09FFd*dc*dsc*dp*icFFisc*ip*in* alias: usb:v13B1p0041d*dc*dsc*dp*ic02isc06ip00in* alias: usb:v13B1p0041d*dc*dsc*dp*icFFisc*ip*in* alias: usb:v17EFpA387d*dc*dsc*dp*ic02isc06ip00in* alias: usb:v17EFpA387d*dc*dsc*dp*icFFisc*ip*in* alias: usb:v17EFp721Ed*dc*dsc*dp*ic02isc06ip00in* alias: usb:v17EFp721Ed*dc*dsc*dp*icFFisc*ip*in* alias: usb:v17EFp7214d*dc*dsc*dp*ic02isc06ip00in* alias: usb:v17EFp7214d*dc*dsc*dp*icFFisc*ip*in* alias: usb:v17EFp720Cd*dc*dsc*dp*ic02isc06ip00in* alias: usb:v17EFp720Cd*dc*dsc*dp*icFFisc*ip*in*
[Kernel-packages] [Bug 1988473] Re: Version 5.15.0-47 Breaks Virtualbox Win10 VM
changing package to virtualbox, as hints lead there ** Package changed: linux (Ubuntu) => virtualbox (Ubuntu) ** Summary changed: - Version 5.15.0-47 Breaks Virtualbox Win10 VM + VirtualBox 6.1.34 guests crash with kernel 5.15.0-47 -- 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/1988473 Title: VirtualBox 6.1.34 guests crash with kernel 5.15.0-47 Status in virtualbox package in Ubuntu: Confirmed Bug description: The updated linux kernel would not allow my Win10 VM to boot. Rebooting Ubuntu into the 5.15.0-46 version restored the avility to boot. The 47 version also corrupted the VM, so I had to use a backup. I don't know if the problem was really with new Intel microcode that was installed with the new kernel. VB kernel modules were updated by dkms with the new version 47 install, so that should not be the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1980 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 14:54:58 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-12-04 (1366 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=ce42a622-1220-4d20-a2b5-97e15e83c527 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (127 days ago) dmi.bios.date: 07/02/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd07/02/2018:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:sku: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1988473/+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 1988473] Re: Version 5.15.0-47 Breaks Virtualbox Win10 VM
This debian bug might be related: VirtualBox 6.1.34 not compatible with with Debian Kernel 5.18.0 and result in crashes - Patch available https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012627 ** Bug watch added: Debian Bug tracker #1012627 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012627 -- 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/1988473 Title: VirtualBox 6.1.34 guests crash with kernel 5.15.0-47 Status in virtualbox package in Ubuntu: Confirmed Bug description: The updated linux kernel would not allow my Win10 VM to boot. Rebooting Ubuntu into the 5.15.0-46 version restored the avility to boot. The 47 version also corrupted the VM, so I had to use a backup. I don't know if the problem was really with new Intel microcode that was installed with the new kernel. VB kernel modules were updated by dkms with the new version 47 install, so that should not be the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1980 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 14:54:58 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-12-04 (1366 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=ce42a622-1220-4d20-a2b5-97e15e83c527 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (127 days ago) dmi.bios.date: 07/02/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd07/02/2018:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:sku: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1988473/+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 1986477] Re: Failure to Suspend With Laptop Lid Closure After Upgrade to 22.04
Suspend mode is not activated when laptop lid closed or when "Suspend" was selected from "Power Off/Log Out". -- 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/1986477 Title: Failure to Suspend With Laptop Lid Closure After Upgrade to 22.04 Status in linux package in Ubuntu: Confirmed Bug description: Dell XPS-15 9550 Laptop lid closure does not result in transition to Suspend mode following upgrade from 20.04 to 22.04. Screen remains on and hard disk does not spin down. If Suspend is enforced from the Power Off/Log Out option, disk remains on. Attempted the following: 1. Edit the file /etc/systemd/logind.conf to uncomment the lines HandleLidSwitch=suspend, HandleLidSwithExternalPower=suspend, and HandleLidSwitchDocked=ignore. Did not result in Suspend mode when lid was closed. 2. Activated Standby Timeout Settings and set time to 5 minutes for the hard disk. The disk remained on. Both gnome-power-manager and pm-utils are installed. Using X.Org X server ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Aug 14 12:03:55 2022 InstallationDate: Installed on 2018-06-01 (1535 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to jammy on 2022-08-12 (2 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986477/+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 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
Hello, I need help, I have an old HP Pavilion computer with problems that no one can fix. He had ubuntu 17.10 installed. Your HD has been removed and formatted, but still not resolved. I don't know much about linux I need to install Windows 10. I was able to boot it with a USB stick with lubuntu 22 : lubuntu@lubuntu:/boot$ efibootmgr -v BootCurrent: 003D Timeout: 2 seconds BootOrder: ,2001,3000,2002,2003 Boot* ubuntu HD(1,GPT,9db0df4a-8506-492a-87ff-3bf8dc8c8678,0x800,0x10)/File(\EFI\ubuntu\shimx64.efi) Boot0001* Ubuntu HD(1,GPT,9db0df4a-8506-492a-87ff-3bf8dc8c8678,0x800,0x10)/File(\EFI\ubuntu\grubx64.efi)RC Boot2001* USB Drive (UEFI) RC Boot2002* Internal CD/DVD ROM Drive (UEFI) RC Boot3000* Internal Hard Disk or Solid State Disk RC Boot3003* Internal Hard Disk or Solid State Disk RC Could anyone tell me what should I do now? Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Boot-Repair: Fix Released Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Warning: 32bit iso on sourceforge for boot-repair-disk still contains unpatched Kernel. This is especially dangerous if boot-repair fails to repair the system to a bootable state, as there will be no way of applying the Fix detailed below. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. If you have applied updates, and find that you can not boot the above fixed kernel because of Secure Boot and that the kernel is unsigned, but can still boot another kernel for your system; here's what you can do: 1) Download http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed: $ wget http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed 2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi: $ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi 3) Reboot; you should now be able to load the new unsigned kernel that allows fixing firmware / SPI. 4) Once you're satisfied that things work; boot to Ubuntu with a standard, signed kernel, and re-install the right GRUB version for your system: $ sudo grub-install --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer
[Kernel-packages] [Bug 1988473] Re: Version 5.15.0-47 Breaks Virtualbox Win10 VM
I'm experiencing the same problem. As a host OS I'm running an up to date Ubuntu 22.04.1 LTS x86_64 with kernel 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64. I'm using the latest VirtualBox from the Ubuntu 22.04 package repository: 6.1.34-dfsg-3~ubuntu1.22.04.1 The host OS is stable. In VirtualBox I'm running a number of guest Ubuntu 22.04 virtual machines. These all crash in some way or other every 30 seconds or so. Generally the guest's Gnome display manager crashes, the guest's desktop disappears and the guest's GUI applications terminate. I'm then returned to the guest's Gnome graphical login prompt, but at a lower resolution than normal. For me this started occurring on the 2nd September 2022. System: AMD Ryzen 5 3600 with NVIDIA GeForce GTX 1050 Ti -- 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/1988473 Title: Version 5.15.0-47 Breaks Virtualbox Win10 VM Status in linux package in Ubuntu: Confirmed Bug description: The updated linux kernel would not allow my Win10 VM to boot. Rebooting Ubuntu into the 5.15.0-46 version restored the avility to boot. The 47 version also corrupted the VM, so I had to use a backup. I don't know if the problem was really with new Intel microcode that was installed with the new kernel. VB kernel modules were updated by dkms with the new version 47 install, so that should not be the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1980 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 14:54:58 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-12-04 (1366 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=ce42a622-1220-4d20-a2b5-97e15e83c527 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (127 days ago) dmi.bios.date: 07/02/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd07/02/2018:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:sku: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988473/+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 1988620] 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 1988620 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Incomplete Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date:
[Kernel-packages] [Bug 1988466] Re: Getting "Operation not permitted" on "sudo apt upgrade"
Ack, thanks for reporting back, closing bug report. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Invalid Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1988620] Re: Asus n61vn Brightness Control Levels Supported
** Package changed: acpi-support (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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Incomplete Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h)
[Kernel-packages] [Bug 1988620] [NEW] Asus n61vn Brightness Control Levels Supported
You have been subscribed to a public bug: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice \_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported
[Kernel-packages] [Bug 1988473] Re: Version 5.15.0-47 Breaks Virtualbox Win10 VM
VM mozilla application crash feedback data ** Attachment added: "mozilla.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988473/+attachment/5613449/+files/mozilla.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/1988473 Title: Version 5.15.0-47 Breaks Virtualbox Win10 VM Status in linux package in Ubuntu: Confirmed Bug description: The updated linux kernel would not allow my Win10 VM to boot. Rebooting Ubuntu into the 5.15.0-46 version restored the avility to boot. The 47 version also corrupted the VM, so I had to use a backup. I don't know if the problem was really with new Intel microcode that was installed with the new kernel. VB kernel modules were updated by dkms with the new version 47 install, so that should not be the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1980 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 14:54:58 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-12-04 (1366 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=ce42a622-1220-4d20-a2b5-97e15e83c527 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (127 days ago) dmi.bios.date: 07/02/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd07/02/2018:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:sku: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988473/+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 1988473] Re: Version 5.15.0-47 Breaks Virtualbox Win10 VM
A more generic title for the bug might be something like "VirtualBox 6.1.34 breaks VMs after kernel 5.15.0-47 update" as the guest VMs are not limited to Windows. -- 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/1988473 Title: Version 5.15.0-47 Breaks Virtualbox Win10 VM Status in linux package in Ubuntu: Confirmed Bug description: The updated linux kernel would not allow my Win10 VM to boot. Rebooting Ubuntu into the 5.15.0-46 version restored the avility to boot. The 47 version also corrupted the VM, so I had to use a backup. I don't know if the problem was really with new Intel microcode that was installed with the new kernel. VB kernel modules were updated by dkms with the new version 47 install, so that should not be the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1980 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 14:54:58 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-12-04 (1366 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=ce42a622-1220-4d20-a2b5-97e15e83c527 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (127 days ago) dmi.bios.date: 07/02/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd07/02/2018:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:sku: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988473/+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 1988473] Re: Version 5.15.0-47 Breaks Virtualbox Win10 VM
Updating to the latest VirtualBox version (6.1.34 -> 6.1.38 r153438) solved the problem for me on Xubuntu (with a running 5.15.0-47 kernel). https://www.virtualbox.org/wiki/Linux_Downloads -- 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/1988473 Title: Version 5.15.0-47 Breaks Virtualbox Win10 VM Status in linux package in Ubuntu: Confirmed Bug description: The updated linux kernel would not allow my Win10 VM to boot. Rebooting Ubuntu into the 5.15.0-46 version restored the avility to boot. The 47 version also corrupted the VM, so I had to use a backup. I don't know if the problem was really with new Intel microcode that was installed with the new kernel. VB kernel modules were updated by dkms with the new version 47 install, so that should not be the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1980 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 14:54:58 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-12-04 (1366 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=ce42a622-1220-4d20-a2b5-97e15e83c527 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (127 days ago) dmi.bios.date: 07/02/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd07/02/2018:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:sku: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988473/+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 1986743] Re: REQUEST add meson vdec firmware to arm64 linux-firmware package
I'm not sure how to change the tag but this is some tests against the binaries using V4L2 M2M. ls /lib/firmware/meson/vdec/ -al total 320 drwxr-xr-x 1 root root 406 Sep 3 14:20 . drwxr-xr-x 1 root root 8 Aug 23 18:36 .. -rw-r--r-- 1 root root 36864 Aug 31 11:11 g12a_h264.bin -rw-r--r-- 1 root root 16384 Aug 31 11:11 g12a_hevc_mmu.bin -rw-r--r-- 1 root root 16384 Aug 31 11:11 g12a_vp9.bin -rw-r--r-- 1 root root 36864 Aug 31 11:11 gxbb_h264.bin -rw-r--r-- 1 root root 16384 Aug 31 11:11 gxl_h263.bin -rw-r--r-- 1 root root 36864 Aug 31 11:11 gxl_h264.bin -rw-r--r-- 1 root root 16384 Aug 31 11:11 gxl_hevc.bin -rw-r--r-- 1 root root 16384 Aug 31 11:11 gxl_hevc_mmu.bin -rw-r--r-- 1 root root 16384 Aug 31 11:11 gxl_mjpeg.bin -rw-r--r-- 1 root root 16384 Aug 31 11:11 gxl_mpeg12.bin -rw-r--r-- 1 root root 16384 Aug 31 11:11 gxl_mpeg4_5.bin -rw-r--r-- 1 root root 16384 Aug 31 11:11 gxl_vp9.bin -rw-r--r-- 1 root root 36864 Aug 31 11:11 gxm_h264.bin -rw-r--r-- 1 root root 16384 Aug 31 11:11 sm1_hevc_mmu.bin -rw-r--r-- 1 root root 16384 Aug 31 11:11 sm1_vp9_mmu.bin gst123 --verbose vp9_fhd.webm Playing file:///root/ltt/asset/vp9_fhd.webm gstreamer pipeline contains: GstPlayBin ( GstPlaySink ( GstStreamSynchronizer GstBin ( GstVideoConvert GstDeinterlace ) GstBin ( GstGLImageSinkBin ( GstGLUploadElement GstGLColorConvertElement GstGLColorBalance GstGLImageSink ) GstQueue GstPlaySinkVideoConvert ( GstIdentity GstVideoConvert GstVideoScale ) ) ) GstURIDecodeBin ( GstFileSrc GstDecodeBin ( GstTypeFindElement GstMatroskaDemux GstMultiQueue GstVp9Parse GstCapsFilter v4l2vp9dec ) ) GstInputSelector ) gst123 --verbose TheaterSquare_1920x1080.mp4 Playing file:///root/ltt/asset/TheaterSquare_1920x1080.mp4 gstreamer pipeline contains: GstPlayBin ( GstPlaySink ( GstStreamSynchronizer GstBin ( GstVideoConvert GstDeinterlace ) GstBin ( GstGLImageSinkBin ( GstGLUploadElement GstGLColorConvertElement GstGLColorBalance GstGLImageSink ) GstQueue GstPlaySinkVideoConvert ( GstIdentity GstVideoConvert GstVideoScale ) ) ) GstURIDecodeBin ( GstFileSrc GstDecodeBin ( GstTypeFindElement GstQTDemux GstMultiQueue GstH264Parse GstCapsFilter v4l2h264dec ) ) GstInputSelector ) Time: 0:00:00.29 of 0:00:09.99 | Bitrate: 15461.3 kbit/sec ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1986743 Title: REQUEST add meson vdec firmware to arm64 linux-firmware package Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Impact] 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 22.04.1 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 20220329.git681281e40ubuntu3.4 3) What you expected to happen Linux Firmware would include meson vdec blobs https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/meson/vdec 4) What happened instead Linux Firmware does not include meson vdec blobs [Test case] Load meson-vdec driver on HW that supports it and watch firmware load failure. [Fix] Include firmware blobs. [Where Problems Could Occur] This only affects very specific HW. And the blobs have shipped in older series but were dropped incorrectly in Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1986743/+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 1988635] 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/1988635 Title: boot failure on ryzen 9 Status in linux package in Ubuntu: Confirmed Bug description: Xubuntu 22.04.1: When booting the 5.15.0-47.51 generic kernel on my AMD Ryzen 9 3900XT I see the following messages: -- [FAILED] Failed to mount /C. -- See 'systemctl status C.mount' for details. -- [DEPEND] Dependency failed for Local File Systems. -- . -- You are in emergency mode. ---. NOTE THAT I HAD TO REVERT TO KERNEL 5.15.0-46.49 TO REPORT THIS PROBLEM. A clone of the installation at hand runs without problems on an Intel Celeron G1620 box. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: burdi012933 F pulseaudio /dev/snd/controlC0: burdi012933 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Sep 3 15:45:02 2022 HibernationDevice: RESUME=none IwConfig: lono wireless extensions. enp39s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C35 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p12 ro pci=noaer RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.30 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MEG X570 UNIFY (MS-7C35) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.30:bd01/16/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C35:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGX570UNIFY(MS-7C35):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C35 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988635/+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 1986743] Re: REQUEST add meson vdec firmware to arm64 linux-firmware package
Hi Timo, Tested linux-firmware (20220329.git681281e4-0ubuntu3.5) and looks good! Thanks a lot Juerg and Timo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1986743 Title: REQUEST add meson vdec firmware to arm64 linux-firmware package Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Impact] 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 22.04.1 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 20220329.git681281e40ubuntu3.4 3) What you expected to happen Linux Firmware would include meson vdec blobs https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/meson/vdec 4) What happened instead Linux Firmware does not include meson vdec blobs [Test case] Load meson-vdec driver on HW that supports it and watch firmware load failure. [Fix] Include firmware blobs. [Where Problems Could Occur] This only affects very specific HW. And the blobs have shipped in older series but were dropped incorrectly in Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1986743/+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 1988635] Re: boot failure on ryzen 9
I can reproduce the problem at will. -- 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/1988635 Title: boot failure on ryzen 9 Status in linux package in Ubuntu: New Bug description: Xubuntu 22.04.1: When booting the 5.15.0-47.51 generic kernel on my AMD Ryzen 9 3900XT I see the following messages: -- [FAILED] Failed to mount /C. -- See 'systemctl status C.mount' for details. -- [DEPEND] Dependency failed for Local File Systems. -- . -- You are in emergency mode. ---. NOTE THAT I HAD TO REVERT TO KERNEL 5.15.0-46.49 TO REPORT THIS PROBLEM. A clone of the installation at hand runs without problems on an Intel Celeron G1620 box. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: burdi012933 F pulseaudio /dev/snd/controlC0: burdi012933 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Sep 3 15:45:02 2022 HibernationDevice: RESUME=none IwConfig: lono wireless extensions. enp39s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C35 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p12 ro pci=noaer RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.30 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MEG X570 UNIFY (MS-7C35) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.30:bd01/16/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C35:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGX570UNIFY(MS-7C35):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C35 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988635/+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 1988635] Re: boot failure on ryzen 9
I have no idea on how to provide the 5.15.0-47 logs ... -- 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/1988635 Title: boot failure on ryzen 9 Status in linux package in Ubuntu: New Bug description: Xubuntu 22.04.1: When booting the 5.15.0-47.51 generic kernel on my AMD Ryzen 9 3900XT I see the following messages: -- [FAILED] Failed to mount /C. -- See 'systemctl status C.mount' for details. -- [DEPEND] Dependency failed for Local File Systems. -- . -- You are in emergency mode. ---. NOTE THAT I HAD TO REVERT TO KERNEL 5.15.0-46.49 TO REPORT THIS PROBLEM. A clone of the installation at hand runs without problems on an Intel Celeron G1620 box. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: burdi012933 F pulseaudio /dev/snd/controlC0: burdi012933 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Sep 3 15:45:02 2022 HibernationDevice: RESUME=none IwConfig: lono wireless extensions. enp39s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C35 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p12 ro pci=noaer RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.30 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MEG X570 UNIFY (MS-7C35) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.30:bd01/16/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C35:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGX570UNIFY(MS-7C35):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C35 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988635/+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 1988635] [NEW] boot failure on ryzen 9
Public bug reported: Xubuntu 22.04.1: When booting the 5.15.0-47.51 generic kernel on my AMD Ryzen 9 3900XT I see the following messages: -- [FAILED] Failed to mount /C. -- See 'systemctl status C.mount' for details. -- [DEPEND] Dependency failed for Local File Systems. -- . -- You are in emergency mode. ---. NOTE THAT I HAD TO REVERT TO KERNEL 5.15.0-46.49 TO REPORT THIS PROBLEM. A clone of the installation at hand runs without problems on an Intel Celeron G1620 box. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: burdi012933 F pulseaudio /dev/snd/controlC0: burdi012933 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Sep 3 15:45:02 2022 HibernationDevice: RESUME=none IwConfig: lono wireless extensions. enp39s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C35 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p12 ro pci=noaer RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.30 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MEG X570 UNIFY (MS-7C35) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.30:bd01/16/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C35:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGX570UNIFY(MS-7C35):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C35 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988635 Title: boot failure on ryzen 9 Status in linux package in Ubuntu: New Bug description: Xubuntu 22.04.1: When booting the 5.15.0-47.51 generic kernel on my AMD Ryzen 9 3900XT I see the following messages: -- [FAILED] Failed to mount /C. -- See 'systemctl status C.mount' for details. -- [DEPEND] Dependency failed for Local File Systems. -- . -- You are in emergency mode. ---. NOTE THAT I HAD TO REVERT TO KERNEL 5.15.0-46.49 TO REPORT THIS PROBLEM. A clone of the installation at hand runs without problems on an Intel Celeron G1620 box. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: burdi012933 F pulseaudio /dev/snd/controlC0: burdi012933 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Sep 3 15:45:02 2022 HibernationDevice: RESUME=none IwConfig: lono wireless extensions. enp39s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C35 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p12 ro pci=noaer RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.30 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MEG X570 UNIFY (MS-7C35) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias:
[Kernel-packages] [Bug 1988473] Re: Version 5.15.0-47 Breaks Virtualbox Win10 VM
I had created a question on askubuntu about the same issue: https://askubuntu.com/questions/1426992/22-04-jammy-is-there-a-kernel- bug-that-causes-virtualbox-to-misbehave-with-5-15/1427135 My system details: Ubuntu 22.04.1 LTS x86_64 HP EliteDesk 805 G6 Desktop Mini PC AMD Ryzen 5 PRO 4650G with Radeon Graphics (12) @ 4.308GHz -- 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/1988473 Title: Version 5.15.0-47 Breaks Virtualbox Win10 VM Status in linux package in Ubuntu: Confirmed Bug description: The updated linux kernel would not allow my Win10 VM to boot. Rebooting Ubuntu into the 5.15.0-46 version restored the avility to boot. The 47 version also corrupted the VM, so I had to use a backup. I don't know if the problem was really with new Intel microcode that was installed with the new kernel. VB kernel modules were updated by dkms with the new version 47 install, so that should not be the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1980 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 14:54:58 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-12-04 (1366 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=ce42a622-1220-4d20-a2b5-97e15e83c527 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (127 days ago) dmi.bios.date: 07/02/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd07/02/2018:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:sku: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988473/+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 1946303] Re: No video after wake from S3 due to Nvidia driver crash
Update: After several failed attempts of reverting back to 20.04 (which all showed that resume from suspend with nvidia-470 driver got stuck, although it did work previously), I finally decided to do a fresh install of Ubuntu 22.04 (using the existing partitions with no formatting, so my /home and other data remained intact). And voila: now resume from suspend works without problems (using driver 515.65.01) So maybe this issue is somehow related to the upgrade process? -- 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/1946303 Title: No video after wake from S3 due to Nvidia driver crash Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+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 1970056] Re: Ubuntu 22.04 unable to mount root partition
Thanks, I have changed the status to 'fix released'. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition Status in linux package in Ubuntu: Fix Released Bug description: After updating from Kubuntu 21.10 to Kubuntu 22.04, boot drops to a (initramfs) prompt/busybox. When I type "exit" I get the "Gave up waiting for root file system device" error message and "ALERT! UUID=[nvme drive UUID] does not exist. Dropping to a shell!" I can still boot into KDE when selecting the older kernel version 5.13.0-40-lowlatency. I have tried the newer kernel versions 5.15.025-generic, 5.15.0.24-lowlatency, 5.17.4-051421-generic and 5.14.21-051421-lowlatency and all have produced the same problem. When removing the the "pci=nocrs" kernel paramater in Grub for these newer versions, the system boots into KDE but the touchpad does not work. Kernel version 5.13.0-40-lowlatency boots into KDE without removing the "pci=nocrs" parameter and everything works as expected, including the touchpad. My hardware is a Lenovo ideapad lenovo ideapad 3 15IIL05, Processors: 8 × Intel® Core™ i5-1035G4 CPU @ 1.10GHz, Memory: 7,3 GiB of RAM, Graphics Processor: Mesa Intel® Iris® Plus Graphics. I have upgraded the hard drive that came with the machine to a Kingston SA2000M8500G 465,8GiB nvme drive. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nick 2376 F jackdbus /dev/snd/pcmC0D0c: nick 2376 F...m jackdbus /dev/snd/pcmC0D0p: nick 2376 F...m jackdbus /dev/snd/seq:nick 2801 F a2jmidid CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-27 (483 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=5a0515ea-30d8-4412-ad65-8abbd8be949f ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip libvirt lpadmin lxd plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 08/10/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32866 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEMCN40WW:bd08/10/2020:br1.40:efr1.40:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrIdeaPad315IIL05:skuLENOVO_MT_81WE_BU_idea_FM_IdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+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
