[Kernel-packages] [Bug 1973391] [NEW] package nvidia-dkms-510 510.60.02-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error
Public bug reported: i don't know anything more than this ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-510 510.60.02-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-107.121-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat May 14 08:52:15 2022 ErrorMessage: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-02-15 (87 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-510 Title: package nvidia-dkms-510 510.60.02-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to focal on 2022-03-31 (43 days ago) ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1973391 Title: package nvidia-dkms-510 510.60.02-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: i don't know anything more than this ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-510 510.60.02-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-107.121-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat May 14 08:52:15 2022 ErrorMessage: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-02-15 (87 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-510 Title: package nvidia-dkms-510 510.60.02-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to focal on 2022-03-31 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1973391/+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 1963568] Re: linux-firmware 20220302.gitee0667aa-0ubuntu1 failed to install/upgrade
[Expired for linux-firmware (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Expired -- 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/1963568 Title: linux-firmware 20220302.gitee0667aa-0ubuntu1 failed to install/upgrade Status in linux-firmware package in Ubuntu: Expired Bug description: QEMU/KVM VM ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220302.gitee0667aa-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marty 1634 F pipewire-media- marty 1635 F pulseaudio /dev/snd/seq:marty 1633 F pipewire CasperMD5CheckResult: pass Date: Thu Mar 3 18:39:26 2022 Dependencies: firmware-sof-signed 1.9-1ubuntu1 DuplicateSignature: package:linux-firmware:20220302.gitee0667aa-0ubuntu1 Setting up libreoffice-pdfimport (1:7.3.1~rc2-0ubuntu1) ... dpkg: error processing package linux-firmware (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-02-11 (20 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) IwConfig: lono wireless extensions. enp1s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet 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=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) PackageArchitecture: all ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_70i6e6@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_70i6e6 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 3.10.1-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu5 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 20220302.gitee0667aa-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: ArchLinux 1.15.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-6.2 dmi.modalias: dmi:bvnSeaBIOS:bvrArchLinux1.15.0-1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-6.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1963568/+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 1964539] Re: [nouveau] 42beta: screen unlock gets stuck on primary display, secondary display is unlocked
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (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/1964539 Title: [nouveau] 42beta: screen unlock gets stuck on primary display, secondary display is unlocked Status in linux package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: [Impact] Occasionally, when the screen has been locked for a medium length of time, > 5 mins, when you press the spacebar, enter your password, the primary display freezes and the lockscreen slider does not slide up. The secondary screen is fine, and unlocks. See screenshot for what it looks like. You can click, interact with the secondary screen. On the primary screen, you can super key and launch an application, but you won't be able to interact with it. You can't see what you are doing. The way to fix is to re-lock the screen, wait a bit, and attempt to unlock. Sometimes you won't be able to unlock immediately, as it is difficult to get the monitor to power on again, it appears gnome-shell does not send the wakeup signal. gnome-shell 42~beta-1ubuntu2 from -proposed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-01-02 (68 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220101) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 RelatedPackageVersions: mutter-common 42~beta-1ubuntu1 Tags: wayland-session third-party-packages jammy package-from-proposed Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964539/+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 1964539] Re: [nouveau] 42beta: screen unlock gets stuck on primary display, secondary display is unlocked
[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/1964539 Title: [nouveau] 42beta: screen unlock gets stuck on primary display, secondary display is unlocked Status in linux package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: [Impact] Occasionally, when the screen has been locked for a medium length of time, > 5 mins, when you press the spacebar, enter your password, the primary display freezes and the lockscreen slider does not slide up. The secondary screen is fine, and unlocks. See screenshot for what it looks like. You can click, interact with the secondary screen. On the primary screen, you can super key and launch an application, but you won't be able to interact with it. You can't see what you are doing. The way to fix is to re-lock the screen, wait a bit, and attempt to unlock. Sometimes you won't be able to unlock immediately, as it is difficult to get the monitor to power on again, it appears gnome-shell does not send the wakeup signal. gnome-shell 42~beta-1ubuntu2 from -proposed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-01-02 (68 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220101) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 RelatedPackageVersions: mutter-common 42~beta-1ubuntu1 Tags: wayland-session third-party-packages jammy package-from-proposed Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964539/+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 1973385] [NEW] nvidia-xconfig produces nonworking xorg.conf
Public bug reported: When I run nvidia-xonfig and then restart to run with the generated xorg.conf, I cannot use/login to my system anymore, because after the boot process I dont get a login screen, but a completely black screen with a tiny little white dot in the top left corner. Booting in rescue mode and deleting/moving the xorg.conf and letting the system start without one fixes the issue and gives me a login screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-utils-510 510.60.02-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 02:21:53 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nvidia-graphics-drivers-510 UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1973385 Title: nvidia-xconfig produces nonworking xorg.conf Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: When I run nvidia-xonfig and then restart to run with the generated xorg.conf, I cannot use/login to my system anymore, because after the boot process I dont get a login screen, but a completely black screen with a tiny little white dot in the top left corner. Booting in rescue mode and deleting/moving the xorg.conf and letting the system start without one fixes the issue and gives me a login screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-utils-510 510.60.02-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 02:21:53 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nvidia-graphics-drivers-510 UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1973385/+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 1842320] Re: Out of Memory on boot with 5.2.0 kernel
Thanks @ufoot . It took quite a while to find that issue, but the solution was hidden among many people reporting other solutions and bugs. Remember after the # chroot ./root and before the # update-initramfs -u -k all You have to edit the file # /etc/initramfs-tools/initramfs.conf as noted above. I submitted the bug, but it was marked as duplicate of this anyway. In a discussion elsewhere which didn't seem as related, the issue of speeding boot times was being discussed for Raspberri Pi systems, and the decision seemed to come down to not needing such a high compression ratio. I am unsure if it is limited to MSI hardware, but an unintended consequence of it all was making our MSI systems not boot regardless of not being important to Raspberry Pi systems. Mine is a MSI GS63VR 6RF Stealth Pro with a 4K screen. Related: https://www.phoronix.com/scan.php?page=news_item=Ubuntu-Initramfs-Zstd-Too-High Related: https://lists.ubuntu.com/archives/ubuntu-devel/2021-December/041726.html -- 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/1842320 Title: Out of Memory on boot with 5.2.0 kernel Status in linux package in Ubuntu: Confirmed Bug description: Upgraded from 19.04 to current 19.10 using "do-release-upgrade -d". Can still boot using the previous 5.0.0-25-generic kernel, but the 5.2.0-15-generic fails to start. On selecting Ubuntu from Grub, the message "error: out of memory." is immediately shown. Pressing a key attempts to start boot-up but fails to mount root fs. Machine is HP Spectre X360 with 8GB RAM. Under kernel 5.0.0, free shows the following (run from Gnome terminal): totalusedfree shared buff/cache available Mem:7906564 1761196 3833240 1020216 2312128 4849224 Swap: 1003516 0 1003516 Kernel packages installed: linux-generic 5.2.0.15.16 amd64 linux-headers-5.2.0-15 5.2.0-15.16 all linux-headers-5.2.0-15-generic 5.2.0-15.16 amd64 linux-headers-generic 5.2.0.15.16 amd64 linux-image-5.0.0-25-generic 5.0.0-25.26 amd64 linux-image-5.2.0-15-generic 5.2.0-15.16+signed1 amd64 linux-image-generic5.2.0.15.16 amd64 linux-modules-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-5.2.0-15-generic 5.2.0-15.16 amd64 linux-modules-extra-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-extra-5.2.0-15-generic 5.2.0-15.16 amd64 Photo of kernel panic attached. NVMe drive partition layout (GPT): Device StartEnd Sectors Size Type /dev/nvme0n1p120481050623 1048576 512M EFI System /dev/nvme0n1p2 10506242549759 1499136 732M Linux filesystem /dev/nvme0n1p3 2549760 1000214527 997664768 475.7G Linux filesystem $ sudo pvs PV VGFmt Attr PSizePFree /dev/mapper/nvme0n1p3_crypt ubuntu-vg lvm2 a-- <475.71g0 $ sudo lvs LV VGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root ubuntu-vg -wi-ao 474.75g swap_1 ubuntu-vg -wi-ao 980.00m Partition 3 is LUKS encrypted. Root LV is ext4. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gmckeown 1647 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-15 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd HP Wide Vision FHD Camera Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.181 Tags: eoan Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-02 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/17/2019 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.43
[Kernel-packages] [Bug 1973378] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources Status in linux package in Ubuntu: Confirmed Bug description: Tried to re-enumerate the device doing: # echo 1 > /sys/bus/pci/devices/\:d8\:00.2/remove # echo "1" > /sys/bus/pci/rescan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 13:58 seq crw-rw 1 root audio 116, 33 May 13 13:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Fri May 13 14:04:51 2022 InstallationDate: Installed on 2021-04-01 (407 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Supermicro SYS-6019U-TR4 PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=tty0 console=ttyS0,115200n8 intel_iommu=on iommu=pt maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPU dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd10/30/2020:svnSupermicro:pnSYS-6019U-TR4:pvr0123456789:rvnSupermicro:rnX11DPU:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: SYS-6019U-TR4 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 14:05 seq crw-rw 1 root audio 116, 33 May 13 14:05 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-14 (241 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType:
[Kernel-packages] [Bug 1965241] Re: Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events
** Summary changed: - Include DPC Fixes in Ubuntu 22.04 and 20.04 + Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events -- 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/1965241 Title: Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events Status in dellserver: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: [Impact] Recovery from DownPort Containment events fail and the NVMe endpoint is not accessible in some scenarios. [Fix] These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Upstream kernel patches to be included into Ubuntu 22.04 and into Ubuntu 20.04.5: Already in Jammy as of Ubuntu-5.15.0-1.1 PCI/portdrv: Enable Bandwidth Notification only if port supports it https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=00823dcbdd415c868390feaca16f0265101efab4 PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=ea401499e943c307e6d44af6c2b4e068643e7884 3134689f98 PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() [Test Case] 1. Disable the memory space of NVMe end point device 2. Issue IO to the device 3. Observe dmesg. dmesg shows that EDR event is generated, link is contained and NVMe device is recovered. 2. Observe the dmesg [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/test_dpc_1965241 To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1965241/+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 1973378] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589669/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources Status in linux package in Ubuntu: Confirmed Bug description: Tried to re-enumerate the device doing: # echo 1 > /sys/bus/pci/devices/\:d8\:00.2/remove # echo "1" > /sys/bus/pci/rescan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 13:58 seq crw-rw 1 root audio 116, 33 May 13 13:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Fri May 13 14:04:51 2022 InstallationDate: Installed on 2021-04-01 (407 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Supermicro SYS-6019U-TR4 PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=tty0 console=ttyS0,115200n8 intel_iommu=on iommu=pt maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPU dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd10/30/2020:svnSupermicro:pnSYS-6019U-TR4:pvr0123456789:rvnSupermicro:rnX11DPU:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: SYS-6019U-TR4 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 14:05 seq crw-rw 1 root audio 116, 33 May 13 14:05 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-14 (241 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human
[Kernel-packages] [Bug 1973378] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589665/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources Status in linux package in Ubuntu: Confirmed Bug description: Tried to re-enumerate the device doing: # echo 1 > /sys/bus/pci/devices/\:d8\:00.2/remove # echo "1" > /sys/bus/pci/rescan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 13:58 seq crw-rw 1 root audio 116, 33 May 13 13:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Fri May 13 14:04:51 2022 InstallationDate: Installed on 2021-04-01 (407 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Supermicro SYS-6019U-TR4 PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=tty0 console=ttyS0,115200n8 intel_iommu=on iommu=pt maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPU dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd10/30/2020:svnSupermicro:pnSYS-6019U-TR4:pvr0123456789:rvnSupermicro:rnX11DPU:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: SYS-6019U-TR4 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 14:05 seq crw-rw 1 root audio 116, 33 May 13 14:05 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-14 (241 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1,
[Kernel-packages] [Bug 1973378] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589666/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources Status in linux package in Ubuntu: Confirmed Bug description: Tried to re-enumerate the device doing: # echo 1 > /sys/bus/pci/devices/\:d8\:00.2/remove # echo "1" > /sys/bus/pci/rescan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 13:58 seq crw-rw 1 root audio 116, 33 May 13 13:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Fri May 13 14:04:51 2022 InstallationDate: Installed on 2021-04-01 (407 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Supermicro SYS-6019U-TR4 PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=tty0 console=ttyS0,115200n8 intel_iommu=on iommu=pt maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPU dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd10/30/2020:svnSupermicro:pnSYS-6019U-TR4:pvr0123456789:rvnSupermicro:rnX11DPU:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: SYS-6019U-TR4 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 14:05 seq crw-rw 1 root audio 116, 33 May 13 14:05 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-14 (241 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human
[Kernel-packages] [Bug 1973378] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589667/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources Status in linux package in Ubuntu: Confirmed Bug description: Tried to re-enumerate the device doing: # echo 1 > /sys/bus/pci/devices/\:d8\:00.2/remove # echo "1" > /sys/bus/pci/rescan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 13:58 seq crw-rw 1 root audio 116, 33 May 13 13:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Fri May 13 14:04:51 2022 InstallationDate: Installed on 2021-04-01 (407 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Supermicro SYS-6019U-TR4 PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=tty0 console=ttyS0,115200n8 intel_iommu=on iommu=pt maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPU dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd10/30/2020:svnSupermicro:pnSYS-6019U-TR4:pvr0123456789:rvnSupermicro:rnX11DPU:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: SYS-6019U-TR4 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 14:05 seq crw-rw 1 root audio 116, 33 May 13 14:05 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-14 (241 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface
[Kernel-packages] [Bug 1973378] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589664/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources Status in linux package in Ubuntu: Confirmed Bug description: Tried to re-enumerate the device doing: # echo 1 > /sys/bus/pci/devices/\:d8\:00.2/remove # echo "1" > /sys/bus/pci/rescan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 13:58 seq crw-rw 1 root audio 116, 33 May 13 13:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Fri May 13 14:04:51 2022 InstallationDate: Installed on 2021-04-01 (407 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Supermicro SYS-6019U-TR4 PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=tty0 console=ttyS0,115200n8 intel_iommu=on iommu=pt maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPU dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd10/30/2020:svnSupermicro:pnSYS-6019U-TR4:pvr0123456789:rvnSupermicro:rnX11DPU:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: SYS-6019U-TR4 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 14:05 seq crw-rw 1 root audio 116, 33 May 13 14:05 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-14 (241 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1,
[Kernel-packages] [Bug 1973378] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589668/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources Status in linux package in Ubuntu: Confirmed Bug description: Tried to re-enumerate the device doing: # echo 1 > /sys/bus/pci/devices/\:d8\:00.2/remove # echo "1" > /sys/bus/pci/rescan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 13:58 seq crw-rw 1 root audio 116, 33 May 13 13:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Fri May 13 14:04:51 2022 InstallationDate: Installed on 2021-04-01 (407 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Supermicro SYS-6019U-TR4 PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=tty0 console=ttyS0,115200n8 intel_iommu=on iommu=pt maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPU dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd10/30/2020:svnSupermicro:pnSYS-6019U-TR4:pvr0123456789:rvnSupermicro:rnX11DPU:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: SYS-6019U-TR4 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 14:05 seq crw-rw 1 root audio 116, 33 May 13 14:05 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-14 (241 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human
[Kernel-packages] [Bug 1973378] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589663/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources Status in linux package in Ubuntu: Confirmed Bug description: Tried to re-enumerate the device doing: # echo 1 > /sys/bus/pci/devices/\:d8\:00.2/remove # echo "1" > /sys/bus/pci/rescan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 13:58 seq crw-rw 1 root audio 116, 33 May 13 13:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Fri May 13 14:04:51 2022 InstallationDate: Installed on 2021-04-01 (407 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Supermicro SYS-6019U-TR4 PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=tty0 console=ttyS0,115200n8 intel_iommu=on iommu=pt maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPU dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd10/30/2020:svnSupermicro:pnSYS-6019U-TR4:pvr0123456789:rvnSupermicro:rnX11DPU:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: SYS-6019U-TR4 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 14:05 seq crw-rw 1 root audio 116, 33 May 13 14:05 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-14 (241 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface
[Kernel-packages] [Bug 1971205] Re: CVE-2022-25258 and CVE-2022-25375
** Changed in: linux-riscv (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1971205 Title: CVE-2022-25258 and CVE-2022-25375 Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws-5.13 package in Ubuntu: Fix Released Status in linux-aws-5.4 package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Fix Released Status in linux-azure-5.13 package in Ubuntu: Fix Released Status in linux-azure-5.4 package in Ubuntu: Fix Released Status in linux-bluefield package in Ubuntu: Confirmed Status in linux-dell300x package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp-4.15 package in Ubuntu: Fix Released Status in linux-gcp-5.13 package in Ubuntu: Fix Released Status in linux-gcp-5.4 package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Fix Released Status in linux-gke-5.4 package in Ubuntu: Fix Committed Status in linux-gkeop package in Ubuntu: Fix Released Status in linux-gkeop-5.4 package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Fix Released Status in linux-hwe-5.4 package in Ubuntu: Fix Released Status in linux-ibm package in Ubuntu: Fix Released Status in linux-ibm-5.4 package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: Fix Released Status in linux-oracle package in Ubuntu: Fix Released Status in linux-oracle-5.13 package in Ubuntu: Fix Committed Status in linux-oracle-5.4 package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi-5.4 package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-riscv package in Ubuntu: Fix Released Status in linux-snapdragon package in Ubuntu: Fix Released Bug description: These packages are vulnerable to CVE-2022-25258 and CVE-2022-25375 in at least one Ubuntu release, as stated in the Ubuntu CVE Tracker. Please release fixed packages. Debian released an advisory on March 7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1971205/+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 1973378] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589662/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources Status in linux package in Ubuntu: Confirmed Bug description: Tried to re-enumerate the device doing: # echo 1 > /sys/bus/pci/devices/\:d8\:00.2/remove # echo "1" > /sys/bus/pci/rescan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 13:58 seq crw-rw 1 root audio 116, 33 May 13 13:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Fri May 13 14:04:51 2022 InstallationDate: Installed on 2021-04-01 (407 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Supermicro SYS-6019U-TR4 PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=tty0 console=ttyS0,115200n8 intel_iommu=on iommu=pt maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPU dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd10/30/2020:svnSupermicro:pnSYS-6019U-TR4:pvr0123456789:rvnSupermicro:rnX11DPU:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: SYS-6019U-TR4 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 14:05 seq crw-rw 1 root audio 116, 33 May 13 14:05 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-14 (241 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human
[Kernel-packages] [Bug 1973378] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589661/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources Status in linux package in Ubuntu: Confirmed Bug description: Tried to re-enumerate the device doing: # echo 1 > /sys/bus/pci/devices/\:d8\:00.2/remove # echo "1" > /sys/bus/pci/rescan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 13:58 seq crw-rw 1 root audio 116, 33 May 13 13:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Fri May 13 14:04:51 2022 InstallationDate: Installed on 2021-04-01 (407 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Supermicro SYS-6019U-TR4 PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=tty0 console=ttyS0,115200n8 intel_iommu=on iommu=pt maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPU dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd10/30/2020:svnSupermicro:pnSYS-6019U-TR4:pvr0123456789:rvnSupermicro:rnX11DPU:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: SYS-6019U-TR4 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 14:05 seq crw-rw 1 root audio 116, 33 May 13 14:05 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-14 (241 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface
[Kernel-packages] [Bug 1973378] Re: kernel BUG in pci_assign_unassigned_bus_resources
apport information ** Tags added: apport-collected ** Description changed: Tried to re-enumerate the device doing: # echo 1 > /sys/bus/pci/devices/\:d8\:00.2/remove # echo "1" > /sys/bus/pci/rescan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 13:58 seq crw-rw 1 root audio 116, 33 May 13 13:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Fri May 13 14:04:51 2022 InstallationDate: Installed on 2021-04-01 (407 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Supermicro SYS-6019U-TR4 PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=tty0 console=ttyS0,115200n8 intel_iommu=on iommu=pt maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPU dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd10/30/2020:svnSupermicro:pnSYS-6019U-TR4:pvr0123456789:rvnSupermicro:rnX11DPU:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: SYS-6019U-TR4 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 May 13 14:05 seq + crw-rw 1 root audio 116, 33 May 13 14:05 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.18 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CasperMD5CheckMismatches: ./boot/grub/efi.img + CasperMD5CheckResult: fail + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-09-14 (241 days ago) + InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd + Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M + |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M + |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M + |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M + MachineType: Supermicro SYS-6019U-TR4 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + LC_CTYPE=C.UTF-8 + TERM=xterm-256color + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: 0 astdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic
[Kernel-packages] [Bug 1973378] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589660/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources Status in linux package in Ubuntu: Confirmed Bug description: Tried to re-enumerate the device doing: # echo 1 > /sys/bus/pci/devices/\:d8\:00.2/remove # echo "1" > /sys/bus/pci/rescan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 13:58 seq crw-rw 1 root audio 116, 33 May 13 13:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Fri May 13 14:04:51 2022 InstallationDate: Installed on 2021-04-01 (407 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Supermicro SYS-6019U-TR4 PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=tty0 console=ttyS0,115200n8 intel_iommu=on iommu=pt maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPU dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd10/30/2020:svnSupermicro:pnSYS-6019U-TR4:pvr0123456789:rvnSupermicro:rnX11DPU:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: SYS-6019U-TR4 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 14:05 seq crw-rw 1 root audio 116, 33 May 13 14:05 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-14 (241 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human
[Kernel-packages] [Bug 1973378] [NEW] kernel BUG in pci_assign_unassigned_bus_resources
Public bug reported: Tried to re-enumerate the device doing: # echo 1 > /sys/bus/pci/devices/\:d8\:00.2/remove # echo "1" > /sys/bus/pci/rescan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 13:58 seq crw-rw 1 root audio 116, 33 May 13 13:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Fri May 13 14:04:51 2022 InstallationDate: Installed on 2021-04-01 (407 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Supermicro SYS-6019U-TR4 PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=tty0 console=ttyS0,115200n8 intel_iommu=on iommu=pt maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPU dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd10/30/2020:svnSupermicro:pnSYS-6019U-TR4:pvr0123456789:rvnSupermicro:rnX11DPU:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: SYS-6019U-TR4 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 14:05 seq crw-rw 1 root audio 116, 33 May 13 14:05 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-14 (241 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Supermicro SYS-6019U-TR4 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=tty0 console=ttyS0,115200n8 intel_iommu=on iommu=pt maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A
[Kernel-packages] [Bug 1965241] Re: Include DPC Fixes in Ubuntu 22.04 and 20.04
** Description changed: SRU Justification: [Impact] Recovery from DownPort Containment events fail and the NVMe endpoint is not accessible in some scenarios. [Fix] These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Upstream kernel patches to be included into Ubuntu 22.04 and into Ubuntu 20.04.5: Already in Jammy as of Ubuntu-5.15.0-1.1 PCI/portdrv: Enable Bandwidth Notification only if port supports it https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=00823dcbdd415c868390feaca16f0265101efab4 PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=ea401499e943c307e6d44af6c2b4e068643e7884 3134689f98 PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() [Test Case] 1. Disable the memory space of NVMe end point device 2. Issue IO to the device 3. Observe dmesg. dmesg shows that EDR event is generated, link is contained and NVMe device is recovered. 2. Observe the dmesg [Other Info] - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965241 + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/test_dpc_1965241 -- 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/1965241 Title: Include DPC Fixes in Ubuntu 22.04 and 20.04 Status in dellserver: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: [Impact] Recovery from DownPort Containment events fail and the NVMe endpoint is not accessible in some scenarios. [Fix] These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Upstream kernel patches to be included into Ubuntu 22.04 and into Ubuntu 20.04.5: Already in Jammy as of Ubuntu-5.15.0-1.1 PCI/portdrv: Enable Bandwidth Notification only if port supports it https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=00823dcbdd415c868390feaca16f0265101efab4 PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=ea401499e943c307e6d44af6c2b4e068643e7884 3134689f98 PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() [Test Case] 1. Disable the memory space of NVMe end point device 2. Issue IO to the device 3. Observe dmesg. dmesg shows that EDR event is generated, link is contained and NVMe device is recovered. 2. Observe the dmesg [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/test_dpc_1965241 To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1965241/+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 1842320] Re: Out of Memory on boot with 5.2.0 kernel
I tried the fix with GFXMODE=800x600 -> it did nothing. I had bigger letters but the same error. I tried the fix with editing mkinitramfs and replacing 1 by 19 on line 196 to restore the high compression level. Then regenerated the image -> it worked. For readers, this is not so easy, because when you get there your system is stuck. What I did is download an Ubuntu image 21.10. From there, boot on the USB stick. Open a terminal, and: 8<--- $ sudo su - # mkdir root # mkdir boot # mkdir efi # cryptsetup luksOpen /dev/nvme0n1p3 nvme0n1p3_crypt # mount /dev/mapper/vgubuntu-root ./root # mount /dev/nvme01p1 ./efi # mount /dev/nvme01p2 ./boot # mount -B ./boot ./root/boot # mount -B ./efi ./root/boot/efi # mount -B ./dev ./root/boot/dev # mount -B ./dev/pts ./root/boot/dev/pts # mount -B ./proc ./root/proc # mount -B ./sys ./root/sys # chroot ./root # update-initramfs -u -k all # update-grub # exit # reboot 8<--- ^ in the above examples, the logical volume names and crypt devices need to be adapted to your setup, obviously. I do not know what is the gain of switching that compression level from 19 to 1, but the side effect (not being able to boot at all...) is quite annoying. Thanks very much @ybdjkfd for the fix, that saved my day (if not my week & month). -- 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/1842320 Title: Out of Memory on boot with 5.2.0 kernel Status in linux package in Ubuntu: Confirmed Bug description: Upgraded from 19.04 to current 19.10 using "do-release-upgrade -d". Can still boot using the previous 5.0.0-25-generic kernel, but the 5.2.0-15-generic fails to start. On selecting Ubuntu from Grub, the message "error: out of memory." is immediately shown. Pressing a key attempts to start boot-up but fails to mount root fs. Machine is HP Spectre X360 with 8GB RAM. Under kernel 5.0.0, free shows the following (run from Gnome terminal): totalusedfree shared buff/cache available Mem:7906564 1761196 3833240 1020216 2312128 4849224 Swap: 1003516 0 1003516 Kernel packages installed: linux-generic 5.2.0.15.16 amd64 linux-headers-5.2.0-15 5.2.0-15.16 all linux-headers-5.2.0-15-generic 5.2.0-15.16 amd64 linux-headers-generic 5.2.0.15.16 amd64 linux-image-5.0.0-25-generic 5.0.0-25.26 amd64 linux-image-5.2.0-15-generic 5.2.0-15.16+signed1 amd64 linux-image-generic5.2.0.15.16 amd64 linux-modules-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-5.2.0-15-generic 5.2.0-15.16 amd64 linux-modules-extra-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-extra-5.2.0-15-generic 5.2.0-15.16 amd64 Photo of kernel panic attached. NVMe drive partition layout (GPT): Device StartEnd Sectors Size Type /dev/nvme0n1p120481050623 1048576 512M EFI System /dev/nvme0n1p2 10506242549759 1499136 732M Linux filesystem /dev/nvme0n1p3 2549760 1000214527 997664768 475.7G Linux filesystem $ sudo pvs PV VGFmt Attr PSizePFree /dev/mapper/nvme0n1p3_crypt ubuntu-vg lvm2 a-- <475.71g0 $ sudo lvs LV VGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root ubuntu-vg -wi-ao 474.75g swap_1 ubuntu-vg -wi-ao 980.00m Partition 3 is LUKS encrypted. Root LV is ext4. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gmckeown 1647 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-15 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd HP Wide Vision FHD Camera Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.181 Tags: eoan Uname: Linux
[Kernel-packages] [Bug 1971205] Re: CVE-2022-25258 and CVE-2022-25375
** Changed in: linux-gkeop-5.4 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-hwe-5.13 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-hwe-5.4 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-ibm (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-ibm-5.4 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-kvm (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-oracle (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-oracle-5.13 (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: linux-oracle-5.4 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-raspi (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-raspi-5.4 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-raspi2 (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: linux-riscv (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: linux-snapdragon (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1971205 Title: CVE-2022-25258 and CVE-2022-25375 Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws-5.13 package in Ubuntu: Fix Released Status in linux-aws-5.4 package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Fix Released Status in linux-azure-5.13 package in Ubuntu: Fix Released Status in linux-azure-5.4 package in Ubuntu: Fix Released Status in linux-bluefield package in Ubuntu: Confirmed Status in linux-dell300x package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp-4.15 package in Ubuntu: Fix Released Status in linux-gcp-5.13 package in Ubuntu: Fix Released Status in linux-gcp-5.4 package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Fix Released Status in linux-gke-5.4 package in Ubuntu: Fix Committed Status in linux-gkeop package in Ubuntu: Fix Released Status in linux-gkeop-5.4 package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Fix Released Status in linux-hwe-5.4 package in Ubuntu: Fix Released Status in linux-ibm package in Ubuntu: Fix Released Status in linux-ibm-5.4 package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: Fix Released Status in linux-oracle package in Ubuntu: Fix Released Status in linux-oracle-5.13 package in Ubuntu: Fix Committed Status in linux-oracle-5.4 package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi-5.4 package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-riscv package in Ubuntu: Fix Committed Status in linux-snapdragon package in Ubuntu: Fix Released Bug description: These packages are vulnerable to CVE-2022-25258 and CVE-2022-25375 in at least one Ubuntu release, as stated in the Ubuntu CVE Tracker. Please release fixed packages. Debian released an advisory on March 7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1971205/+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 1965241] Re: Include DPC Fixes in Ubuntu 22.04 and 20.04
** Description changed: SRU Justification: [Impact] Recovery from DownPort Containment events fail and the NVMe endpoint is not accessible in some scenarios. [Fix] These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Upstream kernel patches to be included into Ubuntu 22.04 and into Ubuntu 20.04.5: Already in Jammy as of Ubuntu-5.15.0-1.1 PCI/portdrv: Enable Bandwidth Notification only if port supports it https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=00823dcbdd415c868390feaca16f0265101efab4 - PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=ea401499e943c307e6d44af6c2b4e068643e7884 3134689f98 PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() [Test Case] 1. Disable the memory space of NVMe end point device 2. Issue IO to the device 3. Observe dmesg. dmesg shows that EDR event is generated, link is contained and NVMe device is recovered. 2. Observe the dmesg + [Other Info] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965241 -- 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/1965241 Title: Include DPC Fixes in Ubuntu 22.04 and 20.04 Status in dellserver: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: [Impact] Recovery from DownPort Containment events fail and the NVMe endpoint is not accessible in some scenarios. [Fix] These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Upstream kernel patches to be included into Ubuntu 22.04 and into Ubuntu 20.04.5: Already in Jammy as of Ubuntu-5.15.0-1.1 PCI/portdrv: Enable Bandwidth Notification only if port supports it https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=00823dcbdd415c868390feaca16f0265101efab4 PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=ea401499e943c307e6d44af6c2b4e068643e7884 3134689f98 PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() [Test Case] 1. Disable the memory space of NVMe end point device 2. Issue IO to the device 3. Observe dmesg. dmesg shows that EDR event is generated, link is contained and NVMe device is recovered. 2. Observe the dmesg [Other Info] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965241 To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1965241/+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 1970819] Re: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
I confirmed today that r1000 in beta fixes this. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970819 Title: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi Status in linux package in Ubuntu: Fix Committed Status in snapd package in Ubuntu: New Bug description: When testing the beta image for uc22 on an Intel NUC, I noticed that bluetooth was not working. This NUC has worked for bluetooth tests on uc18, 20, and even on jammy. However on uc22, we see this in dmesg: [ 11.954649] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 11.962817] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-17-16-1.sfi (-2) [ 11.966951] Bluetooth: hci0: Failed to read MSFT supported features (-56) Here's the full dmesg with grep -i blue: https://pastebin.canonical.com/p/99KvzHY4n9/ On Jammy, for comparison, the firmware gets loaded and bluetoothctl can see nearby devices: [5.650860] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.653214] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi [7.059104] Bluetooth: hci0: Waiting for firmware download to complete [7.059838] Bluetooth: hci0: Firmware loaded in 1373648 usecs [7.059903] Bluetooth: hci0: Waiting for device to boot [7.073886] Bluetooth: hci0: Device booted in 13691 usecs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970819/+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 1970965] Re: Wifi randomly disconnects [AR9462]
a) could somebody point me to some page with the information on how to install and build the official Ubuntu Kernel ? (address of the repository and instructions to build/install it) I plan to bisect from 5.15.4 to 5.15.5 to try to catch what is causing the problem It was suggested to do that with the mainstream kernel (from kernel.org) https://bugzilla.kernel.org/show_bug.cgi?id=215918#c40 but I prefer to start with the kernels from kernel.ubuntu.com , that is what I'm using b)In parallel, while testing each kernel, I wish to profit and collect more information related to the wi-fi, which are the logs related to wi-fi modules/driver/function that I can produce ? (because the output obtained from dmesg didn't provide too much help in this case, or I don't know how to interpret it correctly...) -- 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/1970965 Title: Wifi randomly disconnects [AR9462] Status in linux package in Ubuntu: Confirmed Bug description: my hardware : laptop Asus N751JK Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01) Subsystem: AzureWave AR9462 Wireless Network Adapter I was runing Ubuntu 20.10, 21.04 up to Ubuntu 21.10 with Kernel 5.13.0 without any problem. When migrated to Ubuntu 22.04 which installs Kernel 5.15.5 then the problems started. I upgraded and tested unsuccessfully the following Kernels : 5.15.28, 5.15.36, 5.16.14, 5.16.20, 5.17.4, 5.17.5 I disabled the power save as explained at https://askubuntu.com/questions/1403773/22-04-wifi-keeps-disconnecting-for-a-few-seconds-frequently/1404471#1404471 without improvement in any of the Kernels tested. Also the "intel_iommu=off" mentioned at https://groups.google.com/g/linux.debian.kernel/c/RFpPIp0cncA/m/v9ELDxLICgAJ Bug#994590 didn't help. I downgraded and currently running without any problem using the Kernels 5.13.19-051319-generic or 5.15.0 or 5.15.4 There is no problem in my airpoint (router) nor my internet access, I have other different computers and devices working correctly on wifi. In addition my N751JK works correctly when using the Ethernet adapter for the physical cable. seems to be something between 5.15.4 and 5.15.5 that is also propagated to 5.16.x and 5.17.x (started at https://bugzilla.kernel.org/show_bug.cgi?id=215918) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-02-21 (432 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: jammy Uname: Linux 5.15.5-051505-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970965/+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 1970965] Re: Wifi randomly disconnects [AR9462]
I installed the official 5.15.0-32 (via >apt install linux-generic) released in these days and it also contains the problem Linux ubuntu 5.15.0-32-generic #33-Ubuntu SMP Tue May 10 08:40:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux -- 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/1970965 Title: Wifi randomly disconnects [AR9462] Status in linux package in Ubuntu: Confirmed Bug description: my hardware : laptop Asus N751JK Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01) Subsystem: AzureWave AR9462 Wireless Network Adapter I was runing Ubuntu 20.10, 21.04 up to Ubuntu 21.10 with Kernel 5.13.0 without any problem. When migrated to Ubuntu 22.04 which installs Kernel 5.15.5 then the problems started. I upgraded and tested unsuccessfully the following Kernels : 5.15.28, 5.15.36, 5.16.14, 5.16.20, 5.17.4, 5.17.5 I disabled the power save as explained at https://askubuntu.com/questions/1403773/22-04-wifi-keeps-disconnecting-for-a-few-seconds-frequently/1404471#1404471 without improvement in any of the Kernels tested. Also the "intel_iommu=off" mentioned at https://groups.google.com/g/linux.debian.kernel/c/RFpPIp0cncA/m/v9ELDxLICgAJ Bug#994590 didn't help. I downgraded and currently running without any problem using the Kernels 5.13.19-051319-generic or 5.15.0 or 5.15.4 There is no problem in my airpoint (router) nor my internet access, I have other different computers and devices working correctly on wifi. In addition my N751JK works correctly when using the Ethernet adapter for the physical cable. seems to be something between 5.15.4 and 5.15.5 that is also propagated to 5.16.x and 5.17.x (started at https://bugzilla.kernel.org/show_bug.cgi?id=215918) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-02-21 (432 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: jammy Uname: Linux 5.15.5-051505-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970965/+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 1971712] Re: Add support for Intel DG2
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1842320] Re: Out of Memory on boot with 5.2.0 kernel
@guiverc this is not related to Ubuntu 19.10 or 19.04. It was initially reported at that time, but it is still open. I just stumbled on it, ugrading from 21 to 22.04. Same behavior: "error: out of memory. Press any key to continue..." Then kernel panic message. I created a bootable USB image -> same problem. Now downloading a 21 image, and see if I can boot and try and tweak grub configuration. But the problem, despite old, is still happening on the latest version of Ubuntu. And it is pretty bad, your computer is *really* unuable once you're hit. My hardware is a MSI Prestige 15 A10SC, has a 4k screen, which some users also have apparently. -- 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/1842320 Title: Out of Memory on boot with 5.2.0 kernel Status in linux package in Ubuntu: Confirmed Bug description: Upgraded from 19.04 to current 19.10 using "do-release-upgrade -d". Can still boot using the previous 5.0.0-25-generic kernel, but the 5.2.0-15-generic fails to start. On selecting Ubuntu from Grub, the message "error: out of memory." is immediately shown. Pressing a key attempts to start boot-up but fails to mount root fs. Machine is HP Spectre X360 with 8GB RAM. Under kernel 5.0.0, free shows the following (run from Gnome terminal): totalusedfree shared buff/cache available Mem:7906564 1761196 3833240 1020216 2312128 4849224 Swap: 1003516 0 1003516 Kernel packages installed: linux-generic 5.2.0.15.16 amd64 linux-headers-5.2.0-15 5.2.0-15.16 all linux-headers-5.2.0-15-generic 5.2.0-15.16 amd64 linux-headers-generic 5.2.0.15.16 amd64 linux-image-5.0.0-25-generic 5.0.0-25.26 amd64 linux-image-5.2.0-15-generic 5.2.0-15.16+signed1 amd64 linux-image-generic5.2.0.15.16 amd64 linux-modules-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-5.2.0-15-generic 5.2.0-15.16 amd64 linux-modules-extra-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-extra-5.2.0-15-generic 5.2.0-15.16 amd64 Photo of kernel panic attached. NVMe drive partition layout (GPT): Device StartEnd Sectors Size Type /dev/nvme0n1p120481050623 1048576 512M EFI System /dev/nvme0n1p2 10506242549759 1499136 732M Linux filesystem /dev/nvme0n1p3 2549760 1000214527 997664768 475.7G Linux filesystem $ sudo pvs PV VGFmt Attr PSizePFree /dev/mapper/nvme0n1p3_crypt ubuntu-vg lvm2 a-- <475.71g0 $ sudo lvs LV VGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root ubuntu-vg -wi-ao 474.75g swap_1 ubuntu-vg -wi-ao 980.00m Partition 3 is LUKS encrypted. Root LV is ext4. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gmckeown 1647 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-15 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd HP Wide Vision FHD Camera Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.181 Tags: eoan Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-02 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/17/2019 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.25:bd05/17/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.product.sku:
[Kernel-packages] [Bug 1973104] Re: e1000e report hardware hang
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1973104 Title: e1000e report hardware hang Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] e1000e hardware unit hang after s2idle May 06 15:34:49 ubuntu kernel: e1000e :00:1f.6 enp0s31f6: Detected Hardware Unit Hang: TDH <1> TDT <5> next_to_use <5> next_to_clean <1> buffer_info[next_to_clean]: time_stamp <1000587f0> next_to_watch <1> jiffies <1000589c0> next_to_watch.status <0> MAC Status <40080283> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status <3000> PCI Status <10> [Fix] Below commit fixes this issue https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20220508070905.1878172-1-sasha.nef...@intel.com/ [Test] Verified on the target machine, and confirmed the issue is gone. [Where problems could occur] The impact is low, it keeps the GPT clock enabled for CSME when e1000e_pm_resume() is called. I can't see this may introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1973104/+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 1967988] Re: Support different Cirrus audio codec configurations on Dell laptops
** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1967988 Title: Support different Cirrus audio codec configurations on Dell laptops Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] On Dell's platform, Warlock/Bullseye Laptops have a mono DMIC, Cyborg and some Warlock variants uses a stereo DMIC. They are not correctly mapped to the corresponding configurations so the microphone function are not working as expected. [Fix] Cirrus upstream new FIXUPs to support different microphone configurations on different Dell laptop variants. [Test Case] 1. Go to Audio Settings 2. Make sure the microphone is correctly detected and responds to audio input. 3. Issue command "arecord record_file" and check the record_file is consistent with audio input. [Where problems could occur] Risk should be Low. The patches come from Cirrus and the configurations are mapped based on the audio codec's SSIDs for different Dell variants. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967988/+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 1968861] Re: Support Cirrus audio codec configurations for Odin platform
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1968861 Title: Support Cirrus audio codec configurations for Odin platform Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] CS8409 needs new configuration for Odin platform [Fix] Cirrus provides us 2 patches to add the support which are not in upstream yet ALSA: hda/cs8409: Add Speaker Playback Switch for Cyborg ALSA: hda/cs8409: Support new Odin Variants Below series of patch is required to be applied before these 2. https://lists.ubuntu.com/archives/kernel-team/2022-April/129223.html [Test] Verified on the target machine [Where problems could occur] The first commit only affects the new added Odin platform, and the second one do some modification for other platforms which is hard to know what may lead to. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1968861/+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 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
I just updated my Ubuntu to 22.04 and I'm having the same issue. Hopefully it'll get fixed ASAP. -- 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/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+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 1972747] Re: Speakup modules missing from kernel after upgrad to Ubuntu Jammy/22.04
** This bug is no longer a duplicate of bug 1967702 Enable speakup kernel modules to allow the speakup screen reader to function -- 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/1972747 Title: Speakup modules missing from kernel after upgrad to Ubuntu Jammy/22.04 Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Jammy/22.04, the kernel modules for the speakup screen reader are not available . # modprobe speakup_ltlk modprobe: FATAL: Module speakup_ltlk not found in directory /lib/modules/5.15.0-27-generic Note: This bug is similar to those originally in 21.04 and 21.10. It seems that with each new release, the speakup kernel modules are left out. see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942459 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1997 F pulseaudio /dev/snd/pcmC0D0p: john 1997 F...m pulseaudio /dev/snd/controlC1: john 1997 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon May 9 20:31:45 2022 InstallationDate: Installed on 2021-08-25 (257 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=de5924a4-e0f6-4c11-a364-ea107efc1086 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-10 (0 days ago) dmi.bios.date: 12/13/2018 dmi.bios.release: 65.29 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd12/13/2018:br65.29:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA02:cvnDellInc.:ct7:cvr:sku0617: dmi.product.name: Precision Tower 5810 dmi.product.sku: 0617 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972747/+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 1972802] Re: enable config for fixing 5.17 kernel won't load mok
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1972802 Title: enable config for fixing 5.17 kernel won't load mok Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Mok keys is not trusted after kernel 5.17 [Fix] Enable the CONFIG_IMA_SECURE_AND_OR_TRUSTED_BOOT and CONFIG_IMA_ARCH_POLICY for fixing the patch "[patch] integrity: Do not load MOK and MOKx when secure boot be disabled" was added to check if secureboot enabled for trusting the MOK key [Test] Enroll Mok key and use it to sign kernel modules, make sure secure boot is on and load the kernel module by either modprobe or insmod. [Where problems could occur] Low. only affect the checking secureboot enable function. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1972802/+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 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: In Progress => Invalid
** Changed in: linux-oem-5.14 (Ubuntu Bionic)
Status: New => Invalid
** Changed in: linux-oem-5.14 (Ubuntu Impish)
Status: New => Invalid
** Changed in: linux-oem-5.17 (Ubuntu Impish)
Status: New => Invalid
** Changed in: linux-oem-5.17 (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux-oem-5.17 (Ubuntu Bionic)
Status: New => Invalid
** Changed in: linux-oem-5.17 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-5.14 (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux-oem-5.14 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-5.14 (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.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1937295
Title:
[SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping
is enabled by IOMMU
Status in HWE Next:
New
Status in subiquity:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Invalid
Status in linux-oem-5.14 source package in Bionic:
Invalid
Status in linux-oem-5.17 source package in Bionic:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in linux source package in Impish:
Fix Released
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux-oem-5.17 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-oem-5.14 source package in Jammy:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Invalid
Bug description:
[Impact]
A hardware partner discovered they were unable to install Ubuntu on
some servers using VROC setups. They point to this issue involving
DMAR that is blocking discovery of the VROC RAID devices:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2565e5b69c44b4e42469afea3cc5a97e74d1ed45
`git bisect` points to this offending commit ee81ee84f873 ("PCI:
vmd: Disable MSI-X remapping when possible"), which disables VMD MSI
remapping. The IOMMU hardware blocks the compatibility format
interrupt request because Interrupt Remapping Enable Status (IRES) and
Extended Interrupt Mode Enable (EIME) are enabled. Please refer to
section "5.1.4 Interrupt-Remapping Hardware Operation" in Intel VT-d
spec.
To fix the issue, VMD driver still enables the interrupt remapping
irrespective of VMD_FEAT_CAN_BYPASS_MSI_REMAP if the IOMMU subsystem
enables the interrupt remapping.
[Fix]
2565e5b69c44 PCI: vmd: Do not disable MSI-X remapping if interrupt
remapping is enabled by IOMMU
[Test Plan]
1. Boot into VRoC controller in uEFI Setup and create a raid10 disk.
2. Install affected Ubuntu release on the RAID10.
3. The system hangs at "Partitions formatting 33%".
[Where problems could occur]
The fix itself is a very small change to drivers/pci/controller/vmd.c
and problems should not occur. The root cause was discovered by the
hardware partner's engineers, who tested and submitted it upstream
where it was accepted and landed in 5.16.
That said, I doubt this will fix 18.04.6 as it would require a respin
to get the patched kernel onto the ISO. 20.04 should pick it up in
ISO in 20.04.5, so there could still be the initial issue since those
ISOs would be lacking the patched kernel.
[Other Info]
As noted, this would need to not only land in the kernel but land in
the kernel in the ISO to resolve the issue in the installation
process. I'll bring this back as far as Focal with the expectation
that while 20.04.4 is too late, it will be present using the GA kernel
in 20.04.5 later on.
*
Original Bug Summary:
A hardware partner has been testing 18.04 subiquity images on their
servers with VROC enabled and configured in a RAID 10 setup.
In their own words:
Steps to reproduce:
1. Boot into VRoC controller in uEFI Setup and create a raid10
disk.
2. Install Ubuntu 18.04.5 on the RAID10.
3. The system hangs at "Partitions formatting 33%".
After looking at the launchpad
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/), the
fix was included in the updated kernel.
[Quotes from the launchpad]
The released kernels are:
Hirsute: 5.11.0-22-generic
Groovy: 5.8.0-59-generic
Focal: 5.4.0-77-generic
Bionic: 4.15.0-147-generic
I've asked them to also confirm
[Kernel-packages] [Bug 1972815] Re: Headset mic with Cirrus logic codec doesn't work
** Changed in: linux-oem-5.14 (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.14 in Ubuntu. https://bugs.launchpad.net/bugs/1972815 Title: Headset mic with Cirrus logic codec doesn't work Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] Headset mic doesn't be selected automatically after headset is plugged in. [Fix] Cirrus provides a fix for this issue https://patchwork.kernel.org/project/alsa-devel/cover/20220504161236.2490532-1-sbind...@opensource.cirrus.com/ [Test] Verified on the target platform, and confirmed these patches work. [Where problems could occur] These affect the mic detection on CS8409_BULLSEYE, CS8409_WARLOCK, CS8409_WARLOCK_MLK, CS8409_WARLOCK_MLK_DUAL_MIC, CS8409_CYBORG, and CS8409_ODIN platforms. Hard to tell if it introduce any regression, will keep an eye on it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1972815/+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 1970468] Re: linux-azure: Patch Set for ARM64 Images 20.04 and 18.04
This bug is awaiting verification that the linux-azure/5.13.0-1024.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1970468 Title: linux-azure: Patch Set for ARM64 Images 20.04 and 18.04 Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Microsoft has asked to have the following patches included in impish/linux-azure and focal/linux-azure: commit eaa03d34535872d29004cb5cf77dc9dec1ba9a25 Drivers: hv: vmbus: Replace smp_store_mb() with virt_store_mb() commit b3d6dd09ff00fdcf4f7c0cb54700ffd5dd343502 Drivers: hv: balloon: Support status report for larger page sizes commit be5802795cf8d0b881745fa9ba7790293b382280 Drivers: hv: balloon: Disable balloon and hot-add accordingly [Test Case] Microsoft tested [Where things could go wrong] Hyper-v ballooning could fail. [Other Info] SF: #00333989 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1970468/+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 1972662] Re: [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time
This bug is awaiting verification that the linux-azure/5.13.0-1024.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1972662 Title: [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] A VM on Azure can have 14 GPUs, and each GPU may have a huge MMIO BAR, e.g. 128 GB. Currently the boot time of such a VM can be 4+ minutes, and most of the time is used by the host to unmap/map the vBAR from/to pBAR when the VM clears and sets the PCI_COMMAND_MEMORY bit: each unmap/map operation for a 128GB BAR needs about 1.8 seconds, and the pci-hyperv driver and the Linux PCI subsystem flip the PCI_COMMAND_MEMORY bit eight times (see pci_setup_device() -> pci_read_bases() and pci_std_update_resource()), increasing the boot time by 1.8 * 8 = 14.4 seconds per GPU, i.e. 14.4 * 14 = 201.6 seconds in total. Fix the slowness by not turning on the PCI_COMMAND_MEMORY in pci-hyperv.c, so the bit stays in the off state before the PCI device driver calls pci_enable_device(): when the bit is off, pci_read_bases() and pci_std_update_resource() don't cause Hyper-V to unmap/map the vBARs. With this change, the boot time of such a VM is reduced by 1.8 * (8-1) * 14 = 176.4 seconds. [Test Case] Microsoft tested [Where things could go wrong] PCI BAR setup could fail or be incorrect. [Other Info] SF: #00336342 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1972662/+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 1972832] Re: [Azure] hv_netvsc: Add support for XDP_REDIRECT
This bug is awaiting verification that the linux-azure/5.13.0-1024.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1972832 Title: [Azure] hv_netvsc: Add support for XDP_REDIRECT Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Add support for XDP_REDIRECT to the Azure Hyperv network driver. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=1cb9d3b6185b2a4d1d592632a7faf5d8c8e5f9b3 [Where things could go wrong] User space requests to set XDP_REDIRECT could break packet routing. [Other Info] SF: #00336466 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1972832/+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 1966089] Re: Update OS policy capability handshake
** Changed in: linux-oem-5.17 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966089 Title: Update OS policy capability handshake Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: == SRU JAMMY == Update int340x OS policy capability handshake; required for full functionality in thermald 2.4.9 to improve functionality for newer H/W. == The fix == Upstream commit: commit c7ff29763989bd09c433f73fae3c1e1c15d9cda4 Author: Srinivas Pandruvada Date: Mon Mar 14 15:09:37 2022 -0700 thermal: int340x: Update OS policy capability handshake Update the firmware with OS supported policies mask, so that firmware can relinquish its internal controls. Without this update several Tiger Lake laptops gets performance limited with in few seconds of executing in turbo region. The existing way of enumerating firmware policies via IDSP method and selecting policy by directly writing those policy UUIDS via _OSC method is not supported in newer generation of hardware. There is a new UUID "B23BA85D-C8B7-3542-88DE-8DE2FFCFD698" is defined for updating policy capabilities. As part of ACPI _OSC method: Arg0 - UUID: B23BA85D-C8B7-3542-88DE-8DE2FFCFD698 Arg1 - Rev ID: 1 Arg2 - Count: 2 Arg3 - Capability buffers: Array of Arg2 DWORDS DWORD1: As defined in the ACPI 5.0 Specification - Bit 0: Query Flag - Bits 1-3: Always 0 - Bits 4-31: Reserved DWORD2 and beyond: - Bit0: set to 1 to indicate Intel(R) Dynamic Tuning is active, 0 to indicate it is disabled and legacy thermal mechanism should be enabled. - Bit1: set to 1 to indicate Intel(R) Dynamic Tuning is controlling active cooling, 0 to indicate bios shall enable legacy thermal zone with active trip point. - Bit2: set to 1 to indicate Intel(R) Dynamic Tuning is controlling passive cooling, 0 to indicate bios shall enable legacy thermal zone with passive trip point. - Bit3: set to 1 to indicate Intel(R) Dynamic Tuning is handling critical trip point, 0 to indicate bios shall enable legacy thermal zone with critical trip point. - Bits 4:31: Reserved From sysfs interface, there is an existing interface to update policy UUID using attribute "current_uuid". User space can write the same UUID for ACTIVE, PASSIVE and CRITICAL policy. Driver converts these UUIDs to DWORD2 Bit 1 to Bit 3. When any of the policy is activated by user space it is assumed that dynamic tuning is active. For example $cd /sys/bus/platform/devices/INTC1040:00/uuids To support active policy $echo "3A95C389-E4B8-4629-A526-C52C88626BAE" > current_uuid To support passive policy $echo "42A441D6-AE6A-462b-A84B-4A8CE79027D3" > current_uuid To support critical policy $echo "97C68AE7-15FA-499c-B8C9-5DA81D606E0A" > current_uuid To check all the supported policies $cat current_uuid 3A95C389-E4B8-4629-A526-C52C88626BAE 42A441D6-AE6A-462b-A84B-4A8CE79027D3 97C68AE7-15FA-499c-B8C9-5DA81D606E0A To match the bit format for DWORD2, rearranged enum int3400_thermal_uuid and int3400_thermal_uuids[] by swapping current INT3400_THERMAL_ACTIVE and INT3400_THERMAL_PASSIVE_1. If the policies are enumerated via IDSP method then legacy method is used, if not the new method is used to update policy support. Signed-off-by: Srinivas Pandruvada Signed-off-by: Rafael J. Wysocki To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966089/+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 1970426] Re: [i915] screen is flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
*** This bug is a duplicate of bug 1958191 *** https://bugs.launchpad.net/bugs/1958191 > Is there any reliable solution to this bug ? It looks like the following is working for everyone so far: 1. Edit /etc/default/grub to add append i915.enable_dc=0 intel_idle.max_cstate=2 to the contents of GRUB_CMDLINE_LINUX_DEFAULT (so, unless you've edited it before, the line looks like GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0 intel_idle.max_cstate=2") 2. sudo update-grub 3. reboot I've been flicker-free ever since I've done that, while the flickering was relatively frequent before that. Alternatively, running a 5.13 kernel should work too. -- 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/1970426 Title: [i915] screen is flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: After I updated to 22.04 sometimes (about 3 ~ 4 times a day) the screen starts glitching and flickering like in the attached video and it doesn't stop until I move the cursor. Description: Ubuntu 22.04 LTS Release: 22.04 wayland processor: Intel® Core™ i5-8265U CPU @ 1.60GHz × 8 graphics: Mesa Intel® UHD Graphics 620 (WHL GT2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970426/+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 1971010] Re: [vmwgfx] Desktop is clipped to a rectangle and mouse doesn't work in VirtualBox when paravirtualization is enabled
Unfortunately nothing has changed. So, the bug is actual. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971010 Title: [vmwgfx] Desktop is clipped to a rectangle and mouse doesn't work in VirtualBox when paravirtualization is enabled Status in linux package in Ubuntu: Confirmed Bug description: Screen and mouse doesn't work ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 30 09:35:20 2022 DistUpgraded: 2022-04-29 07:32:33,356 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2021-11-09 (171 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=fdb10ec1-b027-47b9-bcc7-9dc7ae1897d8 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-29 (1 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971010/+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 1971712] Re: Add support for Intel DG2
SRU V3: https://lists.ubuntu.com/archives/kernel- team/2022-May/130313.html (linux-oem-5.17) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in linux-oem-5.17 source package in Jammy: New Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1910928] Re: Intel Killer AX1650i [8086:34f0] Subsystem [8086:0074] Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL
I actually have different Wi-Fi card and Bluetooth but same laptop, the problem is same with mine. The Bluetooth device drops after sleep and never comes back until I restart the system. Here is the device that has been lost after sleep: Bus 003 Device 006: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Ubuntu 22.04 Linux azis-Lenovo-ThinkBook-14-IIL 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux -- 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/1910928 Title: Intel Killer AX1650i [8086:34f0] Subsystem [8086:0074] Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL Status in linux package in Ubuntu: Confirmed Bug description: After I have installed the Ubuntu - I have noticed, that Bluetooth won't go turn on after Suspend. The only way to get it working - reboot the system. WiFi Adapter - AX201 I have tried the latest kernel (5.11.rc2) - no luck. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InterestingModules: rfcomm bnep btusb bluetooth LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20SL NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: bluez 5.55-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-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: 11/18/2020 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN22WW dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 14-IIL dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL: dmi.product.family: Thinkbook 14-IIL dmi.product.name: 20SL dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL dmi.product.version: Lenovo ThinkBook 14-IIL dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:26:49:C4:B9:6C ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:19913 acl:0 sco:0 events:3169 errors:0 TX bytes:770617 acl:0 sco:0 commands:3167 errors:0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InterestingModules: rfcomm bnep btusb bluetooth LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20SL NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: bluez 5.55-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-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: 11/18/2020 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN22WW dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 14-IIL dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL: dmi.product.family: Thinkbook 14-IIL dmi.product.name: 20SL dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL dmi.product.version: Lenovo ThinkBook 14-IIL dmi.sys.vendor: LENOVO hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910928/+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 1931715] Re: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices"
Sorry that it is taking so long to fix this. There have been several attempts at fixing this upstream already, but all of them had to be reverted/dropped because they were causing issues on other laptop models. The latest attempt at fixing this is here: https://lore.kernel.org/linux-pci/20220512202511.34197-2-hdego...@redhat.com/ And this patch, or something close to it will hopefully go upstream soon. Perhaps one of the Ubuntu kernel devs can provide a test kernel with this patch for Ubuntu users with this problem to test? -- 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/1931715 Title: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices" Status in linux package in Ubuntu: Confirmed Bug description: Laptop model: Lenovo Ideapad S145 82DJ0001BR Manufacturer of the Touchpad: Elan, Synaptics When the symptom first appeared: At the time I installed Ubuntu on my notebook (dual-boot) - it works fine on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 11:58:39 2021 InstallationDate: Installed on 2021-06-09 (1 days ago) InstallationMedia: Ubuntu 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/+bug/1931715/+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 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
Sorry that it is taking so long to fix this. There have been several attempts at fixing this upstream already, but all of them had to be reverted/dropped because they were causing issues on other laptop models. The latest attempt at fixing this is here: https://lore.kernel.org/linux-pci/20220512202511.34197-2-hdego...@redhat.com/ And this patch, or something close to it will hopefully go upstream soon. Perhaps one of the Ubuntu kernel devs can provide a test kernel with this patch for Ubuntu users with this problem to test? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+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 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)
Sorry that it is taking so long to fix this. There have been several attempts at fixing this upstream already, but all of them had to be reverted/dropped because they were causing issues on other laptop models. The latest attempt at fixing this is here: https://lore.kernel.org/linux-pci/20220512202511.34197-2-hdego...@redhat.com/ And this patch, or something close to it will hopefully go upstream soon. Perhaps one of the Ubuntu kernel devs can provide a test kernel with this patch for Ubuntu users with this problem to test? -- 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/1884232 Title: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad is not working at all on ACER Spin 5 SP513-54N. According to https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29 I am creating this kernel bug issue. There are more issues, too, like touchscreen not working and Ubuntu not installable - see here if interrested https://askubuntu.com/questions/1251719/ I would like to run Ubuntu on this machine and I am willing to help with any debug or kernel tweaking... Please let me know. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4195 F pulseaudio CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 10:44:58 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Spin SP513-54N ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.00 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.00 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.00 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.00 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+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 1921649] Re: 'Ideapad S145 Touchpad' not working at all. Not even detected after a fresh Ubuntu 20.10 install.
Sorry that it is taking so long to fix this. There have been several attempts at fixing this upstream already, but all of them had to be reverted/dropped because they were causing issues on other laptop models. The latest attempt at fixing this is here: https://lore.kernel.org/linux-pci/20220512202511.34197-2-hdego...@redhat.com/ And this patch, or something close to it will hopefully go upstream soon. Perhaps one of the Ubuntu kernel devs can provide a test kernel with this patch for Ubuntu users with this problem to test? -- 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/1921649 Title: 'Ideapad S145 Touchpad' not working at all. Not even detected after a fresh Ubuntu 20.10 install. Status in linux package in Ubuntu: Expired Bug description: Just installed Ubuntu 20.10 in a new Lenovo Ideapad S145 82DJBR and touchpad does not work. It's not detected as seen here: $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Ideapad extra buttons id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-48-generic 5.8.0-48.54 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: netto 1359 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 28 17:30:14 2021 InstallationDate: Installed on 2021-03-20 (7 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 002: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL (B) [Dell Laser Mouse] Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82DJ ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-48-generic root=UUID=8f45bc43-cd22-4cfa-83ee-4cb09fd58f0c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-48-generic N/A linux-backports-modules-5.8.0-48-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2020 dmi.bios.release: 1.48 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN48WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.ec.firmware.release: 1.48 dmi.modalias: dmi:bvnLENOVO:bvrDKCN48WW:bd07/22/2020:br1.48:efr1.48:svnLENOVO:pn82DJ:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 82DJ dmi.product.sku: LENOVO_MT_82DJ_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921649/+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 1932069] Re: Touchpad not working at all
Sorry that it is taking so long to fix this. There have been several attempts at fixing this upstream already, but all of them had to be reverted/dropped because they were causing issues on other laptop models. The latest attempt at fixing this is here: https://lore.kernel.org/linux-pci/20220512202511.34197-2-hdego...@redhat.com/ And this patch, or something close to it will hopefully go upstream soon. Perhaps one of the Ubuntu kernel devs can provide a test kernel with this patch for Ubuntu users with this problem to test? -- 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/1932069 Title: Touchpad not working at all Status in linux package in Ubuntu: Confirmed Bug description: Notebook Lenovo BS-145 15 HL 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: cesar 1314 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 15 16:36:11 2021 InstallationDate: Installed on 2021-06-15 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 005: ID 10c4:8105 Silicon Labs USB OPTICAL MOUSE Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82HB ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-18-generic root=UUID=2ff10f98-8e1f-42ac-98b7-284459b8d285 ro quiet splash vt.handoff=7 RebootRequiredPkgs: gnome-shell 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.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo BS145-15IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82HB:pvrLenovoBS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoBS145-15IIL: dmi.product.family: BS145-15IIL dmi.product.name: 82HB dmi.product.sku: LENOVO_MT_82HB_BU_idea_FM_BS145-15IIL dmi.product.version: Lenovo BS145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932069/+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 1973357] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1973357/+attachment/5589624/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973357 Title: Kernel update to 4.15.0-177 fails to load some kernel modules Status in linux package in Ubuntu: Confirmed Bug description: After update and reboot, severe delay occurs to log in due to network not available. After about 2-3 minutes login worked. No network, no sound and maybe other items. Upon further troubleshooting, the network module is not being loaded. Loading it enabled network. Details below: Linux Mint Cinnamon 19.1 kernel: from 4.15.0-176-generic to 4.15.0-177-generic 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Lenovo ideapad 330S laptop lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 1) cat /proc/version_signature > version.log Ubuntu 4.15.0-176.185-generic 4.15.18 2) sudo lspci -vnvn > lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:383b] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:396b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] 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 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:3867] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:3865] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR-
[Kernel-packages] [Bug 1973357] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1973357/+attachment/5589623/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973357 Title: Kernel update to 4.15.0-177 fails to load some kernel modules Status in linux package in Ubuntu: Confirmed Bug description: After update and reboot, severe delay occurs to log in due to network not available. After about 2-3 minutes login worked. No network, no sound and maybe other items. Upon further troubleshooting, the network module is not being loaded. Loading it enabled network. Details below: Linux Mint Cinnamon 19.1 kernel: from 4.15.0-176-generic to 4.15.0-177-generic 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Lenovo ideapad 330S laptop lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 1) cat /proc/version_signature > version.log Ubuntu 4.15.0-176.185-generic 4.15.18 2) sudo lspci -vnvn > lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:383b] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:396b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] 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 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:3867] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:3865] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
[Kernel-packages] [Bug 1973357] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1973357/+attachment/5589620/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973357 Title: Kernel update to 4.15.0-177 fails to load some kernel modules Status in linux package in Ubuntu: Confirmed Bug description: After update and reboot, severe delay occurs to log in due to network not available. After about 2-3 minutes login worked. No network, no sound and maybe other items. Upon further troubleshooting, the network module is not being loaded. Loading it enabled network. Details below: Linux Mint Cinnamon 19.1 kernel: from 4.15.0-176-generic to 4.15.0-177-generic 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Lenovo ideapad 330S laptop lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 1) cat /proc/version_signature > version.log Ubuntu 4.15.0-176.185-generic 4.15.18 2) sudo lspci -vnvn > lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:383b] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:396b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] 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 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:3867] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:3865] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR-
[Kernel-packages] [Bug 1973357] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1973357/+attachment/5589622/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973357 Title: Kernel update to 4.15.0-177 fails to load some kernel modules Status in linux package in Ubuntu: Confirmed Bug description: After update and reboot, severe delay occurs to log in due to network not available. After about 2-3 minutes login worked. No network, no sound and maybe other items. Upon further troubleshooting, the network module is not being loaded. Loading it enabled network. Details below: Linux Mint Cinnamon 19.1 kernel: from 4.15.0-176-generic to 4.15.0-177-generic 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Lenovo ideapad 330S laptop lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 1) cat /proc/version_signature > version.log Ubuntu 4.15.0-176.185-generic 4.15.18 2) sudo lspci -vnvn > lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:383b] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:396b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] 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 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:3867] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:3865] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
[Kernel-packages] [Bug 1973357] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1973357/+attachment/5589621/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973357 Title: Kernel update to 4.15.0-177 fails to load some kernel modules Status in linux package in Ubuntu: Confirmed Bug description: After update and reboot, severe delay occurs to log in due to network not available. After about 2-3 minutes login worked. No network, no sound and maybe other items. Upon further troubleshooting, the network module is not being loaded. Loading it enabled network. Details below: Linux Mint Cinnamon 19.1 kernel: from 4.15.0-176-generic to 4.15.0-177-generic 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Lenovo ideapad 330S laptop lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 1) cat /proc/version_signature > version.log Ubuntu 4.15.0-176.185-generic 4.15.18 2) sudo lspci -vnvn > lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:383b] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:396b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] 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 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:3867] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:3865] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR-
[Kernel-packages] [Bug 1973357] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1973357/+attachment/5589619/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973357 Title: Kernel update to 4.15.0-177 fails to load some kernel modules Status in linux package in Ubuntu: Confirmed Bug description: After update and reboot, severe delay occurs to log in due to network not available. After about 2-3 minutes login worked. No network, no sound and maybe other items. Upon further troubleshooting, the network module is not being loaded. Loading it enabled network. Details below: Linux Mint Cinnamon 19.1 kernel: from 4.15.0-176-generic to 4.15.0-177-generic 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Lenovo ideapad 330S laptop lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 1) cat /proc/version_signature > version.log Ubuntu 4.15.0-176.185-generic 4.15.18 2) sudo lspci -vnvn > lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:383b] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:396b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] 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 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:3867] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:3865] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
[Kernel-packages] [Bug 1973357] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1973357/+attachment/5589616/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973357 Title: Kernel update to 4.15.0-177 fails to load some kernel modules Status in linux package in Ubuntu: Confirmed Bug description: After update and reboot, severe delay occurs to log in due to network not available. After about 2-3 minutes login worked. No network, no sound and maybe other items. Upon further troubleshooting, the network module is not being loaded. Loading it enabled network. Details below: Linux Mint Cinnamon 19.1 kernel: from 4.15.0-176-generic to 4.15.0-177-generic 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Lenovo ideapad 330S laptop lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 1) cat /proc/version_signature > version.log Ubuntu 4.15.0-176.185-generic 4.15.18 2) sudo lspci -vnvn > lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:383b] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:396b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] 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 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:3867] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:3865] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR-
[Kernel-packages] [Bug 1973357] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1973357/+attachment/5589617/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973357 Title: Kernel update to 4.15.0-177 fails to load some kernel modules Status in linux package in Ubuntu: Confirmed Bug description: After update and reboot, severe delay occurs to log in due to network not available. After about 2-3 minutes login worked. No network, no sound and maybe other items. Upon further troubleshooting, the network module is not being loaded. Loading it enabled network. Details below: Linux Mint Cinnamon 19.1 kernel: from 4.15.0-176-generic to 4.15.0-177-generic 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Lenovo ideapad 330S laptop lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 1) cat /proc/version_signature > version.log Ubuntu 4.15.0-176.185-generic 4.15.18 2) sudo lspci -vnvn > lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:383b] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:396b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] 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 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:3867] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:3865] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
[Kernel-packages] [Bug 1973357] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1973357/+attachment/5589618/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973357 Title: Kernel update to 4.15.0-177 fails to load some kernel modules Status in linux package in Ubuntu: Confirmed Bug description: After update and reboot, severe delay occurs to log in due to network not available. After about 2-3 minutes login worked. No network, no sound and maybe other items. Upon further troubleshooting, the network module is not being loaded. Loading it enabled network. Details below: Linux Mint Cinnamon 19.1 kernel: from 4.15.0-176-generic to 4.15.0-177-generic 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Lenovo ideapad 330S laptop lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 1) cat /proc/version_signature > version.log Ubuntu 4.15.0-176.185-generic 4.15.18 2) sudo lspci -vnvn > lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:383b] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:396b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] 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 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:3867] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:3865] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR-
[Kernel-packages] [Bug 1973357] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1973357/+attachment/5589615/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973357 Title: Kernel update to 4.15.0-177 fails to load some kernel modules Status in linux package in Ubuntu: Confirmed Bug description: After update and reboot, severe delay occurs to log in due to network not available. After about 2-3 minutes login worked. No network, no sound and maybe other items. Upon further troubleshooting, the network module is not being loaded. Loading it enabled network. Details below: Linux Mint Cinnamon 19.1 kernel: from 4.15.0-176-generic to 4.15.0-177-generic 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Lenovo ideapad 330S laptop lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 1) cat /proc/version_signature > version.log Ubuntu 4.15.0-176.185-generic 4.15.18 2) sudo lspci -vnvn > lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:383b] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:396b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] 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 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:3867] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:3865] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
[Kernel-packages] [Bug 1973357] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1973357/+attachment/5589614/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973357 Title: Kernel update to 4.15.0-177 fails to load some kernel modules Status in linux package in Ubuntu: Confirmed Bug description: After update and reboot, severe delay occurs to log in due to network not available. After about 2-3 minutes login worked. No network, no sound and maybe other items. Upon further troubleshooting, the network module is not being loaded. Loading it enabled network. Details below: Linux Mint Cinnamon 19.1 kernel: from 4.15.0-176-generic to 4.15.0-177-generic 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Lenovo ideapad 330S laptop lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 1) cat /proc/version_signature > version.log Ubuntu 4.15.0-176.185-generic 4.15.18 2) sudo lspci -vnvn > lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:383b] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:396b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] 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 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:3867] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:3865] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR-
[Kernel-packages] [Bug 1973357] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1973357/+attachment/5589612/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973357 Title: Kernel update to 4.15.0-177 fails to load some kernel modules Status in linux package in Ubuntu: Confirmed Bug description: After update and reboot, severe delay occurs to log in due to network not available. After about 2-3 minutes login worked. No network, no sound and maybe other items. Upon further troubleshooting, the network module is not being loaded. Loading it enabled network. Details below: Linux Mint Cinnamon 19.1 kernel: from 4.15.0-176-generic to 4.15.0-177-generic 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Lenovo ideapad 330S laptop lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 1) cat /proc/version_signature > version.log Ubuntu 4.15.0-176.185-generic 4.15.18 2) sudo lspci -vnvn > lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:383b] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:396b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] 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 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:3867] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:3865] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
[Kernel-packages] [Bug 1973357] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1973357/+attachment/5589613/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973357 Title: Kernel update to 4.15.0-177 fails to load some kernel modules Status in linux package in Ubuntu: Confirmed Bug description: After update and reboot, severe delay occurs to log in due to network not available. After about 2-3 minutes login worked. No network, no sound and maybe other items. Upon further troubleshooting, the network module is not being loaded. Loading it enabled network. Details below: Linux Mint Cinnamon 19.1 kernel: from 4.15.0-176-generic to 4.15.0-177-generic 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Lenovo ideapad 330S laptop lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 1) cat /proc/version_signature > version.log Ubuntu 4.15.0-176.185-generic 4.15.18 2) sudo lspci -vnvn > lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:383b] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:396b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] 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 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:3867] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:3865] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR-
[Kernel-packages] [Bug 1973357] Re: Kernel update to 4.15.0-177 fails to load some kernel modules
apport information ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: apport-collected tessa ** Description changed: After update and reboot, severe delay occurs to log in due to network not available. After about 2-3 minutes login worked. No network, no sound and maybe other items. Upon further troubleshooting, the network module is not being loaded. Loading it enabled network. Details below: Linux Mint Cinnamon 19.1 kernel: from 4.15.0-176-generic to 4.15.0-177-generic 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Lenovo ideapad 330S laptop lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 1) cat /proc/version_signature > version.log Ubuntu 4.15.0-176.185-generic 4.15.18 2) sudo lspci -vnvn > lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:383b] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:396b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] 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 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:3867] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:3865] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port
[Kernel-packages] [Bug 1968631] Re: regression in jammy kernel 5.15 for module ath9k
-- 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/1968631 Title: regression in jammy kernel 5.15 for module ath9k Status in linux package in Ubuntu: Confirmed Bug description: wireless connection is unstable with kernel 5.15 in jammy release. the following line is in my log, ath: phy0: DMA failed to stop in 10 ms AR_CR=0x0024 AR_DIAG_SW=0x0220 DMADBG_7=0x6100 the bug appears to no longer be present in kernel 5.17.2 from the mainline kernel ppa. lsb_release -rd output: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1871 F pulseaudio /dev/snd/controlC1: david 1871 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 18:05:36 2022 InstallationDate: Installed on 2022-02-01 (69 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: ASUSTeK COMPUTER INC. X550LA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=eb3fe525-e2d6-4de4-aa48-57ebb0fa0881 ro libata.noacpi=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-09 (2 days ago) dmi.bios.date: 05/14/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.508 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.508:bd05/14/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X550LA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968631/+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 1973357] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1973357 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973357 Title: Kernel update to 4.15.0-177 fails to load some kernel modules Status in linux package in Ubuntu: Incomplete Bug description: After update and reboot, severe delay occurs to log in due to network not available. After about 2-3 minutes login worked. No network, no sound and maybe other items. Upon further troubleshooting, the network module is not being loaded. Loading it enabled network. Details below: Linux Mint Cinnamon 19.1 kernel: from 4.15.0-176-generic to 4.15.0-177-generic 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Lenovo ideapad 330S laptop lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 1) cat /proc/version_signature > version.log Ubuntu 4.15.0-176.185-generic 4.15.18 2) sudo lspci -vnvn > lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:383b] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:396b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] 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 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:3867] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
[Kernel-packages] [Bug 1972806] Re: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855
** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Description changed: [Impact] WCN6855-hw2.1 failed to resume after s2idle on AMD RMB [Fix] Update firmware of WCN6855-hw2.1 wifi to fix the issue of s2idle. [Test] Verified on WCN6855 hw2.0 and hw2.1, they work fine, s2idle OK. Wifi works fine after resume [Where problems could occur] These firmware is specific for WCN6855, it should be low risk. - - Because of the schedule, SRU as SAUCE for focal only. - After this version is landed to linux-firmware, focal and jammy can be aligned with upstream. -- 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/1972806 Title: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: New Bug description: [Impact] WCN6855-hw2.1 failed to resume after s2idle on AMD RMB [Fix] Update firmware of WCN6855-hw2.1 wifi to fix the issue of s2idle. [Test] Verified on WCN6855 hw2.0 and hw2.1, they work fine, s2idle OK. Wifi works fine after resume [Where problems could occur] These firmware is specific for WCN6855, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1972806/+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 1971712] Re: Add support for Intel DG2
SRU V2: * https://lists.ubuntu.com/archives/kernel-team/2022-May/130305.html (linux-oem-5.17) * https://lists.ubuntu.com/archives/kernel-team/2022-May/130306.html (linux-meta-oem-5.17) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in linux-oem-5.17 source package in Jammy: New Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1973357] [NEW] Kernel update to 4.15.0-177 fails to load some kernel modules
Public bug reported: After update and reboot, severe delay occurs to log in due to network not available. After about 2-3 minutes login worked. No network, no sound and maybe other items. Upon further troubleshooting, the network module is not being loaded. Loading it enabled network. Details below: Linux Mint Cinnamon 19.1 kernel: from 4.15.0-176-generic to 4.15.0-177-generic 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Lenovo ideapad 330S laptop lsb_release -rd Description:Linux Mint 19.1 Tessa Release:19.1 1) cat /proc/version_signature > version.log Ubuntu 4.15.0-176.185-generic 4.15.18 2) sudo lspci -vnvn > lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:383b] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:396b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] 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 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:3867] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:3865] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
[Kernel-packages] [Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
OK, so far everything seems to be working great. Performance is good, no UBSAN messages, no other abnormalities. I think we are good now. ** Patch added: "aq_nic.c.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+attachment/5589555/+files/aq_nic.c.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.17 package in Ubuntu: Confirmed Bug description: The undefined behaviour sanitiser picks up an array-index-out-of- bounds in the aquantia atlantic driver. The NIC is (I think) built into my gigabyte motherboard (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME- rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to 22.04 (or at least dmesg didn't previously complain). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 13:02:10 2022 InstallationDate: Installed on 2019-08-07 (899 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS XTREME-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS XTREME dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32
= bionic verification = ubuntu@d06-4:~$ cat /proc/version Linux version 4.15.0-179-generic (buildd@bos02-arm64-025) (gcc version 7.5.0 (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04)) #188-Ubuntu SMP Tue May 10 20:51:17 UTC 2022 ubuntu@d06-4:~$ grep domain2 /proc/schedstat | wc -l 128 ubuntu@d06-4:~$ grep domain3 /proc/schedstat | wc -l 128 ubuntu@d06-4:~$ ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951289 Title: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25 report incorrect sched domain for cpu#32 Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Won't Fix Bug description: [Impact] The LTP cpuset_sched_domains test, authored by Miao Xie, fails on a Kunpeng920 server that has 4 NUMA nodes: https://launchpad.net/bugs/1951289 This does appear to be a real bug. /proc/schedstat displays 4 domain levels for CPUs on 2 of the nodes, but only 3 levels for the others 2 (see below). I assume this means the scheduler is making suboptimal decisions about where to place/move processes. [Test Case] On a 128 core Kunpeng 920 system, observe that half the CPUs are missing a 3rd level scheduling domain: ubuntu@d06-4:~$ grep domain2 /proc/schedstat | wc -l 128 ubuntu@d06-4:~$ grep domain3 /proc/schedstat | wc -l 64 ubuntu@d06-4:~$ [What Could Go Wrong] This changes the code used for populating sched domains, so it could potentially break on other systems, leading to poor scheduling characteristics (higher latencies, lower overall throughput etc). To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1951289/+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 1970293] Re: The system hangs when HDMI external monitor involved on AMD Yellow Carp platforms
Verified focal/linux-firmware 1.187.31 on HP-Lockheed, cannot observe the system hang during plug/unplug in native HDMI. ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1970293 Title: The system hangs when HDMI external monitor involved on AMD Yellow Carp platforms Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Summary] 1. The system will hang on when the HDMI external monitor is connected. 2. The system will hang on after the HDMI external monitor is unplugged. 3. The system will show no display when the HDMI external monitor is unplugged, but the system not hangs on. a. if connect HDMI external monitor back, the system will hang on. b. if connect type-c HDMI external monitor, the system works well. Note: 1. Only built-in HDMI can duplicate. 2. FHD/4K monitor both can duplicate [Steps to reproduce] 2. Boot to OS 3. Connect external montior on HDMI port. [Expected result] The system can work well when the external monitor is connected. [Actual result] The system hangs on with the HDMI external monitor. [Failure rate] 2/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1970293/+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 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
** Changed in: linux-oem-5.14 (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-meta in Ubuntu. https://bugs.launchpad.net/bugs/1969434 Title: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-meta package in Ubuntu: In Progress Status in linux-meta-oem package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-meta source package in Focal: Invalid Status in linux-meta-oem source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Fix Released Status in linux source package in Jammy: In Progress Status in linux-meta source package in Jammy: In Progress Status in linux-meta-oem source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed. However, while we need secureboot to be enabled on these platforms, backport-iwlwifi-dkms must also be signed somehow. There are two possible method to achieve this, too. One, to prebuild this dkms as zfs and v4l2loopback does. However, while backport-iwlwifi-dkms generates kernel modules with exactly the same name as the in-tree ones, when prebuilt, they'll be available directly from the linux-modules package and therefore overrides the in-tree ones always, turning the in-tree driver completely useless and risk the stability of all other generic installations. The second one is to build backport-iwlwifi-dkms as nvidia graphic drivers in the linux-restricted-modules source package. In this way, affected platforms may install the corresponding packages when needed without interfering others. However, l-r-m is for restricted modules that needs special care of redistribution of its binaries, and backport-iwlwifi-dkms is GPL licensed. Here a similar but simpler process in the main kernel tree is re-implemented. Two additional packages, linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package linux-modules-MODULE-FLAVOUR will be created. [Test Case] Test builds: ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb [Where problems could occur] The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails to build under this proposed process. Debdiff attached to the same bug. Different from nvidia packages built from l-r-m, the generated package names do not carry an additional short version string, e.g. nvidia-410, as there is no such necessity to build multiple versions of iwlwifi. The modules are installed to /lib/modules//kernel/iwlwifi, not iwlwifi-9858/. == backport-iwlwifi-dkms SRU == In order to be compiled with dkms-build in kernel source package, the kernel header dir will not be /lib/modules//build but a temporary directory. This change specifies KLIB_BUILD
[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function
** Tags removed: verification-needed-focal ** Tags added: verification-done-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/1967702 Title: Enable speakup kernel modules to allow the speakup screen reader to function Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1967702 [Impact] Blind system administrators rely on the speakup accessibility feature to be able to use screen readers in text mode, like "espeakup". Ubuntu has enabled CONFIG_SPEAKUP for a significant amount of time, although in recent releases it keeps being disabled. In Hirsute and Impish, it was accidentally disabled due to it moving from drivers/staging/ to drivers/accessibility/, and it was re-added by Tim Gardner in LP1942459. When it was recently re-enabled, the patch was never applied to ubuntu-unstable, and thus was never picked up by Jammy. We need to enable CONFIG_ACCESSIBILITY and CONFIG_SPEAKUP in Jammy and ubuntu-unstable. [Fix] We need to enable the following configuration items: CONFIG_ACCESSIBILITY=y CONFIG_SPEAKUP=m and the additional modules: CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_DECTLK=m CONFIG_SPEAKUP_SYNTH_DUMMY=m CONFIG_SPEAKUP_SYNTH_LTLK=m CONFIG_SPEAKUP_SYNTH_SOFT=m CONFIG_SPEAKUP_SYNTH_SPKOUT=m CONFIG_SPEAKUP_SYNTH_TXPRT=m [Testcase] Install the speakup accessibility tool: $ sudo apt install espeakup Check journalctl to see if it is able to load kernel modules: systemd[1]: Starting Software speech output for Speakup... modprobe[27013]: modprobe: FATAL: Module speakup_soft not found in directory /lib/modules/5.15.0-25-generic systemd[1]: espeakup.service: Control process exited, code=exited, status=1/FAILURE systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. systemd[1]: espeakup.service: Scheduled restart job, restart counter is at 1. systemd[1]: Stopped Software speech output for Speakup. systemd[1]: espeakup.service: Start request repeated too quickly. systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. We should see espeakup.service start correctly, instead of failing to load speakup_soft: systemd[1]: Starting Software speech output for Speakup... kernel: input: Speakup as /devices/virtual/input/input5 kernel: initialized device: /dev/synth, node (MAJOR 10, MINOR 123) kernel: speakup 3.1.6: initialized kernel: synth name on entry is: (null) kernel: synth probe kernel: initialized device: /dev/softsynth, node (MAJOR 10, MINOR 122) kernel: initialized device: /dev/softsynthu, node (MAJOR 10, MINOR 121) systemd[1]: Started Software speech output for Speakup. You can also try load the modules manually: $ sudo modprobe speakup_soft There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1967702-test If you install the test kernel, the speakup modules should load successfully. [Where problems could occur] We are enabling CONFIG_ACCESSIBILITY for all arches apart from s390x, and this shouldn't have any affect on config items being turned on, since it simply enables the speakup submenu to be shown. Enabling CONFIG_SPEAKUP* should not have any impact on users that don't use screen reader accessibility software, as it will only be loaded by users of espeakup. If a regression were to occur, users could unload the speakup modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+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 1966194] Re: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering
@kernel when we've already tested a kernel in its GA release, do we also now need to retest the HWE backport? -- 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/1966194 Title: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Add support for software steering on cx7 [Test Case] configure software steering on cx7 setup run asap testing (reference https://github.com/Mellanox/ovs-tests) [Regression Potential] TBD [Other Info] Feature patchset: All patches are cleanly applied on Jamy master-next beside these two who add minor conflicts due to context difference. net/mlx5: Introduce software defined steering capabilities net/mlx5: DR, Add support for matching on #fixes 624bf42c2e39 net/mlx5: DR, Fix querying eswitch manager vport for ECPF 0aec12d97b20 net/mlx5: DR, Fix slab-out-of-bounds in mlx5_cmd_dr_create_fte 9091b821aaa4 net/mlx5: DR, Handle eswitch manager and uplink vports separately #CX7 SMFS support 6862c787c7e8 net/mlx5: DR, Add support for ConnectX-7 steering 638a07f1090e net/mlx5: DR, Refactor ste_ctx handling for STE v0/1 75a3926ca6a4 net/mlx5: DR, Rename action modify fields to reflect naming in HW spec bdc3ab5795a6 net/mlx5: DR, Fix handling of different actions on the same STE in STEv1 11659ef8d28e net/mlx5: DR, Remove unneeded comments 5c422bfad2fb net/mlx5: DR, Add support for matching on Internet Header Length (IHL) #dependencies: 60dc0ef674ec net/mlx5: VLAN push on RX, pop on TX 8348b71ccd92 net/mlx5: Introduce software defined steering capabilities #depencecies: #SW STEERING DEBUG DUMP aa36c94853b2 net/mlx5: Set SMFS as a default steering mode if device supports it 4ff725e1d4ad net/mlx5: DR, Ignore modify TTL if device doesn't support it cc2295cd54e4 net/mlx5: DR, Improve steering for empty or RX/TX-only matchers f59464e257bd net/mlx5: DR, Add support for matching on geneve_tlv_option_0_exist field 09753babaf46 net/mlx5: DR, Support matching on tunnel headers 0 and 1 8c2b4fee9c4b net/mlx5: DR, Add misc5 to match_param structs 0f2a6c3b9219 net/mlx5: Add misc5 flow table match parameters b54128275ef8 net/mlx5: DR, Warn on failure to destroy objects due to refcount e3a0f40b2f90 net/mlx5: DR, Add support for UPLINK destination type 9222f0b27da2 net/mlx5: DR, Add support for dumping steering info 7766c9b922fe net/mlx5: DR, Add missing reserved fields to dr_match_param 89cdba3224f0 net/mlx5: DR, Add check for flex parser ID value 08fac109f7bb net/mlx5: DR, Rename list field in matcher struct to list_node 32e9bd585307 net/mlx5: DR, Remove unused struct member in matcher c3fb0e280b4c net/mlx5: DR, Fix lower case macro prefix "mlx5_" to "MLX5_" 84dfac39c61f net/mlx5: DR, Fix error flow in creating matcher 58a606dba708 net/mlx5: Introduce new uplink destination type 455832d49666 net/mlx5: DR, Fix check for unsupported fields in match param 9091b821aaa4 net/mlx5: DR, Handle eswitch manager and uplink vports separately #SW STEERING SF 515ce2ffa621 net/mlx5: DR, init_next_match only if needed 5dde00a73048 net/mlx5: DR, Fix typo 'offeset' to 'offset' 1ffd498901c1 net/mlx5: DR, Increase supported num of actions to 32 11a45def2e19 net/mlx5: DR, Add support for SF vports c0e90fc2ccaa net/mlx5: DR, Support csum recalculation flow table on SFs ee1887fb7cdd net/mlx5: DR, Align error messages for failure to obtain vport caps dd4acb2a0954 net/mlx5: DR, Add missing query for vport 0 7ae8ac9a5820 net/mlx5: DR, Replace local WIRE_PORT macro with the existing MLX5_VPORT_UPLINK f9f93bd55ca6 net/mlx5: DR, Fix vport number data type to u16 c228dce26222 net/mlx5: DR, Fix code indentation in dr_ste_v1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966194/+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 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
SRU V4: * linux: https://lists.ubuntu.com/archives/kernel-team/2022-May/130284.html (oem-5.14, jammy, oem-5.17, unstable) * linux-meta: https://lists.ubuntu.com/archives/kernel-team/2022-May/130294.html (oem-5.14, jammy, oem-5.17, unstable) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1969434 Title: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-meta package in Ubuntu: In Progress Status in linux-meta-oem package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-meta source package in Focal: Invalid Status in linux-meta-oem source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Focal: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Fix Released Status in linux source package in Jammy: In Progress Status in linux-meta source package in Jammy: In Progress Status in linux-meta-oem source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed. However, while we need secureboot to be enabled on these platforms, backport-iwlwifi-dkms must also be signed somehow. There are two possible method to achieve this, too. One, to prebuild this dkms as zfs and v4l2loopback does. However, while backport-iwlwifi-dkms generates kernel modules with exactly the same name as the in-tree ones, when prebuilt, they'll be available directly from the linux-modules package and therefore overrides the in-tree ones always, turning the in-tree driver completely useless and risk the stability of all other generic installations. The second one is to build backport-iwlwifi-dkms as nvidia graphic drivers in the linux-restricted-modules source package. In this way, affected platforms may install the corresponding packages when needed without interfering others. However, l-r-m is for restricted modules that needs special care of redistribution of its binaries, and backport-iwlwifi-dkms is GPL licensed. Here a similar but simpler process in the main kernel tree is re-implemented. Two additional packages, linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package linux-modules-MODULE-FLAVOUR will be created. [Test Case] Test builds: ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb [Where problems could occur] The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails to build under this proposed process. Debdiff attached to the same bug. Different from nvidia packages built from l-r-m, the generated package names do not carry an additional short version string, e.g. nvidia-410, as there is no such necessity to build multiple versions of iwlwifi. The modules are installed to /lib/modules//kernel/iwlwifi, not iwlwifi-9858/. == backport-iwlwifi-dkms SRU == In order to be compiled with
[Kernel-packages] [Bug 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32
** Description changed: [Impact] The LTP cpuset_sched_domains test, authored by Miao Xie, fails on a Kunpeng920 server that has 4 NUMA nodes: - https://launchpad.net/bugs/1951289 + https://launchpad.net/bugs/1951289 This does appear to be a real bug. /proc/schedstat displays 4 domain levels for CPUs on 2 of the nodes, but only 3 levels for the others 2 (see below). I assume this means the scheduler is making suboptimal decisions about where to place/move processes. [Test Case] On a 128 core Kunpeng 920 system, observe that half the CPUs are missing a 3rd level scheduling domain: ubuntu@d06-4:~$ grep domain2 /proc/schedstat | wc -l 128 ubuntu@d06-4:~$ grep domain3 /proc/schedstat | wc -l 64 - ubuntu@d06-4:~$ + ubuntu@d06-4:~$ [What Could Go Wrong] - This changes the code used for populating sched domains, so it could potentially break on other systems, potentially leading to poor scheduling characteristics (higher latencies, lower overall throughput etc). + This changes the code used for populating sched domains, so it could potentially break on other systems, leading to poor scheduling characteristics (higher latencies, lower overall throughput etc). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951289 Title: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25 report incorrect sched domain for cpu#32 Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Won't Fix Bug description: [Impact] The LTP cpuset_sched_domains test, authored by Miao Xie, fails on a Kunpeng920 server that has 4 NUMA nodes: https://launchpad.net/bugs/1951289 This does appear to be a real bug. /proc/schedstat displays 4 domain levels for CPUs on 2 of the nodes, but only 3 levels for the others 2 (see below). I assume this means the scheduler is making suboptimal decisions about where to place/move processes. [Test Case] On a 128 core Kunpeng 920 system, observe that half the CPUs are missing a 3rd level scheduling domain: ubuntu@d06-4:~$ grep domain2 /proc/schedstat | wc -l 128 ubuntu@d06-4:~$ grep domain3 /proc/schedstat | wc -l 64 ubuntu@d06-4:~$ [What Could Go Wrong] This changes the code used for populating sched domains, so it could potentially break on other systems, leading to poor scheduling characteristics (higher latencies, lower overall throughput etc). To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1951289/+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 1971701] Re: Azure: swiotlb patch needed for CVM
This bug is awaiting verification that the linux-azure/5.15.0-1006.7 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-jammy -- 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/1971701 Title: Azure: swiotlb patch needed for CVM Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] [Azure][CVM] Include the swiotlb patch to increase the disk/network performance Description As we discussed, there will be new CVM-supporting linux-azure kernels that're based on v5.13 and v5.15. Here I'm requesting the below patch to be included into the two kernels because it can significantly improve the disk/network performance: swiotlb: Split up single swiotlb lock: https://github.com/intel/tdx/commit/4529b5784c141782c72ec9bd9a92df2b68cb7d45 We have tested the patch with the upstream 5.16-rc8. BTW, the patch is unlikely to be in the mainline kernel, as the community is trying to resolve the lock contention issue in the swiotlb code using a different per-device per-queue implementation, which would need quite some time to be finalized -- before that happens, we need this out-of-tree patch to achieve good disk/network performance for CVM GA on Azure. (BTW, the v5.4-based linux-azure-cvm kernel does not need the patch, because it uses a private bounce buffer implementation: drivers/hv/hv_bounce.c, which doesn’t have the I/O performance issue caused by lock contention in the mainline kernel’s swiotlb code.) [Test Case] [Microsoft tested] I tried the April-27 amd64 test kernel and it worked great for me: 1. The test kernels booted up successfully with 256 virtual CPUs + 100 GB memory. 2. The kernel worked when I changed the MTU of the NetVSC NIC. 3. The Hyper-V HeartBeat/TimeSync/ShutDown VMBsus devices also worked as expected. 4. I did some quick disk I/O and network stress tests and found no issue. When I did the above tests, I changed the low MMIO size to 3GB (which is the setting for a VM on Azure today) by "set-vm decui-u2004-cvm -LowMemoryMappedIoSpace 3GB". Our test team will do more testing, including performance test. We expect the performance of this v5.15 test kernel should be on par with the v5.4 linux-azure-cvm kernel. [Where things could go wrong] Networking could fail or continue to suffer from poor performance. [Other Info] SF: #00332721 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1971701/+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 1970468] Re: linux-azure: Patch Set for ARM64 Images 20.04 and 18.04
This bug is awaiting verification that the linux-azure/5.15.0-1006.7 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-jammy -- 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/1970468 Title: linux-azure: Patch Set for ARM64 Images 20.04 and 18.04 Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Microsoft has asked to have the following patches included in impish/linux-azure and focal/linux-azure: commit eaa03d34535872d29004cb5cf77dc9dec1ba9a25 Drivers: hv: vmbus: Replace smp_store_mb() with virt_store_mb() commit b3d6dd09ff00fdcf4f7c0cb54700ffd5dd343502 Drivers: hv: balloon: Support status report for larger page sizes commit be5802795cf8d0b881745fa9ba7790293b382280 Drivers: hv: balloon: Disable balloon and hot-add accordingly [Test Case] Microsoft tested [Where things could go wrong] Hyper-v ballooning could fail. [Other Info] SF: #00333989 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1970468/+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 1970977] Re: jammy/linux-azure: Update cifs to 5.15 backport
This bug is awaiting verification that the linux-azure/5.15.0-1006.7 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-jammy -- 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/1970977 Title: jammy/linux-azure: Update cifs to 5.15 backport Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Microsoft has provided updates to the cifs 5.15 backport through 5.18-rc3 at 'git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport'. [Test Case] Microsoft tested. [Where things could go wrong] cifs connections or data transfers could fail. [Other Info] SF: #00327908 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1970977/+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 1972662] Re: [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time
This bug is awaiting verification that the linux-azure/5.15.0-1006.7 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-jammy -- 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/1972662 Title: [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] A VM on Azure can have 14 GPUs, and each GPU may have a huge MMIO BAR, e.g. 128 GB. Currently the boot time of such a VM can be 4+ minutes, and most of the time is used by the host to unmap/map the vBAR from/to pBAR when the VM clears and sets the PCI_COMMAND_MEMORY bit: each unmap/map operation for a 128GB BAR needs about 1.8 seconds, and the pci-hyperv driver and the Linux PCI subsystem flip the PCI_COMMAND_MEMORY bit eight times (see pci_setup_device() -> pci_read_bases() and pci_std_update_resource()), increasing the boot time by 1.8 * 8 = 14.4 seconds per GPU, i.e. 14.4 * 14 = 201.6 seconds in total. Fix the slowness by not turning on the PCI_COMMAND_MEMORY in pci-hyperv.c, so the bit stays in the off state before the PCI device driver calls pci_enable_device(): when the bit is off, pci_read_bases() and pci_std_update_resource() don't cause Hyper-V to unmap/map the vBARs. With this change, the boot time of such a VM is reduced by 1.8 * (8-1) * 14 = 176.4 seconds. [Test Case] Microsoft tested [Where things could go wrong] PCI BAR setup could fail or be incorrect. [Other Info] SF: #00336342 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1972662/+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 1972017] Re: Jammy/linux-azure: CONFIG_BLK_DEV_FD=n
This bug is awaiting verification that the linux-azure/5.15.0-1006.7 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-jammy -- 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/1972017 Title: Jammy/linux-azure: CONFIG_BLK_DEV_FD=n Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] CONFIG_BLK_DEV_FD should be disabled, consistent with Focal and Impish kernel configurations. this config is also considered a security risk on cloud platforms. [Test Case] Look for floppy.ko in either of the modules packages. [Where things could go wrong] There should be no regression due to the removal of this module. [Other Info] SF: #00336330 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1972017/+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 1972832] Re: [Azure] hv_netvsc: Add support for XDP_REDIRECT
This bug is awaiting verification that the linux-azure/5.15.0-1006.7 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-jammy -- 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/1972832 Title: [Azure] hv_netvsc: Add support for XDP_REDIRECT Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Add support for XDP_REDIRECT to the Azure Hyperv network driver. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=1cb9d3b6185b2a4d1d592632a7faf5d8c8e5f9b3 [Where things could go wrong] User space requests to set XDP_REDIRECT could break packet routing. [Other Info] SF: #00336466 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1972832/+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 1973169] Re: [Azure][CVM] Fix swiotlb_max_mapping_size() for potential bounce buffer allocation failure in storvsc
This bug is awaiting verification that the linux-azure/5.15.0-1006.7 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-jammy -- 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/1973169 Title: [Azure][CVM] Fix swiotlb_max_mapping_size() for potential bounce buffer allocation failure in storvsc Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification [Impact] Description of problem: When the v5.15 linux-azure kernel is used for CVM on Azure, it uses swiotlb for bounce buffering. We recently found an issue in swiotlb_max_mapping_size(), which is used by the SCSI subsytem APIs, which are used by the hv_storvsc driver. The issue is: currently swiotlb_max_mapping_size() always reports 256KB (i.e. 128 bounce buffer slots), but swiotlb_tbl_map_single() is unable to allocate a bounce buffer for an unaligned 256KB request, and eventually it can get stuck and we see this call-trace (BTW, this call-trace is obtained from a SLES VM, but I believe the issue exists in all distro kernels supporting CVM, and Tianyu says he's able to repro the issue in a Ubuntu CVM when trying to mount a XFS file system): [ 186.458666][ C1] swiotlb_tbl_map_single+0x396/0x920 [ 186.458669][ C1] swiotlb_map+0xaa/0x2d0 [ 186.458674][ C1] dma_direct_map_sg+0xee/0x2c0 [ 186.458677][ C1] __dma_map_sg_attrs+0x30/0x70 [ 186.458680][ C1] dma_map_sg_attrs+0xa/0x20 [ 186.458681][ C1] scsi_dma_map+0x35/0x40 [ 186.458684][ C1] storvsc_queuecommand+0x20b/0x890 [ 186.458696][ C1] scsi_queue_rq+0x606/0xb80 [ 186.458698][ C1] __blk_mq_try_issue_directly+0x149/0x1c0 [ 186.458702][ C1] blk_mq_try_issue_directly+0x15/0x50 [ 186.458704][ C1] blk_mq_submit_bio+0x4b6/0x620 [ 186.458706][ C1] __submit_bio+0xe8/0x160 [ 186.458708][ C1] submit_bio_noacct_nocheck+0xf0/0x2b0 [ 186.458713][ C1] submit_bio+0x42/0xd0 [ 186.458714][ C1] submit_bio_wait+0x54/0xb0 [ 186.458718][ C1] xfs_rw_bdev+0x180/0x1b0 [xfs 172cb9b0bc08b0ee82c7c88dc584daeab1b34d46] [ 186.458769][ C1] xlog_do_io+0x8d/0x140 [xfs 172cb9b0bc08b0ee82c7c88dc584daeab1b34d46] [ 186.458819][ C1] xlog_bread+0x1f/0x40 [xfs 172cb9b0bc08b0ee82c7c88dc584daeab1b34d46] [ 186.458859][ C1] xlog_find_verify_cycle+0xc8/0x180 [xfs 172cb9b0bc08b0ee82c7c88dc584daeab1b34d46] [ 186.458899][ C1] xlog_find_head+0x2ae/0x3a0 [xfs 172cb9b0bc08b0ee82c7c88dc584daeab1b34d46] [ 186.458937][ C1] xlog_find_tail+0x44/0x360 [xfs 172cb9b0bc08b0ee82c7c88dc584daeab1b34d46] [ 186.458978][ C1] xlog_recover+0x2b/0x170 [xfs 172cb9b0bc08b0ee82c7c88dc584daeab1b34d46] [ 186.459056][ C1] xfs_log_mount+0x15b/0x270 [xfs 172cb9b0bc08b0ee82c7c88dc584daeab1b34d46] [ 186.459098][ C1] xfs_mountfs+0x49e/0x830 [xfs 172cb9b0bc08b0ee82c7c88dc584daeab1b34d46] [ 186.459224][ C1] xfs_fs_fill_super+0x5c2/0x7c0 [xfs 172cb9b0bc08b0ee82c7c88dc584daeab1b34d46] [ 186.459303][ C1] get_tree_bdev+0x163/0x260 [ 186.459307][ C1] vfs_get_tree+0x25/0xc0 [ 186.459309][ C1] path_mount+0x704/0x9c0 Details: For example, the original physical address from the SCSI layer can be 0x1_0903_f200 with size=256KB, and when swiotlb_tbl_map_single() calls swiotlb_find_slots(), it passes "alloc_size + offset" (i.e. 256KB + 0x200 ) to swiotlb_find_slots(), which then calculates "nslots = nr_slots(alloc_size) ==> 129" and fails to allocate a bounce buffer as the maximum allowable number of contiguous slabs to map is IO_TLB_SEGSIZE (128). The issue affects the hv_storvsc driver, as it calls dma_set_min_align_mask(>device, HV_HYP_PAGE_SIZE - 1); dma_set_min_align_mask() is also called by hv_netvsc, but netvsc is not affected as netvsc never calls swiotlb_tbl_map_single() with a near-to-256KB size. dma_set_min_align_mask() is also called by the NVMe driver, but since we don't support PCI device assignment for CVM for now, that's not affected for now. Tianyu Lan made a fix which is under review: https://lwn.net/ml/linux-kernel/20220510142109.38-1-ltykernel%40gmail.com/ Note: the linux-azure-cvm v5.4 kernel doesn't need the fix, as that kernel uses a vmbus private bounce buffering implementation (drivers/hv/hv_bounce.c) rathen than swiotlb. [Test Case] Microsoft tested [Where things could go wrong] Bounce
[Kernel-packages] [Bug 1967338] Re: linux: CONFIG_SERIAL_8250_MID=y
** Tags removed: verification-needed-focal ** Tags added: verification-done-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/1967338 Title: linux: CONFIG_SERIAL_8250_MID=y Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] See discussion at https://lists.ubuntu.com/archives/kernel- team/2022-March/128690.html [Test Plan] Boot with serial console connected [Where things could go wrong] Not really a lot of opportunity for regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338/+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 1971955] Re: systemd-udevd call unshare process when attaching nvme volume
For the record, does /usr/bin/unshare exist in your system? Can you run the command that Alberto provided in the console? -- 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/1971955 Title: systemd-udevd call unshare process when attaching nvme volume Status in dellserver: New Status in linux package in Ubuntu: Invalid Status in snapd package in Ubuntu: In Progress Bug description: env: PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 (Jammy Jellyfish)" VERSION_CODENAME=jammy # lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 host connect dellemc powerstore with nvme-tcp connection # nvme list-subsys nvme-subsys0 - NQN=nqn.1988-11.com.dell:powerstore:00:d42d581e674f2B16F2E2 \ +- nvme1 tcp traddr=172.16.100.165 trsvcid=4420 live +- nvme2 tcp traddr=172.16.200.164 trsvcid=4420 live +- nvme3 tcp traddr=172.16.200.165 trsvcid=4420 live +- nvme4 tcp traddr=172.16.100.164 trsvcid=4420 live when attaching new volume to host. systemd-udevd trigger unshare process to run snap import command on new volumes and it fail. volume finally map to host. it doesn't affect volume usage. but some udev rule need to check for this strange behavior. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33374]: nvme0n234: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n234' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33371]: nvme0n232: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n232' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33378]: nvme0n236: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n236' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33384]: nvme0n239: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n239' failed with exit code 1. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 6 08:14 seq crw-rw 1 root audio 116, 33 May 6 08:14 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-04 (2 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. 8 channel internal hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. 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/2p, 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/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/6p, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/14/2021 dmi.bios.release: 2.13 dmi.bios.version: 2.13.0 dmi.board.name: 072T6D dmi.board.version: A01 dmi.chassis.type: 23 dmi.modalias: dmi:bvn:bvr2.13.0:bd05/14/2021:br2.13:svn:pn:pvr:rvn:rn072T6D:rvrA01:cvn:ct23:cvr:skuSKU=NotProvided;ModelName=: dmi.product.sku: SKU=NotProvided;ModelName= To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1971955/+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 1971955] Re: systemd-udevd call unshare process when attaching nvme volume
Alberto, there still have error. yes. the log report exist status 1. May 13 12:45:43 e2e-l4-094051 kernel: nvme nvme1: rescanning namespaces. May 13 12:45:44 e2e-l4-094051 kernel: nvme nvme4: rescanning namespaces. May 13 12:46:23 e2e-l4-094051 kernel: nvme nvme3: rescanning namespaces. May 13 12:46:23 e2e-l4-094051 kernel: nvme nvme2: rescanning namespaces. May 13 12:46:23 e2e-l4-094051 kernel: nvme nvme4: rescanning namespaces. May 13 12:46:23 e2e-l4-094051 kernel: nvme nvme1: rescanning namespaces. May 13 12:46:27 e2e-l4-094051 kernel: nvme nvme3: rescanning namespaces. May 13 12:46:27 e2e-l4-094051 kernel: nvme nvme4: rescanning namespaces. May 13 12:46:27 e2e-l4-094051 kernel: nvme nvme1: rescanning namespaces. May 13 12:46:27 e2e-l4-094051 kernel: nvme nvme2: rescanning namespaces. May 13 12:46:28 e2e-l4-094051 systemd-udevd[131706]: nvme0n32: Process '/usr/bin/unshare -m /bin/echo hello' failed with exit code 1. May 13 12:46:28 e2e-l4-094051 systemd-udevd[131704]: nvme0n31: Process '/usr/bin/unshare -m /bin/echo hello' failed with exit code 1. May 13 12:46:32 e2e-l4-094051 systemd-udevd[131721]: nvme0n35: Process '/usr/bin/unshare -m /bin/echo hello' failed with exit code 1. May 13 12:46:33 e2e-l4-094051 systemd-udevd[131718]: nvme0n33: Process '/usr/bin/unshare -m /bin/echo hello' failed with exit code 1. May 13 12:46:33 e2e-l4-094051 systemd-udevd[131719]: nvme0n34: Process '/usr/bin/unshare -m /bin/echo hello' failed with exit code 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/1971955 Title: systemd-udevd call unshare process when attaching nvme volume Status in dellserver: New Status in linux package in Ubuntu: Invalid Status in snapd package in Ubuntu: In Progress Bug description: env: PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 (Jammy Jellyfish)" VERSION_CODENAME=jammy # lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 host connect dellemc powerstore with nvme-tcp connection # nvme list-subsys nvme-subsys0 - NQN=nqn.1988-11.com.dell:powerstore:00:d42d581e674f2B16F2E2 \ +- nvme1 tcp traddr=172.16.100.165 trsvcid=4420 live +- nvme2 tcp traddr=172.16.200.164 trsvcid=4420 live +- nvme3 tcp traddr=172.16.200.165 trsvcid=4420 live +- nvme4 tcp traddr=172.16.100.164 trsvcid=4420 live when attaching new volume to host. systemd-udevd trigger unshare process to run snap import command on new volumes and it fail. volume finally map to host. it doesn't affect volume usage. but some udev rule need to check for this strange behavior. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33374]: nvme0n234: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n234' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33371]: nvme0n232: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n232' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33378]: nvme0n236: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n236' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33384]: nvme0n239: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n239' failed with exit code 1. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 6 08:14 seq crw-rw 1 root audio 116, 33 May 6 08:14 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-04 (2 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. 8 channel internal hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. 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/2p, 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/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/6p, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash
[Kernel-packages] [Bug 1970426] Re: [i915] screen is flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
*** This bug is a duplicate of bug 1958191 *** https://bugs.launchpad.net/bugs/1958191 I am also getting the same screen flickering issue after fresh installation of Ubuntu 22.04 LTS running on xorg (x11). CPU in my case is: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 version: 6.78.3 size: 2406MHz capacity: 2800MHz GPU: product: GK208BM [GeForce 920M] vendor: NVIDIA Corporation Is there any reliable solution to this 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/1970426 Title: [i915] screen is flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: After I updated to 22.04 sometimes (about 3 ~ 4 times a day) the screen starts glitching and flickering like in the attached video and it doesn't stop until I move the cursor. Description: Ubuntu 22.04 LTS Release: 22.04 wayland processor: Intel® Core™ i5-8265U CPU @ 1.60GHz × 8 graphics: Mesa Intel® UHD Graphics 620 (WHL GT2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970426/+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 1971205] Re: CVE-2022-25258 and CVE-2022-25375
** Changed in: linux-gcp-5.13 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-gke (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-gke-5.4 (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: linux-gkeop (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1971205 Title: CVE-2022-25258 and CVE-2022-25375 Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws-5.13 package in Ubuntu: Fix Released Status in linux-aws-5.4 package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Fix Released Status in linux-azure-5.13 package in Ubuntu: Fix Released Status in linux-azure-5.4 package in Ubuntu: Fix Released Status in linux-bluefield package in Ubuntu: Confirmed Status in linux-dell300x package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp-4.15 package in Ubuntu: Fix Released Status in linux-gcp-5.13 package in Ubuntu: Fix Released Status in linux-gcp-5.4 package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Fix Released Status in linux-gke-5.4 package in Ubuntu: Fix Committed Status in linux-gkeop package in Ubuntu: Fix Released Status in linux-gkeop-5.4 package in Ubuntu: Confirmed Status in linux-hwe-5.13 package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in linux-ibm package in Ubuntu: Confirmed Status in linux-ibm-5.4 package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-oracle-5.4 package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi-5.4 package in Ubuntu: Confirmed Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-riscv package in Ubuntu: Confirmed Status in linux-snapdragon package in Ubuntu: Confirmed Bug description: These packages are vulnerable to CVE-2022-25258 and CVE-2022-25375 in at least one Ubuntu release, as stated in the Ubuntu CVE Tracker. Please release fixed packages. Debian released an advisory on March 7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1971205/+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 1970923] Please test proposed package
Hello AaronMa, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.31 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1970923 Title: [SRU][F/J] Update firmware of MT7922 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] MT7922 is not stable to connect. [Fix] Update firmware of MT7922 wifi and bluetooth. [Test] Verified on RZ616, it works fine, suspend OK. Wifi b/g can be connected. iperf test result looks fine. Bluetooth is stable. [Where problems could occur] These firmware is specific for MT7922, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1970923/+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 1971539] Re: Add firmware for i915/DG2
Hello Timo, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => Fix Committed -- 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/1971539 Title: Add firmware for i915/DG2 Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] New hardware being enabled needs the firmware for DMC and GuC, freshly merged to upstream git. [Fix] Merge the files from upstream git. [Test case] Boot a machine with DG2 using oem-5.17 kernel plus a dkms, check that both firmware get loaded and i915.ko is used. [Where things could go wrong] This is for new hardware, there is no chance of regressing shipping platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971539/+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 1970923] Please test proposed package
Hello AaronMa, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1970923 Title: [SRU][F/J] Update firmware of MT7922 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] MT7922 is not stable to connect. [Fix] Update firmware of MT7922 wifi and bluetooth. [Test] Verified on RZ616, it works fine, suspend OK. Wifi b/g can be connected. iperf test result looks fine. Bluetooth is stable. [Where problems could occur] These firmware is specific for MT7922, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1970923/+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 1970293] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.31 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1970293 Title: The system hangs when HDMI external monitor involved on AMD Yellow Carp platforms Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Summary] 1. The system will hang on when the HDMI external monitor is connected. 2. The system will hang on after the HDMI external monitor is unplugged. 3. The system will show no display when the HDMI external monitor is unplugged, but the system not hangs on. a. if connect HDMI external monitor back, the system will hang on. b. if connect type-c HDMI external monitor, the system works well. Note: 1. Only built-in HDMI can duplicate. 2. FHD/4K monitor both can duplicate [Steps to reproduce] 2. Boot to OS 3. Connect external montior on HDMI port. [Expected result] The system can work well when the external monitor is connected. [Actual result] The system hangs on with the HDMI external monitor. [Failure rate] 2/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1970293/+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 1972806] Please test proposed package
Hello AaronMa, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.31 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1972806 Title: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] WCN6855-hw2.1 failed to resume after s2idle on AMD RMB [Fix] Update firmware of WCN6855-hw2.1 wifi to fix the issue of s2idle. [Test] Verified on WCN6855 hw2.0 and hw2.1, they work fine, s2idle OK. Wifi works fine after resume [Where problems could occur] These firmware is specific for WCN6855, it should be low risk. Because of the schedule, SRU as SAUCE for focal only. After this version is landed to linux-firmware, focal and jammy can be aligned with upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1972806/+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 1971205] Re: CVE-2022-25258 and CVE-2022-25375
I filed this bug to alert that these vulnerabilities were unpatched for 2 months. Some kernels in supported Ubuntu releases are still affected: $ wget https://git.launchpad.net/ubuntu-cve-tracker/plain/active/CVE-2022-25258 $ grep -vE '^(upstream_[a-z0-9.-]+: |Patches_[a-z0-9.-]+:$| break-fix:|([a-z]+|trusty/esm|esm-infra/xenial)_[a-z0-9.-]+: (DNE$|released |not-affected($| )|ignored)|$)' CVE-2022-25258 bionic_linux-aws-5.4: pending (5.4.0-1073.78~18.04.1) focal_linux-bluefield: needed fips/xenial_linux-fips: needs-triage fips-updates/xenial_linux-fips: needs-triage fips/bionic_linux-fips: needs-triage fips-updates/bionic_linux-fips: needs-triage fips/focal_linux-fips: needs-triage fips-updates/focal_linux-fips: needs-triage bionic_linux-gke-5.4: pending (5.4.0-1069.72~18.04.1) bionic_linux-raspi2: pending (4.15.0-1109.116) impish_linux-riscv: pending (5.13.0-1021.23) focal_linux-oracle-5.13: pending (5.13.0-1028.33~20.04.1) Please release patched versions of linux-bluefield and linux-fips. ** Changed in: linux-aws (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-aws-5.13 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-aws-5.4 (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: linux-azure (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-azure-4.15 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-azure-5.13 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-azure-5.4 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-dell300x (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-gcp (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-gcp-4.15 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-gcp-5.4 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1971205 Title: CVE-2022-25258 and CVE-2022-25375 Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws-5.13 package in Ubuntu: Fix Released Status in linux-aws-5.4 package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Fix Released Status in linux-azure-5.13 package in Ubuntu: Fix Released Status in linux-azure-5.4 package in Ubuntu: Fix Released Status in linux-bluefield package in Ubuntu: Confirmed Status in linux-dell300x package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp-4.15 package in Ubuntu: Fix Released Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.4 package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Confirmed Status in linux-gke-5.4 package in Ubuntu: Confirmed Status in linux-gkeop package in Ubuntu: Confirmed Status in linux-gkeop-5.4 package in Ubuntu: Confirmed Status in linux-hwe-5.13 package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in linux-ibm package in Ubuntu: Confirmed Status in linux-ibm-5.4 package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-oracle-5.4 package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi-5.4 package in Ubuntu: Confirmed Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-riscv package in Ubuntu: Confirmed Status in linux-snapdragon package in Ubuntu: Confirmed Bug description: These packages are vulnerable to CVE-2022-25258 and CVE-2022-25375 in at least one Ubuntu release, as stated in the Ubuntu CVE Tracker. Please release fixed packages. Debian released an advisory on March 7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1971205/+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 1970923] Re: [SRU][F/J] Update firmware of MT7922
** Summary changed: - [SRU][F/J] Update firmware of MT7922 + [SRU][F/J] Update firmware of MT7922 -- 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/1970923 Title: [SRU][F/J] Update firmware of MT7922 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] MT7922 is not stable to connect. [Fix] Update firmware of MT7922 wifi and bluetooth. [Test] Verified on RZ616, it works fine, suspend OK. Wifi b/g can be connected. iperf test result looks fine. Bluetooth is stable. [Where problems could occur] These firmware is specific for MT7922, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1970923/+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 1972806] Re: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855
** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Focal) Status: New => Fix Committed -- 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/1972806 Title: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] WCN6855-hw2.1 failed to resume after s2idle on AMD RMB [Fix] Update firmware of WCN6855-hw2.1 wifi to fix the issue of s2idle. [Test] Verified on WCN6855 hw2.0 and hw2.1, they work fine, s2idle OK. Wifi works fine after resume [Where problems could occur] These firmware is specific for WCN6855, it should be low risk. Because of the schedule, SRU as SAUCE for focal only. After this version is landed to linux-firmware, focal and jammy can be aligned with upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1972806/+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 1973168] Re: Package still suggests to install crda whereas it was removed
https://launchpad.net/ubuntu/+source/wireless-regdb/2021.08.28-0ubuntu2 ** Changed in: wireless-regdb (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1973168 Title: Package still suggests to install crda whereas it was removed Status in wireless-regdb package in Ubuntu: Fix Released Bug description: This package still suggests crda to be installed whereas it was removed from jammy already: simply remove this from debian/control as done in [1]. [1] https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13612257/+listing- archive-extra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1973168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.15/5.15.0.28.29~20.04.8)
All autopkgtests for the newly accepted linux-meta-hwe-5.15 (5.15.0.28.29~20.04.8) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.17 (armhf) linux-hwe-5.15/5.15.0-28.29~20.04.1 (armhf) lxc/1:4.0.6-0ubuntu1~20.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
