[Kernel-packages] [Bug 1927019] Re: System freeze, continuous NVME PCIe errors
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1927019 Title: System freeze, continuous NVME PCIe errors Status in linux package in Ubuntu: Expired Bug description: Ubuntu 21.04 Freeze sometime ( using wayland ) . A black screen appear from top to bottom and ubuntu doesn't react to any keyboard shortcut. It's appears, maybe after 2 hours of work. I didn't see this bug with my previous ubuntu 20.10. My computer is a new DELL XPS 13 - intel core i7. I disabled the 4K screen and I am using a resolution 1920x1080. I enabled the night mode. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 4 00:10:39 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Xe Graphics [1028:0a5c] InstallationDate: Installed on 2021-04-30 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9305 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=37473b6f-8714-4a48-91c1-f6964b09347d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: 0PPYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd01/13/2021:br1.0:svnDellInc.:pnXPS139305:pvr:rvnDellInc.:rn0PPYW4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9305 dmi.product.sku: 0A5C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927019/+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 1904480] Re: RTL8822CE Realtek Wi-Fi dropping connection
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1904480 Title: RTL8822CE Realtek Wi-Fi dropping connection Status in linux package in Ubuntu: Expired Bug description: Wifi is still connected but it just stops working, this can be resolved by disconnecting or putting wifi on airplane mode and turning it back again. A few cases this does not work and the Wifi stops working and a system restart is needed. This is happening on Ubuntu 20.10 x64 Below the info for the wifi card: description: Wireless interface product: RTL8822CE 802.11ac PCIe Wireless Network Adapter vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 00 serial: 8c:c8:4b:95:0f:8b width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=rtw_8822ce driverversion=5.8.0-29-generic firmware=N/A latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:79 ioport:2000(size=256) memory:fc70-fc70 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kain 2109 F pulseaudio /dev/snd/controlC0: kain 2109 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-06-25 (145 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81X2 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 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=70cc7384-d3bc-4d41-8c3c-d4c54a560bef ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-17 (31 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/22/2020 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: EECN21WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14ARE05 dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrEECN21WW:bd04/22/2020:br1.21:efr1.16:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05: dmi.product.family: IdeaPad Flex 5 14ARE05 dmi.product.name: 81X2 dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05 dmi.product.version: IdeaPad Flex 5 14ARE05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kain 2109 F pulseaudio /dev/snd/pcmC2D0p: kain 2109 F...m pulseaudio /dev/snd/controlC0: kain 2109 F pulseaudio /dev/snd/timer: kain 2109 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-06-25 (146 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81X2 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 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=70cc7384-d3bc-4d41-8c3c-d4c54a560bef ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 RebootRequiredPkgs: gnome-shell RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-17 (31 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True
[Kernel-packages] [Bug 1925768] Re: Losing Wifi connection when USB-C Hub was plugged-in
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1925768 Title: Losing Wifi connection when USB-C Hub was plugged-in Status in linux package in Ubuntu: Expired Bug description: Hello Ubuntu community, I have a problem with my system: when i connect my new USB-C hub to my Intel Nuc, my wifi-connection get disconnected and try to reconnect to my Wifi. The System cannot connect until i disconnect my USB-C hub. I also tries do disable the cable-connection-Ports without success. I always receive the message: could not connect to wifi... My OS: Ubuntu 20.04.2 LTS always up to date. Here is my Nuc: https://www.notebooksbilliger.de/intel+nuc+kit+nuc8i3bek2+388252?gclid=Cj0KCQjw4ImEBhDFARIsAGOTMj_in7Zc6RBlqYMqtxrxwSDscYZsqcbmHjb9JM_ipyPl3cFjDsigaDsaAqOpEALw_wcB_id=Cj0KCQjw4ImEBhDFARIsAGOTMj_in7Zc6RBlqYMqtxrxwSDscYZsqcbmHjb9JM_ipyPl3cFjDsigaDsaAqOpEALw_wcB:G:s_kwcid=AL!8069!3!504856654760!!!g!626707857982!=6004 Link to my Adapter: https://www.amazon.de/1-Adapter-USB-C-Stromversorgung-RJ45-Gigabit- Ethernet-TF-Kartenleser-5-mm- Audiobuchse/dp/B08N424Y25/ref=sr_1_4?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91=1=usb+c+hub=1619169213=8-4 Best Regards Miro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925768/+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 1928530] Re: linux mint not booting or freeze on logo
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1928530 Title: linux mint not booting or freeze on logo Status in linux package in Ubuntu: Expired Bug description: bug report on the screen : watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [NetworkManager:630] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wili 1010 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-05-06 (9 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Acer Aspire 4738 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c115b4b7-e7fb-4f44-ae67-7b016b824bea ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: ulyssa Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2010 dmi.bios.vendor: INSYDE dmi.bios.version: V1.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: ZQ8 dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.02:bd08/09/2010:svnAcer:pnAspire4738:pvrV1.02:rvnAcer:rnZQ8:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Aspire 4738 dmi.product.sku: Calpella_CRB dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928530/+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 1868105] Re: No Sound, dummy output in settings
This same bug affects me as well. It might of happened the last time I updated but hard to say (I didn't notice right away) I have several sound card/devices; NVIDIA 1080 graphics card, intel, and a sound blaster, all of which are now gone. Running Ubuntu 20.04.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1868105 Title: No Sound, dummy output in settings Status in linux-oem-osp1 package in Ubuntu: Confirmed Bug description: After I updated my laptop today, sound is gone, "dummy output" is shown. SoundTroubleshootingProcedure did not help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-1043-oem-osp1 5.0.0-1043.48 ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21 Uname: Linux 5.0.0-1043-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: verigraf 3039 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 17:36:18 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 InstallationDate: Installed on 2019-10-28 (143 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. G3 3590 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 root=UUID=9f6f0954-fa11-47dc-99b3-a4088a85724e ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-1043-oem-osp1 N/A linux-backports-modules-5.0.0-1043-oem-osp1 N/A linux-firmware 1.173.16 SourcePackage: linux-oem-osp1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.2 dmi.board.name: 0201H1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.2:bd01/03/2020:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn0201H1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3590 dmi.product.sku: 0949 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1868105/+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 1845048] Re: Improve sysctl handling on kdump-tools
** No longer affects: makedumpfile (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/1845048 Title: Improve sysctl handling on kdump-tools Status in kdump-tools package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Opinion Status in makedumpfile source package in Bionic: In Progress Status in makedumpfile source package in Eoan: Won't Fix Status in makedumpfile source package in Focal: In Progress Status in makedumpfile source package in Groovy: Fix Released Status in kdump-tools package in Debian: New Bug description: [impact] Documentation, and past behavior, for kdump-tools was that the KDUMP_SYSCTL variable in the /etc/default/kdump-tools file would be applied to the system kernel params at kdump 'load'. However this is no longer true, and those params are no longer applied to the system's kernel param settings. [test case] install linux-crashdump (and kdump-tools). Edit the /etc/default/kdump-tools file to set the KDUMP_SYSCTL param to something other than default, e.g.: KDUMP_SYSCTL="kernel.panic_on_oops=1 kernel.panic_on_warn=1" reboot, or unload/reload kdump, to pick up the changes to the file. Check if the panic_on_warn param is set: $ cat /proc/sys/kernel/panic_on_warn 0 the problem does not seem to be with sysctl, as manually calling it does work: $ KDUMP_SYSCTL="kernel.panic_on_oops=1 kernel.panic_on_warn=1" $ cat /proc/sys/kernel/panic_on_warn 0 $ sudo sysctl -w $KDUMP_SYSCTL kernel.panic_on_oops = 1 kernel.panic_on_warn = 1 $ cat /proc/sys/kernel/panic_on_warn 1 [regression potential] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1845048/+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 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
This bug is affecting me too!! Please fix! The Intel AX201 Wi-fi 6 driver is broken on all current versions of Ubuntu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932548 Title: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0] Status in Linux Firmware: New Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: New Bug description: Whenever I am using a wireless connection, the image freezes roughly every two minutes. Sometimes, email cannot be retrieved / computer complains the connection was momentarily lost. - If I am on a wire, this problem does NOT occur. - This problems occurs on wireless independent of the platform used (behavior seen in both Google Hangout and Zoom) - This problem does NOT occur on Windows. I did a meeting where both my Linux and Windows machines were connected to the same meeting and using the same wifi router, and while the performance on Windows was flawless, unfortunately it was not so on the Ubuntu box. So I don't think my wifi router or network is to blame. - As far as I can recall, the problem used not to be there 2 weeks ago. So it may have been introduced by a recent update. - As communicated before, I am on a certified machine from Dell, recently purchased with Ubuntu already on board from factory (I assume the logs there were sent to you would contain the information). - I tried to generate a log on the wireless, but the process did not let me do this very easily. I am more than happy to send you additional information - but please let me know which package you want me to spy upon exactly, as I am not sure what would be helpful in this matter. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 Uname: Linux 5.10.0-1029-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:47:58 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0991] InstallationDate: Installed on 2021-04-24 (54 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.1 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux-firmware/+bug/1932548/+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 1928047] Re: AX201 BT will cause system could not enter S0i3
This bug is affecting me too!! Please fix! The Intel AX201 Wi-fi 6 driver is broken on all current versions of Ubuntu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928047 Title: AX201 BT will cause system could not enter S0i3 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: New Status in linux-oem-5.10 source package in Impish: Invalid Bug description: [Impact] Platforms with AX201 BT fail to pass the power consumption tests [Fix] Intel provides us the patch to fix it. https://patchwork.kernel.org/project/intel-gfx/patch/20210325120947.11950-1-anshuman.gu...@intel.com/ [Test] Verified on the Dell machines with AX201 BT on them. [Where problems may occur] This patch extend the s0ix fix for gen8 and gen11 to all PCHs. Not sure if it will lead to regressions on different PCH. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1928047/+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 1874241] Re: iwlwifi intel ax201 crashing on intel nuc10i7fnh
This bug is affecting me too!! Please fix! The Intel AX201 Wi-fi 6 driver is broken on all current versions of Ubuntu -- 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/1874241 Title: iwlwifi intel ax201 crashing on intel nuc10i7fnh Status in linux-firmware package in Ubuntu: New Bug description: The intel iwlwifi firmware will crash when you insert a device into the thunderbolt3 port, and this will be trigger probabilistically. wifi card model:Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x354 Firmware version: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 Linux-firmware version: 1.187 thunderbolt3 chip model: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06) dmesg output: [ 103.777908] pcieport :00:1c.0: PME: Spurious native interrupt! [ 103.777918] pcieport :00:1c.0: PME: Spurious native interrupt! [ 104.118148] usb 4-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 104.147184] usb 4-1: New USB device found, idVendor=05e3, idProduct=0749, bcdDevice=15.32 [ 104.147190] usb 4-1: New USB device strings: Mfr=3, Product=4, SerialNumber=2 [ 104.147194] usb 4-1: Product: USB3.0 Card Reader [ 104.147197] usb 4-1: Manufacturer: Generic [ 104.147199] usb 4-1: SerialNumber: 1532 [ 104.183374] usb-storage 4-1:1.0: USB Mass Storage device detected [ 104.183952] scsi host3: usb-storage 4-1:1.0 [ 104.184172] usbcore: registered new interface driver usb-storage [ 104.187897] usbcore: registered new interface driver uas [ 105.217035] scsi 3:0:0:0: Direct-Access Generic STORAGE DEVICE 1532 PQ: 0 ANSI: 6 [ 105.217792] sd 3:0:0:0: Attached scsi generic sg1 type 0 [ 105.233978] sd 3:0:0:0: [sdb] Attached SCSI removable disk [ 109.998995] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 109.999102] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 109.999111] iwlwifi :00:14.3: Status: 0x0040, count: 6 [ 109.999119] iwlwifi :00:14.3: Loaded firmware version: 48.4fa0041f.0 [ 109.999128] iwlwifi :00:14.3: 0x4435 | ADVANCED_SYSASSERT [ 109.999135] iwlwifi :00:14.3: 0x008026F4 | trm_hw_status0 [ 109.999142] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 109.999148] iwlwifi :00:14.3: 0x004CA228 | branchlink2 [ 109.999154] iwlwifi :00:14.3: 0x0E26 | interruptlink1 [ 109.999161] iwlwifi :00:14.3: 0x0E26 | interruptlink2 [ 109.999168] iwlwifi :00:14.3: 0x000161A0 | data1 [ 109.999174] iwlwifi :00:14.3: 0xDEADBEEF | data2 [ 109.999180] iwlwifi :00:14.3: 0xDEADBEEF | data3 [ 109.999186] iwlwifi :00:14.3: 0xF90167B5 | beacon time [ 109.999192] iwlwifi :00:14.3: 0x51938809 | tsf low [ 109.999199] iwlwifi :00:14.3: 0x0010 | tsf hi [ 109.999205] iwlwifi :00:14.3: 0x | time gp1 [ 109.999211] iwlwifi :00:14.3: 0x064A1430 | time gp2 [ 109.999217] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 109.999224] iwlwifi :00:14.3: 0x0030 | uCode version major [ 109.999231] iwlwifi :00:14.3: 0x4FA0041F | uCode version minor [ 109.999239] iwlwifi :00:14.3: 0x0351 | hw version [ 109.999245] iwlwifi :00:14.3: 0x00C89004 | board version [ 109.999252] iwlwifi :00:14.3: 0x069E001C | hcmd [ 109.999259] iwlwifi :00:14.3: 0x8002 | isr0 [ 109.999265] iwlwifi :00:14.3: 0x0100 | isr1 [ 109.999271] iwlwifi :00:14.3: 0x08F2 | isr2 [ 109.999278] iwlwifi :00:14.3: 0x04C1FFCC | isr3 [ 109.999284] iwlwifi :00:14.3: 0x | isr4 [ 109.999290] iwlwifi :00:14.3: 0x069D001C | last cmd Id [ 109.999297] iwlwifi :00:14.3: 0x8B70 | wait_event [ 109.999304] iwlwifi :00:14.3: 0x4208 | l2p_control [ 109.999310] iwlwifi :00:14.3: 0x2020 | l2p_duration [ 109.999317] iwlwifi :00:14.3: 0x033F | l2p_mhvalid [ 109.999324] iwlwifi :00:14.3: 0x00E6 | l2p_addr_match [ 109.999331] iwlwifi :00:14.3: 0x0009 | lmpm_pmg_sel [ 109.999337] iwlwifi :00:14.3: 0x | timestamp [ 109.999344] iwlwifi :00:14.3: 0xB8DC | flow_handler [ 109.999391] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 109.999398] iwlwifi :00:14.3: Status: 0x0040, count: 7 [ 109.999406] iwlwifi :00:14.3: 0x2070 | NMI_INTERRUPT_LMAC_FATAL [ 109.999413] iwlwifi :00:14.3: 0x | umac branchlink1 [ 109.999420] iwlwifi :00:14.3: 0xC008D49C | umac branchlink2 [ 109.999427] iwlwifi :00:14.3: 0x8048DBD2 | umac interruptlink1 [ 109.999434] iwlwifi :00:14.3: 0x8048DBD2 | umac interruptlink2 [ 109.999441] iwlwifi :00:14.3: 0x0400 | umac data1 [ 109.999447] iwlwifi :00:14.3: 0x8048DBD2 | umac data2 [ 109.999454] iwlwifi
[Kernel-packages] [Bug 1933938] Re: Missing CNVi firmware for Intel AX211/AX201 on ADL
This bug is affecting me too!! Please fix! -- 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/1933938 Title: Missing CNVi firmware for Intel AX211/AX201 on ADL Status in HWE Next: New Status in intel: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Incomplete Status in linux-oem-5.13 source package in Focal: Incomplete Status in linux source package in Impish: Incomplete Status in linux-firmware source package in Impish: Incomplete Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.sfi * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: ??? To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1933938/+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 1937872] [NEW] Bluetooth is not working in Ubuntu 20.04
Public bug reported: I have dual OS in my Dell laptop, Bluetooth is working in Windows, but not working in Ubuntu 20.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937872 Title: Bluetooth is not working in Ubuntu 20.04 Status in linux package in Ubuntu: New Bug description: I have dual OS in my Dell laptop, Bluetooth is working in Windows, but not working in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937872/+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 1937868] [NEW] linux-riscv: booting the kernel via the EFI stub with large initrd fails
Public bug reported: The Linux kernel currently requires that the initrd fits into the low 128 MiB which may fail due to reserved regions or large size of the initrd. A patch to resolve the issue has been included into linux-next: [PATCH 1/1] RISC-V: load initrd wherever it fits into memory https://lore.kernel.org/linux-efi/mhng-34467fe7-5a31-4c88-a5ad-6dea683fcfeb@palmerdabbelt-glaptop/T/#t https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20210723=c79e89ecaa246c880292ba68cbe08c9c30db77e3 Best regards Heinrich ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Tags: riscv64 ** Summary changed: - linux-riscv: booting the kernel via the EFI stub with large initrds fails + linux-riscv: booting the kernel via the EFI stub with large initrd fails -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1937868 Title: linux-riscv: booting the kernel via the EFI stub with large initrd fails Status in linux-riscv package in Ubuntu: New Bug description: The Linux kernel currently requires that the initrd fits into the low 128 MiB which may fail due to reserved regions or large size of the initrd. A patch to resolve the issue has been included into linux-next: [PATCH 1/1] RISC-V: load initrd wherever it fits into memory https://lore.kernel.org/linux-efi/mhng-34467fe7-5a31-4c88-a5ad-6dea683fcfeb@palmerdabbelt-glaptop/T/#t https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20210723=c79e89ecaa246c880292ba68cbe08c9c30db77e3 Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1937868/+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 1937867] [NEW] kernel BUG at mm/slub.c:4042!
Public bug reported: There was a page fault at a defined address. I attached the error log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 20:27:00 2021 SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "error.txt" https://bugs.launchpad.net/bugs/1937867/+attachment/5513280/+files/error.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1937867 Title: kernel BUG at mm/slub.c:4042! Status in linux-signed-hwe-5.8 package in Ubuntu: New Bug description: There was a page fault at a defined address. I attached the error log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 20:27:00 2021 SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1937867/+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 1882623] Re: VM enter into hung status after triggering a crash
** Description changed:
- Create VM on Azure using Canonical UbuntuServer 14.04.5-LTS latest using
- size Standard DS2 v2
+ [Impact]
- Install kexec-tools kdump-tools makedumpfile, configure boot kernel
- parameter crashkernel=512M
+ * When kdumping on trusty/4.15 in an Azure instance, we observe quite
+ frequently a stall on the kdump kernel, it gets blocked and soon we see
+ a stack like the following:
- Run sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools and
- sed -i 's/LOAD_KEXEC=true/LOAD_KEXEC=false/g' /etc/default/kexec
+ [ 65.452007] INFO: rcu_sched detected stalls on CPUs/tasks:
+ [ 65.456004] 1-...!: (0 ticks this GP) idle=488/0/0 softirq=1/1 fqs=0
+ [ 65.456004] (detected by 0, t=15002 jiffies, g=707, c=706, q=8457)
+ [ 65.456004] rcu_sched kthread starved for 15002 jiffies! g707 c706 f0x0
RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=1
- Reboot VM, make sure crash kernel memory reserved successfully
+ * By using the Azure serial console, we collected a sysrq-w when the issue
happens:
+ [ 529.515013] sysrq: Show Blocked State
+ [ 529.517730] taskPC stack pid father
+ [ 529.519006] kworker/u4:2D094 2 0x8000
+ [ 529.519006] Workqueue: events_unbound fsnotify_mark_destroy_workfn
+ [ 529.519006] Call Trace:
+ [ 529.519006] __schedule+0x292/0x880
+ [ 529.519006] schedule+0x36/0x80
+ [ 529.519006] schedule_timeout+0x1d5/0x2f0
+ [ 529.519006] ? check_preempt_wakeup+0x162/0x260
+ [ 529.519006] wait_for_completion+0xa5/0x110
+ [ 529.519006] ? wake_up_q+0x80/0x80
+ [ 529.519006] __synchronize_srcu.part.14+0x67/0x80
+ [ 529.519006] ? trace_raw_output_rcu_utilization+0x50/0x50
+ [ 529.519006] ? __switch_to_asm+0x41/0x70
+ [ 529.519006] synchronize_srcu+0xd1/0xd6
+ [ 529.519006] fsnotify_mark_destroy_workfn+0x6d/0xc0
+ [ 529.519006] process_one_work+0x14e/0x390
+ [ 529.519006] worker_thread+0x1cc/0x3d0
+ [ 529.519006] kthread+0x105/0x140
+ [ 529.519006] ? max_active_store+0x60/0x60
+ [ 529.519006] ? kthread_bind+0x20/0x20
+ [ 529.519006] ret_from_fork+0x35/0x40
+ [ 529.519006] udevadm D0 544 1 0x
+ [ 529.519006] Call Trace:
+ [ 529.519006] __schedule+0x292/0x880
+ [ 529.519006] schedule+0x36/0x80
+ [ 529.519006] schedule_timeout+0x1d5/0x2f0
+ [ 529.519006] ? try_to_wake_up+0x4a/0x460
+ [ 529.519006] ? try_to_wake_up+0x4a/0x460
+ [ 529.519006] wait_for_completion+0xa5/0x110
+ [ 529.519006] ? wake_up_q+0x80/0x80
+ [ 529.519006] __flush_work.isra.29+0x119/0x1b0
+ [ 529.519006] ? destroy_worker+0x90/0x90
+ [ 529.519006] flush_delayed_work+0x3f/0x50
+ [ 529.519006] fsnotify_wait_marks_destroyed+0x15/0x20
+ [ 529.519006] fsnotify_destroy_group+0x4e/0xc0
+ [ 529.519006] inotify_release+0x1e/0x50
+ [ 529.519006] __fput+0xea/0x220
+ [ 529.519006] fput+0xe/0x10
+ [ 529.519006] task_work_run+0x8c/0xb0
+ [ 529.519006] exit_to_usermode_loop+0x70/0xa9
+ [ 529.519006] do_syscall_64+0x1b5/0x1e0
+ [ 529.519006] entry_SYSCALL_64_after_hwframe+0x41/0xa6
+ [ 529.519006] dhclientD0 573572 0x
+ [ 529.519006] Call Trace:
+ [ 529.519006] __schedule+0x292/0x880
+ [ 529.519006] schedule+0x36/0x80
+ [ 529.519006] schedule_timeout+0x1d5/0x2f0
+ [ 529.519006] ? aa_profile_af_perm+0xb4/0xf0
+ [ 529.519006] wait_for_completion+0xa5/0x110
+ [ 529.519006] ? wake_up_q+0x80/0x80
+ [ 529.519006] __wait_rcu_gp+0x123/0x150
+ [ 529.519006] synchronize_sched+0x4e/0x60
+ [ 529.519006] ? __call_rcu+0x2f0/0x2f0
+ [ 529.519006] ? trace_raw_output_rcu_utilization+0x50/0x50
+ [ 529.519006] synchronize_net+0x1c/0x30
+ [ 529.519006] __unregister_prot_hook+0xcd/0xf0
+ [ 529.519006] packet_do_bind+0x1bd/0x250
+ [ 529.519006] packet_bind+0x2f/0x50
+ [ 529.519006] SYSC_bind+0xd8/0x110
+ [ 529.519006] ? sock_alloc_file+0x91/0x130
+ [ 529.519006] SyS_bind+0xe/0x10
+ [ 529.519006] do_syscall_64+0x80/0x1e0
+ [ 529.519006] entry_SYSCALL_64_after_hwframe+0x41/0xa6
- Trigger a crash by run echo 1 > /proc/sys/kernel/sysrq, then echo c >
- /proc/sysrq-trigger, VM will reboot automatically and after reboot,
- check crash dump is generated under /var/crash
+ * Bisecting mainline kernels, we found that v4.17-rc1 didn't reproduce
+ the issue, whereas v4.16 reproduced. Then, a fine-grained git bisect led
+ us to the fix - the following patch, when backported to a problematic
+ version, fixes the issue: d8e462e19305 ("Drivers: hv: vmbus: Implement
+ Direct Mode for stimer0")
- Install linux-azure kernel
+ * In Azure/Hyper-V, before the aforementioned commit, timer interrupts
+ were passed to the hypervisor through a vmbus message, a mechanism of
+ communication of hyper-v guests/hypervisor. With the patch, a check is
+ made (through MSR-like mechanism) and if the hypervisor supports, a
+ direct timer IRQ mechanism is put in-place instead of the vmbus channel.
- Enable private-ppa canonical-kernel-esm
+ * Our theory is that
[Kernel-packages] [Bug 1931254] Re: Google Confidential Compute fails to boot with shim version 1.47
Verification steps: 1. Enabled Confidential Compute 2. Change image to daily-ubuntu-2104-hirsute-v20210510 (last working image) 3. Launched image 4. Enabled proposed 5. Updated system https://paste.ubuntu.com/p/mNrZNkVYtB/ 6. Rebooted sucessfully! https://paste.ubuntu.com/p/G9CmvhW9tx/ Marking verification-done ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1931254 Title: Google Confidential Compute fails to boot with shim version 1.47 Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Bug description: # Overview Hirsute and Impish daily builds are currently not booting on Google Confidential Compute. Confidential compute is Google's platform that enables the use of Secure Encrypted Virtualization extension via AMD EPYC CPUs. Booting an image with version 1.45 works, but once upgraded to 1.47, the VM no longer boots, and instead the kernel panics. Launching the image with secure boot, but without confidential compute works as expected. # Expected result The system is able to reboot after the upgrade. # Actual result Kernel panic: https://paste.ubuntu.com/p/mHrvVc6qBc/ # Steps to reproduce Launch a VM in GCE with confidential compute enabled with a serial v20210511a or later and look at the serial log for the kernel panic. Example CLI command to launch a VM: $ gcloud beta compute instances create $USER-confidential-testing --zone=us-west1-b --machine-type=n2d-standard-2 --image=daily- ubuntu-2104-hirsute-v20210511a --image-project=ubuntu-os-cloud-devel --confidential-compute --maintenance-policy=TERMINATE The last known good working image is daily- ubuntu-2104-hirsute-v20210510. The upgrade that fails is when shim signed is updated from 1.46+15.4-0ubuntu1 to 1.47+15.4-0ubuntu2 # Logs & notes * 20210510 manifest (good): https://paste.ubuntu.com/p/QjnMPcJj7G/ * 20210511a manifest (bad): https://paste.ubuntu.com/p/PvJQwRXHcG/ * diff between manifests: https://paste.ubuntu.com/p/4nJtGxqGn7/ * serial logs of failed boot: https://paste.ubuntu.com/p/mHrvVc6qBc/ # Cause: shim changed the memory type for pages reserved for EFI runtime services, from EfiRuntimeServicesData to EfiBootServicesData. Memory reserved for EFI runtime/boot services must be remapped as encrypted in the kernel (during boot) if SEV (secure encrypted virtualization) is enabled. The original kernel implementation of ioremap only correctly mapped the region as encrypted for EfiRuntimeServicesData regions, so when shim changed the type to EfiBootServicesData the kernel bug was exposed Note that this affects all 5.11 kernels not just gcp. It is possible that gcp is the only cloud that uses sev currently (for "Confidential Computing"). # Fix: Both EfiRuntimeServicesData and EfiBootServicesData must be mapped as encrypted if SEV is active, as per: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8d651ee9c71bb12fc0c8eb2786b66cbe5aa3e43b # Test Without the fix applied, confirmed that I was able to reproduce the issue described here (complete failure to boot, kernel panic) With fix, confirmed no issues booting # Regression potential The fix could potentially cause boot failures, if a memory region is marked encrypted when it shouldn't be. I assume in that case it would cause a panic similar to the one seen here for this bug: general protection fault, probably for non-canonical address 0x314836c31124d346: [#1] SMP NOPTI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931254/+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 1937773] Re: WARNING: CPU: 0 PID: 1 at kernel/softirq.c:173 __local_bh_disable_ip+0xce/0xe0
Tested 100 boots, failure rate is 1 in ~15 boots. Some are hard locks w/o any information. ** Attachment added: "RCU lockup" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937773/+attachment/5513258/+files/Screenshot%20from%202021-07-23%2017-16-11.png -- 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/1937773 Title: WARNING: CPU: 0 PID: 1 at kernel/softirq.c:173 __local_bh_disable_ip+0xce/0xe0 Status in linux package in Ubuntu: In Progress Status in linux source package in Impish: In Progress Bug description: I just hit this oops running impish:linux-realtime (5.13) inside a kvm instance. It looks like there's a locking issue between cgroups (idr allocator) and some real-time specific patches: [5.278177] DEBUG_LOCKS_WARN_ON(this_cpu_read(softirq_ctrl.cnt)) [5.278184] WARNING: CPU: 0 PID: 1 at kernel/softirq.c:173 __local_bh_disable_ip+0xce/0xe0 [5.278189] Modules linked in: nls_utf8 isofs nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ccp kvm input_leds joydev serio_raw mac_hid qemu_fw_cfg sch_fq_codel msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear qxl drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core virtio_net psmouse virtio_blk i2c_i801 ahci net_failover xhci_pci failover xhci_pci_renesas drm libahci i2c_smbus lpc_ich [5.278209] CPU: 0 PID: 1 Comm: systemd Not tainted 5.13.0-1001-realtime #1-Ubuntu [5.278211] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 [5.278212] RIP: 0010:__local_bh_disable_ip+0xce/0xe0 [5.278213] Code: 76 ff ff ff e8 a3 bd 50 00 85 c0 74 a3 8b 05 11 92 0f 02 85 c0 75 99 48 c7 c6 88 29 3c 9e 48 c7 c7 02 cd 3a 9e e8 7b ee b4 00 <0f> 0b eb 82 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 0f 1f 44 00 [5.278214] RSP: 0018:ac46c0013d40 EFLAGS: 00010286 [5.278216] RAX: RBX: 0200 RCX: 0027 [5.278216] RDX: 0027 RSI: 4000e2df RDI: 9df4fbc18a58 [5.278217] RBP: ac46c0013d48 R08: 9df4fbc18a50 R09: 9f30a523 [5.278218] R10: R11: 284e4f5f4e524157 R12: 9edd1e30 [5.278218] R13: R14: 0002 R15: [5.278219] FS: 7f1d42909900() GS:9df4fbc0() knlGS: [5.278220] CS: 0010 DS: ES: CR0: 80050033 [5.278221] CR2: 561b36c201a0 CR3: 00010280 CR4: 06f0 [5.278222] Call Trace: [5.278224] cgroup_idr_alloc.constprop.0+0x38/0xd0 [5.278226] css_create+0x117/0x1e0 [5.278228] cgroup_apply_control_enable+0x13b/0x160 [5.278229] cgroup_mkdir+0xe2/0x1c0 [5.278230] kernfs_iop_mkdir+0x5c/0x90 [5.278232] vfs_mkdir+0x181/0x220 [5.278234] do_mkdirat+0x122/0x150 [5.278236] __x64_sys_mkdir+0x1b/0x20 [5.278237] do_syscall_64+0x61/0xb0 [5.278239] ? syscall_exit_to_user_mode+0x27/0x50 [5.278241] ? __x64_sys_mkdir+0x1b/0x20 [5.278242] ? do_syscall_64+0x6e/0xb0 [5.278243] ? do_syscall_64+0x6e/0xb0 [5.278244] ? asm_exc_page_fault+0x8/0x30 [5.278245] entry_SYSCALL_64_after_hwframe+0x44/0xae [5.278246] RIP: 0033:0x7f1d430ca81b [5.278247] Code: 8b 05 59 86 0d 00 41 bc ff ff ff ff 64 c7 00 16 00 00 00 e9 37 ff ff ff e8 c2 0c 02 00 66 90 f3 0f 1e fa b8 53 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 25 86 0d 00 f7 d8 64 89 01 48 [5.278248] RSP: 002b:7fffaf9cdc78 EFLAGS: 0202 ORIG_RAX: 0053 [5.278249] RAX: ffda RBX: 561b36d8d940 RCX: 7f1d430ca81b [5.278249] RDX: RSI: 01ed RDI: 561b36db9700 [5.278250] RBP: 7f1d434ef52f R08: R09: [5.278250] R10: R11: 0202 R12: [5.278251] R13: 561b36d8d940 R14: 0001 R15: 0073 [5.278252] ---[ end trace 0002 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937773/+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 1937846] Re: linux-azure: Ensure the latest linux-image-sgx is installed with the 5.11 kernels
** Also affects: linux-azure-5.11 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-azure-5.11 (Ubuntu) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-azure-5.11 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-azure-5.11 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-azure-5.11 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-azure (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Hirsute) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-azure-5.11 (Ubuntu Focal) Assignee: (unassigned) => Marcelo Cerri (mhcerri) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1937846 Title: linux-azure: Ensure the latest linux-image-sgx is installed with the 5.11 kernels Status in linux-azure package in Ubuntu: In Progress Status in linux-azure-5.11 package in Ubuntu: New Status in linux-azure source package in Focal: Invalid Status in linux-azure-5.11 source package in Focal: New Status in linux-azure source package in Hirsute: In Progress Status in linux-azure-5.11 source package in Hirsute: Invalid Bug description: [Impact] The 5.11 kernels include the upstream version of the SGX support. To ensure a better transition from the DCAP module, it's necessary to ensure the latest linux-base-sgx is installed with the kernel. [Test Plan] Check if the latest linux-base-sgx is installed when installing the 5.11 linux-azure kernels. [Where problems could occur] Problems with the linux-base-sgx dependency will cause the kernel to not be installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1937846/+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 1937415] Re: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199
btw, pick up the different firmware binary related to iwlwifi here. $ git diff Ubuntu-1.199 Ubuntu-1.198 https://paste.ubuntu.com/p/t3bpy68MMp/ ``` Binary files a/iwlwifi-ty-a0-gf-a0.pnvm and b/iwlwifi-ty-a0-gf-a0.pnvm differ # and a lot of files in intel/ibt differ ``` -- 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/1937415 Title: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199 Status in linux-firmware package in Ubuntu: New Bug description: After upgrading from linux-firmware 1.198 to 1.199 my connectivity became unstable and I could see repeating hardware resets in `dmesg` output. Downgrading to linux-firmware 1.198 again resolved the issue. Note: this bug was filed after downgrading the package, but hopefully apport would have caught the kernel logs from previous boot as well. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.199 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 15:25:46 2021 Dependencies: InstallationDate: Installed on 2021-01-18 (185 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.198 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.release: 14.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA 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.:bvr1402:bd01/15/2021:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: 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-firmware/+bug/1937415/+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 1937846] [NEW] linux-azure: Ensure the latest linux-image-sgx is installed with the 5.11 kernels
Public bug reported: [Impact] The 5.11 kernels include the upstream version of the SGX support. To ensure a better transition from the DCAP module, it's necessary to ensure the latest linux-base-sgx is installed with the kernel. [Test Plan] Check if the latest linux-base-sgx is installed when installing the 5.11 linux-azure kernels. [Where problems could occur] Problems with the linux-base-sgx dependency will cause the kernel to not be installed. ** Affects: linux-azure (Ubuntu) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1937846 Title: linux-azure: Ensure the latest linux-image-sgx is installed with the 5.11 kernels Status in linux-azure package in Ubuntu: In Progress Bug description: [Impact] The 5.11 kernels include the upstream version of the SGX support. To ensure a better transition from the DCAP module, it's necessary to ensure the latest linux-base-sgx is installed with the kernel. [Test Plan] Check if the latest linux-base-sgx is installed when installing the 5.11 linux-azure kernels. [Where problems could occur] Problems with the linux-base-sgx dependency will cause the kernel to not be installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1937846/+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 1845048] Re: Improve sysctl handling on kdump-tools
Correction: looks like it was 1:1.6.7-4. git-debrebase confused me. ** Changed in: makedumpfile (Ubuntu Groovy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/1845048 Title: Improve sysctl handling on kdump-tools Status in kdump-tools package in Ubuntu: Fix Released Status in makedumpfile package in Ubuntu: Invalid Status in makedumpfile source package in Xenial: Opinion Status in makedumpfile source package in Bionic: In Progress Status in makedumpfile source package in Eoan: Won't Fix Status in makedumpfile source package in Focal: In Progress Status in makedumpfile source package in Groovy: Fix Released Status in kdump-tools package in Debian: New Bug description: [impact] Documentation, and past behavior, for kdump-tools was that the KDUMP_SYSCTL variable in the /etc/default/kdump-tools file would be applied to the system kernel params at kdump 'load'. However this is no longer true, and those params are no longer applied to the system's kernel param settings. [test case] install linux-crashdump (and kdump-tools). Edit the /etc/default/kdump-tools file to set the KDUMP_SYSCTL param to something other than default, e.g.: KDUMP_SYSCTL="kernel.panic_on_oops=1 kernel.panic_on_warn=1" reboot, or unload/reload kdump, to pick up the changes to the file. Check if the panic_on_warn param is set: $ cat /proc/sys/kernel/panic_on_warn 0 the problem does not seem to be with sysctl, as manually calling it does work: $ KDUMP_SYSCTL="kernel.panic_on_oops=1 kernel.panic_on_warn=1" $ cat /proc/sys/kernel/panic_on_warn 0 $ sudo sysctl -w $KDUMP_SYSCTL kernel.panic_on_oops = 1 kernel.panic_on_warn = 1 $ cat /proc/sys/kernel/panic_on_warn 1 [regression potential] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1845048/+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 1845048] Re: Improve sysctl handling on kdump-tools
Guillherme's MR was merged in 1.6.8-1, so marking Fix Released. ** Changed in: kdump-tools (Ubuntu) Status: New => Fix Released ** Changed in: makedumpfile (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/1845048 Title: Improve sysctl handling on kdump-tools Status in kdump-tools package in Ubuntu: Fix Released Status in makedumpfile package in Ubuntu: Invalid Status in makedumpfile source package in Xenial: Opinion Status in makedumpfile source package in Bionic: In Progress Status in makedumpfile source package in Eoan: Won't Fix Status in makedumpfile source package in Focal: In Progress Status in makedumpfile source package in Groovy: Fix Released Status in kdump-tools package in Debian: New Bug description: [impact] Documentation, and past behavior, for kdump-tools was that the KDUMP_SYSCTL variable in the /etc/default/kdump-tools file would be applied to the system kernel params at kdump 'load'. However this is no longer true, and those params are no longer applied to the system's kernel param settings. [test case] install linux-crashdump (and kdump-tools). Edit the /etc/default/kdump-tools file to set the KDUMP_SYSCTL param to something other than default, e.g.: KDUMP_SYSCTL="kernel.panic_on_oops=1 kernel.panic_on_warn=1" reboot, or unload/reload kdump, to pick up the changes to the file. Check if the panic_on_warn param is set: $ cat /proc/sys/kernel/panic_on_warn 0 the problem does not seem to be with sysctl, as manually calling it does work: $ KDUMP_SYSCTL="kernel.panic_on_oops=1 kernel.panic_on_warn=1" $ cat /proc/sys/kernel/panic_on_warn 0 $ sudo sysctl -w $KDUMP_SYSCTL kernel.panic_on_oops = 1 kernel.panic_on_warn = 1 $ cat /proc/sys/kernel/panic_on_warn 1 [regression potential] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1845048/+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 1932966] Re: kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
** Changed in: ubuntu-kernel-tests
Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned)
** Changed in: linux-kvm (Ubuntu Bionic)
Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned)
** Changed in: linux-kvm (Ubuntu)
Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1932966
Title:
kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
Status in ubuntu-kernel-tests:
Confirmed
Status in linux-kvm package in Ubuntu:
Confirmed
Status in linux-kvm source package in Bionic:
Confirmed
Bug description:
Found this on B/KVM, current cycle (sru-20210531):
18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
18:27:11 DEBUG| [stderr] KVM internal error. Suberror: 1
18:27:11 DEBUG| [stderr] emulation failure
18:27:11 DEBUG| [stderr] RAX=000a RBX=e000
RCX=03fd RDX=03f8
18:27:11 DEBUG| [stderr] RSI=00419991 RDI=00419991
RBP=0051b440 RSP=0051b420
18:27:11 DEBUG| [stderr] R8 =000a R9 =03f8
R10=000d R11=
18:27:11 DEBUG| [stderr] R12=e000 R13=
R14=d000 R15=
18:27:11 DEBUG| [stderr] RIP=00400a0c RFL=00010006 [-P-] CPL=0
II=0 A20=1 SMM=0 HLT=0
18:27:11 DEBUG| [stderr] ES =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] CS =0008 00a09b00 DPL=0
CS64 [-RA]
18:27:11 DEBUG| [stderr] SS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] DS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] FS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] GS =0010 0051a4d0 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] LDT= 8200 DPL=0 LDT
18:27:11 DEBUG| [stderr] TR =0080 0041207a 8b00 DPL=0
TSS64-busy
18:27:11 DEBUG| [stderr] GDT= 0041100a 106f
18:27:11 DEBUG| [stderr] IDT= 0041 0fff
18:27:11 DEBUG| [stderr] CR0=80010011 CR2=
CR3=01007000 CR4=0220
18:27:11 DEBUG| [stderr] DR0= DR1=
DR2= DR3=
18:27:11 DEBUG| [stderr] DR6=0ff0 DR7=0400
18:27:11 DEBUG| [stderr] EFER=0500
18:27:11 DEBUG| [stderr] Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66
0f 6f 45 e0 <0f> 11 03 48 89 de 48 8d 7d e0 e8 f8 f9 ff ff 0f b6 f8 be a1 8f 41
00 b8 00 00 00 00 e8 05
18:28:40 DEBUG| [stderr] qemu-system-x86_64: terminating on signal 15 from
pid 13634 (timeout)
18:28:40 DEBUG| [stdout] FAIL emulator (timeout; duration=90s)
[...]
TestError: Test failed for emulator
18:28:40 ERROR| child process failed
18:28:40 DEBUG| Traceback (most recent call last):
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/parallel.py", line 25,
in fork_start
18:28:40 DEBUG| l()
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/job.py", line 505, in
18:28:40 DEBUG| l = lambda: test.runtest(self, url, tag, args, dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/test.py", line 125, in
runtest
18:28:40 DEBUG| job.sysinfo.log_after_each_iteration)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
913, in runtest
18:28:40 DEBUG| mytest._exec(args, dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
411, in _exec
18:28:40 DEBUG| _call_test_function(self.execute, *p_args, **p_dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
823, in _call_test_function
18:28:40 DEBUG| return func(*args, **dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
291, in execute
18:28:40 DEBUG| postprocess_profiled_run, args, dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
212, in _call_run_once
18:28:40 DEBUG| self.run_once(*args, **dargs)
18:28:40 DEBUG| File
"/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py",
line 82, in run_once
18:28:40 DEBUG| raise error.TestError("Test failed for
{}".format(test_name))
18:28:40 DEBUG| TestError: Test failed for emulator
18:28:41 INFO | ERROR ubuntu_kvm_unit_tests.emulator
ubuntu_kvm_unit_tests.emulator timestamp=1624040921localtime=Jun 18
18:28:41 Test failed for emulator
18:28:41 INFO | END ERROR ubuntu_kvm_unit_tests.emulator
ubuntu_kvm_unit_tests.emulator timestamp=1624040921localtime=Jun 18
18:28:41
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1937415] Re: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199
Just take a quick look on this issue. from #2, Jul 17 07:05:54 frode-threadripper kernel: [8.847048] iwlwifi :48:00.0: loaded firmware version 59.601f3a66.0 cc-a0-59.ucode op_mode iwlmvm from #1 dmesg, [8.920438] iwlwifi :48:00.0: loaded firmware version 59.601f3a66.0 cc-a0-59.ucode op_mode iwlmvm Looks both boot time (pass and failed) are using the same version of iwlwifi firmware. Compare to linux-firmware 1.199 and 1.198: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-firmware/commit/?h=impish=19185cb1aeb67563dd18f00963f388ceaaa29fcd looks the only firmware change related to iwlwifi is this one: +- iwlwifi: add ty firmware from Core63-43 But there is a bluetooth firmware change for Intel AX200 which not sure will it impact the wifi module on the same chip(after all, the firmware is blackbox binary from IHV): +- linux-firmware: Update firmware file for Intel Bluetooth AX200 Could you please add one of the 2 firmware manually to check if the issue can be reproduced? -- 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/1937415 Title: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199 Status in linux-firmware package in Ubuntu: New Bug description: After upgrading from linux-firmware 1.198 to 1.199 my connectivity became unstable and I could see repeating hardware resets in `dmesg` output. Downgrading to linux-firmware 1.198 again resolved the issue. Note: this bug was filed after downgrading the package, but hopefully apport would have caught the kernel logs from previous boot as well. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.199 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 15:25:46 2021 Dependencies: InstallationDate: Installed on 2021-01-18 (185 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.198 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.release: 14.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA 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.:bvr1402:bd01/15/2021:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: 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-firmware/+bug/1937415/+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 1937773] Re: WARNING: CPU: 0 PID: 1 at kernel/softirq.c:173 __local_bh_disable_ip+0xce/0xe0
** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: linux (Ubuntu Impish) Importance: Undecided => High -- 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/1937773 Title: WARNING: CPU: 0 PID: 1 at kernel/softirq.c:173 __local_bh_disable_ip+0xce/0xe0 Status in linux package in Ubuntu: In Progress Status in linux source package in Impish: In Progress Bug description: I just hit this oops running impish:linux-realtime (5.13) inside a kvm instance. It looks like there's a locking issue between cgroups (idr allocator) and some real-time specific patches: [5.278177] DEBUG_LOCKS_WARN_ON(this_cpu_read(softirq_ctrl.cnt)) [5.278184] WARNING: CPU: 0 PID: 1 at kernel/softirq.c:173 __local_bh_disable_ip+0xce/0xe0 [5.278189] Modules linked in: nls_utf8 isofs nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ccp kvm input_leds joydev serio_raw mac_hid qemu_fw_cfg sch_fq_codel msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear qxl drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core virtio_net psmouse virtio_blk i2c_i801 ahci net_failover xhci_pci failover xhci_pci_renesas drm libahci i2c_smbus lpc_ich [5.278209] CPU: 0 PID: 1 Comm: systemd Not tainted 5.13.0-1001-realtime #1-Ubuntu [5.278211] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 [5.278212] RIP: 0010:__local_bh_disable_ip+0xce/0xe0 [5.278213] Code: 76 ff ff ff e8 a3 bd 50 00 85 c0 74 a3 8b 05 11 92 0f 02 85 c0 75 99 48 c7 c6 88 29 3c 9e 48 c7 c7 02 cd 3a 9e e8 7b ee b4 00 <0f> 0b eb 82 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 0f 1f 44 00 [5.278214] RSP: 0018:ac46c0013d40 EFLAGS: 00010286 [5.278216] RAX: RBX: 0200 RCX: 0027 [5.278216] RDX: 0027 RSI: 4000e2df RDI: 9df4fbc18a58 [5.278217] RBP: ac46c0013d48 R08: 9df4fbc18a50 R09: 9f30a523 [5.278218] R10: R11: 284e4f5f4e524157 R12: 9edd1e30 [5.278218] R13: R14: 0002 R15: [5.278219] FS: 7f1d42909900() GS:9df4fbc0() knlGS: [5.278220] CS: 0010 DS: ES: CR0: 80050033 [5.278221] CR2: 561b36c201a0 CR3: 00010280 CR4: 06f0 [5.278222] Call Trace: [5.278224] cgroup_idr_alloc.constprop.0+0x38/0xd0 [5.278226] css_create+0x117/0x1e0 [5.278228] cgroup_apply_control_enable+0x13b/0x160 [5.278229] cgroup_mkdir+0xe2/0x1c0 [5.278230] kernfs_iop_mkdir+0x5c/0x90 [5.278232] vfs_mkdir+0x181/0x220 [5.278234] do_mkdirat+0x122/0x150 [5.278236] __x64_sys_mkdir+0x1b/0x20 [5.278237] do_syscall_64+0x61/0xb0 [5.278239] ? syscall_exit_to_user_mode+0x27/0x50 [5.278241] ? __x64_sys_mkdir+0x1b/0x20 [5.278242] ? do_syscall_64+0x6e/0xb0 [5.278243] ? do_syscall_64+0x6e/0xb0 [5.278244] ? asm_exc_page_fault+0x8/0x30 [5.278245] entry_SYSCALL_64_after_hwframe+0x44/0xae [5.278246] RIP: 0033:0x7f1d430ca81b [5.278247] Code: 8b 05 59 86 0d 00 41 bc ff ff ff ff 64 c7 00 16 00 00 00 e9 37 ff ff ff e8 c2 0c 02 00 66 90 f3 0f 1e fa b8 53 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 25 86 0d 00 f7 d8 64 89 01 48 [5.278248] RSP: 002b:7fffaf9cdc78 EFLAGS: 0202 ORIG_RAX: 0053 [5.278249] RAX: ffda RBX: 561b36d8d940 RCX: 7f1d430ca81b [5.278249] RDX: RSI: 01ed RDI: 561b36db9700 [5.278250] RBP: 7f1d434ef52f R08: R09: [5.278250] R10: R11: 0202 R12: [5.278251] R13: 561b36d8d940 R14: 0001 R15: 0073 [5.278252] ---[ end trace 0002 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937773/+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 1937773] Re: WARNING: CPU: 0 PID: 1 at kernel/softirq.c:173 __local_bh_disable_ip+0xce/0xe0
** No longer affects: linux ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937773 Title: WARNING: CPU: 0 PID: 1 at kernel/softirq.c:173 __local_bh_disable_ip+0xce/0xe0 Status in linux package in Ubuntu: In Progress Status in linux source package in Impish: In Progress Bug description: I just hit this oops running impish:linux-realtime (5.13) inside a kvm instance. It looks like there's a locking issue between cgroups (idr allocator) and some real-time specific patches: [5.278177] DEBUG_LOCKS_WARN_ON(this_cpu_read(softirq_ctrl.cnt)) [5.278184] WARNING: CPU: 0 PID: 1 at kernel/softirq.c:173 __local_bh_disable_ip+0xce/0xe0 [5.278189] Modules linked in: nls_utf8 isofs nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ccp kvm input_leds joydev serio_raw mac_hid qemu_fw_cfg sch_fq_codel msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear qxl drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core virtio_net psmouse virtio_blk i2c_i801 ahci net_failover xhci_pci failover xhci_pci_renesas drm libahci i2c_smbus lpc_ich [5.278209] CPU: 0 PID: 1 Comm: systemd Not tainted 5.13.0-1001-realtime #1-Ubuntu [5.278211] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 [5.278212] RIP: 0010:__local_bh_disable_ip+0xce/0xe0 [5.278213] Code: 76 ff ff ff e8 a3 bd 50 00 85 c0 74 a3 8b 05 11 92 0f 02 85 c0 75 99 48 c7 c6 88 29 3c 9e 48 c7 c7 02 cd 3a 9e e8 7b ee b4 00 <0f> 0b eb 82 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 0f 1f 44 00 [5.278214] RSP: 0018:ac46c0013d40 EFLAGS: 00010286 [5.278216] RAX: RBX: 0200 RCX: 0027 [5.278216] RDX: 0027 RSI: 4000e2df RDI: 9df4fbc18a58 [5.278217] RBP: ac46c0013d48 R08: 9df4fbc18a50 R09: 9f30a523 [5.278218] R10: R11: 284e4f5f4e524157 R12: 9edd1e30 [5.278218] R13: R14: 0002 R15: [5.278219] FS: 7f1d42909900() GS:9df4fbc0() knlGS: [5.278220] CS: 0010 DS: ES: CR0: 80050033 [5.278221] CR2: 561b36c201a0 CR3: 00010280 CR4: 06f0 [5.278222] Call Trace: [5.278224] cgroup_idr_alloc.constprop.0+0x38/0xd0 [5.278226] css_create+0x117/0x1e0 [5.278228] cgroup_apply_control_enable+0x13b/0x160 [5.278229] cgroup_mkdir+0xe2/0x1c0 [5.278230] kernfs_iop_mkdir+0x5c/0x90 [5.278232] vfs_mkdir+0x181/0x220 [5.278234] do_mkdirat+0x122/0x150 [5.278236] __x64_sys_mkdir+0x1b/0x20 [5.278237] do_syscall_64+0x61/0xb0 [5.278239] ? syscall_exit_to_user_mode+0x27/0x50 [5.278241] ? __x64_sys_mkdir+0x1b/0x20 [5.278242] ? do_syscall_64+0x6e/0xb0 [5.278243] ? do_syscall_64+0x6e/0xb0 [5.278244] ? asm_exc_page_fault+0x8/0x30 [5.278245] entry_SYSCALL_64_after_hwframe+0x44/0xae [5.278246] RIP: 0033:0x7f1d430ca81b [5.278247] Code: 8b 05 59 86 0d 00 41 bc ff ff ff ff 64 c7 00 16 00 00 00 e9 37 ff ff ff e8 c2 0c 02 00 66 90 f3 0f 1e fa b8 53 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 25 86 0d 00 f7 d8 64 89 01 48 [5.278248] RSP: 002b:7fffaf9cdc78 EFLAGS: 0202 ORIG_RAX: 0053 [5.278249] RAX: ffda RBX: 561b36d8d940 RCX: 7f1d430ca81b [5.278249] RDX: RSI: 01ed RDI: 561b36db9700 [5.278250] RBP: 7f1d434ef52f R08: R09: [5.278250] R10: R11: 0202 R12: [5.278251] R13: 561b36d8d940 R14: 0001 R15: 0073 [5.278252] ---[ end trace 0002 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937773/+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 1937773] Re: WARNING: CPU: 0 PID: 1 at kernel/softirq.c:173 __local_bh_disable_ip+0xce/0xe0
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937773 Title: WARNING: CPU: 0 PID: 1 at kernel/softirq.c:173 __local_bh_disable_ip+0xce/0xe0 Status in linux package in Ubuntu: In Progress Status in linux source package in Impish: In Progress Bug description: I just hit this oops running impish:linux-realtime (5.13) inside a kvm instance. It looks like there's a locking issue between cgroups (idr allocator) and some real-time specific patches: [5.278177] DEBUG_LOCKS_WARN_ON(this_cpu_read(softirq_ctrl.cnt)) [5.278184] WARNING: CPU: 0 PID: 1 at kernel/softirq.c:173 __local_bh_disable_ip+0xce/0xe0 [5.278189] Modules linked in: nls_utf8 isofs nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ccp kvm input_leds joydev serio_raw mac_hid qemu_fw_cfg sch_fq_codel msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear qxl drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core virtio_net psmouse virtio_blk i2c_i801 ahci net_failover xhci_pci failover xhci_pci_renesas drm libahci i2c_smbus lpc_ich [5.278209] CPU: 0 PID: 1 Comm: systemd Not tainted 5.13.0-1001-realtime #1-Ubuntu [5.278211] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 [5.278212] RIP: 0010:__local_bh_disable_ip+0xce/0xe0 [5.278213] Code: 76 ff ff ff e8 a3 bd 50 00 85 c0 74 a3 8b 05 11 92 0f 02 85 c0 75 99 48 c7 c6 88 29 3c 9e 48 c7 c7 02 cd 3a 9e e8 7b ee b4 00 <0f> 0b eb 82 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 0f 1f 44 00 [5.278214] RSP: 0018:ac46c0013d40 EFLAGS: 00010286 [5.278216] RAX: RBX: 0200 RCX: 0027 [5.278216] RDX: 0027 RSI: 4000e2df RDI: 9df4fbc18a58 [5.278217] RBP: ac46c0013d48 R08: 9df4fbc18a50 R09: 9f30a523 [5.278218] R10: R11: 284e4f5f4e524157 R12: 9edd1e30 [5.278218] R13: R14: 0002 R15: [5.278219] FS: 7f1d42909900() GS:9df4fbc0() knlGS: [5.278220] CS: 0010 DS: ES: CR0: 80050033 [5.278221] CR2: 561b36c201a0 CR3: 00010280 CR4: 06f0 [5.278222] Call Trace: [5.278224] cgroup_idr_alloc.constprop.0+0x38/0xd0 [5.278226] css_create+0x117/0x1e0 [5.278228] cgroup_apply_control_enable+0x13b/0x160 [5.278229] cgroup_mkdir+0xe2/0x1c0 [5.278230] kernfs_iop_mkdir+0x5c/0x90 [5.278232] vfs_mkdir+0x181/0x220 [5.278234] do_mkdirat+0x122/0x150 [5.278236] __x64_sys_mkdir+0x1b/0x20 [5.278237] do_syscall_64+0x61/0xb0 [5.278239] ? syscall_exit_to_user_mode+0x27/0x50 [5.278241] ? __x64_sys_mkdir+0x1b/0x20 [5.278242] ? do_syscall_64+0x6e/0xb0 [5.278243] ? do_syscall_64+0x6e/0xb0 [5.278244] ? asm_exc_page_fault+0x8/0x30 [5.278245] entry_SYSCALL_64_after_hwframe+0x44/0xae [5.278246] RIP: 0033:0x7f1d430ca81b [5.278247] Code: 8b 05 59 86 0d 00 41 bc ff ff ff ff 64 c7 00 16 00 00 00 e9 37 ff ff ff e8 c2 0c 02 00 66 90 f3 0f 1e fa b8 53 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 25 86 0d 00 f7 d8 64 89 01 48 [5.278248] RSP: 002b:7fffaf9cdc78 EFLAGS: 0202 ORIG_RAX: 0053 [5.278249] RAX: ffda RBX: 561b36d8d940 RCX: 7f1d430ca81b [5.278249] RDX: RSI: 01ed RDI: 561b36db9700 [5.278250] RBP: 7f1d434ef52f R08: R09: [5.278250] R10: R11: 0202 R12: [5.278251] R13: 561b36d8d940 R14: 0001 R15: 0073 [5.278252] ---[ end trace 0002 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937773/+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 1937415] Re: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199
Apparently the kern.log just shows boot, adding syslog excerpt with the kernel messages ** Attachment added: "syslog-excerpt.txt" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1937415/+attachment/5513209/+files/syslog-excerpt.txt -- 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/1937415 Title: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199 Status in linux-firmware package in Ubuntu: New Bug description: After upgrading from linux-firmware 1.198 to 1.199 my connectivity became unstable and I could see repeating hardware resets in `dmesg` output. Downgrading to linux-firmware 1.198 again resolved the issue. Note: this bug was filed after downgrading the package, but hopefully apport would have caught the kernel logs from previous boot as well. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.199 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 15:25:46 2021 Dependencies: InstallationDate: Installed on 2021-01-18 (185 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.198 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.release: 14.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA 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.:bvr1402:bd01/15/2021:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: 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-firmware/+bug/1937415/+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 1937415] Re: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199
Attaching the kern.log from previous boot which shows the issues. ** Attachment added: "kern.log.1" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1937415/+attachment/5513187/+files/kern.log.1 -- 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/1937415 Title: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199 Status in linux-firmware package in Ubuntu: New Bug description: After upgrading from linux-firmware 1.198 to 1.199 my connectivity became unstable and I could see repeating hardware resets in `dmesg` output. Downgrading to linux-firmware 1.198 again resolved the issue. Note: this bug was filed after downgrading the package, but hopefully apport would have caught the kernel logs from previous boot as well. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.199 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 15:25:46 2021 Dependencies: InstallationDate: Installed on 2021-01-18 (185 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.198 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.release: 14.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA 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.:bvr1402:bd01/15/2021:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: 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-firmware/+bug/1937415/+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 1937415] [NEW] Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199
Public bug reported: After upgrading from linux-firmware 1.198 to 1.199 my connectivity became unstable and I could see repeating hardware resets in `dmesg` output. Downgrading to linux-firmware 1.198 again resolved the issue. Note: this bug was filed after downgrading the package, but hopefully apport would have caught the kernel logs from previous boot as well. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.199 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 15:25:46 2021 Dependencies: InstallationDate: Installed on 2021-01-18 (185 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.198 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.release: 14.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA 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.:bvr1402:bd01/15/2021:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: 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 ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Description changed: After upgrading from linux-firmware 1.198 to 1.199 my connectivity became unstable and I could see repeating hardware resets in `dmesg` output. Downgrading to linux-firmware 1.198 again resolved the issue. Note: this bug was filed after downgrading the package, but hopefully apport would have caught the kernel logs from previous boot as well. ProblemType: Bug DistroRelease: Ubuntu 21.10 - Package: linux-firmware 1.198 + Package: linux-firmware 1.199 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 15:25:46 2021 Dependencies: - + InstallationDate: Installed on 2021-01-18 (185 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.11.0-16-generic N/A - linux-backports-modules-5.11.0-16-generic N/A - linux-firmware 1.198 + linux-restricted-modules-5.11.0-16-generic N/A + linux-backports-modules-5.11.0-16-generic N/A + linux-firmware 1.198 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.release: 14.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA 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.:bvr1402:bd01/15/2021:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: 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 -- 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/1937415 Title: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199 Status in linux-firmware package in Ubuntu: New
[Kernel-packages] [Bug 1937350] Re: USB HDD not properly spin down after safely remove
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937350 Title: USB HDD not properly spin down after safely remove Status in Linux: New Status in Ubuntu MATE: New Status in linux package in Ubuntu: New Bug description: I do not know which package I should file the bug for. I am using Ubuntu MATE 20.04 LTS and Microsoft Windows 10. On Microsoft Windows 10, no issue with safely remove any USB external HDD. When using Microsoft Windows 10, after safely remove my external HDD, the HDD will spin down. But, on Ubuntu MATE 20.04 LTS, some issues occur after I try to safely remove my external HDD. Tried different hard drive, different enclosures, and also some external hard drive that came bundled with enclosure. All having same or different issues after safely remove them in Ubuntu MATE. Problems will also occur on those branded external HDD that came bundled with enclosure, for example, those Seagate Backup Plus drives ( https://www.seagate.com/as/en/consumer/backup/backup-plus/ ). Here are the common problems after safely remove (in Ubuntu MATE): 1. The external HDD will spin down and then spin up again, and then being automatically remounted again. The "dmesg" command shows errors. 2. The external HDD will spin down and then spin up again, no remount. The LED on the enclosure keep flashing. The "dmesg" command shows errors. After you unplug the HDD, you can connect another HDD. 3. The external HDD will spin down and then spin up again, no remount. The LED on the enclosure keep flashing. The "dmesg" command shows errors. BUT, after you unplug the HDD, when you connect another HDD, the computer will not detect it and will not mount it until you reboot the computer. But, before reboot connecting another device (e.g. keyboard, mouse, etc) to the same USB port, the device works perfectly. 4. The external HDD will spin down and then spin up again, no remount. But, after a few seconds, it spin down again. But, still, the "dmesg" command shows errors. Different HDD, different enclosure, show different symptoms or problems. Some HDD enclosures, number 1 above will occur. Some HDD enclosures, either number 2 or 3 above will occur. Sometimes, problem number 2 above will occur. Sometimes, problem number 3 will occur. Some enclosure, problem number 4 will occur. Here, I will use the following enclosure as example in this bug report: Product link: https://www.ugreen.com/products/usb-c-2-5-sata-iii-hard- drive-enclosure Purchase link in my country: https://shopee.com.my/UGREEN-USB-3.1-To- SATA-III-External-Hard-Drive- Enclosure-(2.5-)-i.64923440.1583255569?position=1 Here are the steps to reproduce (for the enclosure above): 1. Connect the external HDD to any available USB 3.0 port. The HDD will be mounted. Caja (Ubuntu MATE default file manager) will launch. 2. Close the Caja window. Do not do anything on the HDD. 3. Use left or right hand, touch the HDD enclosure to feel the spinning. Do not let your hand leave the enclosure, so that you can continue feel the spinning. 4. Use your another hand to operate your computer. 5. Go to desktop. 6. Right click on the external HDD icon. 7. Click "Safely Remove Drive". The HDD unmounted. Assume that one of your hands still touching the enclosure of the HDD, you will feel that the HDD will spin down and then spin up again. No remount. The LED indicator on the enclosure will keep flashing. These are described in problem number 2 and 3 above. Sometimes, after you unplug the drive and try to connect another drive, it will not be detected until you reboot your computer. Almost all external HDDs I tested will cause "dmesg" command to shows "Buffer I/O error" and "Synchronize Cache() failed" error after "Safely Remove Drive". In Microsoft Windows 10, all above mentioned problems WILL NOT occur. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cshong 1059 F pulseaudio /dev/snd/controlC0: cshong 1059 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-23 (242 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=cad772fa-c02b-4268-bc15-e366825ac807 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 RelatedPackageVersions:
[Kernel-packages] [Bug 1937350] [NEW] USB HDD not properly spin down after safely remove
You have been subscribed to a public bug: I do not know which package I should file the bug for. I am using Ubuntu MATE 20.04 LTS and Microsoft Windows 10. On Microsoft Windows 10, no issue with safely remove any USB external HDD. When using Microsoft Windows 10, after safely remove my external HDD, the HDD will spin down. But, on Ubuntu MATE 20.04 LTS, some issues occur after I try to safely remove my external HDD. Tried different hard drive, different enclosures, and also some external hard drive that came bundled with enclosure. All having same or different issues after safely remove them in Ubuntu MATE. Problems will also occur on those branded external HDD that came bundled with enclosure, for example, those Seagate Backup Plus drives ( https://www.seagate.com/as/en/consumer/backup/backup-plus/ ). Here are the common problems after safely remove (in Ubuntu MATE): 1. The external HDD will spin down and then spin up again, and then being automatically remounted again. The "dmesg" command shows errors. 2. The external HDD will spin down and then spin up again, no remount. The LED on the enclosure keep flashing. The "dmesg" command shows errors. After you unplug the HDD, you can connect another HDD. 3. The external HDD will spin down and then spin up again, no remount. The LED on the enclosure keep flashing. The "dmesg" command shows errors. BUT, after you unplug the HDD, when you connect another HDD, the computer will not detect it and will not mount it until you reboot the computer. But, before reboot connecting another device (e.g. keyboard, mouse, etc) to the same USB port, the device works perfectly. 4. The external HDD will spin down and then spin up again, no remount. But, after a few seconds, it spin down again. But, still, the "dmesg" command shows errors. Different HDD, different enclosure, show different symptoms or problems. Some HDD enclosures, number 1 above will occur. Some HDD enclosures, either number 2 or 3 above will occur. Sometimes, problem number 2 above will occur. Sometimes, problem number 3 will occur. Some enclosure, problem number 4 will occur. Here, I will use the following enclosure as example in this bug report: Product link: https://www.ugreen.com/products/usb-c-2-5-sata-iii-hard- drive-enclosure Purchase link in my country: https://shopee.com.my/UGREEN-USB-3.1-To- SATA-III-External-Hard-Drive- Enclosure-(2.5-)-i.64923440.1583255569?position=1 Here are the steps to reproduce (for the enclosure above): 1. Connect the external HDD to any available USB 3.0 port. The HDD will be mounted. Caja (Ubuntu MATE default file manager) will launch. 2. Close the Caja window. Do not do anything on the HDD. 3. Use left or right hand, touch the HDD enclosure to feel the spinning. Do not let your hand leave the enclosure, so that you can continue feel the spinning. 4. Use your another hand to operate your computer. 5. Go to desktop. 6. Right click on the external HDD icon. 7. Click "Safely Remove Drive". The HDD unmounted. Assume that one of your hands still touching the enclosure of the HDD, you will feel that the HDD will spin down and then spin up again. No remount. The LED indicator on the enclosure will keep flashing. These are described in problem number 2 and 3 above. Sometimes, after you unplug the drive and try to connect another drive, it will not be detected until you reboot your computer. Almost all external HDDs I tested will cause "dmesg" command to shows "Buffer I/O error" and "Synchronize Cache() failed" error after "Safely Remove Drive". In Microsoft Windows 10, all above mentioned problems WILL NOT occur. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cshong 1059 F pulseaudio /dev/snd/controlC0: cshong 1059 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-23 (242 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=cad772fa-c02b-4268-bc15-e366825ac807 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-63-generic N/A linux-backports-modules-5.8.0-63-generic N/A linux-firmware1.187.15 RfKill: Tags: focal Uname: Linux 5.8.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name:
[Kernel-packages] [Bug 1916554] Re: Cirrus Audio Codec CS8409/CS42L42 support
** Changed in: linux-oem-5.10 (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1916554 Title: Cirrus Audio Codec CS8409/CS42L42 support Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Fix Released Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] No driver for Cirrus CS8409 HDA bridge/CS42L42 codec, no playback/capture device available. [Fix] Patchset https://lore.kernel.org/alsa-devel/20210306111934.4832-1-vita...@opensource.cirrus.com/ currently in https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git branch for-next. [Test Case] On platform with Cirrus CS8409 HDA bridge: /sys/class/sound/card0/device/$ cat hdaudioC0D0/vendor_* 0x10138409 Cirrus Logic /sys/class/sound/card0/device/$ cat hdaudioC0D0/chip_name Generic Its chip_name should be updated with correct model name and sound system should be working: /sys/class/sound/card0/device/$ cat hdaudioC0D0/chip_name CS8409/CS42L42 APLAY and ARECORD should also list new audio devices: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CS8409/CS42L42 Analog [CS8409/CS42L42 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CS8409/CS42L42 Analog [CS8409/CS42L42 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 [Where problems could occur] New device driver landing, may bring in new issues bound to new driver/device configuration such as suspend/resume issues. == original bug description == $ sudo dmesg|grep hda [ 19.253994] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [ 19.254515] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 19.317386] snd_hda_codec_generic hdaudioC0D0: autoconfig for Generic: line_outs=1 (0x2c/0x0/0x0/0x0/0x0) type:speaker [ 19.317390] snd_hda_codec_generic hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 19.317392] snd_hda_codec_generic hdaudioC0D0:hp_outs=1 (0x24/0x0/0x0/0x0/0x0) [ 19.317393] snd_hda_codec_generic hdaudioC0D0:mono: mono_out=0x0 [ 19.317395] snd_hda_codec_generic hdaudioC0D0:inputs: [ 19.317397] snd_hda_codec_generic hdaudioC0D0: Internal Mic=0x44 [ 19.317399] snd_hda_codec_generic hdaudioC0D0: Mic=0x34 Vendor driver in progress: https://github.com/CirrusLogic/product-support/tree/cs8409_hda Upstream submission: https://patchwork.kernel.org/project/alsa-devel/list/?series=441331 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.10.0-1013-oem 5.10.0-1013.14 ProcVersionSignature: Ubuntu 5.10.0-1013.14-oem 5.10.6 Uname: Linux 5.10.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 22 22:13:32 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-beric-icl+X44 InstallationDate: Installed on 2021-02-04 (18 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.10 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1673 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-beric-icl+X44 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-04 (18 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3501 Package:
[Kernel-packages] [Bug 1937078] Re: Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
Test kernels at https://launchpad.net/~timg-tpi/+archive/ubuntu/hyperv-
azure-lp1937078
--
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/1937078
Title:
Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
Status in linux package in Ubuntu:
New
Bug description:
SRU Justification
[Impact]
Customers have degraded network performance on Hyper-V/Azure
This is a request to pick up a patch from the upstream, the patch
fixes an issue with Ubuntu as a hyper-v and Azure guest. This patch
need to get picked up for 20.04, 18.04. The link to the upstream patch
follows:
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv-
fixes=7c9ff3d61b253715dcf968a6307af148c9b2
Description of issue and solution:
The vmbus module uses a rotational algorithm to assign target CPUs to
a device's channels. Depending on the timing of different device's channel
offers, different channels of a device may be assigned to the same CPU.
For example on a VM with 2 CPUs, if NIC A and B's channels are offered
in the following order, NIC A will have both channels on CPU0, and
NIC B will have both channels on CPU1 -- see below. This kind of
assignment causes RSS load that is spreading across different channels
to end up on the same CPU.
Timing of channel offers:
NIC A channel 0
NIC B channel 0
NIC A channel 1
NIC B channel 1
VMBUS ID 14: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {cab064cd-1f31-47d5-a8b4-9d57e320cccd}
Sysfs path: /sys/bus/vmbus/devices/cab064cd-1f31-47d5-a8b4-9d57e320cccd
Rel_ID=14, target_cpu=0
Rel_ID=17, target_cpu=0
VMBUS ID 16: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {244225ca-743e-4020-a17d-d7baa13d6cea}
Sysfs path: /sys/bus/vmbus/devices/244225ca-743e-4020-a17d-d7baa13d6cea
Rel_ID=16, target_cpu=1
Rel_ID=18, target_cpu=1
Update the vmbus CPU assignment algorithm to avoid duplicate CPU
assignments within a device.
The new algorithm iterates num_online_cpus + 1 times.
The existing rotational algorithm to find "next NUMA & CPU" is still here.
But if the resulting CPU is already used by the same device, it will try
the next CPU.
In the last iteration, it assigns the channel to the next available CPU
like the existing algorithm. This is not normally expected, because
during device probe, we limit the number of channels of a device to
be <= number of online CPUs.
[Test Plan]
This could be tough to test as the patch fixes a race condition.
[Where problems could occur]
Network performance issues could persist.
[Other Info]
SF:#00315347
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937078/+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 1934652] Re: Graphics Tearing on 5.8 kernel (Intel(R) HD Graphics 2500, Ivy Bridge)
Same here. Still not fixed in 5.8.0-63. Package installed: linux-generic-hwe-20.04/focal-updates,focal-security,now 5.8.0.63.71~20.04.45 amd64 [installed] Downgrade to 5.8.0-43-generic fixes the issue. $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz stepping: 9 microcode : 0x21 cpu MHz : 2318.777 cache size : 6144 KB ... ** Attachment added: "another example of how it looks like (mostly appears when text selected)" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1934652/+attachment/5513159/+files/kubuntu_bug_1934652.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1934652 Title: Graphics Tearing on 5.8 kernel (Intel(R) HD Graphics 2500, Ivy Bridge) Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: Intel(R) Core(TM) i5-3470 with Intel(R) HD Graphics 2500 Problems experienced on fresh install of kubuntu or mate 20.04.02 (Automatically) Chosen kernel in these instances is the 5.8 kernel. NO issues with the 5.4 kernel - or the 5.8.0-48 kernel Problem: Operating system graphics (eg kubuntu calendar) and firefox (using webrender) have issues (see attached for example) This bug follows on from #1924624 Description:Ubuntu 20.04.2 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Jul 5 09:49:19 2021 InstallationDate: Installed on 2021-07-05 (0 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1934652/+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 1927749] Re: ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927749 Title: ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-aws source package in Focal: New Status in linux source package in Groovy: Fix Committed Status in linux-aws source package in Groovy: New Status in linux source package in Hirsute: Fix Committed Status in linux-aws source package in Hirsute: New Status in linux source package in Impish: In Progress Status in linux-aws source package in Impish: New Bug description: [Impact] arm64 only focal/aws 5.8.0-1031.33~20.04.1-aws and 5.8.0-1032.34~20.04.1-aws - regression. Works fine on previous Focal cycle (5.8.0-1028.30~20.04.3-aws) and current Groovy 5.8. 12. 05/06 07:01:39 DEBUG| utils:0153| [stdout] TAP version 13 13. 05/06 07:01:39 DEBUG| utils:0153| [stdout] 1..1 14. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 15. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 16. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 17. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 18. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 19. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check [PASS] 20. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 21. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 22. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 23. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct functions against tracers [UNRESOLVED] 24. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] 25. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - add/remove kprobe events [PASS] 26. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - add/remove synthetic events [PASS] 27. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event - selective clear (compatibility) [PASS] 28. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [13] Generic dynamic event - generic clear event [PASS] 29. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with event level files [PASS] 30. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [15] event tracing - restricts events based on pid notrace filtering [FAIL] 31. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [16] event tracing - restricts events based on pid [PASS] 32. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [17] event tracing - enable/disable with subsystem level files [PASS] 33. 05/06 07:01:46 DEBUG| utils:0153| [stdout] # [18] event tracing - enable/disable with top level files [PASS] [Test Plan] * Run ftrace test from kernel selftests. [Where problems could occur] * Only kernel selftests should be affected. * ftrace test can have false positives or negatives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927749/+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 1934110] Re: ubuntu-host driver lacks lseek ops
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1934110
Title:
ubuntu-host driver lacks lseek ops
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Bug description:
[ SRU Justification ][GROOVY][HIRSUTE][IMPISH]
== Impact ==
The ubuntu-host driver lacks procfs lseek ops and lseeking on the
procfs esm-token file will jump to a NULL address causing the
following splat:
942.470568] BUG: kernel NULL pointer dereference, address:
[ 942.471157] #PF: supervisor instruction fetch in kernel mode
[ 942.471724] #PF: error_code(0x0010) - not-present page
[ 942.472297] PGD 0 P4D 0
[ 942.472867] Oops: 0010 [#1] SMP PTI
[ 942.473435] CPU: 2 PID: 5661 Comm: stress-ng Not tainted 5.13.0-9-generic
#9
[ 942.474012] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0
02/06/2015
[ 942.474599] RIP: 0010:0x0
[ 942.475194] Code: Unable to access opcode bytes at RIP 0xffd6.
[ 942.475792] RSP: 0018:aacf80ff7eb8 EFLAGS: 00010246
[ 942.476383] RAX: RBX: 9eaa8a175240 RCX:
0001
[ 942.476986] RDX: RSI: RDI:
9eaa838d5800
[ 942.477600] RBP: aacf80ff7ed0 R08: 4000 R09:
0004
[ 942.478203] R10: 0002 R11: R12:
[ 942.478800] R13: R14: ffea R15:
9eaa838d5800
[ 942.479399] FS: 7f998d487f00() GS:9eaaffc8()
knlGS:
[ 942.480006] CS: 0010 DS: ES: CR0: 80050033
[ 942.480607] CR2: ffd6 CR3: 00010a774002 CR4:
00370ee0
[ 942.481219] DR0: DR1: DR2:
[ 942.481855] DR3: DR6: fffe0ff0 DR7:
0400
[ 942.482458] Call Trace:
[ 942.483052] proc_reg_llseek+0x4e/0x80
[ 942.483646] ? __fdget_pos+0x43/0x50
[ 942.484234] ksys_lseek+0x84/0xc0
[ 942.484815] __x64_sys_lseek+0x1a/0x20
[ 942.485412] do_syscall_64+0x61/0xb0
[ 942.485966] ? asm_exc_page_fault+0x8/0x30
[ 942.486476] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 942.486994] RIP: 0033:0x7f998d5c1cdb
[ 942.487512] Code: ff ff c3 0f 1f 40 00 48 8b 15 89 81 0d 00 f7 d8 64 89 02
48 c7 c0 ff ff ff ff eb ba 0f 1f 00 f3 0f 1e fa b8 08 00 00 00 0f 05 <48> 3d 00
f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 59 81 0d 00 f7 d8
[ 942.488593] RSP: 002b:7ffdf61c5328 EFLAGS: 0246 ORIG_RAX:
0008
[ 942.489148] RAX: ffda RBX: RCX:
7f998d5c1cdb
[ 942.489710] RDX: RSI: RDI:
0004
[ 942.490252] RBP: 0004 R08: 01785e4740dd R09:
562dbebb9e50
[ 942.490801] R10: 7ffdf61c5300 R11: 0246 R12:
7ffdf61c63f0
[ 942.491354] R13: 7ffdf61c53f0 R14: 0003 R15:
01e9
== Fix ==
Add the default_llseek ops:
diff --git a/ubuntu/ubuntu-host/ubuntu-host.c
b/ubuntu/ubuntu-host/ubuntu-host.c
index 1abd402..a4c0636 100644
--- a/ubuntu/ubuntu-host/ubuntu-host.c
+++ b/ubuntu/ubuntu-host/ubuntu-host.c
@@ -38,6 +38,8 @@ static ssize_t esm_token_write(struct file *f, const char
__user *buf,
static const struct proc_ops esm_token_fops = {
.proc_read = esm_token_read,
.proc_write = esm_token_write,
+ .proc_lseek = default_llseek,
+
};
== Test plan ==
modrobe ubuntu-host
stress-ng --procfs 0 -t 60
without the fix we hit the splat. With the fix it's OK.
== Where problems could occur ==
This one liner adds the missing proc_lseek op. It is hard to see where
it can cause a regression since it affects the driver no other way. I
doubt any code is relying on the current semantics of lseek not
working.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934110/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe :
[Kernel-packages] [Bug 1934652] Re: Graphics Tearing on 5.8 kernel (Intel(R) HD Graphics 2500, Ivy Bridge)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1934652 Title: Graphics Tearing on 5.8 kernel (Intel(R) HD Graphics 2500, Ivy Bridge) Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: Intel(R) Core(TM) i5-3470 with Intel(R) HD Graphics 2500 Problems experienced on fresh install of kubuntu or mate 20.04.02 (Automatically) Chosen kernel in these instances is the 5.8 kernel. NO issues with the 5.4 kernel - or the 5.8.0-48 kernel Problem: Operating system graphics (eg kubuntu calendar) and firefox (using webrender) have issues (see attached for example) This bug follows on from #1924624 Description:Ubuntu 20.04.2 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Jul 5 09:49:19 2021 InstallationDate: Installed on 2021-07-05 (0 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1934652/+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 1934175] Re: Kernel oops due to uninitialized list on kernfs (kernfs_kill_sb)
** Changed in: linux (Ubuntu)
Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned)
** Changed in: linux (Ubuntu Bionic)
Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Krzysztof Kozlowski (krzk)
--
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/1934175
Title:
Kernel oops due to uninitialized list on kernfs (kernfs_kill_sb)
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
* We had a recent report of a kernel crash due to a NULL pointer dereference
in a Bionic 4.15 derivative kernel, as per the following log collected:
[...]
[537105.767348] SLUB: Unable to allocate memory on node -1,
gfp=0x14000c0(GFP_KERNEL)
[...]
[537105.767368] BUG: unable to handle kernel NULL pointer dereference at
0008
[537105.11] IP: kernfs_kill_sb+0x31/0x70
[537105.783582] PGD 0 P4D 0
[537105.787844] Oops: 0002 [#1] SMP PTI
[...]
RIP: 0010:kernfs_kill_sb+0x31/0x70
RSP: 0018:b90aec1afd00 EFLAGS: 00010286
RAX: RBX: 9fdbd567d900 RCX: a0143885ae01
RDX: RSI: a0143885ae00 RDI: a2937c40
RBP: b90aec1afd10 R08: a0150b581510 R09: 0001814d
R10: b90aec1afcd8 R11: 0100 R12: a01436e43000
R13: a01436e43000 R14: R15: 9fdbd567d900
FS: 7fe41a615b80() GS:a01afea4() knlGS:
CS: 0010 DS: ES: CR0: 80050033
CR2: 0008 CR3: 007dfe3cc003 CR4: 003606e0
DR0: DR1: DR2:
DR3: DR6: fffe0ff0 DR7: 0400
Call Trace:
sysfs_kill_sb+0x1f/0x40
deactivate_locked_super+0x48/0x80
kernfs_mount_ns+0x1eb/0x230
sysfs_mount+0x66/0xc0
mount_fs+0x37/0x160
? alloc_vfsmnt+0x1b3/0x230
vfs_kern_mount.part.24+0x5d/0x110
do_mount+0x5ed/0xce0
[...]
* The following detailed call stack plus the disassembly help to
understand the cause of the issue:
mount_fs()
--sysfs_mount()
kernfs_mount_ns()
--deactivate_locked_super()
sysfs_kill_sb()
--kernfs_kill_sb()
The below disassembly of kernfs_kill_sb() clarifies exactly the issue:
812f46e0 :
[ ... prologue ...]
48 8b 9f 08 04 00 00mov0x408(%rdi),%rbx # %rbx = kernfs_super_info
*info = sb->s_fs_info
49 89 fcmov%rdi,%r12 # %r12 = super_block *sb
48 c7 c7 40 7c 53 82mov$0x82537c40,%rdi # %rdi =
_mutex (global)
812f46f9: R_X86_64_32S kernfs_mutex
e8 ee da 67 00 callq 819721f0 #
mutex_lock(_mutex);
[...]
48 8b 53 18 mov0x18(%rbx),%rdx # %rdx = info->node
48 8b 43 20 mov0x20(%rbx),%rax # based on splat, RAX == 0x0
[info->head.prev]
48 89 42 08 mov%rax,0x8(%rdx) # <- OOPS [tried to assign
next->prev = prev, see __list_del()]
48 89 10mov%rdx,(%rax)
48 b8 00 01 00 00 00movabs $0xdead0100,%rax # node->next =
LIST_POISON1
[...]
* The fix for this issue comes from upstream commit 82382acec0c9
("kernfs: deal with kernfs_fill_super() failures"); this commit is a
very trivial fix that adds an INIT_LIST_HEAD(>node) in
kernfs_mount_ns(), making the list prev/next pointers valid since the
beginning. Unfortunately this commit wasn't CCed to stable email when
sent, so it wasn't automatically picked up by Ubuntu kernel; now it
was properly submitted to stable list [0].
* Along with this fix, we found another commit (7b745a4e4051) which is
a small/simple fix to correlated code, that also should have been sent
to 4.14.y stable branch, but for some reason wasn't. Since both
commits were accepted in linux-stable, we are hereby proposing the
backport for Ubuntu kernel 4.15.
[0]
https://lore.kernel.org/stable/20210622210622.9925-1-gpicc...@canonical.com/
[Test Case]
* We don't have a real test case, although low-memory condition or an
artificial kprobe reproducer could easily trigger the issue.
* We booted a qemu virtual machine with a kernel containing both
patches with no issues.
[Where problems could occur]
* The likelihood of issues are low, specially due to the fact both patches
are very simple and they are on upstream kernel for more than 3 years (and were
quickly accepted in 4.14.y stable branch last week).
* With that sad, the second patch could potentially introduce issues
with super_block references - I honestly cannot conceive any issues
potentially caused by patch 1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934175/+subscriptions
--
Mailing list:
[Kernel-packages] [Bug 1932367] Re: Pixel format change broken for Elgato Cam Link 4K
Installed linux 5.11.0.26.28 and verified that it is working. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1932367 Title: Pixel format change broken for Elgato Cam Link 4K Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Triaged Bug description: [Impact] The Elgato Cam Link 4K HDMI video capture card reports to support three different pixel formats, where the first format depends on the connected HDMI device. ``` $ v4l2-ctl -d /dev/video0 --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [1]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [2]: 'YU12' (Planar YUV 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) ``` Changing the pixel format to anything besides the first pixel format does not work: ``` $ v4l2-ctl -d /dev/video0 --try-fmt-video pixelformat=YU12 Format Video Capture: Width/Height : 3840/2160 Pixel Format : 'NV12' (Y/CbCr 4:2:0) Field : None Bytes per Line: 3840 Size Image: 12441600 Colorspace: sRGB Transfer Function : Rec. 709 YCbCr/HSV Encoding: Rec. 709 Quantization : Default (maps to Limited Range) Flags : ``` User space applications like VLC might show an error message on the terminal in that case: ``` libv4l2: error set_fmt gave us a different result than try_fmt! ``` Depending on the error handling of the user space applications, they might display a distorted video, because they use the wrong pixel format for decoding the stream. [Fix] The Elgato Cam Link 4K responds to the USB video probe VS_PROBE_CONTROL/VS_COMMIT_CONTROL with a malformed data structure: The second byte contains bFormatIndex (instead of being the second byte of bmHint). The first byte is always zero. The third byte is always 1. The firmware bug was reported to Elgato on 2020-12-01 and it was forwarded by the support team to the developers as feature request. There is no firmware update available since then. The latest firmware for Elgato Cam Link 4K as of 2021-03-23 has MCU 20.02.19 and FPGA 67. Therefore correct the malformed data structure for this device. The change was successfully tested with VLC, OBS, and Chromium using different pixel formats (YUYV, NV12, YU12), resolutions (3840x2160, 1920x1080), and frame rates (29.970 and 59.940 fps). [Test Case] Connect an input device to the Cam Link 4K and try all three pixel formats with VLC: vlc v4l2:///dev/video0 --v4l2-chroma=NV12 vlc v4l2:///dev/video0 --v4l2-chroma=YU12 [Other Info] The fix was reviewed and accepted by the subsystem maintainer and will be included upstream: https://git.linuxtv.org/media_stage.git/commit/?id=4c6e0976295add7f0ed94d276c04a3d6f1ea8f83 Attached a backported patch for Ubuntu. I successfully tested it with Linux 5.11 on Ubuntu 21.04 and Linux 5.8 on Ubuntu 20.10. It should work on older kernel versions as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932367/+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 1924997] Re: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80%
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] On a few CS8409 installed platforms, there are crack sounds when playing audio with output volume set to 100%. [Fix] The hardware is not capable of generating smooth audio output at the maximum volume that codec chip can be configured. A fix proposed to lower the maximum output volume using CS8409 equalizer. [Test Case] Use GNOME Settings / Sound Settings, set volume to 100%, play test audio for both right and left channels; set volume back to 70%, and repeat the same to compare to differences. While we don't have acoustic lab to perform precise measurements, the result was confirmed by partner. [Where problems could occur] This is to add a preconfigured, equalizer driver default values. This will introduce non-uniformed frequency response in comparison to that in the hardware preset. The net effect observable to general users is a lower maximum output volume. For those Hi-Fi users, audio output always takes additional calibration via extra software like ALSAEqual and/or hardware. [Other Info] By SRU we skipped a couple of refactoring changes in asound upstream tree, so additional changes to the original patch are required to backport. == original bug description == A cracking noises is noticed when doing audio playback from the built- in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1444 F pulseaudio CasperMD5CheckResult: skip DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-proposed-release+X90 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3500 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 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.10.0-1020-oem N/A linux-backports-modules-5.10.0-1020-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.10.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/02/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 09YKK0 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1933716] Re: Black screen on boot after stable update
*** This bug is a duplicate of bug 1934647 *** https://bugs.launchpad.net/bugs/1934647 This bug in kernel bugtracker https://bugzilla.kernel.org/show_bug.cgi?id=213615 ** Bug watch added: Linux Kernel Bug Tracker #213615 https://bugzilla.kernel.org/show_bug.cgi?id=213615 -- 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/1933716 Title: Black screen on boot after stable update Status in linux package in Ubuntu: Confirmed Bug description: After kernel update from 5.11.0-18-generic to 5.11.0-22-generic system boots into black screen. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 1374 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 26 11:55:00 2021 InstallationDate: Installed on 2021-05-02 (55 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Pavilion Laptop 15-eg0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9625a19f-eeea-4a92-ab4b-1549d4950f3b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2021 dmi.bios.release: 15.12 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 87CB dmi.board.vendor: HP dmi.board.version: 34.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 34.27 dmi.modalias: dmi:bvnInsyde:bvrF.12:bd03/17/2021:br15.12:efr34.27:svnHP:pnHPPavilionLaptop15-eg0xxx:pvrType1ProductConfigId:rvnHP:rn87CB:rvr34.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eg0xxx dmi.product.sku: 2Q2T4EA#AKD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933716/+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 1923557] Re: CirrusLogic: The default input volume is "0%" on Dell Bullseye
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1923557
Title:
CirrusLogic: The default input volume is "0%" on Dell Bullseye
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On some platforms with Cirrus CS8409 audio codec, DMIC volume default
value in kernel driver is 0, which follows no audio sound will be played
during installation and OOBE until being explicitly configured again via
GNOME Settings GUI or other methods.
[Fix]
Commit 0e853a9c3937 ("ALSA: hda/cirrus: Set Initial DMIC volume for
Bullseye to -26 dB") currently landed in upstream tiwai/sound.git is
required this address this issue. It's also being proposed to v5.13
merge window.
[Test Case]
Try to remove all the user space settings caches and reboot. The
detailed steps are:
$ sudo systemctl disable alsa-restore.service
$ sudo rm /var/lib/alsa/asound.state
$ sudo reboot
$ amixer sget 'Internal Mic',0
Simple mixer control 'Internal Mic',0
Capabilities: cvolume cswitch
Capture channels: Front Left - Front Right
Limits: Capture 0 - 63
Front Left: Capture 0 [0%] [-51.00dB] [off]
Front Right: Capture 0 [0%] [-51.00dB] [off]
Expect 40% in the front left/right capture volumes.
[Where problems could occur]
This gives the default value of Cirrus CS8409 audio codec capture volume
on Bullseye only. Cannot come out with any side effect it may produce so
far.
[Other Info]
By SRU we skipped a couple of refactoring changes in asound upstream
tree, so additional changes to the original patch are required to
backport.
== original bug description ==
The initial default input volume right after Ubuntu installation is
set to 0% while 16% is expected.
$ amixer
...
Simple mixer control 'Internal Mic',0
Capabilities: cvolume cswitch
Capture channels: Front Left - Front Right
Limits: Capture 0 - 63
Front Left: Capture 0 [0%] [-51.00dB] [off]
Front Right: Capture 0 [0%] [-51.00dB] [off]
Simple mixer control 'Internal Mic Boost',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 2
Front Left: 0 [0%] [0.00dB]
Front Right: 0 [0%] [0.00dB]
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: u 1523 F pulseaudio
CasperMD5CheckResult: skip
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-proposed-release+X90
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-04-13 (0 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd.
FingerPrint
Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Vostro 3500
Package: linux-oem-5.10
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem
root=UUID=c666f936-5b87-4cbd-bde6-21fa93b89036 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25
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.10.0-1020-oem N/A
linux-backports-modules-5.10.0-1020-oem N/A
linux-firmware 1.187.10
Tags: focal
Uname: Linux 5.10.0-1020-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 02/02/2021
dmi.bios.release: 1.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.2
dmi.board.name: 09YKK0
dmi.board.vendor: Dell Inc.
dmi.board.version: X00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
[Kernel-packages] [Bug 1913342] Re: zfs.8 man page snapshot listing instructions are confusing
** Changed in: zfs-linux (Ubuntu) Status: New => Fix Committed ** Changed in: zfs-linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1913342 Title: zfs.8 man page snapshot listing instructions are confusing Status in Native ZFS for Linux: Unknown Status in zfs-linux package in Ubuntu: Fix Released Bug description: The zfs.8 man page describes in 3 places how to include snapshots in "zfs list": 1) Snapshots are displayed if the listsnaps property is on (the default is off). 2) Snapshots are displayed if the listsnaps property is on. The default is off. See zpool(8) for more information on pool properties. 3) For example, specifying -t snapshot displays only snapshots. The first of these has twice now (I'm just learning zfs) sent me down a rabbit hole, looking for a zfs dataset property "listsnaps". There is no such property (of datasets). I'm on version 0.8.3 of zfsutils-linux that has this man page, but when I look at https://zfsonlinux.org/manpages/0.8.6/man8/zfs.8.html it seems that the above is still true in 0.8.6 Suggestion, to help us newbies reduce our learning time to list snapshots: Change both of the first 2 of the above 3 places in zfs.8 to: " "zfs list" displays snapshots only if either the "listsnapshots" property of the underlying zpool is on, or if the "zfs list -t snapshot" option is specified. Extra Credit: Just now it seems to me that the following command does _NOT_ list snapshots, on a dataset that has some snapshots ... so the zfs.8 documentation that the "zfs list -t type" can be a "comma-separated list of types to display" seems incorrect: zfs list -t filesystem,snapshot myzfsdataset Whether this "Extra Credit" discrepancy is a bug in the documentation, or in the zfs command code, or newbie operator error, I'll leave as an exercise to the reader . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.5 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Jan 26 13:41:16 2021 SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1913342/+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 1936988] Re: Apt has unmet dependencies for libzpool5linux, zfs-zed, zfsutils-linux
A 3rd party zfs from 2.1.0-0york2~18.04 was used and is causing this issue. Remove these and re-install the official packages. Marking this as won't fix. ** Changed in: zfs-linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1936988 Title: Apt has unmet dependencies for libzpool5linux, zfs-zed, zfsutils-linux Status in zfs-linux package in Ubuntu: Won't Fix Bug description: Hi guys, let me first open with I don't know where to post this. I hope someone here can help. Secondly, I use this machine as a headless server with a zpool on it for my home file sharing. I popped on today and saw updates lingering, so I ran my usual command. sudo apt update -y && sudo apt upgrade -y ; sudo apt clean && sudo apt autoclean ; sudo apt autoremove -y It was going fine until it got to the ZoL specific packages; The following packages have unmet dependencies: libzpool5linux : Depends: libnvpair3linux (>= 0.8.2) but it is not installed Depends: libzfs4linux (>= 2.0) but it is not installed zfs-zed : Depends: libnvpair3linux (>= 0.8.2) but it is not installed Depends: libuutil3linux (>= 0.8.2) but it is not installed Depends: libzfs4linux (>= 2.0) but it is not installed zfsutils-linux : Depends: libnvpair3linux (= 2.1.0-0york2~18.04) but it is not installed Depends: libuutil3linux (= 2.1.0-0york2~18.04) but it is not installed Depends: libzfs4linux (= 2.1.0-0york2~18.04) but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). I run apt fix broken install and this is the output; Preparing to unpack .../libnvpair3linux_2.1.0-0york2~18.04_amd64.deb ... Unpacking libnvpair3linux (2.1.0-0york2~18.04) ... dpkg: error processing archive /var/cache/apt/archives/libnvpair3linux_2.1.0-0york2~18.04_amd64.deb (--unpack): trying to overwrite '/lib/x86_64-linux-gnu/libnvpair.so.3.0.0', which is also in package libnvpair1linux 2.0.4-0york0~18.04 Preparing to unpack .../libuutil3linux_2.1.0-0york2~18.04_amd64.deb ... Unpacking libuutil3linux (2.1.0-0york2~18.04) ... dpkg: error processing archive /var/cache/apt/archives/libuutil3linux_2.1.0-0york2~18.04_amd64.deb (--unpack): trying to overwrite '/lib/x86_64-linux-gnu/libuutil.so.3.0.0', which is also in package libuutil1linux 2.0.4-0york0~18.04 Preparing to unpack .../libzfs4linux_2.1.0-0york2~18.04_amd64.deb ... Unpacking libzfs4linux (2.1.0-0york2~18.04) ... dpkg: error processing archive /var/cache/apt/archives/libzfs4linux_2.1.0-0york2~18.04_amd64.deb (--unpack): trying to overwrite '/lib/x86_64-linux-gnu/libzfs_core.so.3.0.0', which is also in package libzfs2linux 2.0.4-0york0~18.04 Errors were encountered while processing: /var/cache/apt/archives/libnvpair3linux_2.1.0-0york2~18.04_amd64.deb /var/cache/apt/archives/libuutil3linux_2.1.0-0york2~18.04_amd64.deb /var/cache/apt/archives/libzfs4linux_2.1.0-0york2~18.04_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Here are my OS details; Ubuntu 18.04.5 LTS (GNU/Linux 5.4.0-77-generic x86_64) Trying the install packages one by one results in the above. So... I'm kinda stuck. Doesn't help that I can't access my zpool either. Thank you for looking. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1936988/+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 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws
Please keep all discussion about the touchpad in bug 1899913. ** Summary changed: - [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws + [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- 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/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws Status in linux package in Ubuntu: Triaged Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1936998] Re: e1000e blocks the boot process when it tried to write checksum to its NVM
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1936998 Title: e1000e blocks the boot process when it tried to write checksum to its NVM Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] While probing e1000e, it checks its NVM checksum, and write correct checksum back if the checksum is not correct. But for recent GBE update for security, its NVM could be written once for MAC address during production, so write checksum during driver probing is not allowed and would block the boot process. [Fix] Intel provides a fix for it. https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20210718041031.3619696-1-sasha.nef...@intel.com/ [Test] Verified on a Dell machine which has wrong NVM checksum. [Where problems could occur] From what Intel told us, the checksum isn't correct is not a big deal, we could ignore it and it won't lead to any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936998/+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 1934741] Re: Add new PCI MMIO based thermal driver [8086:461d] for Intel Alder Lake
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934741 Title: Add new PCI MMIO based thermal driver [8086:461d] for Intel Alder Lake Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] [18/14083] On Intel Alder Lake platforms, processor thermal device provides an additional thermal zone TCPU_PCI that is based on a new PCI MMIO only driver. [Fix] Two upstream v5.14-rc1 commits to backport. [Test Case] $ lspci -vvnns 00:04.0 00:04.0 Signal processing controller [1180]: Intel Corporation Device [8086:461d] (rev 01) Subsystem: Intel Corporation Device [8086:7270] ... # thermal_zones provided by the original driver $ cat /sys/devices/virtual/thermal/thermal_zone*/type acpitz INT3400 Thermal TCPU x86_pkg_temp # thermal_zones provided by the new driver $ cat /sys/devices/virtual/thermal/thermal_zone*/type acpitz INT3400 Thermal TCPU TCPU_PCI x86_pkg_temp [Where problems could occur] These changes do not change existing interface to userspace, but add an additional thermal zone that doesn't involve ACPI method calls for use. [Other Info] ADL targets 5.13 kernel, so only Impish and oem-5.13 are nominated. == original bug description == $ lspci -vvnns 00:04.0 00:04.0 Signal processing controller [1180]: Intel Corporation Device [8086:461d] (rev 01) Subsystem: Intel Corporation Device [8086:7270] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device [original] $ cat /sys/devices/virtual/thermal/thermal_zone*/type acpitz INT3400 Thermal TCPU x86_pkg_temp [patched] $ cat /sys/devices/virtual/thermal/thermal_zone*/type acpitz INT3400 Thermal TCPU TCPU_PCI x86_pkg_temp --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1367 F pulseaudio CasperMD5CheckResult: skip DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X130 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-06-18 (18 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. MachineType: Intel Corporation Alder Lake Client Platform Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-2006-oem root=UUID=a4f90fb9-1c2c-4d37-be7a-1b67b667c378 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-2006.6+lp1934660.1.adl.pmc.core-oem 5.13.0 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.13.0-2006-oem N/A linux-backports-modules-5.13.0-2006-oem N/A linux-firmware 1.187.15
[Kernel-packages] [Bug 1926579] Re: On TGL platforms screen shows garbage when browsing website by scrolling mouse
** Changed in: linux-oem-5.13 (Ubuntu) Status: Invalid => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1926579 Title: On TGL platforms screen shows garbage when browsing website by scrolling mouse Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: [Impact] On Dell TGL platforms screen shows garbage when browsing website by scrolling mouse [Fix] This patch fixes the issue https://patchwork.freedesktop.org/patch/430153/?series=89348=1 [Test] Verified on Dell TGL-H platforms. [Where problems could occur] It disable PSR2 on A0 and B0 TGL-H platforms, should introduce no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926579/+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 1936682] Re: Fix kernel panic caused by legacy devices on AMD platforms
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1936682 Title: Fix kernel panic caused by legacy devices on AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] When a legacy device is only 32bit DMA capable and it's in the same IOMMU group with iommu_v2 capable devices, the device in question will be forced to use identity mapping and triggers kernel panic on DMA operation because it can't do 64bit DMA. [Fix] Keep swiotlb enabled so legacy devices can do 64bit DMA. This is also how Intel and ARM64 platforms deal with legacy devices. [Test] Boot an affected system. Kernel panic in Realtek WiFi driver's probe routine. After the patch is applied, the system can work normally. [Where problems could occur] The default swiotlb uses 64MB memory, so if the system doesn't have any legacy device, there are 64MB ram less for the system to use. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936682/+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 1936296] Re: Fix display output on HP hybrid GFX laptops
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1936296 Title: Fix display output on HP hybrid GFX laptops Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] Video output MUX switched from Intel GPU to Nvidia GPU after S3, so display settings are lost. [Fix] Always use Nvidia GPU to do the video output. This matches the behavior on the other OS. [Test] Connect and external monitor, and change the scaling factor or resolution, suspend the laptop. After wakeup, the custom monitor setting is kept. [Where problems could occur] If nvidia.ko or nouveau.ko is blacklisted, the video output may stop working, as it's now routed away from i915 device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936296/+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 1936785] Re: Add support for AMD BCL DID
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936785 Title: Add support for AMD BCL DID Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] AMD BCL APU shares same code as CZN/RN, but has another DID to be added to kernel. [Fix] Below commit adds the ID. https://lists.freedesktop.org/archives/amd-gfx/2021-July/066502.html [Test] We didn't receive h/w yet, just told by AMD that the new ID is required. [Where problems could occur] Adding a new ID should be pretty safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936785/+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 1937004] Re: Add additional Mediatek MT7921 WiFi/BT device IDs
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937004 Title: Add additional Mediatek MT7921 WiFi/BT device IDs Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] Some Mediatek MT7921 Bluetooth doesn't work out of box. [Fix] One ID for Lite-On was included in upstream, but we need two additional more from different vendors. [Test Case] With firmware from bug 1936452, this will bring up MT7921 Bluetooth. Check BD address from output of `hciconfig`. [Where problems could occur] This brings up new devices that wasn't working. After being up and running, we may face some other runtime issue, e.g. power consumption. == original bug description == Mediatek MT7921 has been added to mainline kernel & firmware. Firmware part is being handled by bug 1936452, and WiFi fw loading failure in bug 1936790. This issue will focus on backport/add device IDs for MT7921: * Bus 001 Device 004: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device * Bus 002 Device 003: ID 13d3:3567 IMC Networks linux$ git log --graph --oneline korg/master -- \ drivers/bluetooth/ \ drivers/net/wireless/mediatek/mt76/mt7921/ linux-firmware$ git log --graph --oneline korg/master -- \ mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin \ mediatek/WIFI_RAM_CODE_MT7961_1.bin \ mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin * a7882719 linux-firmware: update frimware for mediatek bluetooth chip (MT7921) * 2fd5139f linux-firmware: update firmware for MT7921 WiFi device to 20210612122753 * 42a66e5b linux-firmware: update firmware for MT7921 WiFi device * 58fb90a0 linux-firmware: add frimware for mediatek bluetooth chip (MT7921) * 391fd50d linux-firmware: add firmware for MT7921 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1278 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X135 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-05 (16 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 192f:0616 Avago Technologies, Pte. ADNS-5700 Optical Mouse Controller (5-button) Bus 001 Device 002: ID 03f0:344a HP, Inc HP USB Slim Keyboard Bus 001 Device 004: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3910 Package: linux-firmware 1.187.15+staging.9 [origin: LP-PPA-vicamo-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9009-oem root=UUID=6ae05750-3063-48a4-92af-626f62ff75fc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9009.10+staging.2-oem 5.13.0 RelatedPackageVersions: linux-restricted-modules-5.13.0-9009-oem N/A linux-backports-modules-5.13.0-9009-oem N/A linux-firmware 1.187.15+staging.9 Tags: third-party-packages focal Uname: Linux 5.13.0-9009-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/12/2021 dmi.bios.release: 0.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.8.22 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.8.22:bd07/12/2021:br0.8:svnDellInc.:pnInspiron3910:pvr:sku0AD3:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: Inspiron 3910 dmi.product.sku: 0AD3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws
yes ! I am Gonna tell you that same Now its perfectly fine no glitches and tearing issue now.But I want to Know does touchpad issue is solved in UBuntu 20.04LTS for lenovo yoga 7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws
I would edit /etc/default/grub and add i915.enable_psr=0 to the GRUB_CMDLINE_LINUX_DEFAULT line. Then run: sudo update-grub and reboot. -- 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/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1937340] [NEW] nvidia-kernel-source-450-server 450.142.00-0ubuntu0.20.04.1: nvidia-srv kernel module failed to build
Public bug reported: when i was trying to install nvidia-driver-470 or nvidia-driver-460, there was an error. so instead, i then tried to install nvidia-driver-450-server, and i thought it would be working. right now, i do not have a nvidia-driver installed and this is sad because my machine got a nvidia graphic card rtx-5000. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-450-server (not installed) ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-63-generic Date: Fri Jul 23 16:25:16 2021 InstallationDate: Installed on 2021-06-13 (40 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 450.142.00-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-450-server Title: nvidia-kernel-source-450-server 450.142.00-0ubuntu0.20.04.1: nvidia-srv kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-450-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450-server in Ubuntu. https://bugs.launchpad.net/bugs/1937340 Title: nvidia-kernel-source-450-server 450.142.00-0ubuntu0.20.04.1: nvidia- srv kernel module failed to build Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Bug description: when i was trying to install nvidia-driver-470 or nvidia-driver-460, there was an error. so instead, i then tried to install nvidia-driver-450-server, and i thought it would be working. right now, i do not have a nvidia-driver installed and this is sad because my machine got a nvidia graphic card rtx-5000. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-450-server (not installed) ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-63-generic Date: Fri Jul 23 16:25:16 2021 InstallationDate: Installed on 2021-06-13 (40 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 450.142.00-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-450-server Title: nvidia-kernel-source-450-server 450.142.00-0ubuntu0.20.04.1: nvidia-srv kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450-server/+bug/1937340/+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 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws
Please tell me proper procedure to change value to zero -- 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/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws
It said -1 -- 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/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws
Another simple test to verify you've set the parameter is to run: sudo cat /sys/module/i915/parameters/enable_psr It should print zero. -- 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/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws
Also > after booting to recovery boot brightness controlling have some issue is not a bug. It's expected behaviour in recovery mode. -- 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/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws
You may need to run: sudo update-grub and reboot again before it starts working. -- 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/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws
Please check /proc/cmdline and verify it contains the new parameter: i915.enable_psr=0 -- 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/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws
i think there is some issue with intel gpu driver because sometime ubuntu stuck on bootscreen and glitches and tearing is common in every scenario and after booting to recovery boot brightness controlling have some issue and all tends towards the ghraphics bug. -- 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/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws
As you said to change the i915.enable_psr =0 i have save it to suno nano etc/kernal/cmdline after rebooting my pc there is more screen tearing problem. yeah i am using ubuntu in 2 device one in my old lenovo g570 model and new lenovo yoga 7i and in G570 there is no problem such as screen tearing or brightness every thing is perfectly fine in g570 -- 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/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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
